Failing to Deploy

Hi ,

I am trying to deploy files usng OD script.
In the Opendeploy logs its showing "***ERROR - Receiver didn't reply with ack, it replied: nack:6.0.0.0.0
ENG: 2008-06-11 01:48:48 EDT GMT-04:00 Thread-4923 exiting setup" message.
Receiver is using 6.0.2.0.0 version while sender is using 6.0.0.0.0 version.

If I change the name of the OD Script it will work perfectly but for few names its showing the above log error message. How can be OD Script name dependent?

If we deploy the content from higher source version to lower receiver version it will fail but vice versa should work. In my case source is having lower version as compared to receiver so it should work.

Can anyone help me in solving this problem.

Thanks in advance.
Janvi
OD 6.0.0.0.0
Teamsite 6.1

Find more posts tagged with

Comments

Adam Stoller

Hi ,

I am trying to deploy files usng OD script.
In the Opendeploy logs its showing "***ERROR - Receiver didn't reply with ack, it replied: nack:6.0.0.0.0
ENG: 2008-06-11 01:48:48 EDT GMT-04:00 Thread-4923 exiting setup" message.
Receiver is using 6.0.2.0.0 version while sender is using 6.0.0.0.0 version.

If I change the name of the OD Script it will work perfectly but for few names its showing the above log error message. How can be OD Script name dependent?

If we deploy the content from higher source version to lower receiver version it will fail but vice versa should work. In my case source is having lower version as compared to receiver so it should work.

Can anyone help me in solving this problem.

Thanks in advance.
Janvi
OD 6.0.0.0.0
Teamsite 6.1

In general it is better to have the Base Server being a newer or same version as the Receiver and not having the Receiver being newer than the Base Server. That being said, it doesn't seem to make sense that simply the name of the deployment configuration file is the cause of the problems.

Depending on the type of deployment (file-list versus dir-diff for example) it is possible you're running into a bug which was fixed with a patch and you may have to download and apply the patch to either the base server or receiver in order for the down-rev (or up-rev) deployment to work - you should probably spend some time looking at the patches available for your versions of OD and see if any of the bugs fixed would seem to apply to what you're experiencing -- though I still think you should make sure that the sender is at the same or newer version than your receiver.

janhavi

In general it is better to have the Base Server being a newer or same version as the Receiver and not having the Receiver being newer than the Base Server. That being said, it doesn't seem to make sense that simply the name of the deployment configuration file is the cause of the problems.

Depending on the type of deployment (file-list versus dir-diff for example) it is possible you're running into a bug which was fixed with a patch and you may have to download and apply the patch to either the base server or receiver in order for the down-rev (or up-rev) deployment to work - you should probably spend some time looking at the patches available for your versions of OD and see if any of the bugs fixed would seem to apply to what you're experiencing -- though I still think you should make sure that the sender is at the same or newer version than your receiver.

But earlier the OD scripts used to work perfectly even if the version difference was present. Suddenly it started giving Error message . I am deploying the content to two servers, for one server it is getting deploy without any error only for one server it is showing eroror message.

Adam Stoller

But earlier the OD scripts used to work perfectly even if the version difference was present. Suddenly it started giving Error message . I am deploying the content to two servers, for one server it is getting deploy without any error only for one server it is showing eroror message.

This is not the same information you provided in your previous posting - based on this information, I'd suggest restarting the OD Receiver process that's giving you problems, possibly rebooting the box -- and verifying that nobody else changed anything on that server recently (OS patches, applications installed, etc.)