Community Tip - Want the oppurtunity to discuss enhancements to PTC products? Join a working group! X
Version: Windchill 13.0
Use Case: This User clicks on the PDF or attachment in Windchill, it downloads a file, for a moment it looks like its about to open/preview a PDF in his browser, then this error shows in the browser window: Windchill Error Contact your administrator for assistance. Information for their reference follows. Status: 500 Code: Message: The signature from "https://windchill.alkath.group/servlet/WindchillGW ", signed at "Tue Sep 02 03:37:17 GMT 2025", received at "Tue Sep 02 03:37:18 GMT 2025", is already used. Please retry the operation. If the error persists please contact the system administrator. Current Time: 2025-09-02 13:37:18.617 +1000
Description:
This User clicks on the PDF or attachment in Windchill, it downloads a file, for a moment it looks like its about to open/preview a PDF in his browser, then this error shows in the browser window:
Windchill Error
Contact your administrator for assistance. Information for their reference follows.
Status: 500
Code:
Message: The signature from "https://windchill.alkath.group/servlet/WindchillGW
", signed at "Tue Sep 02 03:37:17 GMT 2025", received at "Tue Sep 02 03:37:18 GMT 2025", is already used. Please retry the operation. If the error persists please contact the system administrator.
Current Time: 2025-09-02 13:37:18.617 +1000
Solved! Go to Solution.
We've seen this recent updates to Adobe, Chrome and Microsoft. Cannot remember which one it was but basically, the browser has lots of options on how to handle PDFs. It sometimes is setup to open in the browser or hand off to another application to render. Basically, what is happening is it sends two requests (replay) to the webserver for the PDF and rightly, the browser objects to the second request using the same signature (is this a replay attack its detectecting?). This solved the users issues: https://www.ptc.com/en/support/article/CS375347?source=search
There may be several reasons for this.
Below is the result of research from the PTC support KB.
We've seen this recent updates to Adobe, Chrome and Microsoft. Cannot remember which one it was but basically, the browser has lots of options on how to handle PDFs. It sometimes is setup to open in the browser or hand off to another application to render. Basically, what is happening is it sends two requests (replay) to the webserver for the PDF and rightly, the browser objects to the second request using the same signature (is this a replay attack its detectecting?). This solved the users issues: https://www.ptc.com/en/support/article/CS375347?source=search
Thank you for your reply. Yes! The user had an Adobe PDF plugin installed on his Chrome Browser. Removing that extension fixed the issue!