Skip to main content
B
23-Emerald III
BenLoosli23-Emerald III
23-Emerald III
October 23, 2017
Question

Creo will not start for publishing

  • October 23, 2017
  • 3 replies
  • 6105 views

I have upgraded to CreoView 3.0m032 and now Creo will not launch to publish any files.

I have cleared all of the cache files.

I get a "did not find available worker" error message.

Any suggestions as to what I missed?

 

3 replies

R
RandyJones20-Turquoise
20-Turquoise
October 23, 2017
@BenLoosli wrote:

I have upgraded to CreoView 3.0m032 and now Creo will not launch to publish any files.

I have cleared all of the cache files.

I get a "did not find available worker" error message.

Any suggestions as to what I missed?

 

Perhaps the exec_file path to the dll in the protk.dat? This will almost always change when updating Creo View Adapters.

D
dharlan-21-Visitor
1-Visitor
October 25, 2017

I'm assuming you checked the compatibility matrix to make sure that adapter works with your version of WC?

Did you rebuild the recipe and batch files?

B
23-Emerald III
BenLoosli23-Emerald IIIAuthor
23-Emerald III
October 25, 2017

Yes, the build install was requested by PTC and I verified it both with the tech and by the document matrix.

Recipe and batch files have been rebuild by the adapter_config program.

 

Creo runs on that machine when started standalone.

Creo will start when launched from proepublish.bat.

Creo does not start when launched from proeworker.bat.

B
23-Emerald III
BenLoosli23-Emerald IIIAuthor
23-Emerald III
January 8, 2018

Continuation of same problem but different versions!

I have upgraded to Windchill 11.0 m030 and installed CreoView Adapters 4.1 F000.

The WorkerDaemon starts on the publishing machine at startup from the GS Worker service.

The proeworker will not start automatically. I have to log into the publishing machine and start proeworker.bat every day. Once started publishing runs fine for that day.

 

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.

 

R
RandyJones20-Turquoise
20-Turquoise
January 8, 2018
@BenLoosli wrote:

Continuation of same problem but different versions!

I have upgraded to Windchill 11.0 m030 and installed CreoView Adapters 4.1 F000.

The WorkerDaemon starts on the publishing machine at startup from the GS Worker service.

The proeworker will not start automatically. I have to log into the publishing machine and start proeworker.bat every day. Once started publishing runs fine for that day.

 

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.

 

Basically all proeworker.bat does is to start a workermonitor.exe process. The workermonitor.exe process is what Windchill uses to start/end the Creo Parametric session. 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. So this is why starting it manually would allow publishing to work.

Your issue sounds like one of two possibilities:

  • Your cadworker Windows firewall is preventing Windchill from running proeworker.bat
    • I have had this happen
    • Turn off the Windows firewall to see
  • You have the incorrect path to the proeworker.bat file in your agent.ini file
    • <Windchill>/conv/wvs/agent.ini

A couple of ways to debug:

  • look in the <Windchill>/logs/cadagent directory for log files
    • The log files contained under here will generally provide a good clue as to the issue
  • stick an "echo something to some file" in your proeworker.bat file to see if it is actually getting called ie:
    • echo Here at proeworker.bat >> c:\home\cadworker\proe_setup\startup.log
B
23-Emerald III
BenLoosli23-Emerald IIIAuthor
23-Emerald III
January 9, 2018

Randy,

Not seeing anything out of the ordinary in any log files. Windows firewall is turned off due to it being a private network.

 

The GS Worker service starts automatically and this is the WorkerDaemon.exe. Is this also supposed to start/launch the proeworker,bat to start the workermonitor.exe process?

 

Everything works fine as long as I start the proeworker.bat file manually. What PTC and I could not resolve was how to get the proeworker.bat file to launch at system startup. It used to work fine until one day it just quit. IT has done no system updates for over a year, so we ruled that out. Maybe I need to see if they changed some system level setting that did not require a patch.

 

Terms & ConditionsAccessibility statement