Network Management

License migration utility experienced an error during Configuration Wizard

The license migration utility encountered an issue, or the server was unable to resolve the main poller hostname to make a proper connection to the licensing server or the firewall was blocking the traffic between the two servers. "The license migration utility experienced an error. Product licenses were not transferred correctly." Resolution steps are provided.

First published date

10/19/2018 8:57 PM

Last published date

4/29/2025 11:40 PM

Overview

You may see following Warning in some cases after the Configuration wizard completes. These warnings are noted mostly on Additional pollers or Additional web servers and in exceptional cases on Main pollers as well.

You may receive the error: "The license migration utility experienced an error. Product licenses were not transferred correctly." To determine the specific reason for the failure, see c:\.....\SolarWinds.Orion.Licensing.Migration.log.

To resolve, complete the troubleshooting steps listed below in the Resolution section and run the Configuration Wizard again on the additional poller.

Product section

Orion Platform

Cause

The server was unable to resolve the main poller hostname to make a proper connection to the licensing server or the firewall was blocking the traffic between the two servers.

 

Resolution

Troubleshoot the issue following one of these solutions. To determine the specific reason for the failure, see %ProgramData%\SolarWinds\Logs\Orion\Licensing\SolarWinds.Orion.Licensing.Migration.log.

Issue: If there is a "communication exception", do the following:

  1. Check the system listed in the exception error message located in the migration utility log (c:\.....\SolarWinds.Orion.Licensing.Migration.log).
  2. You can modify your hosts file if there is a DNS problem. Add an IP entry for the unreachable server listed in the error message.
    The hosts file is located in %systemroot%\system32\drivers\etc. Use a program like notepad (Run as administrator) to edit the file and follow the example format included in the hosts file.
  3. In rare cases, ensure port 17777 is not blocked by firewalls.
  4. Verify the Orion Module Engine is up and running on the system the web-based license manager is attempting to connect to (the system listed in the exception error message located in the migration utility log).
  5. You can also check the licensing business layer host log at \ProgramData\SolarWinds\Logs\Orion\Licensing\SolarWinds.Orion.Licensing.BusinessLayer.log for errors.
  6. If you cannot locate a communication error, open a support ticket.

 

Issue: The licenses were not moved to main poller and are not visible to web UI and scalability engines.

Troubleshoot with this command: Migration.exe /console=debug /move

This command moves the licenses correctly.
 

Issue: The scalability engine evaluation was not started. This issue may occur when no commercial or other evaluation licenses are present). Troubleshoot with this command: Migration.exe /console=debug /eval=start

This command resolves the scalability evaluation.


Issue: Leases not transported to this machine. The Configuration Wizard encounters an error not locating licenses. Troubleshoot with this command: Migration.exe /console=debug /leases=pull

After resolving the issue(s) with the troubleshooting command, please run the Configuration Wizard.  The Configuration Wizard will verify the licenses store on the main and Additional pollers and Addtional webservers.

Note: You may want to enter a ticket with Support to troubleshoot. If you are unsure about the commands above and their purpose etc.