Transaction Time-Out can be caused while import of a
large XML or when doing check-in on e.g. study.
This is a problem with the communication between client app (PD or PS) and server (eMServer).
It is not related to the Oracle DB.
It states that the COM transaction was aborted.
Solution
This is mostly caused by timeout value is configured to '60' seconds instead of '0' . To solve 2 steps are recommended:
First:
Refresh / Analyze-Schema:
To refresh the schema: From the Schema Administration->Software Deployment form, click the Refresh Schema button!
https://docs.plm.automation.siemens.com/tdoc/tecnomatix/15.1/tecnomatix_eMS#uid:xid1019415
To analyze the schema: Select the Schema Administration->Schema Actions node, click the Analyze Schema button!
https://docs.plm.automation.siemens.com/tdoc/tecnomatix/15.1/tecnomatix_eMS#uid:xid1019421
Second: The trigger for this message is an MTS transaction default timeout of 60 seconds. You can cancel this timeout by doing the following:
In MTS Explorer, right-click My Computer -> Properties -> Options tab.
Change the transaction timeout value to 0 , as shown in the figure below:
https://docs.plm.automation.siemens.com/tdoc/tecnomatix/15.1/tecnomatix_eMS#uid:xid1064520
Hardware/Software Configuration
Platform: na
OS: windows
OS Version: n/a
Product: TECNOMATIX
Application: EM-SERVER
Version: V_UNKNOWN
Function: EM-SERVER
Ref: 002-8016887