Overview
When migrating a DNN application to a new server, you may encounter licensing errors. These errors can arise from improper license deactivation, incorrect server configuration, network or firewall issues, cached data, or incorrect application pool settings. This article provides a step-by-step guide to troubleshoot and resolve these licensing issues during server migration.
Information
To resolve licensing issues during a DNN server migration, follow these steps:
- Verify License Deactivation: Ensure the license is properly deactivated on the old server. If accessible, navigate to
Settings > Aboutand delete the license. - Check Server Configuration: Confirm the
web.configfile on the new server includes the correct HTTP module entry for licensing. - Network and Firewall Settings: Ensure the new server has outbound access to the DNN licensing web service at http://www.dotnetnuke.com/desktopmodules/bring2mind/licenses/licensequery.asmx. Verify no firewall rules block the connection.
- Clear Cached Data: Clear the server cache and restart the application. Recycle the application pool in IIS.
- Application Pool Settings: Verify the Application Pool Identity account has a valid profile and is not read-only or temporary. Ensure the Load User Profile setting in IIS is correct.
- Manual Activation: If automatic activation fails, attempt manual activation by following the steps in the DNN documentation.
- Temporary License Activation: To avoid downtime, activate a production license as a development type temporarily while the license is not yet deleted from the old server and activated on the new one. This should only be done for a short period and in exceptional circumstances like migrations.
Frequently Asked Questions
- What should I do if I encounter a licensing error during server migration?
- Follow the troubleshooting steps provided, including verifying license deactivation, checking server configuration, ensuring network and firewall settings, clearing cached data, and verifying application pool settings.
- Can I use a production license as a development type during migration?
- Yes, you can temporarily use a production license as a development type to avoid downtime during migration. This should only be done for a short period and in exceptional circumstances.
- How can I ensure my server has access to the DNN licensing web service?
- Verify that the new server has outbound access to the DNN licensing web service and that no firewall rules are blocking the connection.
Priyanka Bhotika
Comments