|
Problem
|
Solution
|
|
Unable to connect to server when creating traces using Add Traces
|
• Verify that ThingWorx is up and running.
• Make sure that appropriate values are set for the Windchill properties. For more information, see the section related to Windchill properties in System Compatibility and Requirements.
• Make sure that the Windchill server is added in CORS setting of ThingWorx server.
|
|
Not Authorized error is returned when creating traces using Add Traces
|
• Make sure correct user permissions are set in ThingWorx. For more information, see Permissions for ThingWorx Platform Entities
Enable the following ThingWorx application loggers:
◦ c.p.t.d.OslcDataServices
◦ c.p.t.r.p.OslcResourceProviderProcessor
◦ c.p.t.r.ProcessorHelper
|
|
Server or Resource value is not displayed in the Add Traces window
|
• Make sure that appropriate values are specified for the specific configuration reference Thing in ThingWorx. For more information, see Configuring the DPT Extension.
• Make sure valid relationship constraints are specified for DPT trace links in WindchillType and Attribute Management. For more information, see System Compatibility and Requirements.
|
|
Data loading in Selection Dialog Context fails in Windchill
|
• Enable the following ThingWorx application loggers:
◦ c.p.t.d.OslcDataServices
◦ c.p.t.r.p.GetHeirarchyProviderProcessor
◦ c.p.t.r.p.ResourceProviderProcessor
|
|
Fetching of remote information for remote column in Windchill fails
|
• Make sure ThingWorx service has passed
• Enable the following ThingWorx application loggers:
◦ c.p.t.d.OslcDataServices
◦ c.p.t.r.p.ResourceProviderProcessor
◦ c.p.t.r.ProcessorHelper
◦ c.p.t.u.TraceLinksUtil
• Enable the following Windchill logger:
◦ com.ptc.mvc.components
|
|
Loading of small preview and OSLC delegated dialog fails
|
Make sure Windchill server is added to whitelist inWindchill RV&S, Windchill Modeler, and IBM Rational Doors NG OSLC servers.
|
|
Creation of invalid resource
|
• Enable the following ThingWorx application logger:
◦ c.p.t.r.p.ResourceProviderProcessor
◦ c.p.t.r.p.ResourceValidator
◦ c.p.t.r.p.ResourceBuilder
◦ c.p.t.v.OslcValidationServices
• Make sure that the validation flow thing is correctly tagged.
• Make sure that the appropriate validation flow thing is invoked.
• Make sure that a valid Terms value exists for the external OSLC server.
• Make sure the correct Tag value is specified in the OSLCServerMappingConfigTable of the external OSLC server.
• Make sure that the customized validation flow thing is working correctly using the following test validation flow service ValidateOslcFlow.The ValidateOslcFlowservice is located in the OslcValidationServicesThing.
|
|
Creation of valid resource fails with the error One or more of the selected resources are not of resource type {0}. Make a valid selection and try again.
|
• Enable the following ThingWorx application loggers:
◦ c.p.t.r.p.ResourceProviderProcessor
◦ c.p.t.r.p.ResourceValidator
◦ c.p.t.r.p.ResourceBuilder
◦ c.p.t.v.OslcValidationServices
• Make sure that the validation flow thing is correctly tagged.
• Make sure that the appropriate validation flow thing is invoked.
• Make sure that a valid Terms value exists for the external OSLC server.
• Make sure the correct Tag value is specified in the OSLCServerMappingConfigTable of the external OSLC server.
• Make sure that the customized validation flow thing is working correctly using the following test validation flow service ValidateOslcFlow.The ValidateOslcFlowservice is located in the OslcValidationServicesThing.
|