[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 6233
  • Last Modified:

SQLServer Agent Missing

OS -> Windows Server 2000
DB -> SQL Server 2000

Recently installed a service pack for office and it "messed" up my access to enterprise manager.  Apparently, the office service pack didn't check for SQL Server.  The resolution was to install the client tools from the SQL CD.  It seemed to work but now realize that scheduled jobs were not running.  

When I look in the event log, the following exists:
   Application:
              Warning: SuperSocket info (SpnRegister): Error 8344
                            Event Id : 19011  Source: MSSQLServer

              Error: The open procedure for service "RemoteAccess" in DLL "C:\\WINNT\System32\rasctrs.dll" has taken longer than the established wait time to complete.  There may be a problem with this extensible counter or the service it is collecting data from or the system may have been very busy when the call was attempted.

    System:
              Error: The MSSQLServerADHelper service terminate with service-specific error 3221225572.


Would like to prevent from having to bak up all databases, uninstall and then reinstall.  Any suggestions?


 
0
Glass
Asked:
Glass
  • 21
  • 6
1 Solution
 
arbertCommented:
Did you reinstall your SQL Server service pack after you reinstalled the tools?  This should probably be your first step--you probably have a mish/mash of old and new DLLs since you reinstalled the tools....
0
 
GlassAuthor Commented:
I reinstalled service pack 3....

What else can I do?

Glass
0
 
arbertCommented:
Well, I think you have a couple of things going on here.

The MSSQLServerADHelper error you're getting indicates a bad user/password.  I would go into control panel and make sure you're using a good user/password on the startup account.


The supersocket error is generated when SQL Server tries to register a SPN in active directory and it fails.  So, I would also verify the MSSQLSErver account in services for it's startup account/password.   When you're in services, see if you have SQLServeragent listed as a service and what the status is....
0
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
GlassAuthor Commented:
Okay,

Have verified that the service pack unloaded but didn't install.  Have verified that the
 the domain/user name with password is correct.   Have now twice attempted to install the service pack but it cannot verify my domain id.  Where else can I look to correct the id/password?

Glass
0
 
GlassAuthor Commented:
BTW can connect to the server using my domain id/password....

Glass
0
 
arbertCommented:
Can you use the original SA userid to install the service pack.  If you can connect with your domain account, you can change the SA password if you don't know it....
0
 
GlassAuthor Commented:
Message reads:

Setup was unable to validate the logged on user.  Press retry to enter another option.  Cancel to exit setup.

Glass
0
 
GlassAuthor Commented:
Will try.  Is the idea to install the service pack and then later change the account once installed?  

Glass
0
 
GlassAuthor Commented:
Still have a problem.  When trying to start a batch job, the following error displays:

Error 22022: SQLServerAgent is not currently running so it cannot be notified of this action.

But it is running.  Help?!

Glass
0
 
arbertCommented:
So you got SP3 reinstalled then?

You're positive it is running--when you look at services SQLServerAgent is listed as started?
0
 
GlassAuthor Commented:
Rechecked and SQLServer Agent is not running...

This is what the event viewer shows on reboot/restart:
System and Security clean.
Application:
     Type: Warning  Event Id: 19011 Source: MSSQLServer

     SuperSocket info (SpnRegister): Error 8344

So went to SQLServer Agent properties and it is trying to start under a local account which doesn't have the appropriate permissions.  When I attempt to change to my domain id/password, it returns with:
   The new service startup account name you have supplied is invalid or does not exist.  

But it does exist and the combination is valid.  Have to use it to gain entry into the PC....  
Is it possible that the file was corrupted or deleted when installing the Office service pack?

Everything else works but really need to get the daily batch jobs running or the database will be useless.

Help.....

Glass






0
 
GlassAuthor Commented:
One more thing... When try to start the SQL Server Agent receive the following message:

An error 1060: (The specified service does not exist as an installed service) occurred while performing this service operation on the SQLServerAgent service.

Glass
0
 
GlassAuthor Commented:
I guess that the bottom line is that the dll is missing or the registry is corrupt.
Is there a way to reinstall the SQL Server Agent without reinstalling everything????

Glass
0
 
GlassAuthor Commented:
Here is a listing of the dll and resouce files for sqlagent that are on my machine....

C:....\MSSQL\BINN
sqlagent.dll
sqlagent.exe

C:.....\MSSQL\BINN\Resources\1033
sqlagent.rll

C:\sql2ksp3\x86\binn
sqlagent.dll
sqlagent.exe

C:\sql2ksp3\x86\binn\res\1033
sqlagent.rll

C:\sql2ksp3\x86\binn\res\other
sqlagent.rll

See anything out of place.....

Glass





0
 
GlassAuthor Commented:
Have found a reference where the registry rebuild can be attempted but there doesn't seem to be very much information .....  Here are the instructions...

cd \MSSQL\BINN

setup /t Registry Rebuild=ON

Glass
0
 
GlassAuthor Commented:
Arbert:

Would you recommend the registry rebuild or do you know of something else that doesn't involve the registers?  Let me know; would rather not mess with the registry.

Glass
0
 
GlassAuthor Commented:
The latest... attempted to manually restart:   sqlagent -c -v

The last few lines are:

date:  260 Unable to start mail session (reason: No mail profile defined).

date:  396 An idle CPU condition has not been defined - OnIdle job schedules will have no effect.  

Then no messages and agent continued running until terminated by user.

There is no mail profile b/c no mail service is available from this server.  

Glass
0
 
arbertCommented:
You have some kind of authentication problem with AD--not sure what happened.  It's weird that it will start from the command prompt but not as a service.

What happens when you run NET START SQLSERVERAGENT    from a DOS prompt?
0
 
GlassAuthor Commented:
It responds with:

Net service name is invalid....


Glass
0
 
GlassAuthor Commented:
I have already refreshed the active directory reference.  I could remove the reference in active directory but it stated that it would delete the databases.....  Wasn't sure what it would be deleting.  Does it touch any of the databases on the PC or is it referring to the database name references in the active directory?  Would be willing to try to delete and add again if it might help.

Glass
0
 
GlassAuthor Commented:
Okay Arbert..... Try this one...

I have started the sqlagent manually in a dos window.... sqlagent -c -v  
(Should it be listed as a running service b/c it doesn't display?  Wouldn't think so but would like to know if you know.)

Also went to EM to attempt to start the SQL Agent and it replies with the 1060 error.  So I started my download job which has been my mission and it is executing properly using domain id/password.  HOORAY!  My database is updating...

So what procedure executes when depress the 'start' option withing EM?  Also what procedure executes when starting the service from SERVICES ?  I would guess that they both drill down to the same dll which is probably corrupted.  Any leads?

By the way, thanxs for sticking with this.

Glass
0
 
GlassAuthor Commented:
By the way, what created this mess is the installation of the Office server extensions which was a part of the office service pack ---  According to microsoft, it was released before SQL Server so it doesn't know to check for it.  

Any other suggestions????

Glass

0
 
GlassAuthor Commented:
Okay,  it seems that the registry for MSSQLServer and SQLSERVERAgent is wrong.  Do you have the appropriate currentversionset settings?

Glass
0
 
GlassAuthor Commented:
Thanxs Arbert for the workaround.  Still looking for the resolution to the problem.

Glass
0
 
GlassAuthor Commented:
Have resolved the problem.  Used scm.exe to install the SQLServerAgent service using the instructions on the following article:
http://groups.google.com/groups?q=install+sqlserveragent&start=20&hl=en&lr=&ie=UTF-8&selm=AoJbhDgvCHA.2304%40cpmsftngxa06&rnum=21

**Please note that the in this case the sqlagent -c -v was working from the dos prompt and the jobs could run properly.  The only problem was that the SQLServerAgent was not automatically starting or couldn't be started within EM.  

Thank you,
dmatta59
 
 
 
 
0
 
arbertCommented:
Please request the question be PAQed/Refunded
0
 
GlassAuthor Commented:
Hey Arbert,

Have already requested the following on Wednesday night:
1) the question/answer be preserved
2) the points be awarded to you since you gave me the workaround.

Awaiting response....

Thanxs,
Glass
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 21
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now