Community Tip - Have a PTC product question you need answered fast? Chances are someone has asked it before. Learn about the community search. X
Solved! Go to Solution.
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.
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.
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.