Target path not available error-od6.02

Hi,
I am using OD6.02 version. When i deploy a job, the log shows an error.

ENG: 2005-05-29 23:23:35 PDT GMT-07:00 Thread-71 Target path unavailable. Will keep checking.

Can anyone help me out with this.

Thanks,
Madan

Find more posts tagged with

Comments

megamala

I am also getting same error. Could you tell me how you solved the issue

ENG: 2006-06-01 15:44:53 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:44:58 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:03 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:08 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:13 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:18 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:23 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:28 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:33 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:38 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:43 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:48 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:53 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:58 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:46:03 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:46:08 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.

Amit_LnT

I am also getting same error. Could you tell me how you solved the issue

ENG: 2006-06-01 15:44:53 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:44:58 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:03 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:08 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:13 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:18 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:23 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:28 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:33 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:38 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:43 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:48 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:53 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:45:58 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:46:03 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.
ENG: 2006-06-01 15:46:08 EDT GMT-04:00 Thread-85543 Target path unavailable. Will keep checking.

Hi Frnds,
Same issue here.. Were you able to find the solution. If yes, pelse post.
Apprecite ur help.

nipper

It typically happens when the receiver is running out of room or resources to do a true transactional deployment. If you run 3 large deployments, transactional, the temp files OD creates can get quite large.

How is the disk space on the receiver ?

Adam Stoller

It typically happens when the receiver is running out of room or resources to do a true transactional deployment. If you run 3 large deployments, transactional, the temp files OD creates can get quite large.

How is the disk space on the receiver ?

It may not be a space issue - just two (or more) transactional deployments to the same target area where the first one(s) are taking a long time to complete ... the transactional deployment will create a .iwold and .iwnew version of the directories to which it is deploying, and OD (apparently) is waiting until those get cleaned up before starting the next transactional deployment that will go to the same target directory.

Another possibility - along the same lines - is a transactional deployment that failed or was killed and was thus unable to clean up after itself - leaving behind the .iwold and .iwnew directories and thus preventing the next transactional deployment from starting ... For this, I suggest finding some time when no deployments are currently active and searching the target root for files and directories that have .iwold and .iwnew extensions - if you find them - remove them, and then re-try your deployment(s).

Amit_LnT

Hi Ghoti,
that is very useful.
I have asked a team member and he told me. He invoked 3 deployments and each deployment has two transactional deployments. When the deployment started, he by mistake deleted the target directories and since then we ran into the problem.
But then I restarted the service and it got resolved.

Thanks for the help.
-Amit