Upgraded from OD 6.0 to 6.1 and it broke DD deployments to sql 2000

I recently upgraded from OD 6.0 to 6.1 and now DD deployments don’t consistently update SQL 2000 tables. They work for the most part if I bounce the sql server but they seem to diminish the more times I run them. If this sounds familiar to anyone I would certainly enjoy hearing from them. Thank You

Find more posts tagged with

Comments

nakumar

Any particular error you had seen in the log, when the DD deployments are broken?

Ambuj

I recently upgraded from OD 6.0 to 6.1 and now DD deployments don’t consistently update SQL 2000 tables. They work for the most part if I bounce the sql server but they seem to diminish the more times I run them. If this sounds familiar to anyone I would certainly enjoy hearing from them. Thank You

There must be some trend as when they are not working.

Did you get any error in logs?
Which TS n OS versions you are working on?

Phanie

Can you attach the error messages you get in the logs and also what do you mean by DD deployments doesn't consistently update SQL 2000 tables. Does that mean few fields are being updated or is it few attempts are succesful and few or not. Also it would be nice if teamsite version is also mentioned

--
Phanie

Migrateduser

We're running TS 6.5 SP2. Everything worked fine with OD 6.0. FYI I have version 6.5.0 specified in the deploy.cfg and daemon_port set in odbase.xml. In regards to updating SQL tables it's sporadic, sometimes it works sometimes it doesnt but when it doesn’t I often see it hung on acquire latch in the micro logs. We're not using eventreporting so I didn’t make necessary changes after upgrade. I'm going to cut down the ipl file to deploy just one workarea to try and isolate any workarea issue however I have seen the following errors in logs currently:
1.)
ENG: 2008-01-07 13:34:12 EST GMT-05:00 Proceed to execute the database deployment
DBD: Deployment : ea-to-db
DBD: **WARN** Smiley Frustrated

ubstituteParameters 104 Replacing undefined parameter $area_vpath with empty string
DBD: **ERROR**:com.interwoven.dd100.dd.TTeamSiteEACfg 103 TeamSite element does not specify a TeamSite area
2.)
DBD: ERROR:Exception occured while executing deployment [ea-to-db]: com.interwoven.ju100.util.TFileSystemElement is in error state - unable to initialize session with null (Unable to establish connection with server)
DBD: ERROR:
java.lang.IllegalArgumentException: com.interwoven.ju100.util.TFileSystemElement is in error state - unable to initialize session with null (Unable to establish connection with server)

Not sure if this matters but this is a vmware win2003 server? I'll post a log after deploying a single workarea that fails. I must also mention at times when things seem to be going good the OD service just quits on me.

Migrateduser

The issue has been resolved so I'm posting the fix in the event anyone else encounters similar issues after upgrading to OD 6.1. Per Interwoven support: For the new TcpTimedWaitDelay Registry entry we recommend that you tune it to 20 seconds rather than the 120 stated in the readme for the patch. The problem is that ports are staying open and aren’t available for subsequent data/file transactions. The change has fixed our issue and our deployments are now running as expected.