Cannot start Agent or join a new domain

Question

We've just installed a pair of new servers today to make a 2 nodes cluster.
These are Windows 2003 server systems.
We started to do a Windows Update and downloaded 44 patches.
Now when we launch the installation procedure, it does not tell anything special, but the agent won't load... if we deinstall all the updates, then the agent runs.

Now better, we install Autostart, add the 44 patches from windows update and the main node run, now on a second node, we try to add an agent to the domain => fails

conclusion: in the microsoft update patches, there is one (which one?) that prevents the agent to correctly register or communicate with the domain.

any idea?

ble1 · Answer

44 patches seems a lot and I'm sure you are not in the mood to play the game where you would install one, test it, install second one, test it, etc... so the best thing would be to talk to support and have them play that game.

tgluzman · Answer

just opened a case, I will update here when we have the info, I think this is interesting for all the installations

ble1 · Answer

Agreed. Usually people tend to have up-to-date productive machines and if some patch is breaking the application then that's very unpleasant situation... especially if patch is critical and so is the application.

tgluzman · Answer

we finally identified the problem, the 8.3 Microsoft short names should not be deactivated on the server, some EMC tasks are using that old old stuff...

Replication Manager

Cannot start Agent or join a new domain

Was this post helpful?