SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


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


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

Author
Message
Welsh Corgi
Welsh Corgi
One Orange Chip
One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)

Group: General Forum Members
Points: 26632 Visits: 4895
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/
SQLRNNR
SQLRNNR
SSC Guru
SSC Guru (66K reputation)SSC Guru (66K reputation)SSC Guru (66K reputation)SSC Guru (66K reputation)SSC Guru (66K reputation)SSC Guru (66K reputation)SSC Guru (66K reputation)SSC Guru (66K reputation)

Group: General Forum Members
Points: 66057 Visits: 18570
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

Welsh Corgi
Welsh Corgi
One Orange Chip
One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)

Group: General Forum Members
Points: 26632 Visits: 4895
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
jonathan.d.myers
SSC Journeyman
SSC Journeyman (84 reputation)SSC Journeyman (84 reputation)SSC Journeyman (84 reputation)SSC Journeyman (84 reputation)SSC Journeyman (84 reputation)SSC Journeyman (84 reputation)SSC Journeyman (84 reputation)SSC Journeyman (84 reputation)

Group: General Forum Members
Points: 84 Visits: 378
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
durai nagarajan
Hall of Fame
Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)Hall of Fame (3.5K reputation)

Group: General Forum Members
Points: 3459 Visits: 2784
I accept Jonathan's comments check the security part.

Regards
Durai Nagarajan
Simon D Richards
Simon D Richards
Old Hand
Old Hand (366 reputation)Old Hand (366 reputation)Old Hand (366 reputation)Old Hand (366 reputation)Old Hand (366 reputation)Old Hand (366 reputation)Old Hand (366 reputation)Old Hand (366 reputation)

Group: General Forum Members
Points: 366 Visits: 639
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
Welsh Corgi
One Orange Chip
One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)One Orange Chip (26K reputation)

Group: General Forum Members
Points: 26632 Visits: 4895
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
sql.swayambhu
Grasshopper
Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)

Group: General Forum Members
Points: 10 Visits: 174
Give SA access to -NT AUTHORITY\SYSTEM
SQLAli
SQLAli
Old Hand
Old Hand (319 reputation)Old Hand (319 reputation)Old Hand (319 reputation)Old Hand (319 reputation)Old Hand (319 reputation)Old Hand (319 reputation)Old Hand (319 reputation)Old Hand (319 reputation)

Group: General Forum Members
Points: 319 Visits: 270
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………….
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search