"Wanna" ransomware outbreak. Please see this Sophos article sophos.com/kb/126733 for advice on how to protect your organization. Immediate action recommended.
2010-01-29 04:27:11.31 Logon Login failed for user 'Domain\Administrator'.
First seen in Enterprise Console 4.0.0
The severity of the error indicates the seriousness of the error. A severity level of 14 indicates an error in the range described as user correctable, which is understandable for login failures. The next item of information the error provides is the state number. Most errors have a state number associated with them which provides further information which is usually unique to the error that has been thrown. For a login error, state: 8, shown in the above example, indicate an invalid password was used. The state number therefore provides invaluable information about the reason for the login failure and can often be enough to identify the cause of an 18456 error. State number is 16: Login valid, but not allowed to use the target database
State number is 16: Login valid, but not allowed to use the target database
Ensure that the account mentioned in the initial error message is listed, under Sophos DB Admins. Make a note of the account name mentioned. You can check this in the Active Directory (Start | Administrative tools | Active Directory User and Computers). Double click Sophos DB Admins and click on members tab and ensure that the account is listed there.
Once installed please Click Start | All Programs | Microsoft SQL Server 2005 or2008 | Configuration Tools | Microsoft® SQL Server® 2005 or 2008 Management Studio Express. Once the SSME program runs it will present you with the logon screen. Please make sure that you:
Every comment submitted here is read (by a human) but we do not reply to specific technical questions. If you need technical support please post a question to our community. Alternatively for licensed products open a support ticket.