Article - CS322265
"Selection Context" table hangs and then displays "Internal Server Error" on the "Add Traces" dialog when using Digital Product Traceability (DPT) between Windchill RV&S or Codebeamer and Windchill PDMLnk
Modified: 14-Jul-2025
Applies To
- Windchill PDMLink 11.2.1.0 to 13.1
- ThingWorx Platform 8.5 SP1 to 9.3
- Codebeamer 22.10 22.10 SP3 to 2.2
- PTC RV&S (formerly Integrity Lifecycle Manager) 12.3 to 13.1
Description
- Selection Dialog Context (renamed to Select Context) table does not stop loading in Windchill
- Selection Context table does not load properly in the Add Traces dialog
- Cannot configure Windchill PDMLink to trace to a Codebeamer Requirement
- Can't list Codebeamer Context information when trying to Add Trace
- Cannot get the Windchill RV&S Projects to load in the Add Traces dialog
- F12/Dev Tools Network tab of client browser shows the following request failure:
- Request Endpoint
- https://<ThingWorx Host>/Thingworx/Things/OslcDataServicesThing/GetServiceProviderHierarchy
- Response Code
- 500
- Response
- Unable to decrypt text due to error
- Request Endpoint
- Client web browser shows the following when hovering over the red exclamation point on the Select Context table in the Add Traces dialog
-
Internal Server Error. Contact your Administrator.
-
- <ThingworxStorage>\logs\ApplicationLog.log shows any one of the following messages:
-
[L: ERROR] [O: c.p.t.r.p.GetHeirarchyProviderProcessor] [I: ] [U: <User>] [S: ] [P: ] [T: https-jsse-nio-8443-exec-7] Executing flow getHeirarchyFlowData timed out [L: ERROR] [O: c.t.w.Things] [I: ] [U: <User>] [S: ] [P: ] [T: https-jsse-nio-8443-exec-7] Unable to Invoke Service GetServiceProviderHeirarchy on OslcDataServicesThing : Request Timed Out._ [L: ERROR] [O: c.t.w.Things] [I: ] [U: <User>] [S: ] [P: ] [T: https-jsse-nio-8443-exec-7] Unable to Invoke Service GetServiceProviderHeirarchy on OslcDataServicesThing : Unable to decrypt text due to error
-
- ThingWorx Flow NGINX <NGINX Install>\logs\error.log shows the following:
-
[error] : *45 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while reading response header from upstream, client: <Client IP Address>, server: <ThingWorx Flow Host>, request: "GET /Thingworx/Flow/triggers HTTP/1.1", upstream: "http://127.0.0.1:8003/triggers", host: "<ThingWorx Flow Host>", referrer: "https://<ThingWorx Platform> /Thingworx/Composer/apps/flow/"
-
- Select Context (formerly Selection Dialog Context) table keeps loading in Add Traces page

- Selection Context shows nothing with error Internal Server Error: Contact your Administrator. in Add Traces page and MethodServer reports following error:
-
ERROR [ajp-nio-127.0.0.1-8010-exec-6] wt.servlet.ServletRequestMonitor.request wcadmin - 2020-03-16 07:43:12.980 +0000, q3l0cxl;k7tsvsms;7656;pjzwgy;22630, wcadmin, 10.192.4.176, /Windchill/netmarkets/jsp/util/getBundleKey.jsp, key=com.ptc.core.ui.remoteMessagesRB._408_level, GET, 503, 0.0, 0.0016594
-

This is a printer-friendly version of Article 322265 and may be out of date. For the latest version click CS322265