Hello Hesam,
Thank you for bringing this to our attention, and sorry for the inconvenience. We identified a license issue as the cause of the error, and we are working right now on a fix.
As a temporary workaround, you can resolve the issue yourself while we work to update the VM with a permanent fix:
Task 1: Update application keys expiration dates
- Open the Chrome web browser and click the Thingworx bookmark.
- Sign in with credentials:
- Username: Administrator
- Password: ptc-university-123
- Click the Search Entities icon at the top of the left toolbar.
- Type es then select the es-public-access application key entity.
Note: Choose the application key entity and not the organization or user entities. - In the General Information tab of the newly opened application key, locate the Expiration Date field.
- Update the expiration date to tomorrow's date.
- Save the changes.
- Repeat steps 3-7 but for the es-authorization application key entity.
Task 2: Restart Tomcat
- Close all Chrome web browser tabs.
- Open Windows Services by searching for services from the start menu.
- Right-click the Apache Tomcat service then select restart.
- After Tomcat has restarted, sign in to Thingworx as the Administrator user.
- Verify the es-public-access and es-authorization application keys expiration dates are in the future.
We will update this thread when the VM has been updated with the permanent fix.
Cheers.
