While at work one day this week, users started complaining about slow access times to a particular application. After confirming that all applicable servers (an application server and a SQL server) were online, and that there were no SQL problems (such as deadlocks), we took a look at the event log, and found an obscure entry:

Type:  Error Source:  Userenv Event ID:  1000 Description:  Windows cannot determine the user or computer name. Return value (1722).

Like many good event log messages this told me little about the actual problem. Rather than scratch my head until an answer mysteriously appeared, I went to perhaps the best resource for understanding event log entries: EventID.net (www.eventid.net).

EventID.net provides a searchable index to events, and has extensive information provided by other users that can be invaluable in troubleshooting problems. Using the site is simple: enter the event ID number and the source . . .

→ Read More: Decoding event log errors with EventID.Net