The previous fix worked and allowed dcom connection again, however now I have another strange issue that I am wondering if anyone can help out with.
Dcom connection seems to run fine on the server for about a week. After a week the server machine stops accepting DCOM connections and I get the same error I did before the fix. Rebooting the server machine allows DCOM to start accepting connections again. Unfortunately I cannot reboot a production server every week so I am wondering if anyone has any suggestions?
The Fix to my last problem if anyone is having the same issue was to unintiall HIPS (Mcafee Host Intrusion Prevention Software). Unexplainable I know, but after removing it DCOM has been accepting connections for 2 weeks now without faillure.
Actually I want to connect to Vista machine through XP.
bcoz DotNet is installed in My XP machine and I want to debug my application on Vista machine through Xp.Is it possible?
Which s/w, I have to install in both machine?
Pls help me, I already spent 2 Man days.
Thanks in advance…
and add a user, it will cause the corresponding button in Component Services to be greyed out.
RESOLUTION:
Delete the users in the security policy (ie. Remove all users and click
Apply and OK.) It will appear as NULL in the security policy, but once
refreshed, it will then show “Not Defined”.
Go back to Component Services and you’ll notice that it’s reset back to the
original.
Thank you very much Jeff and Me for your detailed posts. It did not exactly help in my case, but helped me to find another blog post that finally resolved my problem (for me oleaut32.dll had to be reregistered):
Maybe it helps someone else. On my machine ASP stopped working in High Isolation Mode, putting out just an error code of -2147467259 (0x80004005) and debugging was refused.
Geebus what a pain in the rear that was, like you I was getting dizzy and ready to use a blunt object to end the frustration. It works, wooo fooking hoo.