Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SP3 Applied and now SQL Agent will NOT start

Status
Not open for further replies.

OUCATS

IS-IT--Management
Feb 5, 2002
180
US
SP3 seemed to install fine but now I can't get the SQL agent to start. There are 2 log errors:

(298) SQL Server Error: 208, Invalid object name 'msdb.dbosyscachedcredentials'. [SQLSTATE 42S02] (ConnIsLoginSysAdmin)

(000) SQL Server Agent must be able to connect ot SQLServer as SysAdmin, but '(unknown)' is not a member of the SysAdmin role.

Any help would be appreciated.

Thanks!!
 
The SQLSERVERAGENT is set at (domain)\administrator
 
Is the domain adminstrator account setup as a system administrator in SQL Server? Personally, I don't think it is good practice to use a Windows domain administrator account to start SQL Services. Is the same account is used to start SQL Server? If you want to get the best answer for your question read faq183-874 and faq183-3179.
Terry L. Broadbent - DBA
SQL Server Page:
 
Everything was set at "LocalSystem" but I changed it since we were having problems.

When I look under "Services", this is the current status:

MSSQL$(name) STARTED Logon As LocalSystem
MSSQLSERVER (not started) Logon AS LocalSystem
MSSQLServerAdHelper (not started) Logon As LocalSystem
MSSQLServerOLAPSvc (not started) Logon As LocalSystem
SQLAgent$(name) (not started) Logon As LocalSystem
SQLServerAgent (not started) Logon As LocalSystem

MSSQL$(name), MSSQLSERVER, MSSQLServerOLAPService, SQLAgent$(name) and SQLServerAgent are all set to start automatically but the only one that will start is the MSSQL$(name).

Should I set up a new account just for SQL administration and if so, how should I go about doing that and getting everything setup correctly?

Thanks!!
 
I'm still having the same problem as before. I have tried many different things but I just can't get the SQLAgent to start.

Any ideas??

Thanks.
 
Does the account you start SQL Agent with have access to the msdb database and the dbo.syscachedcredentials table? The account should be a system adminstrator on SQL Server and have access to all databases however, the original message you posted indicates the login isn't a system admin. Do you get the same error message since you chaged the start account?

Are you trying to run multiple instances of SQL Server on the server? Have you tried setting the MSSQL$(name) and SQL Agent(name) services to manually start? Perhaps you should disable these services.

If you want to get the best answer for your question read faq183-874 and faq183-3179.
Terry L. Broadbent - DBA
SQL Server Page:
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top