Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


sql 2005 - server Agent error log file


sql 2005 - server Agent error log file

Author
Message
newdb
newdb
Grasshopper
Grasshopper (21 reputation)Grasshopper (21 reputation)Grasshopper (21 reputation)Grasshopper (21 reputation)Grasshopper (21 reputation)Grasshopper (21 reputation)Grasshopper (21 reputation)Grasshopper (21 reputation)

Group: General Forum Members
Points: 21 Visits: 321
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....
GRE (Gethyn Ellis)
GRE (Gethyn Ellis)
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1066 Visits: 2840
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
Melissa Burg
Melissa Burg
Grasshopper
Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)Grasshopper (10 reputation)

Group: General Forum Members
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.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search