1. Home
  2. Support
Article - CS321993

"Unable to connect to the server." is seen when attempting to launch the "Add Traces" dialog using OSLC Digital Product Traceability (DPT) between Windchill RV&S (formerly Integrity Lifecycle Manager) and Windchill PDMLink

Modified: 02-Mar-2023   


Applies To

  • Windchill PDMLink 11.2.1.0 to 12.1
  • ThingWorx Platform 8.5 SP1 to 9.3
  • PTC RV&S (formerly Integrity Lifecycle Manager) 12.3.0.0 to 13.1

Description

  • Attempting to add a Trace between Windchill PDMLink and Windchill RV&S (Integrity Lifecycle Manager) results in an error
  • Cannot add Traces between Windchill systems using Digital Product Traceability (DPT)
  • DPT is not working when trying to add a Trace in Windchill PDMLink
  • Windchill PDMLink shows the following error in the UI when attempting to add a DPT Trace, no errors are logged in any system:
    • Unable to connect to the server.
  • The following is seen within F12/Developer Tools > Network tab in the web browser when opening the Add Traces dialog
    • Access to XMLHttpRequest at https://<ThingWorx Host>:<ThingWorx Port>/Thingworx/OslcDataServicesThing/services/... No from origin https://<Windchill Host> has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource.
      POST https://<ThingWorx Host>:<ThingWorx Port>/Thingworx/OslcDataServicesThing/services/GetServerResourceDetails net::ERR_FAILED
  • ThingWorx Platform logs within <ThingworxStorage>\logs show the following after opening the Add Traces dialog:
    • ApplicationLog.log
      • [L: ERROR] [O: c.t.s.s.f.FlowUtilities] [I: ] [U: SuperUser] [S: ] [P: ] [T: pool-16-thread-1] Invalid URL: no protocol:
        [L: WARN] [O: c.t.s.s.f.FlowMetricHelper] [I: ] [U: SuperUser] [S: ] [P: ] [T: pool-16-thread-1] Exception while fetching count of executed PTC.DPT workflows triggers per connector: Failed to get metric data for Flow.Connector-ExecutedActionsCount : Invalid URL
    • ErrorLog.log
      • [L: ERROR] [O: E.c.q.l.c.Logger] [I: ] [U: SuperUser] [S: ] [P: ] [T: pool-16-thread-1] Invalid URL: no protocol:  java.net.MalformedURLException: no protocol:
            at java.net.URL.<init>(Unknown Source)
            at java.net.URL.<init>(Unknown Source)
            at java.net.URL.<init>(Unknown Source)
            at com.thingworx.system.subsystems.flow.FlowUtilities.validateUrl(FlowUtilities.java:253)
            at com.thingworx.system.subsystems.flow.FlowUtilities.buildFlowServiceURL(FlowUtilities.java:223)
  • ThingWorx Flow's RabbitMQ.log file is showing the following:
    • =ERROR REPORT==== <timestamp> ===
      connection <0.317.0>, channel 1 - soft error:{amqp_error,not_found,""no queue 'flow-exec-reply-<Reply ID>' in vhost 'orchestration'"",'queue.declare'}"
This is a printer-friendly version of Article 321993 and may be out of date. For the latest version click CS321993