From my experience there are a few things to bear in mind when installing Interwoven Software.  These include

1. Always install your software as administrator or full root (for solaris/Linux).  In respects to root access it must be full root not any sppof such as sudo. At the lease su root would be acceptable.  There have been installs where I have seen the installer not correctly installing, after which issues later arise.  Another reason to install as full root or administrator is that Interwoven will only support the software if they are installed by these users.
2. Always read the release notes, and ensure you fulfill the pre-requisites.
3. When selecting the install path, don’t leave any spaces.  I like to install as below;
   C:/Interwoven/TeamSite or C:/Interwoven/MediaBin
4. Keep a record of your actions whilst the install take place; will come in handy to document and to analyse any potential issues arising at a later date
5. Follow up your installation by executing any actions that are required after the install

Platform: Linux
TeamSite Version: 6.7.1
OpenDeploy Version: 6.2

I was involved in a project where I had just OpenDeploy 6.2 on a Linux environment.  However, the service would not start up. 
The error message appearing in od.log;

We had installed the prerequisite of the required library; libstdc++32-3.2.2-5.fdr.0.rh73.i386.rpm
However it seem to be clashing with other pre-installed libraries and applications on the server

Solution:

The Solution was to install the library in the OpenDeploy directory (e.g. /od-home/opendeployNG/lib), and thereafter modify
the OpenDeploy start-up service (iwod60 – note: make a backup copy of the service before making the changes below),
located in /etc/init.d/ with the following;

Install the library into the OpenDeploy location would not impact the server with clashes. 
Modfiying the start up service pointed to the library installed. After these changes were made,
I started the OpenDeploy service, and it worked!

I really struggled to find these documented so had to refer back to the 6.0 OpenDeploy manuals to find the below information.

Whilst running an OpenDeploy deployment that usually works no problem, I encountered the following below error.

"ERROR: IWDirent::Mkdir failed, err=30"
ERROR: /iwmnt/default/main/www/example/WORKAREA/Content 
could not be created. 
ERROR: Failed deploying local_directory[0] (/iwmnt/default/main
/test/WORKAREA/Content) to (/iwmnt/default/main/www/
example/WORKAREA/Content) 
ERROR: Failed 1 of 1 local_directories

SOLUTION

I created the target “Content” workarea in the above case and then this worked!

I think it is pretty obvious but someone / thing had deleted the “Content” workarea that OpenDeploy was configured to deploy too and so the “mkdir” was failing, presumably because of permissions.

If you try to create the directory that OpenDeploy is trying to deploy to this may resolve the above issue for you.

I wrote a post recently regarding how to install LiveSite 3.0.2 with OpenDeploy 6.1.1

and TeamSite 6.7.1 SP1 http://www.littleforest.co.uk/articles/livesite302-installation/

This post expands on the post written above where by you get OpenDeploy 6.0.2 to work

with LiveSite 3.0.2 and TeamSite 6.7.1 SP1.

As long as you follow the process stated in the post above you can then go ahead and install;

1. OpenDeploy 6.2.0 Base/Receiver
2. OpenDeploy 6.2.0 Admin
3. OpenDeploy 6.2.0 Patch

If you wish to change the user of ‘livesite-od’ after installation you can do so by going to

C:\Interwoven\TeamSite\local\config\lib\content_center\livesite_customer_src\
etc\conf\livesite_customer\opendeploy.properties

Here you will be able view and change the user account information

If your experiencing trouble with OpenDeploy starting up and are seeing ‘ERROR: LicenseException: Bad host name’ errors in the OpenDeployNG/od.log file, this post will help resolve the issue.

To get your domain name and host name, on the Command Line type:

<Your OpenDeploy Home Directory>\OpenDeployNG\jre\bin>java -cp <Your OpenDeploy Home Directory>\opendeployng\lib\odng.jar com.interwoven.license.LicInfo -f <ODlic.log> -p OD

Use the output of this command to help generate the OpenDeploy license key

Now do the following:

On Windows check the following registry keys (Click Start, run, and type regedit)

\\HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\DhcpDomain
\\HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Domain

Make sure they match exactly, same string and case.  If dhcpDomain does not exit, create it (String value)

The key \\HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Domain holds the Primary DNS Domain, and is set as follows:

1. Right click My Computer and select properties
2. Select the ‘Computer Name’ tab
3. Click on the “More” button and populate the “Primary DNS Suffix”
4. A system reboot is required after the change.

Also the key \\HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\hostname holds the system hostname,  should be tied to the correct ip address, and defined in winnt\system32\drivers\etc\hosts.

To verify the hostname and IP “seen” by OD, you can review the odbase.log for the line “Network Address available on localhost” for the correct host or IP which should match the OD.lic file

