Page 1 of 1

Unable to Open the Jobs in DataStage Designer

Posted: Wed Mar 22, 2006 3:15 am
by Latha
Hi,

I am getting the following Error when I am trying to connect to DataStage Server (5.1).
Run Time Error "5": Invalid Procedure call or Argument.
After clicking on OK, I am able to view the Datastage jobs List in Designer, but unable to open any of the jobs.

Please help me on this.

Thanks.

Posted: Wed Mar 22, 2006 3:49 pm
by ray.wurlod
Welcome aboard. :D
This error is occurring on the client side, which may indicate a bad installation of the DataStage client(s). Can you see the job names in Director and/or Manager? Does it work from a different PC?
The easiest "solution" may be to uninstall then re-install the DataStage clients on that machine.
Is it running Windows XP? You may need a patch.

Reinstalled, still having the same problem

Posted: Thu Mar 23, 2006 5:43 am
by Latha
[quote="ray.wurlod"]Welcome aboard. :D
Hi,

I reinstalled DataStage client tools in my machine. But still facing the same problem. Yaah, its working from a different PC. O/S is WIndows XP Professional, 2002, SP 2.
Can you advise me on this.

Thanks,
Latha

Posted: Thu Mar 23, 2006 6:00 am
by ArndW
Is this PC on another network? Can you go to a DOS windown and either ping or tracert or telnet to the server machine?

Posted: Thu Mar 23, 2006 6:02 am
by kumar_s
Arnd - Latha able to view the jobs in Designer.
Perhaps she may need a patch for the machine.

Posted: Thu Mar 23, 2006 6:05 am
by ArndW
Ahh - I missed that; thanks. I thought it might be a connectivity issue.

Latha - are you logging into the Designer with the same userid on your machine (which isn't working) and on the other (which is)? If not, does your userid/login work on the other client PC?

Posted: Thu Mar 23, 2006 6:29 am
by kumar_s
Authentication issues should not even allow to enter into to designer, but Latha can log in but cannot not open the job. But can have a try with the right user id or dsadm.
Latha - What exactly happens if you try to open the job?

Posted: Thu Mar 23, 2006 6:31 am
by ArndW
If a job was created with a userid that had an incorrect umask setting, the it might be possible for one user to open and work with a job while others cannot.