Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

Search the VMware Knowledge Base (KB)

View by Article ID

Automatic and manual backups of the View Connection Server database fail (2040602)

Automatic backups of the View Connection Server database fail
Manually backing up the View Connection Server database in the View Admin console (View Configuration > Servers > Connection Servers > Backup Now... ) fails
Changing the data recovery password in the View Admin console (View Configuration > Servers > Connection Servers > Edit Backup > Change data recovery password) fails with the error:

Internal Error
In the machine where the View Connection Server is installed, backing up the ADAM database via vdmexport as per Performing an end-to-end backup and restore for View Manager (1008046) is successful.
The View Connection Server logs may contain entries similar to:

DEBUG (15C0-1788) <6024> [vdmexport] MessageFrameWork Worker Shutdown, Name=admin, Channel=0000000000000000
WARN (0784-0AD0) <2768> [ws_ldap] LDAP Backup Service LDAP Backup to C:\ProgramData\VMware\VDM\backups failed - exit status 1
WARN (0784-0AD0) <2768> [ws_ldap] LDAP Backup Service failed to backup LDAP data to C:\ProgramData\VMware\VDM\backups\Backup-20121128111043.LDF - file is zero length
ERROR (0784-0AD0) <2768> [ws_ldap] LDAP Backup failed - system error from command execution (1)

Note: For more information on the location of the View log files, see Location of VMware View log files (1027744).

This issue may occur if the permissions on these folders are incorrect:

To resolve this issue, ensure that these folders' NT AUTHORITY\SYSTEM account has Full control permissions enabled:

Right-click the folder C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18, click the Security tab, and check that the NT AUTHORITY\SYSTEM account has Full control set to Allow.

If not, edit the permissions for this account and set Full control to Allow.
Right-click the folder C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys, click the Security tab, and check that the NT AUTHORITY\SYSTEM account has Full control set to Allow.

If not, edit the permissions for this account and set Full control to Allow.

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

1 2 3 4 5
0 Ratings

1 2 3 4 5
0 Ratings

Actions

KB:

Did this article help you?
This article resolved my issue. This article did not resolve my issue. This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)