Article - CS162756
Creo View Adapters : Configuring Creo Workers to Automatically Clean Up Residual Creo Parametric Processes During Helper Restarts in Multi-Worker Environments to Minimize 'Failed to Start' Errors
Modified: 29-Aug-2025
Applies To
- Creo View Adapters 3.0 M010 to 12.1
- Windchill PDMLink 10.0 to 13.1
- Creo Parametric 1.0 to 11.0
Description
- How to fix problems with the Creo View Adapters Worker failure to restart due to residual processes
- If the worker's Creo Parametric session hangs during publishing and does not exit when the Helper process attempts to stop / kill the worker, subsequent attempts to start the worker will fail with a Failed to register... error
- A common message sequence is similar to the one below:
- Registering Server : proe2pv Error:56113: Failed to register Windchill server "http://<windchill_url>" "publish9055191759723715316tmp" - -33
- The adapter has been configured to restart after the current job when this error occurs
- proe2pv Error:13027: Cannot restart adapter, helper returned "Adapter already restarted once"
- Note:
- The error return codes may vary, although this will most commonly occur with Failed to register... messages
- For example, Failed to register... messages ending in Creo/TOOLKIT error code -4 are also common
- This approach is also useful for cleaning up after issues preventing automatic clean-up of the Common File System folders:
- For example, the following WVS Background Method Server exception results in content being left behind:
ERROR [Thread-21477 ProcessMessages] wt.wvs.workeragent.Worker - 550 The process cannot access the file because it is being used by another process.
java.io.FileNotFoundException: 550 The process cannot access the file because it is being used by another process.
at com.ptc.wvs.server.util.FTP.rm(FTP.java:975)
at com.ptc.wvs.server.util.FTP.doRmAll(FTP.java:934)
at com.ptc.wvs.server.util.FTP.rmall(FTP.java:892)
at com.ptc.wvs.server.cadagent.Worker.deleteAllTrash(Worker.java:1514)
at com.ptc.wvs.server.cadagent.ProcessMessages.copyFilesOnDone(ProcessMessages.java:368)
at com.ptc.wvs.server.cadagent.ProcessMessages.run(ProcessMessages.java:232)
- For example, the following WVS Background Method Server exception results in content being left behind:
This is a printer-friendly version of Article 162756 and may be out of date. For the latest version click CS162756