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

OD Post upgrade problems (TS 6.0.1 to 6.7)

Alyssa

Hello,

We have just upgraded our production Teamsite installation from version 6.0.1 to version 6.7.1 (OD 6.0.1) and we now have problems promoting content via OpenDeploy to certain receivers.

We've tried adding the fix "teamsite.version: 6.7.1.0" line to our deploy.cfg and restarted but it doesn't make any difference.

Here is the log from a failed promotion:

ENG: 2007-09-24 11:09:02 BST GMT+01:00 Thread-23 Block max wait time (sec): 1800
ENG: 2007-09-24 11:09:02 BST GMT+01:00 Thread-23 Block check interval (sec): 30
ENG: 2007-09-24 11:09:03 BST GMT+01:00 Thread-23 Remote side has path registry disabled
LIB: 2007-09-24 11:09:03 LOGFILE=[/apps/interwoven/OpenDeployNG/log/src.to_production_webserver26936.DOCROOT.us1531.to.live_webserver_383.log]
LIB: 2007-09-24 11:09:03 Locale=[English_UnitedStates.US-ASCII@Binary]
LIB: 2007-09-24 11:09:03 ERROR: Failed open session with TeamSite
LIB: 2007-09-24 11:09:03 ERROR: Failed converting area(/default/main/nam/EDITION) to VPATH
LIB: 2007-09-24 11:09:03 Interwoven OpenDeploy(6.0.1.0.0 Build 41860 Interwoven 20041018)
LIB: 2007-09-24 11:09:03 LIB: Component Version (6.0.1.0.0 Build 41860 Interwoven 20041018)
LIB: 2007-09-24 11:09:03 ERROR: Failed open session with TeamSite
LIB: 2007-09-24 11:09:03 ERROR: Failed converting area(/default/main/nam/EDITION) to VPATH
LIB: 2007-09-24 11:09:03 Buffer Size (8000)
LIB: 2007-09-24 11:09:03 Protocol Version(5.0) OK
LIB: 2007-09-24 11:09:03 Connection Id(id=m2)
LIB: 2007-09-24 11:09:03 ERROR: Failed open session with TeamSite
LIB: 2007-09-24 11:09:03 ERROR: Failed converting area(/default/main/nam/EDITION) to VPATH
LIB: 2007-09-24 11:09:03 Transaction Mode: ON
LIB: 2007-09-24 11:09:03 Mode(normal)
LIB: 2007-09-24 11:09:03 ERROR: Failed open session with TeamSite
LIB: 2007-09-24 11:09:03 ERROR: Failed converting area(/default/main/nam/EDITION) to VPATH
ENG: 2007-09-24 11:09:03 BST GMT+01:00 Thread-23 After SETUP, res=-1
ENG: 2007-09-24 11:09:03 BST GMT+01:00 Thread-23 exiting setup
ENG: 2007-09-24 11:09:03 BST GMT+01:00 Thread-23 entering awaiting-cleanup
ENG: 2007-09-24 11:09:03 BST GMT+01:00 Thread-23 still waiting for 0
ENG: 2007-09-24 13:06:41 BST GMT+01:00 Thread-23 exiting awaiting-cleanup
ENG: 2007-09-24 13:06:41 BST GMT+01:00 Thread-23 entering cleanup
ENG: 2007-09-24 13:06:41 BST GMT+01:00 Thread-23 After CLEANUP, res=-1
ENG: 2007-09-24 13:06:41 BST GMT+01:00 Thread-23 exiting cleanup
ENG: 2007-09-24 13:06:41 BST GMT+01:00 Thread-23 entering task-failed

To our knowledge nothing has changed other than the upgrade of the Teamsite software. Anybody with some ideas on what we can try?

Many thanks,
Alyssa

Find more posts tagged with

Comments

kaalraa

What is the output result while trying to execute the command through command line? Does that give it as success or a failure? If latter, then you must have some issues with your configuration.

Although, i suggest you to log a support ticket at the earliest mentioning as high priority production issue.

Hello,

We have just upgraded our production Teamsite installation from version 6.0.1 to version 6.7.1 (OD 6.0.1) and we now have problems promoting content via OpenDeploy to certain receivers.

We've tried adding the fix "teamsite.version: 6.7.1.0" line to our deploy.cfg and restarted but it doesn't make any difference.

Here is the log from a failed promotion:

