Sunday, March 11, 2012

Error/Failure Audit in Event Logs (SQL 2005 Express) [Advanced Services]

Q1: Any way to control which db loads when, and perhaps stop this error from happening? Again- when all is said and done, the report server functions, and I am able to access just fine.

Q2: What kind of recovery is being referred to? Given the message type- I assume it's nothing of concern- probably more to do with a system that doesn't run all the time.

Okay- so I get these two event messages each time I boot.

Below are two error message I see daily with each system boot- the services mentioned do "actually" function, and are running- as not 10 seconds after these messages are logged, the successfully loaded messages appear. It's almost as if report services tries to connect before the databases are up and running.

Basically the sequence (today) was:

1. 05:49:01 Failure Audit (MSSQL$SQLEXPRESS)

2. 05:49:01 Error (Report Server Windows Service (SQLEXPRESS)

3. 05:49:02 Recovery is complete. (EventID 3408 MSSQL$SQLEXPRESS)

4. 05:49:06 Starting up database 'ReportServer'

5. 05:49:09 Server Resumed execution (MSSQL$SQLEXPRESS)

I'm assuming based on the events that Report Server Service attempts to connect to the ReportServer database before it's actually started. Doesn't really explain the failure audit-

1. Failure Audit:

Event Type: Failure Audit
Event Source: MSSQL$SQLEXPRESS
Event Category: (4)
Event ID: 18456
Date: 8/9/2007
Time: 05:49:01
User: <MACHINENAME>\<LOCALUSER>
Computer: <MACHINENAME>
Description:
Login failed for user '<MACHINENAME>\<LOCALUSER>'.

[CLIENT: <local machine>]

This is almost immediately followed by this (which I consider a no-brainer, considering the above):

2. Error:

Event Type: Error
Event Source: Report Server Windows Service (SQLEXPRESS)
Event Category: Management
Event ID: 107
Date: 8/9/2007
Time: 05:49:01
User: N/A
Computer: <MACHINENAME>
Description:
Report Server Windows Service (SQLEXPRESS) cannot connect to the report server database.

The master database is started first, you cannot control the order in which the database are started up. if the users tries to connect to the database he will be authenticated by SQL Server and directly tries to change the default database or if explicitly mentioned in the connection string connect to the database. if the database is not yet started he will get a login failed (although authenticated but he was not able to change the database context). if you have these problems, try to set the dependency of Report Server to the SQL Service to make sure that Reporting Server will only be started if the SQL Server Service has been. This might help you getting some additional time for the server to make a regular recovery (which is normal if the database / server was not shutdown properly)

Jens K. Suessmeyer

http://www.sqlserver2005.de

No comments:

Post a Comment