Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQLServerAgent could not be started (reason: Error creating a new session). Expand / Collapse
Author
Message
Posted Thursday, January 19, 2012 5:05 PM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Monday, September 29, 2014 10:57 PM
Points: 4,242, Visits: 4,290
I 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:


SQLServerAgent could not be started (reason: Error creating a new session).



For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Post #1239150
Posted Thursday, January 19, 2012 5:14 PM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Today @ 10:18 AM
Points: 17,809, Visits: 15,731
Here is a KB on it. See if it applies/helps

http://support.microsoft.com/kb/955763




Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Post #1239153
Posted Thursday, January 19, 2012 6:14 PM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Monday, September 29, 2014 10:57 PM
Points: 4,242, Visits: 4,290
Unfortunately it did not work.

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Post #1239163
Posted Thursday, March 7, 2013 3:44 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, October 14, 2014 2:54 PM
Points: 17, Visits: 247
I 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 Builtin-Administrators 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 Builtin-Administrators 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 Myers
DBA Admin, Systems Analyst
BofA
Post #1428307
Posted Friday, March 8, 2013 1:22 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, May 30, 2014 8:15 AM
Points: 1,056, Visits: 2,687
I accept Jonathan's comments check the security part.



Regards
Durai Nagarajan
Post #1428441
Posted Wednesday, March 13, 2013 9:19 AM


SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Yesterday @ 7:45 AM
Points: 177, Visits: 566
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 Agent
Stopped SQL Agent
Changed the service to my account in windows services
Started Agent.

Hope this helps anyone experiencing a similar issue.
Post #1430466
Posted Wednesday, March 13, 2013 9:25 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Monday, September 29, 2014 10:57 PM
Points: 4,242, Visits: 4,290
Simon D Richards (3/13/2013)
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 Agent
Stopped SQL Agent
Changed the service to my account in windows services
Started Agent.

Hope this helps anyone experiencing a similar issue.


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.



For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Post #1430471
Posted Wednesday, June 26, 2013 1:45 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Saturday, September 6, 2014 6:55 PM
Points: 2, Visits: 114
Give SA access to -NT AUTHORITY\SYSTEM
Post #1467850
Posted Friday, June 20, 2014 9:38 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Saturday, October 11, 2014 12:31 AM
Points: 115, Visits: 239
Yes, I do faced the same issue.
Error from Eventvwr: SQLServerAgent could not be started (reason: Error creating a new session)

Resolution:
1) Add the service account as Administrators at server level. i.e. Computer -- Manage -- Administrators -- Add service account

2) Provide the SA privileges to the service account and start the agent service.


Thanks,
I’m nobody but still I’m somebody to someone………….
Post #1584539
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse