OLE Server Has Failed Error
Moderators: chulett, rschirm, roy
OLE Server Has Failed Error
Hi,
When I'm trying to edit the transformer stage properties I'm getting a pop-up message stating,
" (40503) A call to an OLE server has failed, or a runtime error occured within the OLE server itself"
How can I get rid of this.
Thank You
Regards - c341
When I'm trying to edit the transformer stage properties I'm getting a pop-up message stating,
" (40503) A call to an OLE server has failed, or a runtime error occured within the OLE server itself"
How can I get rid of this.
Thank You
Regards - c341
It's a bug in the Client, some sort of .NET issue I assume. We see these once in a great while. The best you can do is clean up the mess when it crashes and start over again from your last saved session.
Unless you are seeing this on a more frequent basis? If it is reproducible, you may need to reinstall either the Client or perhaps just the .NET framework again.
Unless you are seeing this on a more frequent basis? If it is reproducible, you may need to reinstall either the Client or perhaps just the .NET framework again.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
And sometimes it's just a glitch in OLE Automation. These are nearly impossible to diagnose without lots of stuff from MSDN and deep knowledge of how Windows works. Sometimes you will get a "failed to write to/at address 0xnnnnnnnnn" message, sometimes not.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
Some large organisations push software out to desktops overnight to keep them standardised. You can have a happy DataStage at the end of the day and come in the following morning to find OLE automation errors. The standardised changes being pushed out are not tested against DataStage client software and you can get old DLLS overwriting newer ones installed by DataStage. In theory an install should never replace a component with an older version but some of these automated tools do not follow that rule.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
-
- Participant
- Posts: 232
- Joined: Sat May 07, 2005 2:49 pm
- Location: USA
Hi Guys,
When we get the OLE error and we try to close the currently open job. It asks whether it needs to save the changes or not. I have been told to always say "No" to this, as they believe that it will corupt the current job, if we say "Yes". Is it true or Is it one of those Myths?
When we get the OLE error and we try to close the currently open job. It asks whether it needs to save the changes or not. I have been told to always say "No" to this, as they believe that it will corupt the current job, if we say "Yes". Is it true or Is it one of those Myths?
Thanks,
Naveen
Naveen
-
- Participant
- Posts: 3337
- Joined: Mon Jan 17, 2005 4:49 am
- Location: United Kingdom
-
- Participant
- Posts: 232
- Joined: Sat May 07, 2005 2:49 pm
- Location: USA