Skip to main content
K
KevinT1-Visitor
1-Visitor
November 7, 2018
Question

Default thingmarks on new server not being recognized

  • November 7, 2018
  • 1 reply
  • 2285 views

I am in the process of updating all of my projects to a default experience new server. But when I associate any of the 3 default thingmarks to a project and publish, I then scan the thingmark inside of PTC view and get an error saying no experiences found.

 

I already checked and validated that my project is assigned to the new experience server.

1 reply

T
tmccombie21-Topaz I
21-Topaz I
November 8, 2018

The ThingMarks shown in the 'My ThingMarks' section are specific to your trial Experience Service. If you are transitioning to a new commercial Experience Service, these ThingMarks will not work, as they will point your device to your old trial ES. If you have a Cloud hosted Experience Service, you or your team should have received 100 ThingMarks for each instance (dev & prod). If you are using an On-Premises instance of the Experience Service, please open a support ticket requesting ThingMarks if you have not done so yet.

 

These ThingMarks should be used with your new server. You can manually enter the ThingMark ID into Studio. The format is <domain ID>:<instance ID>.

K
KevinT1-VisitorAuthor
1-Visitor
November 8, 2018

Thank you. What are the steps involved in opening up a support ticket for thingmarks?

T
tmccombie21-Topaz I
21-Topaz I
November 9, 2018

Go to support.ptc.com, select 'Open a Support Case' and Vuforia Studio as the product. Please be sure to include your On-Premises Experience Service URL, the number of ThingMarks needed, and whether or not you'd like to have your ES registered in the GXI. 

 

More information on the GXI can be found in Chapter 2 (Plan your deployment) of the Experience Service Deployment Guide here: https://www.ptc.com/support/-/media/907F7AA5CA194DDBB26466D48F608ADE.pdf?sc_lang=en 

 

I can also open a case on your behalf. Please DM me with the required information if you'd like me to do this. 

Terms & ConditionsCookie settingsAccessibility statement