Article - CS59132
How to troubleshoot ProEngineerStart() & ProEngineerConnect() failures on Windows platform for Creo Parametric
Modified: 26-Oct-2020
Applies To
- Pro/ENGINEER and Creo Elements/Pro Wildfire to Wildfire 5.0
- Creo Parametric 1.0 to 8.0
Description
- How to troubleshoot ProEngineerStart() & ProEngineerConnect() failures on Windows platform for Creo Parametric
- ProEngineerStart() works fine. But, ProEngineerConnect() always fails on a specific machine.
- pfcAsyncConnection.AsyncConnection_Start() works fine. But, pfcAsyncConnection.AsyncConnection_Connect() always fails on a specific machine.
- CCpfcAsyncConnection.Start() works fine. But, CCpfcAsyncConnection.Connect() always fails on a specific machine.
- Error PRO_TK_GENERAL_ERROR / PRO_TK_E_NOT_FOUND or XToolkitGeneralError / XToolkitNotFound returned while attempting to Start a new Creo session or connect to an existing session through asynchronous Creo Parametric Toolkit / JLink / VB API applications.
- ProEngineerConnect() API returns PRO_TK_E_BUSY error.
This is a printer-friendly version of Article 59132 and may be out of date. For the latest version click CS59132