Start a conversation

Running in 'disabled' with: "Warning: your Lyris ListManager server has been disabled." - Your activation code was registered for a different hardware ID

Overview

After standing up a test system, you Clear Activation and Get Activation on the test system. Or after swapping hardware or performing an upgrade, when you try to access your production system it is running in 'disabled' mode and the license page displays the following error:

Serial Code: example-12345678XYZ9
Activation Code: example-ABCDEF00GHI12J34567890000KLMN1P2345Q6R7890S0T1
In Disabled Mode: yes
Invalid Hardware ID: yes
DisabledMessage: Your activation code was registered for a different hardware ID than Lyris ListManager is currently running on.

You will also find the following error in the debug log:

Warning: your Lyris ListManager server has been disabled. Your Lyris ListManager
server is disabled because: Your activation code was registered for a different
hardware ID than Lyris ListManager is currently running on.

Solution

NOTE: If the machine where ListManager is installed does not have web access, this solution will not work. See the How to Activate ListManager Without Internet Access or Behind a Firewall or Internet Proxy article for a solution if your system has no internet access.

Refresh Activation in ListManager

  1. Log on to ListManager as an Administrator

  2. Navigate to Utilities > Administration > Server > Operational Statistics > License Capabilities

  3. Click the Clear Activation button 

  4. Click the Get Activation button

  5. Refresh the page to view the updated license capabilities

Refresh Activation from the Windows Command Prompt:

  1. Log on to your ListManager Windows Server as an Administrator

  2. Navigate to Start Menu > Run,  and type cmd in the "Open" field

  3. Navigate to the directory where ListManager is installed, the default location is accessed with:
    cd C:\Program Files\ListManager

  4. Enter lm clearactivation

  5. Enter lm getactivation
NOTE: If the ListManager server's internal IP changes it must be updated in the tclhttpd.rc settings file.  Then the ListManager and Web services must be restarted.  Until this step is performed the ListManager server won't answer HTTP requests.

Back to top


Related Articles

Choose files or drag and drop files
Was this article helpful?
Yes
No
  1. Priyanka Bhotika

  2. Posted
  3. Updated

Comments