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; } } }

Deploment connection error

aloks

We are facing an error while deploying files from one server to another.
Source server has opendeploy6.1.1 while the target server has opendeploy5.1 installed.

On deploying..gives error..

id=0 server: Interwoven OpenDeploy(5.5.1 Build 11146 Interwoven 20020829)
id=0 server: Protocol Version(5.0) OK
id=0 server: Connection Id(id=0)
id=0 server: platform: server(UNIX), client(UNIX)
id=0 server: Transaction Mode: OFF
id=0 server: Mode(normal)
id=0 server: Protocol(normal)
id=0 server: Buffer Size (8000)
id=0 server: Host(pauley)
ERROR: Could not find matching OpenDeploy client for (servername).

Wanted to know whether it is due to different versions on the source and target servers.

Find more posts tagged with

Comments

Adam Stoller

We are facing an error while deploying files from one server to another.
Source server has opendeploy6.1.1 while the target server has opendeploy5.1 installed.

On deploying..gives error..

id=0 server: Interwoven OpenDeploy(5.5.1 Build 11146 Interwoven 20020829)
id=0 server: Protocol Version(5.0) OK
id=0 server: Connection Id(id=0)
id=0 server: platform: server(UNIX), client(UNIX)
id=0 server: Transaction Mode: OFF
id=0 server: Mode(normal)
id=0 server: Protocol(normal)
id=0 server: Buffer Size (8000)
id=0 server: Host(pauley)
ERROR: Could not find matching OpenDeploy client for (servername).

Wanted to know whether it is due to different versions on the source and target servers.

It's apparently not 5.1, it's 5.5.1 (big difference)

According to the support matrix for OD - 6.1.1 should be compatible with 5.5.1 although it's possible that 5.5.1 may need an SP for receiving filelist deployments (like 5.6 does)

However, the same matrix shows that OD 5.5.1 is not a compatible sender to 6.1.1 -- so make sure you know which is sending and which is receiving.

Beyond that - make sure that the receiving server's configuration file specifies the sending server in the allowedHost section and sending server specifies the receiving server in the odnodes.xml file and that both servers have been restarted after any such changes were made.

aloks

Thanks, It worked after restarting the servers.

sspopuri

Did you just restart the OD receiver servers??

curiousmaverick

restarting OD Rcvr is best/safe practice to do.

msrinivas

restarting OD Rcvr is best/safe practice to do.

Sez who? Why would restarting anything be a best practice?

XMLTrial.zip

nipper

Sez who? Why would restarting anything be a best practice?

Microsoft. Smiley Very Happy

msrinivas

Microsoft.

Ooh! That was a toss up!

But IWOV ain't MSFT Smiley Wink

Migrateduser

Becuase those changes are in the server config files an they are loaded at start up, any changes needs a restart.

this is also doc'd in the Od admin guide as well.

OpenDeploy Administration Guide p:59

nipper

Becuase those changes are in the server config files an they are loaded at start up, any changes needs a restart.

this is also doc'd in the Od admin guide as well.

OpenDeploy Administration Guide p:59

But he was saying restart the receiver. Anyway won't iwodserverreset do the same thing ?

Adam Stoller

But he was saying restart the receiver. Anyway won't iwodserverreset do the same thing ?

If the change is on the sending side's server config files only (either allowedHosts or odnodes.xml) - then an iwodcmd serverreset should suffice.

If the change is on the receiving side (allowedHosts) then I think you need to restart the receiver (I don't recall if the iwodcmd or iwodserverreset CLTs exist on the receiver)