ENG: 2007-09-24 11:09:02 BST GMT+01:00 Thread-23 Block max wait time (sec): 1800
ENG: 2007-09-24 11:09:02 BST GMT+01:00 Thread-23 Block check interval (sec): 30
ENG: 2007-09-24 11:09:03 BST GMT+01:00 Thread-23 Remote side has path registry disabled
LIB: 2007-09-24 11:09:03 LOGFILE=[/apps/interwoven/OpenDeployNG/log/src.to_production_webserver26936.DOCROOT.us1531.to.live_webserver_383.log]
LIB: 2007-09-24 11:09:03 Locale=[English_UnitedStates.US-ASCII@Binary]
LIB: 2007-09-24 11:09:03 ERROR: Failed open session with TeamSite
LIB: 2007-09-24 11:09:03 ERROR: Failed converting area(/default/main/nam/EDITION) to VPATH
LIB: 2007-09-24 11:09:03 Interwoven OpenDeploy(6.0.1.0.0 Build 41860 Interwoven 20041018)
LIB: 2007-09-24 11:09:03 LIB: Component Version (6.0.1.0.0 Build 41860 Interwoven 20041018)
LIB: 2007-09-24 11:09:03 ERROR: Failed open session with TeamSite
LIB: 2007-09-24 11:09:03 ERROR: Failed converting area(/default/main/nam/EDITION) to VPATH
LIB: 2007-09-24 11:09:03 Buffer Size (8000)
LIB: 2007-09-24 11:09:03 Protocol Version(5.0) OK
LIB: 2007-09-24 11:09:03 Connection Id(id=m2)
LIB: 2007-09-24 11:09:03 ERROR: Failed open session with TeamSite
LIB: 2007-09-24 11:09:03 ERROR: Failed converting area(/default/main/nam/EDITION) to VPATH
LIB: 2007-09-24 11:09:03 Transaction Mode: ON
LIB: 2007-09-24 11:09:03 Mode(normal)
LIB: 2007-09-24 11:09:03 ERROR: Failed open session with TeamSite
LIB: 2007-09-24 11:09:03 ERROR: Failed converting area(/default/main/nam/EDITION) to VPATH
ENG: 2007-09-24 11:09:03 BST GMT+01:00 Thread-23 After SETUP, res=-1
ENG: 2007-09-24 11:09:03 BST GMT+01:00 Thread-23 exiting setup
ENG: 2007-09-24 11:09:03 BST GMT+01:00 Thread-23 entering awaiting-cleanup
ENG: 2007-09-24 11:09:03 BST GMT+01:00 Thread-23 still waiting for 0
ENG: 2007-09-24 13:06:41 BST GMT+01:00 Thread-23 exiting awaiting-cleanup
ENG: 2007-09-24 13:06:41 BST GMT+01:00 Thread-23 entering cleanup
ENG: 2007-09-24 13:06:41 BST GMT+01:00 Thread-23 After CLEANUP, res=-1
ENG: 2007-09-24 13:06:41 BST GMT+01:00 Thread-23 exiting cleanup
ENG: 2007-09-24 13:06:41 BST GMT+01:00 Thread-23 entering task-failed

To our knowledge nothing has changed other than the upgrade of the Teamsite software. Anybody with some ideas on what we can try?

Many thanks,
Alyssa

nipper

Hello,

We have just upgraded our production Teamsite installation from version 6.0.1 to version 6.7.1 (OD 6.0.1) and we now have problems promoting content via OpenDeploy to certain receivers.

When you state Certain Receivers, that implies some work and some do not, is this a correct assumption ? Does ANYTHING deploy to any receiver ?

Alyssa

Deploys are working to our development site but not to our live site.

We've tried adding in the TS version line to the deploy.cfg files on the OD recievers and restarted them but this hasn't helped either.

kaalraa

We've tried adding in the TS version line to the deploy.cfg files on the OD recievers and restarted them but this hasn't helped either.

This helps only in case when the execution comes as success, however you could not find the files on the server. Just to help the readers out there.

ISCBorisB

Deploys are working to our development site but not to our live site.

We've tried adding in the TS version line to the deploy.cfg files on the OD recievers and restarted them but this hasn't helped either.

I vaguely recall a post indicating that you must not be too precise with your TS Version, OD does not recognize these *details*.

Try "teamsite.version: 6.7.0" first ( 3 digits, basic Version ) and "teamsite.version: 6.7.1" if that does not work. Do not forget to restart Service.
I *think* that you do not need this setting on the receivers

nipper

Deploys are working to our development site but not to our live site.

We've tried adding in the TS version line to the deploy.cfg files on the OD recievers and restarted them but this hasn't helped either.

From the same server, deployments work to one set of receivers but not to another set ?

What is the OD receiver level for each side ?

Alyssa

That's correct, the deploys from the same server work to one reciever but not another.

The recievers that deploys are failing for are on webservers that are behind a firewall. We have checked connectivity through the Firewalls and it looks fine, and the receivers are showing that they are receiving some of the jobs from the base server.

From the same server, deployments work to one set of receivers but not to another set ?

What is the OD receiver level for each side ?

nipper

That's correct, the deploys from the same server work to one reciever but not another.

The recievers that deploys are failing for are on webservers that are behind a firewall. We have checked connectivity through the Firewalls and it looks fine, and the receivers are showing that they are receiving some of the jobs from the base server.

Get the logs from the receivers if you can and post them. Also, what OS and rev are the receivers ? Another thing to check is the firewall settings. I know you said the connectivity is OK, but check both directions. I have seen cases where server A can send to B but the return is not possible.

Finally how is the disk situation on the receivers ? Esp where the logs are stored ? I have seen that cause issues.

Andy

Alyssa

This issue has now been resolved. It seems that OD 6.0.1 isn't compatible with TS 6.7.1. We upgraded OD to 6.1 on base and recievers and deploys are working fine now.

The thing that had me confused was that even with the old "non compatible" version of OD, deploys worked to our development server. That made me assume that it must be a compatible version.

I guess it's always worth checking the compatibility page on the support site!

http://support.interwoven.com/resources/products/compatibility/opendeploy.asp

Thanks for all the helpful replies.

ProfessorX

I vaguely recall a post indicating that you must not be too precise with your TS Version, OD does not recognize these *details*.

Try "teamsite.version: 6.7.0" first ( 3 digits, basic Version ) and "teamsite.version: 6.7.1" if that does not work. Do not forget to restart Service.
I *think* that you do not need this setting on the receivers

This worked out great for me
TY ISCBoris

ISCBorisB

This worked out great for me
TY ISCBoris

My pleasure Jim