vCenter ADAM_VMwareVCMSDS event every 1 minute

Several times I have ran into the following issue with an event being logged in the vCenter Server event log every minute:

Active Directory Web Services encountered an error while reading the settings for the specified Active Directory Lightweight Directory Services instance. Active Directory Web Services will retry this operation periodically. In the mean time, this instance will be ignored. Instance name: ADAM_VMwareVCMSDS

I had fixed this on several vCenters that I managed. However the problem returned on one vCenter this weekend after enabling vCenter Linked Mode. I decided to document the solution here so it is easier to find if I run into this problem again.
As described here this is caused by a simple registry setting. Browse to the following key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ADAM_VMwareVCMSDS\Parameters

Delete the existing key (string) for “Port SSL” and replace it with a DWORD named “Port SSL” with a value of 636 (in decimal).

Restart ADAM_VMwareVCMSDS and ADWS services. Problem solved.

18 comments

  1. TheSaffaGeek says:

    Thanks for the mention

  2. Jason V says:

    While the post is old the issue persists; I get this same error with a clean install of vCenter 5. The fix (thankfully) still works.

  3. Hunter says:

    Work a treat. Many thanks.

  4. Peace says:

    Still works!

  5. Harvey Jimenez says:

    Works for me in vCenter 4.1
    Thanks a lot

  6. Dan says:

    Thanks helped me after vCenter 5 linked mode changes. Seems VMware aren’t addressing this issue.

  7. George Mitchum says:

    I have been getting this error every minute on my 5.0 vCenter 2008R2x64 server and edited the registry. Problem is that I have no services named ADAM* to restart. What’s the deal?

  8. George Mitchum says:

    Sometimes it just takes another set of eyes. “Early to bed and early to rise makes a man tired and blind in the eyes.” Thanks to my buddy who me straight.

  9. It looks like the Display Name of this service is now VMwareVCMSDS. If you open the properties of VMwareVCMSDS the service name attribute is still ADAM_VMwareVCMSDS. This is the service you’ll want to restart.

  10. George Mitchum says:

    Made the changes to the registry and bounced the 2 services. Still getting the messages every minute. What have I overlooked?

  11. George Mitchum says:

    Here is the complete error.

    This computer is now hosting the specified directory instance, but Active Directory Web Services could not service it. Active Directory Web Services will retry this operation periodically. Directory instance: ADAM_VMwareVCMSDS Directory instance LDAP port: 389 Directory instance SSL port: 636

  12. The only thing that has got me on this issue before is not changing the REG_DWORD to decimal before entering the value of 636. The value must be 636 in decimal (which is 27c in hex).

    I’d try the steps again…deleting the “Port SSL” string from the registry, creating a new DWORD 32bit value named “Port SSL” without the quotes and entering 27c (hex) or 636 (dec) for the value. Restarting the services again really should work.

    Just curious, the original post shows you are using Windows 2008 R2 but it doesn’t mention the version of vCenter. If you are running vCenter 4.0, VMware has a recent KB article on this topic that you should check out — “Running vCenter Server 4.0 on a Windows 2008 R2 system results in a log spew in the Windows Event Viewer” at http://kb.vmware.com/kb/1015850 which specifically mentions a compatibility/support issue with running vCenter 4.0 on Windows 2008 R2.

  13. Jeff Raimer says:

    Running vCenter 5.1b on 2008 R2. I cannot resolve this issue to save my life. Two of us have worked on it for three days and have deleted and recreated this key at least 4 times – all to no avail.

  14. servo says:

    Worked perfectly for me! Thanks!

  15. Ric Hochet says:

    Thanks !

  16. Breakdaddy says:

    Worked like a champ! Thanks!

  17. Michael says:

    This solution helped me out for two days.
    Now I have authetication problems again.
    Don’t know what else is going on…

Leave a Reply

Your email address will not be published. Required fields are marked *


*

Notify me of followup comments via e-mail. You can also subscribe without commenting.