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

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » Administering » SQLServerAgent could not be started (reason:...

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

Rate Topic

Display Mode

Topic Options

Author

Message

Welsh Corgi

Posted Thursday, January 19, 2012 5:05 PM

Hall of Fame

Group: General Forum Members
Last Login: Yesterday @ 6:19 AM
Points: 3,833, Visits: 4,052

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

SQLRNNR

Posted Thursday, January 19, 2012 5:14 PM

SSCoach

Group: General Forum Members
Last Login: Monday, May 20, 2013 1:07 PM
Points: 18,733, Visits: 12,332

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 2008

SQL RNNR

Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp

Post #1239153

Welsh Corgi

Posted Thursday, January 19, 2012 6:14 PM

Hall of Fame

Group: General Forum Members
Last Login: Yesterday @ 6:19 AM
Points: 3,833, Visits: 4,052

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

jonathan.d.myers

Posted Thursday, March 07, 2013 3:44 PM

Grasshopper

Group: General Forum Members
Last Login: Monday, May 20, 2013 7:05 AM
Points: 13, Visits: 166

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

durai nagarajan

Posted Friday, March 08, 2013 1:22 AM

SSC Eights!

Group: General Forum Members
Last Login: Today @ 2:05 AM
Points: 856, Visits: 2,115

I accept Jonathan's comments check the security part.

Regards
Durai Nagarajan

Post #1428441

Simon D Richards

Posted Wednesday, March 13, 2013 9:19 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, May 20, 2013 1:40 PM
Points: 141, Visits: 500

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

Welsh Corgi

Posted Wednesday, March 13, 2013 9:25 AM

Hall of Fame

Group: General Forum Members
Last Login: Yesterday @ 6:19 AM
Points: 3,833, Visits: 4,052

Simon D Richards (3/13/2013)

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

« Prev Topic | Next Topic »

Permissions