August 17, 2018 at 7:04 am
I have reviewed about a dozen posts (here and other sites) regarding this issue, tried suggestions where appropriate, and still cannot fix this issue.
Windows Server 2012 R2
SQL Server 2008 R2
Service Logon: LocalSystem (also tried LocalService and NetworkService, all fail to start SQL Agent).
Agent dump directory: C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\LOG\
During setup, copied logs to E:, but did (yet) not configure SQL Agent to the new location. Logs currently exist in both locations; however neither show update activity (either in log content or file datetime).
Only reference in ERRORLOG is a "Configuration option 'Agent XPs' changed from 1 to 0. Run the RECONFIGURE statement to install." after the failed start. (In other words, I manually set 'Agent Xps' to 1 but the attempted start changes it to 0 (zero) and then fails. No other error messages relevant to the issue.
Because the agent won't start, I cannot access (through SSMS) the agent error log configuration to change its setting.
Don't know how to access the configuration setting (or if its appropriate) through regedit, or msb.
Any suggestions would help.
August 17, 2018 at 7:27 am
Are you saying that after you attempt to start SQL Server Agent, no new SQLAGENT.OUT file is created? How are you changing the service account (through Services or in SSCM?) and have you tried a domain account?
John
August 17, 2018 at 7:58 am
John Mitchell-245523 - Friday, August 17, 2018 7:27 AMAre you saying that after you attempt to start SQL Server Agent, no new SQLAGENT.OUT file is created? How are you changing the service account (through Services or in SSCM?) and have you tried a domain account?John
1) Correct. Checking both the C: (original path) and E: (new path, but not yet configured through SSMS), the SQLAGENT.OUT file datetime has not changed -- neither are being touched after restart.
2) Changed service accounts through Sql Server Configuration Manager. (Tried Windows services earlier -- "just in case" -- but to no effect.)
3) Long story short: we generally don't use domain accounts because we are charged for each domain account we create, hence "LocalSystem".
Thanks for asking. Hope this clears up those issues.
August 17, 2018 at 8:09 am
joseph.uher - Friday, August 17, 2018 7:58 AMJohn Mitchell-245523 - Friday, August 17, 2018 7:27 AMAre you saying that after you attempt to start SQL Server Agent, no new SQLAGENT.OUT file is created? How are you changing the service account (through Services or in SSCM?) and have you tried a domain account?John
1) Correct. Checking both the C: (original path) and E: (new path, but not yet configured through SSMS), the SQLAGENT.OUT file datetime has not changed -- neither are being touched after restart.
2) Changed service accounts through Sql Server Configuration Manager. (Tried Windows services earlier -- "just in case" -- but to no effect.)
3) Long story short: we generally don't use domain accounts because we are charged for each domain account we create, hence "LocalSystem".
Thanks for asking. Hope this clears up those issues.
I had an issue quite a few years ago now (maybe 2007 - you can search for it on this site if you wish) where SQL Server Agent either wouldn't start or would start and then immediately stop (I can't remember which). No SQAGENT.OUT file was created, and it turned out to be because the SQL Server Agent service account didn't have permissions on the folder that was configured for the logs. The failure to create the .OUT file in turn led to the failure of the service to start. I'm not sure how NTFS permissions work for built-in Windows accounts, which is why I suggested a domain account. How about trying it with a local Windows account instead, just to see whether it works.
This may help you to locate and change (if necessary) the folder where the logs are kept.
John
August 17, 2018 at 8:36 am
John Mitchell-245523 - Friday, August 17, 2018 8:09 AMjoseph.uher - Friday, August 17, 2018 7:58 AMJohn Mitchell-245523 - Friday, August 17, 2018 7:27 AMAre you saying that after you attempt to start SQL Server Agent, no new SQLAGENT.OUT file is created? How are you changing the service account (through Services or in SSCM?) and have you tried a domain account?John
1) Correct. Checking both the C: (original path) and E: (new path, but not yet configured through SSMS), the SQLAGENT.OUT file datetime has not changed -- neither are being touched after restart.
2) Changed service accounts through Sql Server Configuration Manager. (Tried Windows services earlier -- "just in case" -- but to no effect.)
3) Long story short: we generally don't use domain accounts because we are charged for each domain account we create, hence "LocalSystem".
Thanks for asking. Hope this clears up those issues.I had an issue quite a few years ago now (maybe 2007 - you can search for it on this site if you wish) where SQL Server Agent either wouldn't start or would start and then immediately stop (I can't remember which). No SQAGENT.OUT file was created, and it turned out to be because the SQL Server Agent service account didn't have permissions on the folder that was configured for the logs. The failure to create the .OUT file in turn led to the failure of the service to start. I'm not sure how NTFS permissions work for built-in Windows accounts, which is why I suggested a domain account. How about trying it with a local Windows account instead, just to see whether it works.
This may help you to locate and change (if necessary) the folder where the logs are kept.
John
Thanks, John. Taking a look at this now.
August 17, 2018 at 8:42 am
joseph.uher - Friday, August 17, 2018 8:36 AMJohn Mitchell-245523 - Friday, August 17, 2018 8:09 AMjoseph.uher - Friday, August 17, 2018 7:58 AMJohn Mitchell-245523 - Friday, August 17, 2018 7:27 AMAre you saying that after you attempt to start SQL Server Agent, no new SQLAGENT.OUT file is created? How are you changing the service account (through Services or in SSCM?) and have you tried a domain account?John
1) Correct. Checking both the C: (original path) and E: (new path, but not yet configured through SSMS), the SQLAGENT.OUT file datetime has not changed -- neither are being touched after restart.
2) Changed service accounts through Sql Server Configuration Manager. (Tried Windows services earlier -- "just in case" -- but to no effect.)
3) Long story short: we generally don't use domain accounts because we are charged for each domain account we create, hence "LocalSystem".
Thanks for asking. Hope this clears up those issues.I had an issue quite a few years ago now (maybe 2007 - you can search for it on this site if you wish) where SQL Server Agent either wouldn't start or would start and then immediately stop (I can't remember which). No SQAGENT.OUT file was created, and it turned out to be because the SQL Server Agent service account didn't have permissions on the folder that was configured for the logs. The failure to create the .OUT file in turn led to the failure of the service to start. I'm not sure how NTFS permissions work for built-in Windows accounts, which is why I suggested a domain account. How about trying it with a local Windows account instead, just to see whether it works.
This may help you to locate and change (if necessary) the folder where the logs are kept.
John
Thanks, John. Taking a look at this now.
John: I did not know about sp_get_sqlagent_properties. Thank you so much.
The results from that procedure showed me that I had the incorrect directory defined for SQLAGENT.OUT. I created the directory with a copy of the log file, and SQL Agent started up promptly with no errors. (Now I can reconfigure the correct location of the error logs.)
Thanks for your help.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply