VMware View 5.1.1 Security Server LDAP Errors

[VirT3ck]

Im having a serious amount of errors on my VMware View Security Server (5.1.1)

The debug log shows a large amount of LDAP errors, see below.

2012-09-06T10:46:49.075+02:00 ERROR (0610-0940) <WSAdminDomainTimerThread> [ws_admin] Failed to bind to LDAP://rootDSE
2012-09-06T11:01:50.102+02:00 ERROR (0610-0CB8) <WSAdminDomainTimerThread> [ws_admin] Failed to bind to LDAP://rootDSE
2012-09-06T11:16:50.109+02:00 ERROR (0610-0FE8) <WSAdminDomainTimerThread> [ws_admin] Failed to bind to LDAP://rootDSE
2012-09-06T11:31:51.120+02:00 ERROR (0610-0DD8) <WSAdminDomainTimerThread> [ws_admin] Failed to bind to LDAP://rootDSE
2012-09-06T11:46:51.132+02:00 ERROR (0610-0244) <WSAdminDomainTimerThread> [ws_admin] Failed to bind to LDAP://rootDSE
2012-09-06T12:01:52.159+02:00 ERROR (0610-0F3C) <WSAdminDomainTimerThread> [ws_admin] Failed to bind to LDAP://rootDSE
2012-09-06T12:16:52.155+02:00 ERROR (0610-0E5C) <WSAdminDomainTimerThread> [ws_admin] Failed to bind to LDAP://rootDSE
2012-09-06T12:31:53.182+02:00 ERROR (0610-0F68) <WSAdminDomainTimerThread> [ws_admin] Failed to bind to LDAP://rootDSE
2012-09-06T12:46:53.194+02:00 ERROR (0610-092C) <WSAdminDomainTimerThread> [ws_admin] Failed to bind to LDAP://rootDSE
2012-09-06T13:01:54.217+02:00 ERROR (0610-08E4) <WSAdminDomainTimerThread> [ws_admin] Failed to bind to LDAP://rootDSE
2012-09-06T13:16:54.227+02:00 ERROR (0610-0504) <WSAdminDomainTimerThread> [ws_admin] Failed to bind to LDAP://rootDSE

Anyone got any suggestions?

[mpryor · Accepted solution]

Hi,

The ws_admin plugin is attempting to do domain checks every 15 minutes, but since your security server isn't on the domain these checks are failing. This is completely harmless but they do not need to be running in the first place, I've raised this internally.

Mike

Edit:

There's a simple fix for this in 5.1.x:

Under the existing registry key HKLM\Software\VMware, Inc.\VMware VDM\plugins\wsnm\admin create a new key named Params, and under that a new DWORD value named InitiateDomainChecks with data of 0. Once set, you will need to restart the VMware View Security Server service for the change to take effect.

[VirT3ck]

Hi Mike,

I'm going to add this registery key as you recommend and I'll let you know the results! Thank you for your time!

René

[VirT3ck]

The messages are now indeed gone! Thanks again Mike!

[VirT3ck]

Sadly.. I was too fast with my response and the messages are still appearing in the logs ;(

Any other ideas out there?

[mpryor]

Hmm, the registry entry should work - I'll have to go back and re-test.

[bretttenney]

Thanks. That worked for me.

[VirT3ck]

Just to make it complete, below the entries in the registery in the admin key.

[HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VDM\Plugins\wsnm\admin]
"Filename"="ws_admin.dll"
"NoUnload"="true"
"InitiateDomainChecks"=dword:00000000

VMware View Version: 5.1.1.799444

[bretttenney]

It doesn't look like you created the Params key as mentioned. Inside that key is where you put the DWORD value named InitiateDomainChecks.

HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VDM\Plugins\wsnm\admin\Params

[VirT3ck]

Dang! Good catch thank you