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

Question

Post reply

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

Welsh Corgi

SSC Guru

Points: 116520
More actions
January 19, 2012 at 5:05 pm

#266910

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/

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply

SQLRNNR SSC Guru Points: 281334 More actions · Answer 1

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[/url]
Learn Extended Events

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 2

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/

jonathan.d.myers Old Hand Points: 325 More actions · Answer 3

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

durai nagarajan SSCoach Points: 15778 More actions · Answer 4

I accept Jonathan's comments check the security part.

Regards
Durai Nagarajan

Simon D Richards Ten Centuries Points: 1048 More actions · Answer 5

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.

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 6

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/

sql.swayambhu SSC Enthusiast Points: 106 More actions · Answer 7

sql.swayambhu

SSC Enthusiast

Points: 106

June 26, 2013 at 1:45 pm

#1627715

Give SA access to -NT AUTHORITY\SYSTEM

SQLAli Ten Centuries Points: 1109 More actions · Answer 8

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………….

alnor Right there with Babe Points: 761 More actions · Answer 9

Hi Guys

I had the same issue - above did not resolve issue
Checked under alias (more than 1 of these) in config manager

They all had different IP addresses to the one under network TCP/IP
changed them all to be the same and it worked.

under Client Protocols
Under Aliases

Thanks