相关文章推荐
){outline:none;box-shadow:none;}select::-ms-expand{;}:root,:host{--chakra-vh:100vh;}@supports (height: -webkit-fill-available){:root,:host{--chakra-vh:-webkit-fill-available;}}@supports (height: -moz-fill-available){:root,:host{--chakra-vh:-moz-fill-available;}}@supports (height: 100dvh){:root,:host{--chakra-vh:100dvh;}}
Link to home
Create Account Log in
Avatar of eclipsenet
eclipsenet

asked on

SQL Server Error: 4060 for deleted database Error: 18456 Login failed for user

SQL Server 2005 Management/SQL Server Logs are writing errors every minute for a database that has been deleted.  Messages are:
[298] SQLServer Error: 4060, Cannot open database "DatabaseName" requested by the login. The login failed. [SQLSTATE 42000].
[298] SQLServer Error: 18456, Login failed for user 'domain\username'.. [SQLSTATE 28000].
How do I  inform SQL that the subject databases are gone and there's no need to clutter the logs?
I would suggest locating the application that is constantly trying to connect and make it stop.  That is going to be your best solution.
ASKER CERTIFIED SOLUTION
Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
BIngo. Thanks.  We had a test MOSS2007 deployment that was decommisioned, and we didn't realize that the MOSS SSP instantiated a "...DeleteExpiredSessions" job on SQL.
BIngo. Thanks.  We had a test MOSS2007 deployment that was decommisioned, and we didn't realize that the MOSS SSP instantiated a "...DeleteExpiredSessions" job on SQL.
 
推荐文章