SQL Server Home
Error: 18456, Severity: 14, State: 16(10)
as By Design
7/14/2006 1:28:49 PM
User(s) can reproduce this bug
I have SQL 2005 Expess installed on Windows Server 2003 SP1.
My application is running as a service and is set to depend on SQL Server instance...
During the startup my app attempts to connect to the databes and it fails to do so, after 30 retries (1second appart). After I login and attempt to start the service manualy, everything is OK, and the service connects to Sql and runs fine....
SQL Server log has this error msg, if using SQL authentication:
Error: 18456 "Severity: 14, State: 10"
Error: 18456 "Severity: 14, State: 16"
if I use Windows authentication.
I've attached ERRORLOG and a trace dump created by running sql service with
'-y 18456' acommand arg.
That was suggested by Laurentiu Cristofor
SQL Server 2005 - Express Edition (32)
Windows Server 2003
Operating System Language
Steps to Reproduce
any app that tries runs as service and connects to SQl db at the startup time...
2006-07-14 16:03:14.89 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2006-07-14 16:03:15.32 Logon Error: 18456, Severity: 14, State: 16.
2006-07-14 16:03:15.32 Logon Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <local machine>]
2006-07-14 16:03:15.34 spid8s Clearing tempdb database.
2006-07-14 16:03:15.40 Logon Error: 18456, Severity: 14, State: 16.
2006-07-14 16:03:15.40 Logon Login failed for user 'NT AUTHORITY\SYSTEM'. [CLIENT: <local machine>]
2006-07-14 16:03:15.89 spid8s Starting up database 'tempdb'.
2006-07-14 16:03:15.98 spid5s Recovery is complete. This is an informational message only. No user action is required.
2006-07-14 16:03:15.98 spid11s The Service Broker protocol transport is disabled or not configured.
2006-07-14 16:03:15.98 spid11s The Database Mirroring protocol transport is disabled or not configured.
2006-07-14 16:03:16.03 spid11s Service Broker manager has started.
2006-07-14 16:03:20.35 spid51 Starting up database 'ReportServer$TRBR'.
2006-07-14 16:03:20.42 spid52 Starting up database 'RbrDb_260'.
2006-07-14 16:04:14.98 Server Server resumed execution after being idle 25 seconds: user activity awakened the server. This is an informational message only. No user action is required.
unsucesfull login to database
sucesfull login to database
to post a comment.
Please enter a comment.
on 8/21/2006 at 3:21 PM
Thank you for raising this issue. The error message appears to be by design. After SQL Server start up, the database is not immediately available and needs to come online before one can connect to it. Please see: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=552680&SiteID=1.
SQL Server Engine
to post a workaround.
Please enter a workaround.
© 2013 Microsoft