nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Time Deployments Failing

SethHickel

I periodically have (last night it occured) time deployments (transactional, file list) fail. Last night was an example. When I look at the log (D:\Interwoven\OpenDeployNG\log) for the different servers in the replicationFarmSet I get pretty much the same thing as is below.

 Thread-28 entering commit
LIB: 2010-05-05 00:00:09  ***  Proceed 
LIB: 2010-05-05 00:00:09  *** fFailedCommitFromEngine   0 
LIB: 2010-05-05 00:00:09  COMMITTING Transactional Deployment
LIB: 2010-05-05 00:00:09  Receiver-ERROR: ERROR: commit-failed.
LIB: 2010-05-05 00:00:09  ERROR: Failed to deploy local_directory[.] of area[Y:\default\main\MyBranch\EDITION\ed_2923] for filelist[D:\Interwoven\TeamSite\tmp\filelist.534021.534047.20100505-000000.txt]
LIB: 2010-05-05 00:00:09  ERROR: Failed 1 of 1 filelists
ENG: 2010-05-05 00:00:09 EDT GMT-04:00 Thread-28 After COMMIT, res=-1
ENG: 2010-05-05 00:00:09 EDT GMT-04:00 Thread-28 exiting  commit

Also, if I look at the failed jobs from the Quick report and follow the link for the External Task ID I get the following error: "An unknown error has occurred on the server."

This morning the business was able to re-deploy the file without issue or failure,

I would love to track this down and know if there is any additional information available (logs, etc) that could help explain why this happens.

Thanks.

Find more posts tagged with

Comments

nipper

Any logs available from the receiver ?

SethHickel

Trying to get those ... I don't have the access to the receiving servers logs.

Migrateduser

You may also want to check the Windows Server Event Log as well to see if anything happened at deployment time.

SethHickel

You may also want to check the Windows Server Event Log as well to see if anything happened at deployment time.

Thanks - did that first thing - nothing but informational messages.

Adam Stoller

What DB are you using for the scheduler?
The OOTB one (which is not recommended for production usage) or something more robust?
Other things to check:

SethHickel

What DB are you using for the scheduler?

This is something I will have to look into. We use SQL server for the event subsystem. I honestly do not recall making any configurations changes for the scheduler (I inherited much of this). A quick look at the WF, Install and Admin documentation didn't provide much help.

This from my odbase.xml on my base server makes me think we are using OOTB. Is that correct? (Not sure why the code tag puts odd spaces in the output below)

    
schedulerProperties jdbcDriverClass="org.hsql.jdbcDriver"
dbUrl="jdbc:HypersonicSQL:\Interwoven\OpenDeployNG\db\schedDB"
dbUser="XXXYYYZZZ"
dbPassword=""

Adam Stoller

This is something I will have to look into. We use SQL server for the event subsystem. I honestly do not recall making any configurations changes for the scheduler (I inherited much of this). A quick look at the WF, Install and Admin documentation didn't provide much help.

This from my odbase.xml on my base server makes me think we are using OOTB. Is that correct? (Not sure why the code tag puts odd spaces in the output below)
    
schedulerProperties jdbcDriverClass="org.hsql.jdbcDriver"
dbUrl="jdbc:HypersonicSQL:\Interwoven\OpenDeployNG\db\schedDB"
dbUser="XXXYYYZZZ"
dbPassword=""

The forum code has been buggy for years and sporadically inserts spaces into 'code' text.
The above shows that you're using the OOTB Hypersonic DB which is not intended for production usage. If you look through the OD manuals you should see some stuff in there about how to configure it to use a different DB.
Although this might be a complete red-herring, it probably is worthwhile following it up just in case it solves your problem.

SethHickel

Although this might be a complete red-herring, it probably is worthwhile following it up just in case it solves your problem.

I agree. I plan on making this change.

Thanks.