March 3, 2008 at 1:18 pm
Fellow collegues,
I can not restart my sql server agent. I check the sql logs and nothing, however there are a series of application logs that suggest regesitry and .dll files are not there or can not be read. I will include all of the errors and informational messages I think is pertinent. I have checked online and checked and checked and can not find anything concrete. Please Please Please if you have seen this error provide as much as detalied information to resolve it.
FYI: I am starting this service with the same start up account id as for SQL Server Services. I tested the login and it logins in successfully through terminal services and is included ofcourse in the local administrator group.
Application logs indicate the following error:
Event Type:Information
Event Source:SQLSERVERAGENT
Event Category:Disk
Event ID:102
Date:3/3/2008
Time:11:32:21 AM
User:N/A
Computer:LBMKT1QASUNWH
Description:
The description for Event ID ( 102 ) in Source ( SQLSERVERAGENT ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: The event log file is corrupt..
Event Type:Error
Event Source:SQLSERVERAGENT
Event Category:Disk
Event ID:103
Date:3/3/2008
Time:11:32:21 AM
User:N/A
Computer:LBMKT1QASUNWH
Description:
The description for Event ID ( 103 ) in Source ( SQLSERVERAGENT ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: Unable to connect to server '(local)'; SQLServerAgent cannot start.
Event Type:Error
Event Source:Userenv
Event Category:None
Event ID:1000
Date:3/3/2008
Time:10:49:51 AM
User:NT AUTHORITY\SYSTEM
Computer:LBMKT1QASUNWH
Description:
Windows cannot unload your registry file. If you have a roaming profile, your settings are not replicated. Contact your administrator.
DETAIL - Access is denied. , Build number ((2195)).
Event Type:Information
Event Source:MSSQLSERVER
Event Category:Disk
Event ID:17055
Date:3/3/2008
Time:10:22:26 AM
User:SUNAMERICA-LA\rrahyab
Computer:LBMKT1QASUNWH
Description:
The description for Event ID ( 17055 ) in Source ( MSSQLSERVER ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: 8128, Using 'xplog70.dll' version '2000.80.760' to execute extended stored procedure 'xp_msver'.
.
Data:
0000: c0 1f 00 00 0a 00 00 00 À.......
0008: 0e 00 00 00 4c 00 42 00 ....L.B.
0010: 4d 00 4b 00 54 00 31 00 M.K.T.1.
0018: 51 00 41 00 53 00 55 00 Q.A.S.U.
0020: 4e 00 57 00 48 00 00 00 N.W.H...
0028: 07 00 00 00 6d 00 61 00 ....m.a.
0030: 73 00 74 00 65 00 72 00 s.t.e.r.
0038: 00 00 ..
Event Type:Information
Event Source:MSSQLSERVER
Event Category:Disk
Event ID:17055
Date:3/3/2008
Time:10:17:00 AM
User:SUNAMERICA-LA\rrahyab
Computer:LBMKT1QASUNWH
Description:
The description for Event ID ( 17055 ) in Source ( MSSQLSERVER ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: 8128, Using 'xpstar.dll' version '2000.80.760' to execute extended stored procedure 'sp_MSgetversion'.
.
Data:
0000: c0 1f 00 00 0a 00 00 00 À.......
0008: 0e 00 00 00 4c 00 42 00 ....L.B.
0010: 4d 00 4b 00 54 00 31 00 M.K.T.1.
0018: 51 00 41 00 53 00 55 00 Q.A.S.U.
0020: 4e 00 57 00 48 00 00 00 N.W.H...
0028: 07 00 00 00 6d 00 61 00 ....m.a.
0030: 73 00 74 00 65 00 72 00 s.t.e.r.
0038: 00 00 ..
Event Type:Information
Event Source:Horizon RCC
Event Category:None
Event ID:1
Date:3/3/2008
Time:7:53:59 AM
User:N/A
Computer:LBMKT1QASUNWH
Description:
The description for Event ID ( 1 ) in Source ( Horizon RCC ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: MonoSphere Storage Horizon collection being performed from host WHPWMSPHERE1.
Event Type:Information
Event Source:MSSQLSERVER
Event Category:Disk
Event ID:17177
Date:3/3/2008
Time:12:00:57 AM
User:N/A
Computer:LBMKT1QASUNWH
Description:
The description for Event ID ( 17177 ) in Source ( MSSQLSERVER ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: 1928, 2/29/2008 11:54:44 PM, 3/1/2008 7:54:44 AM.
Data:
0000: 19 43 00 00 0a 00 00 00 .C......
0008: 0e 00 00 00 4c 00 42 00 ....L.B.
0010: 4d 00 4b 00 54 00 31 00 M.K.T.1.
0018: 51 00 41 00 53 00 55 00 Q.A.S.U.
0020: 4e 00 57 00 48 00 00 00 N.W.H...
0028: 00 00 00 00 ....
:w00t:
March 3, 2008 at 2:31 pm
March 3, 2008 at 3:27 pm
Based on your error message, I would like to say you may need to restore your registry or re-install your SQL Server.
March 3, 2008 at 6:29 pm
So when was it last running? Any ideas as to why it stopped running? Hint: what changed?
Presumably SQL Server is running. Can you connect to any of the databases?
I had a similar experience recently (dev server thank goodness). Someone came around and said they couldn't connect to a DB. I tried logging in and got a message that the default DB couldn't be opened - disturbing as 'master' was the default db for that login. Found out the data drive had ran out of space. Freed up some disk space, restarted SQL Server, all go.
MARCUS. Why dost thou laugh? It fits not with this hour.
TITUS. Why, I have not another tear to shed;
--Titus Andronicus, William Shakespeare
March 4, 2008 at 1:36 pm
Hey Guys,
Thanks alot for your feeback I really appreciate it. I talked to Info Sec regarding the roaming profile and they said it usually happens on unsuccessful logins. I said ok , so I go and try logging in under "What I thought was being used as the start up account" and I logged on successfully.
Finally! We noticed that the builtin\administrator group was removed because we had no control on who is local admin on the servers so the id was not being authenticated. We noticed that there has been obviously a change and we added the account back in and changed the start up account unders sql agent and it worked fine.
WAIT !! KEEP READING.....
SQL Agent is working fine now but why was sql server still running before then? It uses the same login ....Twlight Zone!
Another time another dollar...:) Thanks again.
June 5, 2008 at 2:33 pm
THANKS FOR THIS ARTICLE. THIS FIXED MY ISSUE............
May 12, 2012 at 9:34 pm
how did you fixed the issue?
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply