Getting error - Target path unavailable.Will keep checking.

Hi,

We are executing opendeply file programatically.

/iw-home/OpenDeployNG/bin/iwodstart odfolder/move_delete_opendeploy.xml -inst 2103636 -k filelist=2103636_delete_list_move.txt

We ar getting following error in the loop -
Target path unavailable.Will keep checking.
Target path unavailable.Will keep checking.
.
.
.
ERROR: Path registry check timed-out/cancelled/error

When we are calling this config file directly , working fine. But calling from another opendeploy trnsaction gettting this error.
Any idea when this error comes.

Thanks in advance.
-Vijay

Find more posts tagged with

Comments

motlnt

Hi,

We are executing opendeply file programatically.

/iw-home/OpenDeployNG/bin/iwodstart odfolder/move_delete_opendeploy.xml -inst 2103636 -k filelist=2103636_delete_list_move.txt

We ar getting following error in the loop -
Target path unavailable.Will keep checking.
Target path unavailable.Will keep checking.
.
.
.
ERROR: Path registry check timed-out/cancelled/error

When we are calling this config file directly , working fine. But calling from another opendeploy trnsaction gettting this error.
Any idea when this error comes.

Thanks in advance.
-Vijay

This might be a firewall issue.
Can you share the move_delete_opendeploy.xml?

Vijay_Lnt

Hi,

Thanks for your reply.
Actual scenarios is like this -
1) In the workflow we are executing one ipl as external task.

2) In this external task are calling one open deploy config as below -

my $fileName = "XX/XX_move_opendeploy.xml";

my $opendeploycmd= "D:/iw-home/OpenDeployNG/bin/iwodstart $fileName -inst $taskId -k \"sourcearea=$soruceFolder\" -k \"targetarea=$targetFolder\" -k \"job_id=$jobId\" -k \"task_id=$taskId\" -k \"workarea=$workarea\" -k \"tmpFolder= $soruceFolder\"" ;

3) From this xml we are calling another ipl.

<script cmd='d:\iw-home\iw-perl\bin\iwperl.exe

\iw-home\local\bin\XX\XX_mrd_move_changes.ipl $job_id $task_id $workarea "$targetarea" "$tmpFolder"' async="no"/>

4) And again from this second ipl we are calling another open deploy config file -
my $fileName = "XX/XX_move_delete_opendeploy.xml";
my $opendeploycmd= "D:/iw-home/OpenDeployNG/bin/iwodstart $fileName -inst $job_id -k filelist=$deleteFileList";
(Attaching both the config files for your ref)

Same code works in one environment but throwing above error in another environment.
And target in both XMLs is also different.

Kindly let me know if you need any other information.

Thanks in advance.
-Vijay

Vijay_Lnt

This might be a firewall issue.
Can you share the move_delete_opendeploy.xml?

An actual scenario is like this -
1) In the workflow we are executing one ipl as external task.

2) In this external task we are calling one open deploy config as below -
my $fileName = "XX/XX_move_opendeploy.xml";
my $opendeploycmd= "D:/iw-home/OpenDeployNG/bin/iwodstart $fileName -inst $taskId -k \"sourcearea=$soruceFolder\" -k \"targetarea=$targetFolder\" -k \"job_id=$jobId\" -k \"task_id=$taskId\" -k \"workarea=$workarea\" -k \"tmpFolder= $soruceFolder\"" ;

3) From this xml we are calling another ipl.
cmd='d:\iw-home\iw-perl\bin\iwperl.exe

\iw-home\local\bin\XX\XX_mrd_move_changes.ipl $job_id $task_id $workarea "$targetarea" "$tmpFolder"'

4) Again from this second ipl we are calling another open deploy config file - XX_move_delete_opendeploy.xml

as below –
my $fileName = "InsideMarsh/inside_marsh_move_delete_opendeploy.xml";
my $opendeploycmd= "D:/iw-home/OpenDeployNG/bin/iwodstart $fileName -inst $job_id -k filelist=$deleteFileList";

I am attaching both the config files for your reference.
Same code is working in one environment but throwing above error in another environment.

Any idea??

Thanks in advance….
- Vijay

Migrateduser

Did you check in the ipl if you are getting all the parameters with correct values? If yes, try putting a usesr that should be used for running the script in your od xml as follows -

<script cmd='d:\iw-home\iw-perl\bin\iwperl.exe

\iw-home\local\bin\XX\XX_mrd_move_changes.ipl $job_id $task_id $workarea "$targetarea" "$tmpFolder"' async="no" as="xyzuser" />

jayantb

HI Sam1,

I am replying on behalf of Vijay. I couldn't see your full reply. Can you please reply to this post again with your od xml suggestion.

Thanks in advance.

Adam Stoller

[...]
my $opendeploycmd= "D:/iw-home/OpenDeployNG/bin/iwodstart $fileName -inst $taskId -k \"sourcearea=$soruceFolder\" -k \"targetarea=$targetFolder\" -k \"job_id=$jobId\" -k \"task_id=$taskId\" -k \"workarea=$workarea\" -k \"tmpFolder= $soruceFolder\"" ;

3) From this xml we are calling another ipl.
<dnrDeployment location="source" when="after" state="success">
<script cmd='d:\iw-home\iw-perl\bin\iwperl.exe \iw-home\local\bin\XX\XX_mrd_move_changes.ipl $job_id $task_id $workarea "$targetarea" "$tmpFolder"' async="no"/>

4) And again from this second ipl we are calling another open deploy config file -
my $fileName = "XX/XX_move_delete_opendeploy.xml";
my $opendeploycmd= "D:/iw-home/OpenDeployNG/bin/iwodstart $fileName -inst $job_id -k filelist=$deleteFileList";
(Attaching both the config files for your ref)

Same code works in one environment but throwing above error in another environment.
And target in both XMLs is also different.

Kindly let me know if you need any other information.

Thanks in advance.
-Vijay

What do you mean by "works in one environment but throwing above error in another environment"? Are you talking about two different servers? two different workflows? two different deployment configurations? etc.

Also - what versions of TeamSite and OpenDeploy are you using (including service pack and patch information)?

My initial suggestion is to replace the use of:

/iw-home/OpenDeployNG/bin/iwodstart

with

/iw-home/OpenDeployNG/bin/iwodcmd start

in both places and see if that resolves the issue - beyond that, if the problem persists - I think you need to provide more information about when your implementation works and when it fails and try to define all the differences between the two.

Migrateduser

HI Sam1,

I am replying on behalf of Vijay. I couldn't see your full reply. Can you please reply to this post again with your od xml suggestion.

Thanks in advance.

Try adding as="your_user_id" attribute in the script tag in the deployment XML.