Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

sql 2005 - server Agent error log file Expand / Collapse
Author
Message
Posted Saturday, May 23, 2009 7:43 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, July 18, 2014 7:35 AM
Points: 22, Visits: 317
Hello,

2 years ago I took intro to SQL DBA 2 and never touch an SQL server until April of this year. I have 2 problems I hope you all can help me:

1. Since the day our DBA left, there's this error message every minute in the Serever Agent error log file:

[298] SQLServer Error: 15404, Could not obtain information about Windows NT group/user 'domain\username', error code 0x534. [SQLSTATE 42000] (ConnIsLoginSysAdmin).

I looked through all the job or maintenance job plan and don't see anything that have the username appear anywhere. Where can that error coming from ?

2. At 3AM everynight since our DBA left, these errors message also appear in the Server Agent error log file:

[298] SQLServer Error: 4060, Cannot open database "SQLdmRepository" requested by the login. The login failed. [SQLSTATE 42000]
and
[298] SQLServer Error: 18456, Login failed for user 'domain\sqlservices'. [SQLSTATE 28000]

I found in the daily job schedule there's a job that call "groom SQLdmRepository" and in the Steps it has this "EXEC [p_GroomRepository]". I can't find anywhere what this "GroomRepository" is about.

I also asked users if they experience anything weird with the database and all answer no.

Any help is appreciate....
Post #722568
Posted Saturday, May 23, 2009 4:45 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Thursday, June 5, 2014 3:57 AM
Points: 1,030, Visits: 2,793
Hi

I think your first problem maybe related to the fact that when your DBA left your sys admins probably disabled or deleted his windows account...which is usually the case...I don;t have enough detail to be sure but with regard to your first problem check all the jobs to ensure that they are not owned by or running under the context of your DBA's old windows domain account...this maybe the cause of your problem

Your second question, i think maybe to do with some third party monitoring tool, from memory, which is not always the best i think IDERA uses a database with that name...Do you still use IDERA or a monitoring tool of osomekind?...It could be that the job was setup to groom idera which i believe, although i'm 100% sure, removes uneccessary/old/redeundant data from the database... If the db no longer exists becuase you have stopped using iDERA but the job is still running it will fail because it can't connect to the database...

Not sure if this is helpful but hopefully provides a place to start

cheers


Gethyn Ellis

gethynellis.com
Post #722646
Posted Thursday, June 11, 2009 3:59 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Friday, August 12, 2011 2:02 PM
Points: 10, Visits: 49
This is part of the Quest/Spotlight SQL Monitoring suite. Ever figure out what was causing the issue, I'm having it too but I know the user ID is active that it is running under and is able to log into SQL. The one thing I did find in the job was that the database was not selected on the step to call the procedure and I can't locate the stored procedure anywhere on the server.
Post #732871
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse