KB40681 - License client is prompting with the message: Code=(0x32) Error="Stale Lease Id"

This article describes an issue where license client fails to lease license from the license server with the message "License server protocol error- code(0x32) Error="Stale Lease Id".

The license client will fail to lease the licenses from the server with an error message:

System()[] - License Server Protocol Error: Code=(0x32) Error="Stale Lease Id"

The following messages will appear inthe event log snippet from the License Server: 

Major LIC30528 System()[] - License server low-level protocol error, check server configuration 
Major LIC30523 System()[] - License Server Protocol Error: Code=(0x20) Error="Machine Id Mismatch" 
Minor LIC30581 System()[] - Client has not registered with the server. This client will try to register again. 
Major LIC30523 System()[] - License Server Protocol Error: Code=(0x25) Error="Client Not Registered"

 This issue occurs when one of the following conditions are true:

1. If the lease id does not match either the stored lease id or the interim lease id
2. If the lease id in the ACK is 0 or the lease id is not the same as the expected lease id (the interim id stored in the server for this client)

Starting with 8.2R9 / 8.3R3 and above, a new option to reset lease ID was add to the license server admin console. This option helps in renegotiating the lease ID between license server and client.

1. Login to the license server
2. Navigate to System > Configuration > Licensing > Configure Clients
3. Under list of license clients, select the checkbox for license client
4. Click Reset LeaseID

Workaround in versions prior to 8.2R9 and 8.3R3 :

• Delete the existing license server/client configuration and add the license client back to the license server.

If the problem continues to occur, please open a support case with the following logs from the license server and the affected License Client.

System snapshot with debug log enabled while replicating the issue.  (See below for debug log settings.)

• PCS device logs: (Event, User and Admin Access logs)

Please follow the steps below to gather the required logs:

1. Navigate to Troubleshooting > Tools > Licensing Protocol Trace
2. Click Start Trace
3. Navigate to Troubleshooting > Monitoring > Debug Logging

• Set the Max Debug log size to 50
• Set the Debug lLog level to 10
• Enter the following Event Codes: pbLogHandler, ClientMessageHandler

4. Leave the above logging running long enough to replicate the issue.  Once the license client fails to lease the license from the server with the error "License server protocol error- code(0x32)", follow the below steps to gather the logs.
5. Navigate to Troubleshooting > System Snapshot
6. At the bottom of the page, select the checkbox to Include Debug Log.
7. Click Take Snapshot to take the system snapshot and wait for the file to be generated before browsing away from the page. 
8. Download the system snapshot from the device. 
9. Navigate to Troubleshooting > Monitoring > Debug Logging and disable debug logging and Save Changes. 
10. Navigate to Log / Monitoring > Event Log.
11. Click to Save All Logs.
12. Attach the System Snapshot and device logs to the case.