Atbroker.exe "application failed to initialize properly" on remote des

[markm75]

I get this error message when trying to connect to my remote vista RTM (Ultimate) machine.. It happens at random.. the only fix is to remotely reboot the machine via a "shutdown" command.

It says to click ok to terminate the application, that only results in a blank screen.

Anyone found a solution as of yet?

 

[linney]

The only bit of information I found on the Web is that it seemed to start occurring after installing some unknown Vista Update.

Because of the random nature of the error it is hard to suggest any troubleshooting steps using the "eliminate and verify" steps normally tried.

Are there any clues in the Event Viewer?

 

[markm75]

Actually there is an entry in the event viewer:

Faulting application atbroker.exe, version 6.0.6000.16386, time stamp 0x4549b800, faulting module USER32.dll, version 6.0.6000.16386, time stamp 0x4549d372, exception code 0xc0000142, fault offset 0x0000000000001d28, process id 0xeb8, application start time 0x01c749630f7606db.


Event ID 1000 , Application Error...


No real solutions here either:

http://www.eventid.net/display.asp?eventid=1000&eventno=1475&source=Application Error&phase=1

 

[linney]

You could check the date of the first error in the Event Viewer and see if you can figure what updates or other things happened on that date or just prior to it.

C:\Users\Usernamexxxx\AppData\Local\VirtualStore\Windows, will/might have a DrWatson log (remember them), if you want the highly technical cause of the crash look in the above folder for the Drwtsn.log.

Find the entry that is relevant by date and time to the crash you are investigating. The exact cause of the crash is indicated by "FAULT ->" on the left of page next to line of code causing crash. This, if your as cluey as me, wont tell you much but you can use it to see if it is the same fault all the time, and further up the log you can find what processes and modules are running.

It hardly likely that the atbroker.exe is corrupt, it is in the System32 folder, and it is a bit like "Fort Knox" to get in and change anything in there, but you could run the System File Checker program anyway.

How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program generates in Windows Vista

http://support.microsoft.com/kb/928228#appliesto

SFC /? from an elevated command prompt should help you there.

 

[markm75]

Unfortunately the good old drwatson logs werent there.

I checked back.. about the only windows OS based update that was made just prior to this was the service pack for Visual Studio 2005 and the hotfix after that.

I dont see any real programs installed just prior to the first instance that could be the culprit either.

I really cant remove the SP for VS either.

Thanks for the ideas though.