March 3, 2014 at 1:31 am
Hi,
I have installed SQL Server 2008R2 and 2012 on my testing server.
Microsoft SQL Server 2012 - 11.0.2218.0 (Intel X86)
Jun 12 2012 13:16:18
Copyright (c) Microsoft Corporation
Standard Edition on Windows NT 6.1 <X86> (Build 7601: Service Pack 1)
My All serverices are running file but when i run SQL Server Agent its display error:-
The request fail or the service did not respond in a timely fashion. Consult the event log for details.
In event log following system disply following:-
SQLServerAgent could not be started (reason: Unable to connect to server '(local)'; SQLServerAgent cannot start).
Please help me on urgent basis.
Regards
Dharmendra
March 3, 2014 at 5:02 am
Which agent is it that will not start, the SQL 2008 R2 instances agent or the SQL 2012 instances agent?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 3, 2014 at 8:31 am
Dharmendra JKT (3/3/2014)
Hi,I have installed SQL Server 2008R2 and 2012 on my testing server.
Microsoft SQL Server 2012 - 11.0.2218.0 (Intel X86)
Jun 12 2012 13:16:18
Copyright (c) Microsoft Corporation
Standard Edition on Windows NT 6.1 <X86> (Build 7601: Service Pack 1)
My All serverices are running file but when i run SQL Server Agent its display error:-
The request fail or the service did not respond in a timely fashion. Consult the event log for details.
In event log following system disply following:-
SQLServerAgent could not be started (reason: Unable to connect to server '(local)'; SQLServerAgent cannot start).
Please help me on urgent basis.
Regards
Dharmendra
Did you change the service acct of the agent ? Do you know what chnage triggered this error ?
--
SQLBuddy
March 4, 2014 at 12:15 am
SQL Server 2012 Agent
March 4, 2014 at 12:16 am
yes, i have change service account but its not work
March 4, 2014 at 8:03 am
Dharmendra JKT (3/4/2014)
yes, i have change service account but its not work
Try to chnage the service account to System acccount and start it. Once started try to use a domain account and check if it starts.
--
SQLBuddy
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply