Shop floor device registration fails with license error when adding new terminal for time tracking

ERP Microsoft Dynamics 365
, , , , , , , ,
1

We’re trying to register a new shop floor device for employee time tracking in our production area, but the registration fails with a license error. The terminal shows “Device license not available” even though we have purchased additional device licenses through LCS.

The error appears during the device registration process:


Error: DEVICE_LICENSE_UNAVAILABLE
Device registration failed: No available device licenses
Check LCS portal for license allocation

I’ve verified in LCS Admin Center that we have 15 device licenses purchased, and only 12 are currently assigned. The license refresh was performed yesterday, but the new terminal still can’t register. This is blocking our expansion to a new production line where employees need to clock in/out. Has anyone encountered this license assignment issue after adding new device licenses?

2

This might be a service update timing issue. If you’re on 10.0.41, there was a known issue with device license validation in the March release. Microsoft released a hotfix (KB5043821) that addresses device registration failures after license additions. The fix corrects the license cache refresh mechanism. You should apply this hotfix and then restart the AOS service to clear any cached license states.

3

I had this exact issue last month. The problem is usually a mismatch between the device license assignment in LCS and the actual device activation in D365. Here’s what worked for me - check all three areas systematically.

First, verify the LCS license refresh actually completed. In LCS Admin Center, go to License allocation and confirm your device licenses show the correct count (15 in your case). Click on Device licenses to see the detailed allocation - make sure they’re assigned to your production environment specifically, not sandbox.

Second, force the terminal registration process to recognize the new licenses. The key is rebuilding the license cache:

<Configuration>
  <LicenseRefresh forceSync="true" clearCache="true"/>
  <DeviceActivation validateLicense="true"/>
</Configuration>

In D365, go to System administration > Periodic tasks > License synchronization and run it with the “Force full synchronization” option checked. This clears the cached license state and pulls fresh data from LCS. Wait 15 minutes after this completes.

Third, address the terminal registration process itself. Go to Production control > Setup > Manufacturing execution > Configure job card for devices. Find your new terminal in the list (it might show as “Pending” status). Delete any existing registration attempts for this device ID. Then on the actual shop floor terminal, clear the device configuration by holding the reset button for 10 seconds, and start the registration wizard fresh.

The critical step is ensuring the device ID being registered matches exactly what’s expected in the device configuration table. If the terminal auto-generated a device ID that doesn’t align with your naming convention, the license validator won’t find it. You may need to manually create the device record in D365 first with the exact device ID, assign it to a worker, then register the physical terminal using that same ID.

Also verify your worker records have the “Allow time registration” checkbox enabled in Human resources > Workers > Time registration. Without this flag, the device registration will fail license validation even if licenses are available.

After following these steps, the new terminal should register successfully. The root cause is usually the license cache not updating after LCS changes, combined with device ID mismatches during first-time registration. Let me know if you need more details on any of these steps.

4

Check the device activation status in the database. Sometimes the device record gets created but stuck in a pending state. You can query the JmgTerminalTable to see if there’s already a record for your new terminal with an incorrect status. If the terminal ID already exists with status other than “Active”, you’ll need to either delete that record or update its status. Also verify in LCS that the device license allocation shows the correct environment - I’ve seen cases where licenses were assigned to the wrong environment slot.

5

Also verify that the device registration is using the correct configuration. In Production control > Setup > Manufacturing execution > Configure job card for devices, make sure the device group has the proper authentication settings. Sometimes the license check fails if the device configuration references an old or inactive worker ID. The terminal needs to be associated with a valid worker record before license validation occurs.