When running LSclient or testconnection.exe, RPC fails and OS shuts down

[tomazj]

Hi,
when testing successfully installed LS, I encountered strange problem. For some machines, when they run LSclient.exe at login or if I test them with testconnection.exe, RPC server fails on that machine and OS pops up "shutdown in 1 minute" dialog. I can stop shutdown process with shutdown -a command, but RPC no longer works. If I try to start RPC service manually, it fails again and shutdown countdown starts again. Machine must be rebooted to resolve this problem. Very inconvenient for my clients.
Event viewer records something like "... rpcrt4.dll error failed on address 0x0007c081...".
Any clues?
Thanks.

[tomazj]

I checked, on all puters DCOM is enabled.
All ideas are welcome.
Thanks.

[Hemoco]

Try to run "dcomcnfg"
Right click "my computer"/properties
Make sure that "Enable Distributed Com on this computer" is checked

[tomazj]

Hi,
I tried your suggestion, scf scanned OS, but did not want CD, so I assume that everything was OK. I did this on several machines.
Then I downloaded MS WMIDIAG tool and did a scan on a system. There are several WMI errors on scanned systems. It's hard to say, how serious they are. Now I have to analyze reports and try to find a solution.
This problem is quite serious, because it appears on several machines with different OSes, mostly XP, but also Win2k. On latter, PRC service fails, but shutdown dialog does not pop up.
If I find a solution, I will write a report here.
Thanks for help.

[Hemoco]

try a "sfc /scannow" from the command line and insert the windows XP cdrom when asked for.

[tomazj]

This happens on XP SP2, but only on some machines. It's not firewall related, because only one machine had Tiny Firewall installed, other are without. I know it's not LS problem, because before LS I tried Spiceworks with same problem. I just ask if anyone else had same problem. I searched on MS KB and through the net, but didn't find anything useful.

[Hemoco]

On which operating system/service pack do you have this behaviour?
Lansweeper only uses standard WMI / remote regisrty calls