Page 1 of 1

Datastage job Compilation Failed with 40503 OLE error

Posted: Tue Nov 03, 2009 3:50 pm
by mandyli
Hi

In my project I have lot of jobs. Now If i compile or run any of my jobs.

I am getting following error

" (40503) A call to on OLE server has failed or , a run time error occurred with in the OLE itself)


Thanks
Man

Posted: Tue Nov 03, 2009 4:18 pm
by chulett
Are you on AIX by any chance? How many jobs is "a lot"?

Posted: Tue Nov 03, 2009 5:12 pm
by ray.wurlod
This is usually a problem entirely within the client. Does it occur with the same jobs on someone else's client machine? The solution may be as simple as re-starting your client machine or, at the next step, reinstalling your client software.

Posted: Tue Nov 03, 2009 9:02 pm
by mandyli
Hi Ray/Chulett,


Thanks for your mail.

using Sun OS.
Not only same job all the jobs.

Posted: Tue Nov 03, 2009 9:14 pm
by chulett
Let's see if we can get a clearer answer. Is this an issue just for you or does it happen to everyone? The answer will give us a better idea if this is a Client or a Server issue.

Posted: Thu Jun 09, 2011 3:47 pm
by gsbrown
This issue just occurred to me today. Restarting the client machine didn't help and had to resort to reinstalling the IIS client and now it's resolved.

Also, this error was only happening if I was logged into Windows. I could log into the Windows client machine as somebody else, log into DataStage as myself and I wouldn't get the error. The error seemed specific to the operating system logged in user. BTW, our client is running on a Windows 2008 Terminal Server.

Re: Datastage job Compilation Failed with 40503 OLE error

Posted: Thu Jan 03, 2019 12:18 am
by MIMO
hello
i have a same problem ? any chance to find the solution ?
and i have another problem
i loose the links when i save my jobs i dont know why ?

Posted: Thu Jan 03, 2019 5:26 am
by chulett
Usually best to start your own topic for problems rather than saying years later that you have "the same problem" as someone else with no details. Right now we don't even know what version you are running. The post before you noted their version of the problem was resolved by reinstalling the client, did you try that?

As to your other problem, definitely start a new (i.e. separate) post for that and provide details, please.