nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Failed FindServerByName with TeamSite

JeremyP

I have an issue with a couple of Deployments on OD 6.0.0.

I have recently upgraded our Teamsite version from 6.5 SP3 to 6.7.1 SP1 in our Development Environment.

There are several deployments that were not used on this server, but were used in it's Production equivalent. They seem to have been configured for Development Previously, so I am attempting to use them. They still work on Production, but I would like to test them in Development if at all possible.

Both of the deployments have two config files, and both fail on the second file reporting the same errors right before connecting to the receiver:

LIB: 2008-09-09 13:23:38 LOGFILE=[D:\iw-home\opendeploy\OpenDeployNG\log\src.Portal_DevToTest_B.Deploy to Test.msinwvp1.to.testapp1.log]
LIB: 2008-09-09 13:23:38 Locale=[English_UnitedStates.MS1252@Binary]
LIB: 2008-09-09 13:23:38 ERROR: Failed FindServerByName with TeamSite
LIB: 2008-09-09 13:23:38 ERROR: Failed converting area(Y:\default\main\MESC\Internet\en\EDITION) to VPATH
ENG: 2008-09-09 13:23:38 CDT GMT-05:00 Thread-23 Connecting to host=x.x.x.x port=20014

Any ideas of where to begin to look?

Thanks

Find more posts tagged with

Comments

Pawan

Not sure what the error means, but OD 6.0.0 is not compatible with TS 6.7.1.
What is the OD details of the receiver? Do you mean to say all other deployments are working fine except these two which you mentioned?
I would recommend you should upgrade the OD on your dev server and try.

JeremyP

Not sure what the error means, but OD 6.0.0 is not compatible with TS 6.7.1.
What is the OD details of the receiver? Do you mean to say all other deployments are working fine except these two which you mentioned?
I would recommend you should upgrade the OD on your dev server and try.

The receiver is version 5.6 and I believe on Solaris.

Yes, all other deployments (2) are working fine.

Thanks for the the suggestion. I wanted to avoid upgrading OD until after TS if at all possible, but it might not be feasible.

Adam Stoller

LIB: 2008-09-09 13:23:38 ERROR: Failed FindServerByName with TeamSite

This generally means that the deployment configuration file defines its localNode as "TeamSite" - and the Receiver does not recognize it as an allowedHost (the allowedHost section should have the actual hostname or IP address registered - and OD will generally do a lookup to find the actual hostname after it doesn't find "TeamSite")

Since your receiver is old, it is possible that version doesn't do the full hostname verification - in which case you might try adding another allowedHost section for "TeamSite" - with the same allowedDirectory entries - in your odrcvr.xml file - and then stop/start the OD Receiver process and try the deployment again.

I'm assuming that you correctly changed the odnodes.xml file and/or the target replicationFarm settings for your DEV TS box to go to the desired DEV receiver.

JeremyP

This generally means that the deployment configuration file defines its localNode as "TeamSite" - and the Receiver does not recognize it as an allowedHost (the allowedHost section should have the actual hostname or IP address registered - and OD will generally do a lookup to find the actual hostname after it doesn't find "TeamSite")

Since your receiver is old, it is possible that version doesn't do the full hostname verification - in which case you might try adding another allowedHost section for "TeamSite" - with the same allowedDirectory entries - in your odrcvr.xml file - and then stop/start the OD Receiver process and try the deployment again.

I'm assuming that you correctly changed the odnodes.xml file and/or the target replicationFarm settings for your DEV TS box to go to the desired DEV receiver.

Thanks for the input, I tried your suggestions and unfortunately none of them seemed to resolve the issue. Support recommended an upgrade to 6.1.1 so I went that route. I upgraded the base then admin, and after fixing a minor issue, the deployments worked successfully.