Deploying to OD Downward revision

Good morning everyone.
Been trying to run a simple OpenDeploy from an NT4 SP6a server running TS 5.0.1 and OD5.5.2 to an OD receiver 4.5.2 on an HP-UX box.

The deploy fails ar directory comparison phase with the error;
client: ERROR: nt authority\system is not authorized for this deploy!
...
client: ERROR: could not authenticate client.

Am using IP addresses in the config files.
Attached our deploy config file.
Anyone seen something similar?
Thanks and regards,
Chico
T-Mobile MSC

Francis Pacheco
www.t-zones.co.uk

Find more posts tagged with

Comments

Adam Stoller

Sorry - no answers yet - need some more information for diagnosis

Please attach (preferably as zip or tar file) the odbase.xml and odserver.cfg (or whatever it's called for 4.5.2) files for the receiving end too.

Since you're using sourceFilesystem - you shouldn't need to specify the down-revision of TeamSite (though it probably wouldn't hurt).

I am assuming that you still have OpenDeploy 4.5.2 installed on the Base Server machine as well as the OpenDeploy 5.5.1 Base Server (note: it's 5.5.1 not 5.5.2) - yes?

Is the OpenDeploy 4.5.2 server ("Receiver") running as root on the HP-UX box?

What version of HP-UX?

You may want to gather up all the sending side and receiving side logs as well and include them in the zip (or tar) file.

--fish
(Interwoven Senior Technical Consultant)

Chico

Here goes - attached zip file with configuration and log files - though couldn't access the log files on the receiver... will get admin to get these if necessary.

Regarding your questions fish;
. Have OpenDeploy 4.5.2 Base Server software also installed as when installed 5.5.1 this didn't uninstall 4.5.2 i'm assuming
. The receiver is on AIX 4.4.3 - my mistake, but will do similar onto HP-UX 11.
. Receiver running as www not root.

Thanks for your extra prompt reply - u in europe or just an insomniac?
Chico

Francis Pacheco
www.t-zones.co.uk

Adam Stoller

First - thanks for deleting the old stuff in the log files - it's a small thing to do but greatly aids in focusing the attention where it's needed (just in case you thought I wouldn't notice :-)

Because you're running the receiving side as non-root - you may need to change some of the deployment configuration file's defaults:

For comparisonRules - you may need to change ignoreAcls, ignoreUser, and ignoreGroup to "yes". Also, are you sure you want dateDifferent set to "yes"? (it means newer *or* older files get deployed, not just newer.

For permissionRules - you may need to explicitly set the user and group settings to be those of the OpenDeploy 4.5.2 server ("Receiver") process owner's.

The OpenDeploy 5.5.1 Base Server seems to be doing something wrong with regard to launching the OpenDeploy 4.5.2 client. Do you perhaps have more than one old version of OpenDeploy software installed on the Base Server machine? I ask because you seem to properly define:

<oldOdHome path="D:\iw-home\OpenDeploy" />

In your odbase.xml file, but the 5.5.1 source log file indicates:

ENG: 2002-12-09 09:51:58 GMT+00:00 Thread-16 *****Cmd = C:\Program Files\Interwoven\OpenDeployOld\bin\iwdeploy -fs C:\PROGRA~1\INTERW~1\OPENDE~1\lib\.TMTEST7_at_web_t-zones.AT_WEB_T-Templates.daxora01 .TMTEST7_at_web_t-zones.AT_WEB_T-Templates.daxora01

I'm not sure where it's getting the second path from if you specified the first path - please check both paths out to see whether or not you have more than one version of OpenDeploy 4.x installed on that (sending) machine.

That's all I can think of right now - if the above doesn't help you solve the problem, and if nobody else has any constructive thoughts to further the diagnosis - I would suggest you contact Interwoven Support for more direct assistance.

And no, I'm not in Europe - just an insomniac ;-)

--fish
(Interwoven Senior Technical Consultant)

Chico

Changed the comparisonRules and the permissionRules attributes but to no avail, still get the same error message.

The error message you saw in the source log file was me playing around with <oldOdHome> path but then deciding I had it right in the first place;
<oldOdHome path="D:\iw-home\OpenDeploy" />
One point I would like to make here is that I have found over the last three years that I've been using teamsite, I am often misled by your documentation. On page 89 of the OD 551 admin guide it gives an example of the oldOdHome element path as c:\program files\Interwoven\OpenDeploy... when OD 452 path is normally d:\\iw-home\OpenDeploy!

Anyway, IW support have referred this problem to a more speciailised support group apparently.

Thanks again for your help, we are definitely closer to the solution.

Best regards,
Chico

Francis Pacheco
www.t-zones.co.uk

Edited by Chico on 12/10/02 01:18 AM (server time).

Adam Stoller

On page 89 of the OD 551 admin guide it gives an example of the oldOdHome element path as c:\program files\Interwoven\OpenDeploy... when OD 452 path is normally d:\\iw-home\OpenDeploy!

Just to be clear - the following is my personal opinion on this matter ...

The documentation is written to be politically correct with respect to Windows applications - i.e. the Windows doctrine is that all applications get installed under C:\Program Files\...

Most folks in the field, on the other hand, dislike spaces in path names and also like relatively short path names - and so install products like OpenDeploy in something like c:\od-home or c:\iw-home\opendeploy

Because you can basically install the software anywhere on your local disk - the documentation has to refer to some standard location - and for better or worse, the standard chosen is the Microsoft standard.

--fish
(Interwoven Senior Technical Consultant)

Chico

That's surprisingly useful to know!!!

Anyway, got the deploy to work... one of our unix admin's cleaned up the iw.odserver.cfg file thereby removing the entry for our development Teamsite box from which I was attempting to deploy from...

Till the next one... ciao and thank you indeed.
Chico

Francis Pacheco
www.t-zones.co.uk