After upgrading the Core Service to 5.4.x, the following error is present on the Core UI.
“Following services have failed to initialize:
◦ephemeralAccountsService: NetLocalGroupAdd failed - The request is not supported
To solve this problem , try to restart them.”
Restarting the service does not work. Also, when attempting to mount a recovery point the task will fail with the following error:
“Mounting RP as writable:
Exception chain:
•NetUserAdd failed - The request is not supported
•One or more errors occurred.
Replay.Common.Contracts.Win32Api.Win32ApiFailedException: NetUserAdd failed - The request is not supported
at Replay.Core.NativeWrapper.EphemeralAccounts.UserAccountsApiNative.CreateUser(String name, String password, IEnumerable`1 groups)
at Replay.Core.Implementation.EphemeralAccounts.EphemeralAccountsService.GenerateEphemeralAccount(String nameHint)
at Replay.Core.Implementation.ReplayEngine.ReplayEngineService.GenerateEphemeralAccount(Guid agentId)
at Replay.Core.Implementation.Mounts.LocalMountFactory.MountLocal(IVolumeImage imageToMount, UInt32 startEpochNumber, MountFlags mountFlags, String driveLetter, String securityProvider, Action`2 progressCallback, CancellationToken cancellationToken)
at Replay.Core.Implementation.Mounts.LocalMountVolumeImageJob.b__0()
at System.Threading.Tasks.Task.Execute()"
The Core Service is installed on a Domain Controller where local accounts cannot exist. If the domain controller is read-only then an account still cannot be created.
AppAssure creates ephemeral (temporary) accounts when mounting recovery points. Recovery points are mounted for restores, exports, and numerous other integrity checks. Backups and replication are not affected with the creation of ephemeral accounts.
If a Core has this behavior, the solution is to move the Core Service off of the Domain Controller machine. If that is not possible or not wanted, then there are a couple of workarounds.
Workaround 1: If the recovery points are replicated to another Core, the recovery points should be mountable from the Target Core.
Workaround 2: The Local Mount Utility can be used from another machine, connect to the Core, and then mount the recovery points.
