InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comTue, 21 May 2013 16:09:38 GMT20http://www.sqlservercentral.com/Forums/Topic1239150-146-1.aspx[quote][b]Simon D Richards (3/13/2013)[/b][hr]I know this is old, but I had a similar issue recently. It was a security issue. For whatever reason, the security was not propagated properly during install, I did the following to fix:Switched the account in windows services to a local system account.Started SQL AgentStopped SQL AgentChanged the service to my account in windows servicesStarted Agent.Hope this helps anyone experiencing a similar issue.[/quote]I forgot to post that I resolved this issue.If you switch to a local account, start and stop the SQL Agent and change the Domain Account it works.I had a situation yesterday where I had to do that and it works.Wed, 13 Mar 2013 09:25:33 GMTWelsh Corgihttp://www.sqlservercentral.com/Forums/Topic1239150-146-1.aspxI know this is old, but I had a similar issue recently. It was a security issue. For whatever reason, the security was not propagated properly during install, I did the following to fix:Switched the account in windows services to a local system account.Started SQL AgentStopped SQL AgentChanged the service to my account in windows servicesStarted Agent.Hope this helps anyone experiencing a similar issue.Wed, 13 Mar 2013 09:19:25 GMTSimon D Richardshttp://www.sqlservercentral.com/Forums/Topic1239150-146-1.aspxI accept Jonathan's comments check the security part.Fri, 08 Mar 2013 01:22:05 GMTdurai nagarajanhttp://www.sqlservercentral.com/Forums/Topic1239150-146-1.aspxI have a potential suggestion and solution around this issue. I ran into a similar situation within the last bit on some of my lower level instances. Those a currently still SQL 2005, but this issue may apply to SQL 2008 and SQL 2012 upgrades.We were running an audit and removing some legacy accounts, as well as the [b]Builtin-Administrators [/b]group, as is standard after a SQL 2005 server install and on a regularly scheduled basis. The next morning, the SQL Job Agent on one of my instances started throwing the same error as above when someone attempted to run the job. After a few minutes of troubleshooting, I figured out my service ID was not explicitly added to the security in the server instance. It had been on all the other instances, which is why no one else was complaining.After adding the service ID to the SQL security with sysadmin, the service started right up. After removing the [b]Builtin-Administrators[/b] group, the ID apparently did not have the rights to access the system tables it needed to be able to start.So, let me know if this also resolved it for you. And please provide feedback if you believe I've not fully explained the solution or need more details. Thank you!Jonathan MyersDBA Admin, Systems AnalystBofAThu, 07 Mar 2013 15:44:13 GMTjonathan.d.myershttp://www.sqlservercentral.com/Forums/Topic1239150-146-1.aspxUnfortunately it did not work.Thu, 19 Jan 2012 18:14:02 GMTWelsh Corgihttp://www.sqlservercentral.com/Forums/Topic1239150-146-1.aspxHere is a KB on it. See if it applies/helps[url]http://support.microsoft.com/kb/955763[/url]Thu, 19 Jan 2012 17:14:10 GMTSQLRNNRhttp://www.sqlservercentral.com/Forums/Topic1239150-146-1.aspxI can't start the SQL Server Agent Service on a new installation.During the install I chose not to start the service.When I attempt to start the service it failed to start.I checked the application event log and following error occurred:[quote]SQLServerAgent could not be started (reason: Error creating a new session).[/quote]Thu, 19 Jan 2012 17:05:15 GMTWelsh Corgi