Skip to main content
1-Visitor
March 7, 2015
Question

CAD Worker Issues

  • March 7, 2015
  • 14 replies
  • 6611 views

We migrated to new Windows 2008 servers this weekend, and things went fairly smoothly. However, I am not able to get my CAD Workers started.


I have updated the proeworker.bat file to point to the new application server. The CAD Worker server did not change (it was already a 2008 machine).


When I go to Worker Agent Administration, do a Reload, and then attempt to start one of the workers, I get the status "Fails to Start" I haven't been able to find any matching messages in the log files.


On the CAD Worker side, I can run the proeworker.bat. In the monitor.log file, I see:


Connecting to server <fqdn> on port <n>


Connection established


Got INIT SUCCESS reply



But when I try to TestServer from the Adapter Configuration (using our .pvi file), I get


Testing Connection to server...Failed


Set keepalive ok


The CADAgent rejected the connection, is it configured for a PROE worker on machine <worker server="> (alias not set)?



Any ideas???


Thanks,


Mary-Ann


14 replies

avillanueva
23-Emerald I
March 7, 2015
Simple checks. Can you ping both systems from each other? Did you use an alias in the proeworker.bat file for the CAD worker? Check DNS or hosts files.
23-Emerald IV
March 7, 2015
Check the “wt.auth.trustedHosts” property. Make sure it’s set to either the DNS name or IP address of the CAD worker.

Tom U.
mmuth1-VisitorAuthor
1-Visitor
March 7, 2015

Yes I can ping in both directions. I updated my hosts file with the servernames (both the app server and cad worker server), and when I run the proeworker.bat, I now get


Connecting to server <app server=" fqdn="> on port <n>


Connection established


Got version 8 INIT FAILURE (with no description) from WVS


Monitor shutting down.


Still nothing in the method server logs, and the Agent still Fails to Start.


Mary-Ann

1-Visitor
March 7, 2015
Also verify that the ports 5600 and 601 are not blocked from firewall?



>
mmuth1-VisitorAuthor
1-Visitor
March 7, 2015

I checked them. And updated the auth.properties file.


I'm sure this is some simple thing, if I could just find it!


Mary-Ann

1-Visitor
March 9, 2015

Hi Mary Ann,


Did you check if your firewalls are turned off? Are you using SSL/https? Did you install both 32bit and 64 bit java on your worker? Does your java have security off or allow your server?


Here's something to help. Did you try just to re-install/update the worker?

1-Visitor
March 9, 2015

You state that the agent fails to start,


Did you try to put the agent in debug mode? Is the agent remote or local to Windchill server? Is the background methodserver starting? How many method servers do you have configured.


Regards,



Patrick

12-Amethyst
March 9, 2015

We've had issues when UAC was turned on for the server. Also, if the CADWorker is running as a service, you could try starting it manually from a command prompt:


<creo view=" adapters=">\i486_nt\obj\WorkerDaemon.exe <port>


Sometimes it will show you if applications are crashing. I would also turn on debugging as suggested in one of the previous comments.


Good luck!

CraigPater
20-Turquoise
March 9, 2015
“Got version 8 INIT FAILURE (with no description) from WVS” means there is a mismatch between the worker hostname defined in Worker Agent Administration and that being returned by the Worker when it connects back to the Windchill server on startup.

Try using the short Worker hostname as defined in the Worker Windows Control Panel > System when defining the Worker definition in Worker Agent Administration.
17-Peridot
March 9, 2015
All,

Make sure that the two names match because it is case sensitive. Did you
also add the server to host file on the CAD Worker?


Lance Lie
Sr. Info Sys Technologist II
Global Business Services - Information Technology
Raytheon Company



714-446-2806 (office)
-

1801 Hughes Way
Fullerton, CA 92833 USA
www.raytheon.com

This message contains information that may be confidential and privileged.
Unless you are the addressee (or authorized to receive mail for the
addressee), you should not use, copy or disclose to anyone this message or
any information contained in this message. If you have received this
message in error, please so advise the sender by reply e-mail and delete
this message. Thank you for your cooperation.