TeamSite Version: 6.7.1
Operating System: Windows Server 2003

I recently experienced a major issue with the TeamSite server, where by it was not displaying the TeamSite url on the browser.  I was getting a Apache error.

I scrolled through the TeamSite logs to find an error which was causing TeamSite not load correctly.  This can be seen below;

ERROR com.interwoven.livesite.iw.impl.CSBackingStoreService (com.interwoven.livesite.iw.impl.CSBackingStoreService:254) – Error while creating/updating branch: /iwadmin/main/livesite
com.interwoven.cssdk.common.CSException: (Insufficient space to complete operation)

This was found in iw-home/local/logs/ccsdk.log

Solution:

As you can see in the error there is insufficient space detected on the TeamSite Server.  To overcome this problem there are 2 options you have to get TeamSite back up and running

Option 1 – Add more memory to the server, and re-size the partition where TeamSite is installed.  This can be done with a partitioning tool software.  There are quite a few commercialware applications that can achieve the re-size of a partition.

Option 2 – Get a freeware application tool such as ccleaner to remove all unnecessary files on the server.  Also identify applications which are unnecessary and uninstall.  Once this is complete you will have save some space.  In conjunction with this you should also edit the file iw-home/etc/iw.cfg

and change the following line from;

disklowpercent=10

to

disklowpercent=5

Now on the command line do a iwreset – a to restart TeamSite.  TeamSite should now come back up and running and above the 5% threshold of disk space left rahter then the default 10%.  This should buy some time and allow your TeamSite server to run again.

Problem

You are trying to setup Derby database for use with the Interwoven Event SubSystem.

You have followed the installation instructions manual

You get the following error in the eventsubd.log when starting the Event Subsytem:
“Cannot create PoolableConnectionFactory”.

Potential Solution

Check where the testdb database file has been created as the default in the Interwoven instructions creates the db file in your current working directory. Derby looks for the database by default in it derby/bin

Other possible problems:

1. Check the database exists by connecting to it and doing a “show tables” as per the Interwoven instructions
2. Check the driver exists and is in the correct location (/usr/iw-home/eventsubsystem/lib/derbyclient.jar – is “374965″ in size for TS 6.7.1)

3. Check your configuration in “/usr/iw-home/eventsubsystem/conf/jmsconfignew.xml”

Should be as follows:

<DatabaseConfiguration>
<RdbmsDatabaseConfiguration
driver=”org.apache.derby.jdbc.ClientDriver”
url=”jdbc:derby://localhost:1527/testdb”
user=”usr”
maxActive=”10″
maxIdle=”5″
minIdleTime=”1800″
evictionInterval=”3600″ />
</DatabaseConfiguration>
ERROR

EVENTSUBD_HOME is set to /usr/iw-home/eventsubsystem
OpenJMS 0.7.6.1
The OpenJMS Group. (C) 1999-2004. All rights reserved.
http://openjms.sourceforge.net
org.exolab.jms.server.ServerException: org.exolab.jms.persistence.PersistenceException: org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory, cause:

java.sql.SQLException: The connection was refused because the database testdb was not found.
at org.apache.derby.client.am.SQLExceptionFactory.getSQLException(Unknown Source)
at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source)
at org.apache.derby.jdbc.ClientDriver.connect(Unknown Source)
at org.apache.commons.dbcp.DriverConnectionFactory.createConnection
(DriverConnectionFactory.java:82)
Caused by: org.apache.derby.client.am.DisconnectException: The connection was refused because the database testdb was not found.

Problem

You are seeing the following error in the TeamSite user interface and in the server logs:

“ILOG Teamserver is currently unavailable. Contact your system administrator for details.”

Potential Solution 

You may only need to restart the Interwoven Rules Service. 
You can do this on UNIX by the following commands:

 /etc/rc3.d/S15iw.rules stop

 /etc/rc3.d/S15iw.rules start 

Full Error Message 

com.interwoven.livesite.common.service.ServiceUnavailableException: ilog.rules.teamserver.model.IlrConnectException: javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server 

Problem

Had a really tricky problem where workflow was not calling OpenDeploy and giving an error “User name from csContextString is blank”.

Potential Solution

Do the following

1. /usr/iw-home/bin/iwsessionkeygen and then check in /usr/iw-home/private/etc that the passphrase file has a recent time stamp

2. Run the new version of this /usr/iw-home/CSF/AccessService/bin/iwsharedkeyfilegen

3. Then re-start the iwaccess service in /etc/init.d/iwaccess stop and /etc/init.d/iwaccess start

4. /usr/iw-home/bin/iwreset -a

Errors

The below was in the workflow errors:

API: 2008-12-03 17:11:35 GMT+00:00 ***WARNING – User name from csContextString is blank or null,
request app: APP_WORKFLOW

OpenDeploy Status Unknown. FAILED. Locating OpenDeploy service. Got OpenDeploy service
***ERROR – Caught exception in runIt(). Details: REQUEST_DENIED message:
REQUEST_DENIED Request denied: NO_USER_NAME Item: ,
Details: Got blank or no user name from CSContextString at
com.interwoven.deployapi.deploy.IWODServerAction.
getODAPIServerVersion(IWODServerAction.java:1437)
at com.interwoven.deployapi.deploy.IWODServerRemoterImpl.
getODAPIServerVersion
(IWODServerRemoterImpl.java:363) at

etc…

