DSX is not importing properly

soumya5891 · Post by **soumya5891** » Fri Feb 10, 2012 11:11 am

I'm importing one DSX(with executable) from one environment to another environment. But the job didn't import,after a particular state it hangs.

But when I tried without executable and import then it imports properly.

Is there any problem with the DSX itself,but the other job with executable imported properly.

qt_ky · Post by **qt_ky** » Fri Feb 10, 2012 11:23 am

Was the DSX file edited at all, or in a bad way, or possibly corrupted upon export?

Does it contain any stage types that don't exist on the target server?

pandeesh · Post by **pandeesh** » Fri Feb 10, 2012 11:34 am

qt_ky wrote: Does it contain any stage types that don't exist on the target server?

This scenario i have faced once, and i got the error explicitly that "Stage type not found"

soumya5891 · Post by **soumya5891** » Fri Feb 10, 2012 2:03 pm

DSX file was not edited and I also tried for several time to compile the job and then take the DSX then deploy.But the same thing happens every time,after certain part of import it got hanged.

qt_ky · Post by **qt_ky** » Fri Feb 10, 2012 2:30 pm

Try taking the DSX file that hangs on import, and import it into the third, separate environment as a test. If you do not have another environment, open a support case and attach the DSX file in question. I will be curious to learn the results.

kandyshandy · Post by **kandyshandy** » Sun Feb 12, 2012 8:58 pm

Few things to check..

When you say it hung, how long did you wait to see whether it proceeds further or actually hung?
How many jobs (export/import) are we talking about here?
Did you check whether all jobs are in known status in source environment?

soumya5891 · Post by **soumya5891** » Mon Feb 13, 2012 2:13 am

It hung for almost 45 mins. And I have tried several time by compiling the job and taking DSX and then try to deploy that DSX.I'm taking about only one job here. A single DSX for a single job.

kandyshandy · Post by **kandyshandy** » Mon Feb 13, 2012 2:58 am

ok... try importing that job without executable and compile in the target environment!!

If that works, then there is something fishy in your DSX.

BI-RMA · Post by **BI-RMA** » Mon Feb 13, 2012 7:32 am

Try to export your job with executables and include dependent items. See wether there are additional items in the dsx-file. In a Parallel-Job this should not be the case.

soumya5891 · Post by **soumya5891** » Mon Feb 13, 2012 10:31 am

I have tried with executable then the problem occurs. But when I took the DSX without executable then it imported properly. I guess it is the problem with the DSX itself.

kandyshandy · Post by **kandyshandy** » Mon Feb 13, 2012 7:59 pm

But when I took the DSX without executable then it imported properly

You did not answer my question... read my last question..