Platform: Windows 2003 SP1
TeamSite Version: 6.7.1

A recent issue I experienced on TeamSite 6.7.1 was that I couldn’t get access to the TeamSite 6.7.1 interface on the browser.  I would get a HTTP 404 error appearing on the screen

Solution:

- Find the file libeay32.dll under the c:\program files\common files\Interwoven\lib directory.

- Replace the libeay32.dll under C:\Windows\System32 directory with the one in Interwoven directory (mentioned above)
Note: Remember to keep a backup of System32 directory before making the change.

- Reboot the server

Doing this resolved the HTTP 404 error

To index branches in TeamSite Search you need to edit the following file;

Search-home/etc/branches.cfg
(Note: Search-home is TeamSite Search Install Location)

Branches should be inputted as;

/default/main/branch1
/default/main/branch1/branch1a

Points to consider;
- If /default/main is not in use, it is not worth indexing
- You must input each and every branch you want to index including sub branches in the file individually

Process of indexing a branch;

1. Stop the TeamSite Search service
2. Stop the TeamSite Search Index Service
3. Edit the file mentioned above
4. Start the TeamSite Search Index Service
5. Start the TeamSite Search Service

This will begin the indexing of staging area of the inputted branches in step 3.  To enable workarea search, please refer to enable workarea search post.  The process above applies to all operating systems

Platform: Linux
TeamSite Version: 6.7.1

I was involved in a recent project where I was having webdeamon issues.  The service was not starting up, and in due course TeamSite interface could not be seen on the web.  The first thing I looked at was Apache.  However seem to be installed ok, and the service seem to be running ok.  After a thorough investigation of potential reasons why the service was failing to start we found the issue and the solution.

Issue:

The reason why the service fail to start was the nfslock service was disabled (not started in run level 345).

Solution:

Enable the nfslock service (rpc.statd and rpc.lockd)

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 was recently involved in a project where the requirement was to migrate from one server to another.  Part of the requirement was to create all the local users from the previous server to the new server, and later add them to TeamSite.  Initially I thought this may not take long.  However, this was not the case.  I received the number of users, and this came to 800+ users.  I thought this is going to take ages to do!

However, after doing a bit of research I found the command line tool to add local users

NET USER username password /ADD /FULLNAME:”fullname”

e.g.

NET USER vealimy oSEinfam /ADD /FULLNAME:”Linda Myllerup”

From this I added this to my create_user Perl script, which in turn created all the users within hour, rather then weeks!!

Platform: Linux
TeamSite Version: 6.7.1
Content Store: Located on a NFS Share mounted on version 2

I was involved in a project where the UNIX team said they do not support nfs version 2.  This was seen as a major problem as on an Interwoven article it clearly states only nfs version 2 is fully supported by Interwoven.

After speaking with Interwoven Support and Engineering, they confirmed NFS version 3 is supported on Linux

Platform: Linux
TeamSite Version: 6.7.1
Content Store: Located on a NFS Share mounted on version 2

I was involved in a project where TeamSite reported the following warning in the iwtrace.logs

Warning: disk low    “/local/data/interwoven/iw-store/workflow”    Less than 50000 inodes (0 free of 0 inodes).

Cause:

This was diagnosed, and the following diagnosis was made

- The server reported a low number of inodes.
– ‘df -i’ showed that there were inodes at all (available, used and free) on the interwoven nfs share.
- This issue was triggered during diagnosis of a nfs lock (refer to content store lock article)
- netapp filer is confused when NFS share is mounted both as nfs v2 and nfs v3.

Solution:

Mounting the interwoven nfs share under nfs v3

A key requirement for any log is to log the time and date of any action taking place in a script.  The command below will print the time to your log in a readable format

print LOG scalar localtime;

The output of this in a log will be as follows;

Thu Nov 27 14:48:48 2008

Note: (LOG) is the log file you adding or appending to

I was recently involved in a upgrade of TeamSite 6.1 to 6.7.1, and had to migrate the old 6.1 content store to the new 6.7.1 content store format.  To do this I decided I would add a new 6.7.1 format content store to TeamSite, and thereafter run my migrate commands.

To add an additional Content Store to TeamSite, you need to execute the following;

1. Browse to the file iw.cfg (On  Solaris/Linux this is located in /etc/.  On Windows iw-home/etc/)
2. Add the following lines to the file under the [iwserver] section
   

   store_directory_new-store=/local/data/interwoven/new-store
   store_comment_new-store=New TeamSite Store

   The 1st line names the store and points to the location of the new store.  The 2nd line is optional, but adds comments to the store

3. Save the file and do a iwreset
4. Navigate to iw-home/bin and run the command iwstoreadm -a new-store (new-store is the name of the content store name inputted in point 2)

5. You should now get a message appearing store has been added.
   
6. You can further verify this by running the command,
   
   iwstoreadm -l (This will display all active stores TeamSite are pointing to with comments)
   
7. You now have another content store added to TeamSite