Skip to main content
E
ErikZabokrtsky12-Amethyst
12-Amethyst
June 13, 2023
Solved

CAD Worker Fails to Start, no worker.log

  • June 13, 2023
  • 1 reply
  • 4141 views

I have one CAD worker running a machine separate to the Windchill server and have had no issues with it. I wanted to create another temporary one, also on a separate machine, to run for a while as we are putting a lot of new files onto the server that need representations created. I cannot figure out what is causing my issue of Fails to Start.

 

I have gone through multiple times and checked that everything is setup the same on the temp worker as it is on the production worker. I even removed the production worker and tried just the temp, to see if there was a conflict between them. Temp still threw the error so I recreated the production worker in "Worker Agent Administration" and it connected perfectly and started working on jobs right away.

 

Every post I have found keeps pointing back to looking at logs on the worker machine, but there are none being created. Where else are there logs on the server that possibly could point to what I have wrong? Permission wise, I have Everyone with Full Control to the "Creoview_Temp" shared folder for jobs to be transferred to.

Best answer by avillanueva

Make sure you did this on your temp cad worker:

https://support.ptc.com/help/creo/view/r7.0/en/index.html#page/creo_view/adapter_install_config_guide/Introduction_Installation/Worker_Daemon_2.html

it should be running automatic. This is what the CAD Agent on the Windchill side communicates with to start up the CAD worker. Port 601 is the default.

1 reply

avillanueva
23-Emerald I
avillanueva23-Emerald I
23-Emerald I
June 13, 2023

If no logs are being generated, its not being triggered to run. You can manually start the worker by clicking on the batch file from the worker end. That can verify in the CAD Agent that the back end is working allowing you to verify part of the execution chain. I wonder if you need to adjust the wvs.properties and edit the worker.exe.whitelist.prefixes property. Perhaps you did not allow the new folder location to be executed.

E
ErikZabokrtsky12-AmethystAuthor
12-Amethyst
June 13, 2023

When I look in the wvs.properties file, I don't see anything specifying a certain machine name as allowed the property you mentioned is set to "worker.exe.whitelist.prefixes=C\:". 

 

The production worker is "eng-vis-worker" and the temp is "eng-vis-temp2", but beyond that the file path is identical.

avillanueva
23-Emerald I
avillanueva23-Emerald I
23-Emerald I
June 13, 2023

That prefix just means that you executable must exist on c:\. I see that you are on different machine.  Did you configure the worker daemon service to listen on the port defined in the agent administration? Started? Sry for basic question.  How about manually starting cad worker from the cad worker machine? Did the agent see it come online?

Terms & ConditionsCookie settingsAccessibility statement