Reverse Deployment limitation

andyRDX

Is there any directory specific limitations for the reverse deployments?

I discovered that when I am doing a reverse deployment, using a deployment descriptor inside folder [OpenDeploy-Dir}/conf/{someDir} the deployment fails.

OD Base logs:
ENG: 2008-04-07 17:05:50 PDT GMT-07:00 Thread-50 ***ERROR - I/O error with [/opt/local/{ts-user}/iw-home/OpenDeployNG/log/dd/src.dd_reverse.{receiver-Server}-def.{TeamSite-Server}.to.{receiver-Server}-20014.log.mf]: File not found

OD Receiver log:
ENG: 2008-04-07 17:01:50 PDT GMT-07:00 Thread-377 ***ERROR - Failed writing internal config file C:\Interwoven\OpenDeployNG\db\.{someDir}/dd_reverse.{receiver-Server}-def.{receiver-Server}-20014.reverse. Got file I/O exception. Detail: C:\Interwoven\OpenDeployNG\db\.{someDir}\dd_reverse.{receiver-Server}-def.{receiver-Server}-20014.reverse (The system cannot find the path specified)
ENG: 2008-04-07 17:01:50 PDT GMT-07:00 Thread-377 Failed logging internal config file [C:\Interwoven\OpenDeployNG\db\.dd/dd_reverse.{receiver-Server}-def.{receiver-Server}-20014.reverse]

ENG: 2008-04-07 17:01:50 PDT GMT-07:00 Thread-377 ** Simulate flag = false
ENG: 2008-04-07 17:01:50 PDT GMT-07:00 Thread-377 ** Synchronous flag = false
ENG: 2008-04-07 17:01:50 PDT GMT-07:00 Thread-377 exiting initial
ENG: 2008-04-07 17:01:50 PDT GMT-07:00 Thread-377 entering task-failed
ENG: 2008-04-07 17:01:50 PDT GMT-07:00 Thread-377 Path registry checking is disabled
ENG: 2008-04-07 17:01:50 PDT GMT-07:00 Thread-377 exiting task-failed
ENG: 2008-04-07 17:01:50 PDT GMT-07:00 Thread-377 entering task-failed
ENG: 2008-04-07 17:01:50 PDT GMT-07:00 Thread-377 exiting task-failed
ENG: 2008-04-07 17:01:50 PDT GMT-07:00 Thread-377 entering task-failed
ENG: 2008-04-07 17:01:50 PDT GMT-07:00 Thread-377 exiting task-failed
ENG: 2008-04-07 17:01:50 PDT GMT-07:00 Thread-377 entering task-failed
ENG: 2008-04-07 17:01:50 PDT GMT-07:00 Thread-377 still waiting for 0
ENG: 2008-04-07 17:01:50 PDT GMT-07:00 Thread-377 Job ID=m11 Deployment leg=dd/dd_reverse.{receiver-Server}-def.{receiver-Server}-20014 Elapsed Time=0 ms {{{
ENG: 2008-04-07 17:01:50 PDT GMT-07:00 Thread-377 End logfile [C:\Interwoven\OpenDeployNG\log\dd\rcv.dd_reverse.{receiver-Server}-def.{TeamSite-Server}.to.{receiver-Server}-20014.log]


But if I use the same Deployment descriptor from {OpenDeploy-Dir}/conf Directory, the Deployment works perfectly. So the OD base and receiver configuration as well as the deployment descriptor is fine.
If you see the Receiver log, you will see that the od receiver is trying to create the temp deployment file in
"C:\Interwoven\OpenDeployNG\db\.{someDir}/dd_reverse.{receiver-Server}-def.{receiver-Server}-20014.reverse." and is getting a I/O exception.

Thats why I am asking whether the OD reverse deployment can only work from {OpenDeploy-Dir}/conf Directory.
In past I done many forward deployment from sub-folders inside {OpenDeploy-Dir}/conf folder and that works fine, I just faced this problem during reverse deployment only.

Adam Stoller

I don't know of any such limitation - but I think this is a perfect kind of case to enter with Interwoven Support. You might have run into an aspect of the product that got missed in the test suite.