com.interwoven.ui.teamsite.workflow.task.URLExternalTaskCommand.execute
(URLExternalTaskCommand.java:109) at com.interwoven.ui.base.impl.command.
CommandHandler.doExecuteCommand(CommandHandler.java:917) at
com.interwoven.ui.base.impl.command.CommandHandler.
tryRunCommandDescriptor
(CommandHandler.java:753) java.lang.Thread.run(Thread.java:595)

Please check that the OpenDeploy server is running. [wasadm: 12/3/08 5:59:20 PM ]

etc…

Problem

OpenDeploy deployments are failing with the following type of errors:

Error during task execution: Production Deployment, message:
java.lang.NullPointerException *** START STACK TRACE ***
com.interwoven.livesite.rules.ilog.RuleSession.
<init>(RuleSession.java:77)
com.interwoven.livesite.rules.ilog.RuleSession.getContentSession
(RuleSession.java:285)
com.interwoven.livesite.rules.ilog.RuleAppUtils.getContentRuleAppArchives
(RuleAppUtils.java:221)
com.interwoven.livesite.rules.ilog.RuleAppUtils.getContentRuleApps
(RuleAppUtils.java:196)
com.interwoven.livesite.opendeploy.impl.OpenDeploymentServiceAdapter.
buildDeployment
(OpenDeploymentServiceAdapter.java:154)
com.interwoven.livesite.opendeploy.impl.OpenDeploymentServiceAdapter.
buildDeployments
(OpenDeploymentServiceAdapter.java:222)
com.interwoven.livesite.opendeploy.impl.OpenDeploymentServiceAdapter.
buildDeployments
(OpenDeploymentServiceAdapter.java:55)
com.interwoven.livesite.deployment.impl.BaseDeploymentService.
buildDeploymentList
(BaseDeploymentService.java:213)
com.interwoven.livesite.deployment.impl.BaseDeploymentService.deployFiles
(BaseDeploymentService.java:85)
com.interwoven.livesite.workflow.task.DeploymentTask.deployFiles
(DeploymentTask.java:82) *** END STACK TRACE *** [user: 12/15/08 1:56:11 PM ]

Potential Solution

Re-start the TeamSite Services including the rules service, it might be hung due to a port conflict or other issue.

Problem

The Site Publisher Sitemap is not loading in the user interface.

Potential Solution

Reset the user interface services via the iwreset -ui command (e.g) /usr/iw-home/bin/iwreset -ui

Errors seen

(Error in Action)
javax.servlet.ServletException: Java heap space
        at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:294)
        at org.apache.struts.actions.DispatchAction.execute(DispatchAction.java:187)
        at com.interwoven.livesite.common.web.action.BaseAction.execute(BaseAction.java:273)
        at com.interwoven.livesite.web.LivesiteAction.execute(LivesiteAction.java:78)
        at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
        at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
        at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
        at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
        at com.interwoven.livesite.spring.hibernate.web.filter.OpenSessionsInViewFilter.doFilterInternal(OpenSessionsInViewFilter.java:141)

Platform: Linux
TeamSite Version: 6.7.1

I was recently involved in a project where I was getting a constant error message appearing in my iwtrace.log (iw-home/local/logs).

The error casued TeamSite not to start correctly.  I was looking up reasons and solutions for the error, and found the below;

Cause:

TeamSite is reading over a 1000+ users and groups. Once a investigation was done on where this came from, it became apparent that the users and groups were for a requirement for a previous project.  Each time the server rebooted, the server would synchronise with the main server, so the configuration of 1000+ users and groups would continue to exist.

Solution:

- Remove group and users’ db on the server, along with reference to the users and group db in the file nscd, located in the /etc directory in the parent directory.
- Also the removal of Server synchronization with users and groups from the main server.

Making these changes helped to resolve the issue, with error message not appearing again

I was recently involved in a project where I was getting a constant error message appearing in my iwtrace.log (iw-home/local/logs).

I was looking up reasons and solutions for the error, and found the below;

Cause:

The error is caused by an attempt to run TeamSite on an NTLM domain. TeamSite no longer supports NTLM domains: you must run TeamSite on a Windows 2000 or later (Active Directory) domain.

Solution:

Add your TeamSite server to a Windows 2000 or later (Active Directory) domain then the error messages should go away.

Also, it is recommended to add the line set domain_list=<DomainName>
under the [iwserver] section of iw.cfg,
located in iw-home/etc.

<DomainName> is the list of domains not including the local machine name the local machine name. If domain_list is incorrect, then you will see a variety of error messages in the iwtrace.log (mostly referencing ADSI problems) and possibly even a server crash.

Platform: Linux
TeamSite Version: 6.7.1

I was involved in a recent project where each time the client logged out of TeamSite, they would get a log out error.  Initially we weren’t sure why the error was appearing.  After thorough investigation of the TeamSite logs I came across some errors/warnings in the file servletd_out.log (located in logs/iwui).  Errors included;

The errors did not actually say that there was something wrong in respect to the solution given below, but it got me thinking in respects to the locations it mentioned in the log. I did a search of the location;

/iw-home/servletd/work/Catalina/localhost/iw-cc/org/apache/jsp/teamsite/common/

compared them to a working TeamSite directory from Interwoven Support.  I found the files;
start_jsp.class,
start_jsp.java
were missing in that location.

Solution:

- Get the missing files from Interwoven Support and place them in the location above
- Reset user & group permissions from the directory /iw-home/servletd/work/ onwards to the user iwui and group nobody

TeamSite now logged out with no errors

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