Vista - VS "Service Connection points" error after Patch Tuesday

+My VS 2005 SR2 has been working fine, until this week's patches were
installed. Now if I try to connect with VMRC+ it hangs, and when I open the
VS website it times out.

The event log shows event 1136:
"An error has occured during the creation of Service Connection points for
Virtual Server in Active Directory. Either a domain controller is not
available to complete the operation or there is a security problem accessing
the domain. This operation will be retried the next time the service starts.
Error 0x80070005 - Access is denied."

Any suggestions, please? The COM+ component has all the correct permissions
for Local Launch etc, as they have been unchanged since install ages ago.

Thanks

OK, this one sorted too.

FYI, Patch Tuesday was a red herring, other than it was responsible for the
server rebooting. But more in a moment...

Firstly, the Event log error is a red herring. See
http://www.windowsbbs.com/showthread.php?t=66376

My VS is running on a DC, but after spending some time tweaking permissions,
stopping and starting the service, setting to manual and juggling and
restarting the server when the service "didn't shut down in a timely fashion"
I observed that the service was suddenly shutting and restarting cleanly and
fairly responsively.

I tried the VS website and it opened :-O

Tried to start a VM and it hung till it timed out. I couldn't stop the
service and had to reboot the server again. Twice, just to make sure.

Then I found some references to VMs not starting when the host had been
restarted with the VMs in a Saved state. And so it was.

So I created a dummy VM (minimum config, no OS installed) and kicked that
off first.

It worked. (Well, it asked for a boot disk but it attempted to work!)

I fired up the others and they started, so normal service resumed.

Unhelpfully, I'm afraid, I'm not sure if VMRC was having a problem
connecting because of the state of the machines or whether it was some other
issue that a
seemed to be interfering with the service. If the situation reoccurs I'll
try to get a clearer picture, but right now it's working and that's all I
need till I get 2008 and Hyper-V installed in a month or so

Either way, ignore the log on a DC and don't restart the server with VMs in
a Saved state.

YMMV but good luck.


"Double-02" wrote: