Skip to main content
7-Bedrock
January 15, 2025
Solved

Cad worker issues

  • January 15, 2025
  • 1 reply
  • 1255 views
I am using Windchill PDMLink Release 12.0 and Datecode with CPS 12.0.2.2

Windchill server and creo cad worker server both are installed separately in AWS EC2. Firewall in cad worker is on and enabled only the inbound ports "20-21, 80, 443, 137-139, 445, 601". With this I can telnet 601 from Windchill server and 5600 from cad worker without any issues. But still the cad worker is not getting turn on while hitting the Start workers in Windchill. Is there any other port need to be enabled ? PL. confirm
    Best answer by avillanueva

    Walk the process. From the Windchill server, it should try to contact the worker daemon service on port 601 (typically). Is that running and responding? From there the worker daemon will issue the shortcut command to the batch file to start the worker. There should be evidence that it was executed and some log files there. The worker process will start and connect to the Windchill server on port 5600 (typically). Somewhere along the line its broken. Triple check your agent.ini file for typos. Also check that your whitelist setting in the wvs.properties is allowing those paths to the batch file to start. Let is know what you find.  

    1 reply

    avillanueva
    23-Emerald I
    23-Emerald I
    January 15, 2025

    Walk the process. From the Windchill server, it should try to contact the worker daemon service on port 601 (typically). Is that running and responding? From there the worker daemon will issue the shortcut command to the batch file to start the worker. There should be evidence that it was executed and some log files there. The worker process will start and connect to the Windchill server on port 5600 (typically). Somewhere along the line its broken. Triple check your agent.ini file for typos. Also check that your whitelist setting in the wvs.properties is allowing those paths to the batch file to start. Let is know what you find.  

    7-Bedrock
    January 17, 2025

    Thanks for your response, I could able to see the Monitor log files, the issue is with the license server reachability for Creo Parametric. I can fix this.