March 29, 2012 at 3:46 am
Hi,
I recently upgraded SQL server to 2008 standard R2.
The upgrade appears to of gone well, but i have a historic problem from the previous version.
The SQL server agent, refuses to start and gives the following error message:
The SQL Server Agent (MSSQLSERVER) service failed to start due to the following error:
The system cannot find the file specified.
This is logged with an Event ID 7000.
I would appreciate assistance on this issue.
Regards
Alan Craddock
March 29, 2012 at 3:57 am
Check this blog post.
It might have something to do with the Agent error logs:
http://blogs.msdn.com/b/sqlserverfaq/archive/2009/06/12/unable-to-start-sql-server-agent.aspx
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
March 29, 2012 at 4:40 am
Hi,
The strange thing is, i upgraded the SQL server last night at around 17:30 from standard 2008 to 2008 R2.
I have this morning since tried to restart the service, but no sign of any update to the log file with errors??
Does the below version number, not refer to the old version and not the upgraded r2 version?
It would seem that maybe the upgrade is not complete?
2012-03-28 17:31:59 - ? [100] Microsoft SQLServerAgent version 10.0.1600.22 ((Unknown) unicode retail build) : Process ID 464
2012-03-28 17:31:59 - ? [101] SQL Server SOLD010 version 10.00.1600 (0 connection limit)
2012-03-28 17:31:59 - ? [102] SQL Server ODBC driver version 10.00.1600
2012-03-28 17:31:59 - ? [103] NetLib being used by driver is DBNETLIB.DLL; Local host server is
2012-03-28 17:31:59 - ? [310] 8 processor(s) and 12277 MB RAM detected
2012-03-28 17:31:59 - ? [339] Local computer is SOLD010 running Windows NT 6.0 (6001) Service Pack 1
2012-03-28 17:31:59 - ? [432] There are 12 subsystems in the subsystems cache
2012-03-28 17:32:14 - ! [364] The Messenger service has not been started - NetSend notifications will not be sent
2012-03-28 17:32:14 - ? [129] SQLSERVERAGENT starting under Windows NT service control
2012-03-28 17:32:14 - + [260] Unable to start mail session (reason: No mail profile defined)
2012-03-28 17:32:14 - + [396] An idle CPU condition has not been defined - OnIdle job schedules will have no effect
2012-03-28 18:08:53 - ? [131] SQLSERVERAGENT service stopping due to a stop request from a user, process, or the OS...
2012-03-28 18:08:55 - ? [098] SQLServerAgent terminated (normally)
What do you think?
Regards
Alan
March 29, 2012 at 4:57 am
The version number indeed appears to be from 2008.
Maybe try a repair using the SQL Server installation media?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
March 29, 2012 at 5:08 am
When i look at the path to 'sqlagent.exe' from the services.msc it shows the following path:
D:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn
But, in fact the sqlagent.exe is located at the following location:
D:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn
When i run the file manually, it in fact shows the version number to be:
Microsoft (R) SQLServerAgent 10.50.1600.1 (which i believe is the correct version for r2?)
So, do you think i can simply change the registry setting relating to the file location for sqlagent.exe?
Regards
Alan
March 29, 2012 at 5:14 am
I haven't meddled with the registry before, so I would take a backup before you change anything 🙂
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
March 29, 2012 at 5:41 am
I have taken a backup and found the registry key that relates to the sqlagent service.
I have succesfully modified, and when i now check the path against the service it points to the correct location.
Still the same error when i attempt to restart the service though...
If i try to start the service with the following command through the command prompt i get the following error:
command :
D:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\SQLAGENT.EXE" -i MSSQLSERVER
Error received:
Microsoft (R) SQLServerAgent 10.50.1600.1
Copyright (C) Microsoft Corporation.
StartServiceCtrlDispatcher failed (error 6).
Any ideas?
March 29, 2012 at 5:44 am
I'm a bit out of ideas. Maybe try a repair or uninstall and re-install the service?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
March 29, 2012 at 5:52 am
Honestly, it could be an OS issue. I know there's one with 2k8 and Vista, where the inability to get the service started is related to the fact that I can't seem to install certain files or programs.
Have you verified that everything in the OS is capable of supporting R2, and have you updated your OS recently?
March 29, 2012 at 6:07 am
March 29, 2012 at 6:07 am
I have now tried to run from the command prompt with the following command:
sqlagent.exe -c -v
I now get the following error:
2012-03-29 12:54:43 - ! [246] Startup error: Unable to read SQLServerAgent registry settings (from Software\Microsoft\Microsoft SQLServer\MSSQL10_50.MSSQLSERVER\SQLServerAgent)
2012-03-29 12:54:43 - ? [098] SQLServerAgent terminated (normally)
I have the service configured to log on as: 'local system account'
Is that a standard setting?
Could it be a permissions issue?
2 parts of the above registry settings shown below:
An error log entry with the following path: D:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Log\SQLAGENT.OUT
Also a working directory with the following path: D:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\JOBS
March 29, 2012 at 6:17 am
acraddock (3/29/2012)
Startup error: Unable to read SQLServerAgent registry settings (from Software\Microsoft\Microsoft SQLServer\MSSQL10_50.MSSQLSERVER\SQLServerAgent)
When googling this error, I find it under SQL 2005 forums. The advice says to check your protocols (make sure the ones you need are enabled) and to set up a registry key for the server's virtual name (assuming you have a virtual name).
Here's the link to the later one: http://social.msdn.microsoft.com/Forums/en-US/sqlgetstarted/thread/73327808-c24d-4b01-be70-840c15c9ff3a
Not sure if either solution can help you solve this problem, but it can't hurt to check.
March 29, 2012 at 6:47 am
Did you verify that the upgrade was really successful?
That might be a key before trying to fix something.
March 29, 2012 at 6:58 am
Hi Brandie,
Thank you for the link.
In fact the server does not have a virtual name, but the error shown in the article is the same...
It does mention entering a host name at one point, maybe i can add the server name?
Do you think a reboot would be required after the registry change?
Alan.
March 29, 2012 at 7:07 am
Hi,
I have took a look at the SQL install log and found the following towards the end:
2012-03-28 18:13:32 Slp: Error result: -2068119551
2012-03-28 18:13:32 Slp: Result facility code: 1211
2012-03-28 18:13:32 Slp: Result error code: 1
2012-03-28 18:13:32 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2012-03-28 18:13:32 Slp: Sco: Attempting to open registry subkey
2012-03-28 18:13:32 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
2012-03-28 18:13:32 Slp: Sco: Attempting to get registry value DW0201
2012-03-28 18:13:34 Slp: Submitted 1 of 1 failures to the Watson data repository
Below extract from Dr Watson repositary file:
Watson bucket data:
Bucket param 1: SQL Server 2008 R2@RTM@
Bucket param 2: 0xCE4CA027
Bucket param 3: 0xCE4CA027
Bucket param 4: 0xD3BEBD98@1211@1
Bucket param 5: 0xD3BEBD98@1211@1
Bucket param 6: SqlEngineConfigAction_upgrade_configrc
Bucket param 7: 0xA7341117
Bucket param 8:
Bucket param 9:
Bucket param 10:
Can you advise if this is significant or not?
Am i looking at the right files for errors / issues?
Alan
Viewing 15 posts - 1 through 15 (of 26 total)
You must be logged in to reply to this topic. Login to reply