Teamcenter 12 rich client crashes with PDF xChange 10.7.0-398

[rjw1014]

We (SLAC National Lab) have been using PDF Xchange Pro as a standard PDF editor for many years and this application is a default app made available and installed on all users' computers at SLAC , and also configured as the default in our Teamcenter 12 PLM application. It seems that something has changed in version 10.7.0 -398 which is now causing the Teamcenter 12 application to crash and exit if a .PDF dataset (File) is selected in the Rich Client (Teamcenter 12 GUI) and the VIEWER tab is enabled in Tc 12.

This issue is present with both 10.7.0-398 as well as 10.7.1-399 installed, but when we revert back to the previous version 10.6.1-397, we do not see any issues and the Teamcenter VIEWER is able to display the .PDF image directly within the Rich Client for Teamcenter 12 and we see no issues.

We are not sure if this is an issue with the updated PLUG-IN for Teamcenter or if a registry setting is being updated that causes the issue, but we need to have this resolved so we can use the latest version and be required to revert back to a previous version (10.6.1-397).

We are happy to trouble shoot in any way that might help resolve the issue.

Thanks

Richard J. Wilson

[Daniel - PDF-XChange]

Hello, rjw1014

I cannot be 100% certain if this is the same issue because of your environment, however, 10.7 and 10.7.1 both have a known issue which matches the majority of what you report here.

This is caused by an improperly installed (or missing) copy of the latest VCRedist from microsoft.
You can advise anyone experiencing this issue to please download and install the VC Redistributable pack from Microsoft's site: https://learn.microsoft.com/en-us/cpp/w ... w=msvc-170
Which should fix the issue in the meantime.

This should be resolved in the next release, as we plan to include any required VCredist installers in our installation files going forward.

Kind regards,

[rjw1014]

Dear Tracker Software,

The same issue with Teamcenter 12 crashing when trying to view a PDF, that I reported back on Aug 27th, 2025 is now back in both the 10.8.1.406 version of PDF-Xchange Pro as well as in the lasted update 10.8.2.407.

The issue was fixed in the 10.7.6.404 version and we can roll back to this version as a temporary fix, but we have hundreds of users that rely on PDF XChange Pro with Teamcenter 12 and this is a major issue for us at the moment.

Can you please let us (Teamcenter Admin at SLAC) know when this issue has been resolved and we can download a version of the application for testing

regards

Richard J. Wilson
rjw1014@slac.stanford.edu

[Daniel - PDF-XChange]

Hello, rjw1014

Thank you for the followup report. I was under the impression that the issue had been resolved with the VCRedist intaller that I mentioned last time, due to your radio silence on the topic this far. If you have not already done so, please do try installing that VCredist again ant let me know if it helps at all.

If the error does persist into 10.8.2, we will need to see the generated Crash dumps from one of the affected systems.

These should be automatically generated during a crash event, so please open the file explorer to:
%localappdata%\Crashdumps
Then locate any with PDF in the name. Please upload the most recent ones here: https://files.pdf-xchange.com/s/CgwSyKFmYYo7TPb
Then let me know as soon as the upload is complete - so I can pass it on to the Dev team for review.

Kind regards,

[rjw1014]

Daniel,

I have added a dmp file to the location you provided, and this is the error we get when the Teamcenter 12 application crashes, when attempting to VIEW a .PDF file in the built in VIEWER tab in Teamcenter 12.

image.png

Based on you r suggestion in a previous port, I loaded and installed the https://aka.ms/vc14/vc_redist.x64.exe. on the same computer that has Teamcenter 12 and PDF XChange Pro 10.8.2.407 and it is still producing the same error (no change). and it causes the Teamcenter 12 Rich-Client to crash. In Fact, it will even crash the Teamcenter 12 application when a user tried to double click on a file and open that specific file into the default Windows application configured for .pdf file extensions. (By the way, this does not happen when Adobe Acrobat is configured as the default)

I'm not sure what has changed, but in early Sept 2025 we began using the PDF XChange Pro version 10.7.6.404 and we had no issues, so whatever was done in that version to package the update and push it out, is no longer in the latest 10.8.2.407.

TC12_PDF_XChange Pro error.pdf

Please get back to me as soon as possible, as we have hundreds of Teamcenter/PDF XChange Pro users at SLAC that are experiencing this issue and we need to find a solution ASAP.

Thanks

[Daniel - PDF-XChange]

Hello, rjw1014

Thank you again. I have forwarded these to the dev team with urgency - we will be back as soon as their investigation is complete.

Kind regards,

[Roman - Tracker Supp]

Hello, rjw1014,

The problem is caused by the incompatible version of MSVCRT your product uses. As an immediate workaround you can disable PDF-XChange AzureRMS plugin. In the next maintenance release (10.8.3) we will add a workaround to gracefully fail that plugin when such a problem occurs.
Alternatively, consider using the same (or newer) MSVCRT as the PDF-XChange Editor does (our MSVCRT binaries are located at "%CommonProgramFiles%\Tracker Software\Common\MSVCRT").

[rjw1014]

Daniel,

Just wanted to let you know that we tried your suggestion and disabled the PDF-XChange AzureRMS plugin in version 10.8.2.407 and then tried to open a .PDF file from Teamcenter into the PDF XChange application and it does open the selected .PDF file in the application, but it still crashes the Teamcenter 12 application with the same "Teamcenter _ Java"
error that I provided in an earlier post.

[Roman - Tracker Supp]

Hello rjw1014,
Please ask the user to delete "c:\Program Files\Tracker Software\PDF Editor\Plugins.x64\AzureRMS.pvp" and "c:\Program Files\Tracker Software\PDF Editor\Plugins.x86\AzureRMS.pvp" files.
Assuming they do not need to work with documents protected by Azure RMS.
They might want to backup the files just in case.