Connection failed: Could not find matching OpenDeploy client for

I am getting this error when trying to deploy a file list from a virtual server to six servers, transactional. I've read other posts and the articles on the support site but can't seem to find any errors in my configuration files. Attached are odnodes.xml from the base server, odrcvr.xml from one of the receivers, the particular od deployment configuration file I am using, and the log from the deployment to one of the servers. I'm wondering if the fact that I am using a virtual Windows server would have some affect on the make-up of my configuration files. I can deploy to the same six servers from my production server (not virtual) without issue using nearly the same od deployment configuration (file list, transactional, ...)

Any suggestions?

Thank you.

Find more posts tagged with

Comments

Natasha

I am getting this error when trying to deploy a file list from a virtual server to six servers, transactional. I've read other posts and the articles on the support site but can't seem to find any errors in my configuration files. Attached are odnodes.xml from the base server, odrcvr.xml from one of the receivers, the particular od deployment configuration file I am using, and the log from the deployment to one of the servers. I'm wondering if the fact that I am using a virtual Windows server would have some affect on the make-up of my configuration files. I can deploy to the same six servers from my production server (not virtual) without issue using nearly the same od deployment configuration (file list, transactional, ...)

Any suggestions?

Thank you.

There is a mismatch between the odnodes and odrcvr.xml.
The node host used in odrcvr.xml(msviwtstest) is not defined in odnodes.xml so you have to define it the way like other servers have been defined.
Although what I have learnt from the configuration file is that msviwtstest and MSVIWTSTEST.lowes.com are the same servers so just replace msviwtstest with MSVIWTSTEST.lowes.com in odrcvr.xml and it should work.

Natasha.

RonaldV

Hi Seth,

please refer to this post http://devnet.interwoven.com/forums_vb/showthread.php?t=23167&forumid=12&highlight=matching+client

The way it works in your case is:
1. strictPartner is false BUT your localhost-name (MSVIWTSTEST.lowes.com) does not match ANY of your allowedHosts (by string compare)

2. it (the receiver that is) will then try to resolve the ip adress of your localhost 'MSVIWTSTEST.lowes.com' and this fails as well. Either because the ip can't be resolved or the ip does not match ANY of the allowed-hosts-ip's.

3. Your done. Deploy fails. :-(

BTW, odnodes.xml has nothing to do with it here..... (as far as I know)

Hope this helps to resolve your problem.

SethHickel

Success summary with some confusion. See attached for before and after values.

Pinging the sender from the receiving server with and without the ".lowes.com" resolves the same: msviwtstest.lowes.com and the same IP.

I edited my odrcvr.xml for my receiving server to use the latter: "msviwtstest.lowes.com" The deployment works now.

I'm not sure that I understand why, when both pings resolve the same, it would make a difference which was in the odrcvr.xml file.

Is it something to do with ssh keys and such?

I agree that odnodes.xml has no bearing on this situation. I have edited the reference to this server, providing many different values with no affect on my ability to deploy with this particular OD configuration.

While it is now working I would love to be able to understand why so that I can work with my server admins in the future, providing one set of values for these files that works the first time.

Thank you.

Adam Stoller

Out of curiosity (not looking at any of the files you posted right now - don't have time) - what was the value of localNode in the deployment configuration file (not the server config, the deployment config)?

The localNode value is what is initially compared against the allowedHosts values.

SethHickel

The localNode in my deployment configuration had the value of MSVIWTSTEST before I edited it. It now has the value MSVIWTSTEST.lowes.com. Since I updated the odrcvr.xml file as described below I have tried both and both of those values will work now.

What seems to have fixed the issues is changing the odrcvr.xml that sits on the server to which I am deploying. The allowedHosts value was msviwtstest and is now msviwtstest.lowes.com. The latter value seems to be the correct one.