-
Title
Error Quest.MigrationManager.Exchange.Agent.LicenseMailboxException: Mailbox [legacyExchangeDN] cannot be licensed for migration, check your license in Console (Help->About), Internal exception: The network path was not found. File: 'RegKey.hpp' Line: '1 -
Description
Error Quest.MigrationManager.Exchange.Agent.LicenseMailboxException: Mailbox [legacyExchangeDN] cannot be licensed for migration, check your license in Console (Help->About), Internal exception: The network path was not found. File: 'RegKey.hpp' Line: '183'at Quest.MigrationManager.Exchange.Agent.LicenseHelper.LicenseMailbox(LicenseCounterType LicenseType, ILogger _log, String MailBoxDN, IAeLicenceWrapper aeLWExternal)at Quest.MigrationManager.Exchange.Agent.Jobs.DisJob.LicenseMailbox()at Quest.MigrationManager.Exchange.Agent.Jobs.DisJob.BeforeSync()at Quest.MigrationManager.Exchange.Agent.Jobs.DisBaseJob.RunJob() -
Cause
The issue might be caused by one of the two reasons below:
1. The service account under which the Migration Agent for Exchange (MAgE) is running does not have access to the registry of the server which is specified as QMM (Quest Migration Manager) License server. By default that is the QMM console server. (Can be verified at Tools | Options | License page).2. The Remote Registry Service is not running on the server specified as License server for QMM migration.
-
Resolution
To troubleshoot the issue, please follow the steps below:
1. Check what account is specified for MAgE on its agent host server. This can be done in the Agent Manager view when mailbox collection is selected in the MMEX Management Tree.
2. Log on to the agent host server in question with this account.
3. Start regedit, and select Connect Network Registry command from the File menu.
4. Specify the name of the server which is selected as License server in Tools | Options | License.
If you get an 'Access Denied' error or other connectivity error when connecting to the remote server registry, please do the following:1) Add the MAgE service account to the Administrators local group on the MMEX console server and make sure you can successfully open the registry remotely from the agent host server.
2) Ensure interconnectivity from MAgE agent host server to MMEX console server when logged on to the MAgE agent host with the service account.
3) Start the Remote Registry service on the MMEX console machine.