57827: Acronis Backup Advanced: vCenter Integration Is Reset by Acronis Management Server Service Restart if Temporary User Profile Is Used

use Google Translate

Operating Systems: 

Last update: 04-09-2019

After AMS service restart you get the error "The specified entry does not exist: 'ID'."


  1. Management Server (AMS) is installed and vCenter integration is configured.
  2. After restart of AMS service or after machine reboot vCenter integration is reset and cannot be accessed. When trying to configure it again, an error similar to this one occurs:

Failed to enumerate the registered VMware vCenters.
Additional info:
Error code: 32774
Module: 224
LineInfo: a20120e20d7da150
Fields: $module : virtual_center_addon_vs_43994
Message: Failed to enumerate the registered VMware vCenters.
Error code: 32771
Module: 248
LineInfo: 88f44f36da889cd4
Fields: $module : management_server_vs_43994
Message: The specified entry does not exist: 'DDD4BE85-C159-4838-02B7-B7BA1623D439'.


AMS service is running under a user with temporary profile. It is similar to local profile except that it is deleted when the user logs off. The user can be the automatically created AMS User or any manually created user except for the local or domain Administrator. Under local/domain Administrators issue does not occur.

After service restart or machine reboot configuration of temporary profiles is completely deleted from windows registry and ESX configuration of the AMS User is deleted from HKU\<AMS_USER_SID>\Software\Acronis\CredStorage.


To resolve this issue make sure you are using a standard local profile instead of a temporary one. There can be different reasons why only temporary user profiles are used:

Solution 1: Local profile folder was deleted without deleting the associated registry hive

A user profile is a folder and a registry hive storing user's settings. A temporary profile may be used, if the user profile folder was deleted, but the associated registry hive wasn't. Beginning with Windows Vista you need to delete the ProfileList registry key associated with the profile that was removed.

You can either restore of delete the cofiguration as described in this Microsoft KB article: Error message: “The User Profile Service failed the logon. User profile cannot be loaded”, when logging on to Windows 7 or Windows Vista

Solution 2: Roaming profile is set by global group policy in domain

If you have specified Set roaming profile path for all users logging onto this computer in the group settings and log on with a local user account, the local user cannot access the roaming profile path and a temporary profile is used.

Disable permissions check in group policies: Machine -> System -> User Profiles -> Do not check for user ownership of Roaming Profile Folders

See also: The “Set roaming profile path for all users logging onto this computer” Group Policy setting also applies to local user accounts in Windows Server 2008

Solution 3: Registry hive cannot be loaded

In Windows, user's registry settings are stored in ntuser.dat file. This data is mounted to HKEY_CURRENT_USER upon logon. If that file is missing, corrupt, is already loaded, or has incorrect permissions, Windows cannot use the profile and uses a temporary profile instead. Create or use another user.

See also: “Windows cannot load your profile because it may be corrupted” error message when you try to log on to Windows XP Error message when you use a migrated user account to log on to a migrated computer that is running Windows Vista, Windows Server 2003, or Windows XP: “Windows cannot find the local profile and is logging you on with a temporary profile”

Solution 4: User is a guest

If a user is a member of the local group Guests or the domain group Domain Guests, Windows issues temporary profiles. Do not use a user that is a member of the Guests group.

See also: A temporary user profile is created every time that you log on to a Windows Vista-based computer that is connected to a domain

Solution 5: User is a member of too many groups

As the SIDs of all user groups are added to the users' Kerberos Tokens, the maximum allowed token size may not suffice for users that are members of many groups. This issue has been occuring since Windows 2000. Increase the MaxTokenSize registry value as described in Microsoft KB article.