Microsoft Help! SQLServerAgent Missing Something....

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.
dmatta59Windows Service Dependancies are stored in the "DependOnService" value under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\SQLAgent$[Instance
name]. The value should be "MSSQL$[Instance name]. There is a
"DependOnGroup" value which should be empty as there are no dependant
service groups for SQL Agent.
I'm wondering how you think installing an Office Service Pack could have
anything to do with this SQL Agent's auto startup? I could understand it
mucking up SQL Enterprise Manager, but I'd be amazed if it actually messed
with the Winndows Service Control Manager registry values for services that
have nothing to do with Office..
What did you mean when you said "but after the registers were cleaned.."?
Did you manually alter the registry? I don't mean this to be antagonistic,
but I really suggest you learn to backup the registry before making changes.
Obviously you didn't do this or you wouldn't be asking for what the values
should be. I assure you this is a valuable lesson to learn.
Did you check the Windows Event Log?
Regards,
Greg Linwood
SQL Server MVP
"dmatta59" <anonymous@.discussions.microsoft.com> wrote in message
news:3B363F0E-C782-40A2-8B2F-BB0AB4E14FFF@.microsoft.com...
> Have posted previously under the subject 'Missing What To Start SQLServer
Agent 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 this service operation on the
SQLServerAgent service.
> History: Installed Office service pack and it 'messed' up the Enterprise
Manager. After reinstalling the client tools and the sp3a service pack all
worked but scheduled jobs. It turns out that the SQL Server Agent is not
running. It doesn't automatically 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
were cleaned and errors removed the event error no longer appears. When
viewing the registry for SQLServerAgent there was some mention in one of the
previous posts about "dependancies" 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 SQLServerAgent can properly run without manual
intervention.
> Please advise.
> dmatta59
>
>|||1) Regarding Office Service Pack: It didn't dawn on me that an office servi
ce pack would have impacted the SQL Server EM either. However after the se
rvice pack installation, the EM was not accessable and the 'clean up' has be
en given to me.
"Article from MSDN: OSE: Error Messages When You Install Office Server Exten
sions on Computer with SQL Server 2000
http://support.microsoft.com/defaul...kb;en-us;281460"
2) I installed the client tools followed by the service pack 3a. The EM wor
ked great but not the SQLServer agent which in turn meant that the batch job
s would not execute. The message in the event id was 8344 and some of the o
ptions for 'fixing' were ut
ilized but didn't work. Meanwhile, it was determined that the SQLServerAgen
t wasn't automatically starting after reboot or from within EM. However, th
e SQLServerAgent could be manually started from a DOS window and the batch j
obs work fine.
3) The registers were not cleaned manually but with a tool developed by Micr
osoft. A copy of the registers before the clean routine was made and is sti
ll available. An error was detected and corrected. The event id of 8344 d
oesn't happen anymore but t
hen the SQLServerAgent still doesn't start except manually from a dos windo
w....
It seems that common to an automatic startup and to a manual startup within
the EM would be a dll and/or a registry that is corrupt and/or missing, resp
ectively. Any ideas?
Thanxs,
dmatta59|||Greg,
A few more bits of information ......
The Sql database and EM was working fine on the 15th am. Then the service p
ack was installed on the 15th pm. The EM not working was noticed immediatel
y so client tools and 3a service pack were installed -- all was working exce
pt SQLServer Agent which wa
s not detected until a few days later. Viewing the history reveals that th
e 5am download worked fine on the 15th but no other downloads were attempted
after the 15th and no errors were generated. For this reason, I suspect t
hat the office service pack
affected the SQLServer agent ... Maybe it is a coincidence and something el
se 'hit' at the same time but still need to fix the problem of the SQLServer
Agent not starting automatically or from within the EM...
As the registry reference,
Windows Service Dependancies are stored in the "DependOnService" value under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\SQLAgent$[Instance
name]. The value should be "MSSQL$[Instance name]. There is a
"DependOnGroup" value which should be empty as there are no dependant
service groups for SQL Agent.
Here is what I see in the registry for my default named instance is under:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services--SQLAgent
--Enum
--(Default) REG_SZ (value not set)
--0 REG_SZ Root\LEGACY_SQLSERV
ERAGENT\0000
--Count REG_DWORD (1)
--NextInstance REG_DWORD (1)
There is nothing else.
Would appreciate your input...
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
"Greg Linwood" <g_linwoodQhotmail.com> wrote in message news:<ucDcvxkFEHA.3880@.TK2MSFTNGP10
.phx.gbl>...
> Windows Service Dependancies are stored in the "DependOnService" value und
er
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControl
Set\Services\SQLAgent$[Instanc
e
> name]. The value should be "MSSQL$[Instance name]. There is a
> "DependOnGroup" value which should be empty as there are no dependant
> service groups for SQL Agent.
> I'm wondering how you think installing an Office Service Pack could have
> anything to do with this SQL Agent's auto startup? I could understand it
> mucking up SQL Enterprise Manager, but I'd be amazed if it actually messed
> with the Winndows Service Control Manager registry values for services tha
t
> have nothing to do with Office..
> What did you mean when you said "but after the registers were cleaned.."?
> Did you manually alter the registry? I don't mean this to be antagonistic,
> but I really suggest you learn to backup the registry before making change
s.
> Obviously you didn't do this or you wouldn't be asking for what the values
> should be. I assure you this is a valuable lesson to learn.
> Did you check the Windows Event Log?
> Regards,
> Greg Linwood
> SQL Server MVP
> "dmatta59" <anonymous@.discussions.microsoft.com> wrote in message
> news:3B363F0E-C782-40A2-8B2F-BB0AB4E14FFF@.microsoft.com...
> Agent in EM' but haven't received any suggestions.
> 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 this service operation on the
> SQLServerAgent service.
> Manager. After reinstalling the client tools and the sp3a service pack al
l
> worked but scheduled jobs. It turns out that the SQL Server Agent is not
> running. It doesn't automatically start up but can be started from DOS
> whereby my jobs in turn can execute with no problem.
> were cleaned and errors removed the event error no longer appears. When
> viewing the registry for SQLServerAgent there was some mention in one of t
he
> previous posts about "dependancies" in the registry which is not presen
t.
> Suspect that the registry is not complete and would like to know what is
> missing so that so that SQLServerAgent can properly run without manual
> intervention.