Skip to main content
M
mmuth1-Visitor
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

Show previous replies
M
mmuth1-VisitorAuthor
1-Visitor
March 9, 2015

We have 2 background servers and 5 method servers running on the app server. On the CAD worker server we have 2 workers defined, with 2 Agents corresponding to the workers on the app server. To communicate with the CAD worker, we use a directory on the worker server - the app server pushes files out there, and the worker checks the drive for incoming work.We aren't using FTP.


I've updated the hosts files on both servers.


We've been using the short name in the Agent definitions. I tried changing one to the full name, and it didn't seem to matter. I also deleted one of the Agents, and recreated it with no luck.


I did a reboot on the worker server, and the proeworker.bat file now works - I get an INIT SUCCESS. Testing the connection to the app server is still failing - I am still geting "The CADAgent rejected the connection, is it configured for a PROE worker on machine <short server=" name="> (alias not set)?"


What properties would turn on verbose logging for the CAD Agent? I'm wondering if I could get any more info from it (versus the none I get now!).


Mary-Ann

M
mmuth1-VisitorAuthor
1-Visitor
March 10, 2015

Turns out it was the etc/hosts file. Since we have two CAD workers defined, and want to be able to refer to the workers uniquely, we have 'named' them proeworker_p1 and proeworker_p2 (rather than giving them the host name). Interestingly, even though the path to the commands and directory used the FQDN, Windchill uses this name to connect to the server. So my etc/hosts file needed to be updated to add these two CAD worker names to the aliases for the CAD worker server.


Thanks for all the suggestions and help!


Mary-Ann

C
clawrenz-21-Visitor
1-Visitor
March 12, 2015
In the Adapter configuration you may want to use the show version of hostname with out the domain.

Use wcserver instead wcserver.domain.com<">http://wcserver.domain.com>



Best Regards,

Carsten Lawrenz
KALYPSO<">http://kalypso.com/?utm_source=internal&utm_medium=email&utm_campaign=kalypsosig>
MOBILE
415.378.6374
kalypsonian.com/Carsten.Lawrenz<">http://kalypsonian.com/Carsten.Lawrenz>



On Mar 7, 2015, at 9:48 AM, Mary-Ann Muth <-<<a style="COLOR:" blue;=" text-decoration:=" underline&quot;=" target="_BLANK" href="mailto:-">>">mailto:->> wrote:


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 on port

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 (alias not set)?



Any ideas???

Thanks,

Mary-Ann


S
sshankaracharya10-Marble
10-Marble
March 12, 2015
Hi Mary-Ann,

I would check below points

1. Check host name is correct by launching adapter.config file

2. telnet from both the machines should be success

3. check the shared directory for the worker, if its pointing to same location as before (if you do not have ftp configuration)

4. sometimes if worker instance is not running with admin rights, it would result fail to start issues

5. try to launch worker.bat file manually and refresh Worker agent administrator list


- Shashi
Terms & ConditionsAccessibility statement