Have posted previously under the subject 'Missing What To Start SQLServer Ag
ent in EM' but haven't received any suggestions.
Problem: The SQLServerAgent can be started from DOS Prompt but doesn't start
on reboot and cannot be started from within the Enterprise manager without
error 1060: (The specified service does not exist as an installed service)
occurred while performing t
his service operation on the SQLServerAgent service.
History: Installed Office service pack and it 'messed' up the Enterprise Man
ager. After reinstalling the client tools and the sp3a service pack all wor
ked but scheduled jobs. It turns out that the SQL Server Agent is not runni
ng. It doesn't automatical
ly start up but can be started from DOS whereby my jobs in turn can execute
with no problem.
There used to be an error 8344 SuperSocket Error but after the registers we
re cleaned and errors removed the event error no longer appears. When viewi
ng the registry for SQLServerAgent there was some mention in one of the prev
ious posts about "dependa
ncies" in the registry which is not present. Suspect that the registry is
not complete and would like to know what is missing so that so that SQLServ
erAgent can properly run without manual intervention.
Please advise.
dmatta59
Have posted previously under the subject 'Missing What To Start SQLServer Ag
ent in EM' but haven't received any suggestions.
Problem: The SQLServerAgent can be started from DOS Prompt but doesn't start
on reboot and cannot be started from within the Enterprise manager without
error 1060: (The specified service does not exist as an installed service)
occurred while performing t
his service operation on the SQLServerAgent service.
History: Installed Office service pack and it 'messed' up the Enterprise Man
ager. After reinstalling the client tools and the sp3a service pack all wor
ked but scheduled jobs. It turns out that the SQL Server Agent is not runni
ng. It doesn't automatical
ly start up but can be started from DOS whereby my jobs in turn can execute
with no problem.
There used to be an error 8344 SuperSocket Error but after the registers we
re cleaned and errors removed the event error no longer appears. When viewi
ng the registry for SQLServerAgent there was some mention in one of the prev
ious posts about "dependa
ncies" in the registry which is not present. Suspect that the registry is
not complete and would like to know what is missing so that so that SQLServ
erAgent can properly run without manual intervention.
Please advise.
dmatta59dmatta59,
You could try and install the latest SQL Server service pack. That might fix
it. If not, you may wish to raise a call with MS PSS.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk|||Service pack 3a was installed after the client tools were installed. The on
ly glitch in the installation was that it had to be installed using the sa i
d and password b/c it couldn't verify a valid domain id and password. (I be
lieve related to the SQLSer
verAgent not working somehow). Otherwise installation was successful...|||Have resolved the problem. Used scm.exe to install the SQLServerAgent servi
ce using the instructions on the following article:
http://groups.google.com/groups?q=i...tngxa06&rnum=21
**Please note that the in this case the sqlagent -c -v was working from the
dos prompt and the jobs could run properly. The only problem was that the S
QLServerAgent was not automatically starting or couldn't be started within E
M.
Thank you,
dmatta59|||Status: SQLServerAgent Service Re-Installed
Problem: Missing SQLServerAgent
Symptoms: SQLServerAgent would not automatically start and could not
be started using Enterprise Manager. However, the SQLServerAgent could
be started from a dos command prompt using sqlagent -c -v from the
directory that sqlagent.exe resided.
Used scm.exe to INSTALL the SQLServerAgent service using the
instructions on the following article:
http://groups.google.com/groups?q=i...tngxa06&rnum=21
dmatta59
Mark Allison <marka@.no.tinned.meat.mvps.org> wrote in message news:<FC8661CC-BF2D-492E-93CE
-C73B040F7D17@.microsoft.com>...
> dmatta59,
> You could try and install the latest SQL Server service pack. That might fix it. I
f not, you may wish to raise a call with MS PSS.sql
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment