Overview

You are experiencing an issue when activating one of DNN's microservices. You check your logs and see the error 'Error occurred while obtaining a token for portalId {ID} and application {ApplicationName} ... "The instance <instance-ID>has already been registered". 

Solution

If you have two servers (Production and Development), and both have different instance IDs, the quickest fix would be to change the name of the database on the Development server. This will change your connection string and the tenant ID there. Refer to Using the Same TenantID for 2 Different Environments for more details.

Otherwise, there might have been an activation issue, and the solution involves unregistering the instance from the DNN side. Here are the steps:

1. Finding your Microservices Tenant ID.
   • Alternatively, a superuser can see the TenantID through this request: http(s)://<hostname>/API/DNNCorp/EvoqMicroservicesLibrary/MicroServices/GetClientTenantGroupId
2. Contact DNN Support to unregister the instance causing the error. This needs to be done by the DNN Infrastructure Team. Include:
   • The TenantID from step 1.
   • Your license details.
3. Activate your microservices.

<supportagent>Use this PRF</supportagent>

Summary

This article provides a solution to the DNN error 'The instance <instance-ID>has already been registered'. The solution involves unregistering the instance from the DNN side, and changing the database name in the DEV server if necessary.