Skip to main content
18-Opal
April 25, 2025
Solved

License is not available for Product: TWX_PLATFORM Feature: twx_named_user

  • April 25, 2025
  • 2 replies
  • 906 views

Hi, 

 

When trying to create a user in Thingworx, the following error is showing up on the screen:

"License is not available for Product: TWX_PLATFORM Feature: twx_named_user"

pshashipreetham_4-1745580846025.jpeg

I tried out the PTC Knowledge Centre but didn't find any solution. Why is it occurring?

 


Thingworx Version: 9.7.0-b47

 

Thanks,

Best answer by pshashipreetham

Hi @slangley ,

 

Thanks for the response. Followed the same as per your suggestion. During the last time, it looks like I made a mistake. When we were using the old License Portal, we just added the device ID and got the license file, but as per the latest License Portal, we needed to select the products that would be part of the license. I missed selecting the 'Thingworx User,' which caused this issue during product selection.

 

When I created a new license file with the 'Thingworx User' product selected in the latest License Management Portal and tried to create a new user in the Thingworx Composer, the error vanished, and users are being made now.

 

Thanks,

2 replies

Rocko
19-Tanzanite
April 25, 2025

This is a problem statement. What is your specific question?

 

You can check your available licenses in the licensing subsystem.

This will list which licenses are available. They might be expired.

 

Community Manager
April 30, 2025

Hi @pshashipreetham 

 

Unfortunately, it's somewhat difficult to determine which part numbers in the License Mgmt tool contains the features required for ThingWorx.  There are a number of things to be aware of:

 

  • If you know the Sales Order number related to your specific implementation (many of our customers have multiple business units resulting in multiple contracts), you can filter on this number and then select all the ThingWorx-related items for generating the license.
    • When selecting the counts, you will need to be sure you enter only the number that should be allocated for the given host--if generating a Production license.
    • When generating a non-production license, you can select all counts. 
  • Your contract allows you to have as many non-production servers as needed.
  • If you are generating Production licenses, you need to be aware of the number of production servers your contract allows for as well as the allocations for those servers.  If you over-allocate, you will be unable to generate Production licenses for the remaining servers.
  • It is not a requirement to generate a Production license for a production server.  However, you need to ensure you do not violate the terms of the contract.  Note that when using Connected mode, the license is generated as non-production.  

Please let us know if you continue to have issues and I can open a case to walk you through the process.

 

Regards.

 

--Sharon

pshashipreetham18-OpalAuthorAnswer
18-Opal
May 1, 2025

Hi @slangley ,

 

Thanks for the response. Followed the same as per your suggestion. During the last time, it looks like I made a mistake. When we were using the old License Portal, we just added the device ID and got the license file, but as per the latest License Portal, we needed to select the products that would be part of the license. I missed selecting the 'Thingworx User,' which caused this issue during product selection.

 

When I created a new license file with the 'Thingworx User' product selected in the latest License Management Portal and tried to create a new user in the Thingworx Composer, the error vanished, and users are being made now.

 

Thanks,

Community Manager
May 1, 2025

Hi @pshashipreetham 

 

Glad to hear you resolved it.

 

Before generating a new license, I recommend taking a screenshot of the existing licensing features in Composer (Monitoring > Subsystems > LicensingSubsystemSettings), and then do a comparison once the new license is installed to confirm that no features are missing.

 

Please feel free to mark your last post as the Accepted Solution for the benefit of others in the community.

 

Regards.

 

--Sharon