File list bizzare error - 7.3.2->5.6

All Windows-based OD. Deploying to a farm of two servers from a new 7.3.2 box (both TS and OD),

Looks like a VERY bizzare set of errors - just trying to see if anyone has encountered before.

Deployment is a file list deployment with area and file list sent to the config file as parameters. I took the config file from the server (production), where everything works fine. All is configured properly for the new server as well.

What happens - deployment to one of the two server fails, the error message is as follows (on both server and receiver):

LIB: 2013-02-08 15:40:53 Local_directories to deploy: 1
LIB: 2013-02-08 15:40:53 ERROR: begin out of phase..
LIB: 2013-02-08 15:40:53 Receiver-ERROR: .
LIB: 2013-02-08 15:40:53 ERROR: Failed to begin transaction.

NOW. if I deploy using the SAME config file, just removing the filelist attribute, it works like magic! So it does enter into the comparison mode, etc. That means that there is no issue with handshake, etc. The log file also shows that OD 7.3.2 has no issue with deploying to 5.6 (down-rev happens). And as I can see it happily deploys to the other box that is OD 5.6

the dateDifferent is set to 'no'

anyone, any ideas?????

Find more posts tagged with

Comments

sheikh1

All Windows-based OD. Deploying to a farm of two servers from a new 7.3.2 box (both TS and OD),

Looks like a VERY bizzare set of errors - just trying to see if anyone has encountered before.
What happens - deployment to one of the two server fails, the error message is as follows (on both server and receiver):

LIB: 2013-02-08 15:40:53 Local_directories to deploy: 1
LIB: 2013-02-08 15:40:53 ERROR: begin out of phase..
LIB: 2013-02-08 15:40:53 Receiver-ERROR: .
LIB: 2013-02-08 15:40:53 ERROR: Failed to begin transaction.

Do you see anything else in the receiver logs where the deployment is failing or at ODBase level?

gzevin

Do you see anything else in the receiver logs where the deployment is failing or at ODBase level?

nope. same error

sheikh1

nope. same error

It seems to me that it might be because of version incompatibility, mostly due to differences of 7.3.2 and 5.6 OD versions. See if there is a possibility for upgrading your 5.6 OD receivers.

Adam Stoller

It seems to me that it might be because of version incompatibility, mostly due to differences of 7.3.2 and 5.6 OD versions. See if there is a possibility for upgrading your 5.6 OD receivers.

OpenDeploy has been supporting up-rev deployments since 5.5.1 and down-rev deployments since 5.6 - with a few minor hiccups that tended to be fixed by patches.

The only place where you'd be likely to encounter down-rev deployment issues is if you were using a feature from the Base Server side that wasn't supported on the Receiver side.

And since Greg already indicated that of the 2 (or more) OD 5.6 Receivers he has - one works without any problems - so it isn't a blanket version incompatibility issue.

You should verify that the explicit version of OD on both receivers is identical - perhaps use checksums to compare all the files within ODHOME on both Receivers too (make sure that a library wasn't updated on one and not the other)

gzevin

OpenDeploy has been supporting up-rev deployments since 5.5.1 and down-rev deployments since 5.6 - with a few minor hiccups that tended to be fixed by patches.

The only place where you'd be likely to encounter down-rev deployment issues is if you were using a feature from the Base Server side that wasn't supported on the Receiver side.

And since Greg already indicated that of the 2 (or more) OD 5.6 Receivers he has - one works without any problems - so it isn't a blanket version incompatibility issue.

You should verify that the explicit version of OD on both receivers is identical - perhaps use checksums to compare all the files within ODHOME on both Receivers too (make sure that a library wasn't updated on one and not the other)

Adam, will actually check the versions, maybe there is a patch that has not been applied. The receivers are (some at least) in an infrastructure setting that I cannot access myself....

As usual thanks, you were very gracious to the previous poster ... Smiley Happy

sheikh1

OpenDeploy has been supporting up-rev deployments since 5.5.1 and down-rev deployments since 5.6 - with a few minor hiccups that tended to be fixed by patches.

The only place where you'd be likely to encounter down-rev deployment issues is if you were using a feature from the Base Server side that wasn't supported on the Receiver side.

And since Greg already indicated that of the 2 (or more) OD 5.6 Receivers he has - one works without any problems - so it isn't a blanket version incompatibility issue.

You should verify that the explicit version of OD on both receivers is identical - perhaps use checksums to compare all the files within ODHOME on both Receivers too (make sure that a library wasn't updated on one and not the other)

My apologies for that.. I was kind of skeptical before mentioning compatibility issues also I don't find any OD product matrix for 7.3.2