August 16, 2004 at 7:19 am
SQL Server 7.00.961 will not start. When you view the services it states it is running. When you view the SQL Server Agent log, this message appear [129]SQLServerAgent starting under Windows NT service control. It gets hung up here and will not go past this point. No errors appear in the event viewer or the SQL log. SQL Server is configured for thread processin. I have tried starting it manually instead of automatic. I have changed the user login to see if this would work. I have rebooted the server, shut down the server. I am out of ideas and desperately need help!!!
August 16, 2004 at 7:36 am
"SQL Server 7.00.961 will not start. When you view the services it states it is running."
Have you tried to run any jobs? Do you get jobs failure?
August 16, 2004 at 7:45 am
Yes, I have tried to run jobs and I get the error 14258: Cannot perform the operation while SQLServerAgent is starting. Try again later.
August 16, 2004 at 7:49 am
From control panel --> services, You should see SQL Server Agent Service is still in starting status. Try to kill and restart it.
What type service account do you use to start it?
August 16, 2004 at 8:01 am
Start is greyed out and it will not let me kill it. In NT services it states that it is started. I can go into NT Services and try to kill it there. It just hangs up with Could not stop the SQLServerAgent Server Error 2186: The service is not responding to the control functions, but then when I press OK, it is stopped. Then it allows me to press start in enterprise manager or NT Services and I get the error 1056 -(An instance of the service is already running) occured while performing this service operation on the SQLServerAgent service. Then I have to reboot the server and we start all over with the same set of problems.
August 16, 2004 at 8:02 am
I start the services with system account
August 16, 2004 at 8:07 am
Has the system account be granted to access SQL Server? Is BUILTIN\Administrators account in SQL Server logins?
August 16, 2004 at 8:14 am
Yes, This server has worked for a couple of years without any problems. We had to reboot the server and then the SQL Server agent would not work.
August 16, 2004 at 9:19 am
Try sp_grantlogin 'NT Authority\System' and assign this account with 'sa' privilege.
August 16, 2004 at 11:11 am
I ran sp_grantlogin for my NT authority\system and assigned sa privileges and rebooted the server. I am getting the same results. The agent looks like it started but the sql server agent error log reports that it is starting but never gets past the first line [129] SQLServerAgent starting under Windows NT Service control.
August 16, 2004 at 11:55 am
It might be waiting for some other service to be started if there is any dependency.
Can you change SQLAgent Service to be manaul and reboot the box and then run this from command line
sqlagent -c -v
and post the result?
Also I read, some folks fixed by enableing the "Messanger" serivce to be automatic. I don't know why that worked but it worked.
August 17, 2004 at 5:58 am
Did you enable a mail profile? I've seen problems with agent starting when mail gets hung. I don't have a solution but maybe another place to investigate.
August 17, 2004 at 6:27 am
The mail profile is not enabled. The messenger service was on automatic. I will reboot and try sqlagent -c -v and post the results after the users allow me to have the system.
August 17, 2004 at 8:21 am
I just rebooted the server and ran sqlagent -c -v and had the following results:
[094] SqlServerAgent started from command line
Then an error window pops up
ODBC Installer Error
The Program D:\MSSQL7\BINN\sqlagent.exe or one of its DLLs attempted to call the function SQLGetPrivatePRofileStringW which is not supported in the loaded ODBC installer DLL(D:\WINNT\System32\odbccp32.dll) press OK to proceed.
I pressed OK 15 times and the same error appeared again. Any ideas on what is causing this problem????
August 17, 2004 at 8:47 am
What is your MDAC version? Any update to it recently?
Viewing 15 posts - 1 through 15 (of 19 total)
You must be logged in to reply to this topic. Login to reply