On a Unix box, verify that the primary domain in /etc/resolv.conf matches the domain in /etc/hosts and the domain returned by nslookup on the server.

On UNIX servers it is useful to have ’sudo’ setup in order to not always have to use or get ‘root’ access.

The below lists should help with the kind of commands you typically want to setup to be run under ’sudo’.

Interwoven Commands for TeamSite and OpenDeploy Base Server:

/etc/rc3.d/S99iw.local stop
/etc/rc3.d/S80iwod60 stop
/etc/rc3.d/S50iw.samba stop
/etc/rc3.d/S16iw.server stop
/etc/rc3.d/S16iw.server start/etc/rc3.d/S50iw.samba start
/etc/rc3.d/S80iwod60 start
/etc/rc3.d/S99iw.local start
/etc/init.d/iwod60 stop
/etc/init.d/iwod60 start
/etc/init.d/iw.server start
/etc/init.d/iw.server stop
/path to apache/bin/apachectl start(for the machine in question)
/usr/iw-home/bin/iwreset
/usr/iw-home/bin/iwstoreadm
/usr/iw-home/bin/iw* (all scripts would be very useful if possible)

Commands for OpenDeploy Receiver Server

/etc/rc3.d/S80iwod60 stop
/etc/rc3.d/S80iwod60 start
/etc/init.d/iwod60 stop
/etc/init.d/iwod60 start

The below commands may already be setup for ’sudo’ but it is worth checking:

File
view
ps
Netstat
Prstat
last -a
Vmstat
Iostat
Nfsstat

This page is created to hold Common OpenDeploy errors with their possible causes.

It was originally based on a Interwoven Support article but I have updated and extended this to include more and newer errors.

Where there is more than one possible cause, this is noted as #1 and #2 and so forth.

ERROR: outer-loop send failure, err=32 [Unknown socket error]
ERROR: recv failure, err=131 [Unknown socket error]
 Possible Cause#1: Firewall - make sure port is open
 Possible Cause#2: Need to put timeout=25000 (or more)
at top of both server and client config files

ERROR: Failed applying access to (path_to_file)
ERROR: Could not get file data(./filename) from socket.
 Possible Cause:Need to run OD as root

Error: Can Not read Version String Response
 Possible Cause: Port already in use or not open
Possible Cause: If you have multiple deployments to the same
server using the same port number, you will get this message.
In order to deploy simultaneously to the same server,
you need to run each deployment on different ports.

ERROR: Could not read src-dir ack from client.
 Possible Cause: Seems to have many causes including permissions

ERROR: Could not read directive.
 Possible Cause: problem with a script called by OpenDeploy

Error: Ambiguous cross-platform name comparison
 Possible Cause: On solaris to NT if there are files with same name
but different case. Need to change the name.

Error: 'c:\Program' is not recognized as an internal
or external command, operable program or batch file.
 Possible Cause: Need to set $IWODHOME to
Progra1~ from Program Files

ERROR: Could not write content size to client
ERROR: Could not write status to client
 Possible Cause: Using different versions of OD

ERROR: Could not read check-keyfile result.
 Possible Cause: Using wrong version of OD

Error: Outer loop send failure. Err 10053.
Cannot return status to server. Could not authenticate client
 Possible Cause: Usually because of the names put into the .cfg files.
Double check the names or use the ip numbers

ERROR: User is not authorized for this deploy!
ERROR: Could not authenticate client.
 Possible Cause: OpenDeploy not running as root on Solaris or
Local System on Windows

ERROR: Could not read deployment name.
 Possible Cause: Check to see if the the OD versions are the same on
both server and client (iwdeploy -v)

ERROR: Could not find matching OpenDeploy client for (ServerX)
 Possible Cause: Configuration has a host name instead of an IP address
set up for deployment

ERROR: Could not rename
 Possible Cause: Disk space on target server

ERROR: Could not read content size from remote.
 Possible Cause: Firewall timeout

ERROR: Could not read server status, client OK
 Possible Cause: Firewall timeout

ERROR: Could not read commit complete
 Possible Cause: Firewall timeout

ERROR: Failed 1 of 1 local_directories
 Possible Cause: Firewall timeout

ERROR: Could not read rollback start state
 Possible Cause: Firewall timeout

ERROR: Unable to do hand shake with the sender
 Possible Cause: Firewall timeout

ERROR: Could not write content size to client.
 Possible Cause: Firewall timeout

ERROR: Could not write status to client
 Possible Cause: Firewall timeout

ERROR: outer-loop send failure, fd=4, err=32 [Unknown socket error]
 Possible Cause: Firewall timeout

ERROR: not an allowed deployment path
 Possible Cause: NAT source IP must be configure in odrcvr.xml

ERROR: Failed to locate Access Service,
 Possible Cause: Update the OD-conf/framework.properties file
to reflect correct server name