![]() ![]() Your issue sounds like one of two possibilities: So this is why starting it manually would allow publishing to work. The workermonitor.exe process then "lives" forever unless you kill it the the Worker Agent Administration dialog or from the cadworker machine's task manager or you restart Windchill. The workermonitor.exe process is what Windchill uses to start/end the Creo Parametric session. Has anyone seen this issue with the system not fully starting automatically? When I had the issue earlier, PTC tech support could not find a solution so I closed the call hoping WC 11 and the new adapter would allow the startup to work.īasically all proeworker.bat does is to start a workermonitor.exe process. Once started publishing runs fine for that day. I have to log into the publishing machine and start proeworker.bat every day. ![]() The proeworker will not start automatically. The WorkerDaemon starts on the publishing machine at startup from the GS Worker service. I have upgraded to Windchill 11.0 m030 and installed CreoView Adapters 4.1 F000. Continuation of same problem but different versions!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |