OpenDeploy Fails with iwodstart.ipl at line 110

... and virtually no logging info is recorded. That is, od.err is not touched when this happens and the two log files that are created or appended to as a result of the deployment do not state anything of consequence. Event logging is also turned off because of the OpenJMS bug.

I'm using the DataDeploy module for OpenDeploy 6.0.1/Windows 2003. That said, I can run the query just fine in Toad -- no errors whatsoever. So, why would OpenDeploy bug out like this and best of all, not report anything?

Dave

Environments:
(1,2) TS6.5, TS6.5SP1 on W2K3
(3) Vignette V7 Portal on Solaris 9

Find more posts tagged with

Comments

Adam Stoller

iwodstart.ipl was written initially as a means of reliably getting exit status values from OD 5.5.1 on Windows.

I would recommend NOT using iwodstart.ipl and instead using: iwodcmd start

It's possible that iwodstart.ipl shouldn't be shipped anymore (it predates iwodcmd)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

Yeah, in just looking at the script, it seems kinda hokey but I'm doing most of my deployment with using iwodcmd start and I've tried this one the same way. I see the same results via iwodcmd start, as well, however.

Dave

Environments:
(1,2) TS6.5, TS6.5SP1 on W2K3
(3) Vignette V7 Portal on Solaris 9

Adam Stoller

Well - if the problem happens with iwodcmd start - then it's likely to be a "real" problem and thus it would probably help if you provided a lot more detailed information.

What gets displayed on the command line after attempting to run the deployment?
What (if anything) goes into IWODHOME/od.log?
What (if anything) goes into the odbase.log ?
What (if anything) goes into the deployment log(s)?

Can you post the deployment configuration?
etc., etc., etc.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

I just tried doing some much simpler functions with DD and it still does not work. I reinstalled OD+DD today but turned OFF event reporting. I think something in my configuration is still pointing to OpenJMS. Here is what it says in od.log:


DD Home : C:\Interwoven\OpenDeployNG
args[0]:cfg=C:\Interwoven\OpenDeployNG\etc\daemon.cfg
args[1]:runmode=threadperbranch
args[2]ort=2345
args[3]:svrlogfile=C:\Interwoven\OpenDeployNG\log\TEAMSITE_odbase.log
numArgs=4
Server log file C:\Interwoven\OpenDeployNG\log\TEAMSITE_odbase.log
Log Directory is: C:/Interwoven/OpenDeployNG/log
DriverManager.initialize: jdbc.drivers = null
JDBC DriverManager initialized
registerDriver: driver[className=org.hsql.jdbcDriver,org.hsql.jdbcDriver@9ffe3f]
DriverManager.getConnection("jdbc:HypersonicSQL:C:\Interwoven\OpenDeployNG\db\schedDB")
    trying driver[className=org.hsql.jdbcDriver,org.hsql.jdbcDriver@9ffe3f]
getConnection returning driver[className=org.hsql.jdbcDriver,org.hsql.jdbcDriver@9ffe3f]
DriverManager.getConnection("jdbc:HypersonicSQL:C:\Interwoven\OpenDeployNG\db\schedDB")
    trying driver[className=org.hsql.jdbcDriver,org.hsql.jdbcDriver@9ffe3f]
getConnection returning driver[className=org.hsql.jdbcDriver,org.hsql.jdbcDriver@9ffe3f]
Database Deployment error state: false

and HERE is the abundant information presented in od.err (yes, this is the entire file):


**ERROR**:com.interwoven.dd100.dd.TConfiguration        103     Parser error: Content is not allowed in prolog.

I'm convinced that it's something in my configuration but it's kind of like looking for the proverbial needle in the haystack.

Dave

Environments:
(1,2) TS6.5, TS6.5SP1 on W2K3
(3) Vignette V7 Portal on Solaris 9