Yep, sometimes you do get these in your log files. Today’s fun and games started out with me checking my log files on my production SQL Server box and seeing the above error hitting my server about once a minute for the past 12 hours or so. Digging a little bit deeper I opened up the event viewer and found the Application Failure Audit which handily listed the client ip address that was trying to log on to my SQL Server. Now, I’m a humble programmer and know very little about networking…and indeed very little about the set up of the network in my organisation (it is large, and complex). However, WinXP provides a nice command line utility called nslookup which provided me with the computer name that was issuing the logon request.
After a little more investigation, it seems this new server was cloned from my current sql server box for someone else…..unfortunately, they didn’t finish or didn’t realise that they needed to finish changing server names in *a lot” of different places and. SQL Server Reporting Services (you old nemesis you) on the new server was still trying to open a connection to my production SSRS, but using the new local machine name account to try and log on. Of course it failed.
Turn off SSRS on the new box (we don’t need it on there anyway) and voila. Error message goes away.