Fatal error

Dedicated to DataStage and DataStage TX editions featuring IBM<sup>®</sup> Service-Oriented Architectures.

Moderators: chulett, rschirm

Post Reply
har
Participant
Posts: 118
Joined: Tue Feb 17, 2004 6:23 pm
Location: cincinnati
Contact:

Fatal error

Post by har »

Hello,
One of PRD Job aborted due to this error:
Fatal Error: Fatal: <ns1:Fault xmlns:ns1="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode xmlns:ns1="http://xml.apache.org/axis/">ns1:HTTP</faultcode>
<faultstring>(500)Internal Server Error</faultstring>
<detail>
<string>return code: 500
Error 500:
</string>
</detail>
</ns1:Fault>

Ran this job againg after 30 min, and its ran sucessfully.
Any idea about this error or why this occurs....
Thanks,
Har
Har
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

There was a problem and someone fixed it. One of many Google results for that error message:

http://www.checkupdown.com/status/E500.html
-craig

"You can never have too many knives" -- Logan Nine Fingers
har
Participant
Posts: 118
Joined: Tue Feb 17, 2004 6:23 pm
Location: cincinnati
Contact:

Post by har »

Hello,
I really appreciate your approach,but this job is in production.I guess you know company's will have lot of procedues to buy a new software and it will take lof of time.I feel ver strong web service or xml stage is not causing this error,correct me if i wrong.
I mean is their alterante way to slove this issue.
Thanks,
Har
Har
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Reread the linked post. It's not a problem you can solve. Never implied there was any problem with your job - you simply called a web service that was unavailable for an unknown reason. You did about all you can do in that situation - unless you own the service, of course - wait and try again.
-craig

"You can never have too many knives" -- Logan Nine Fingers
eostic
Premium Member
Premium Member
Posts: 3838
Joined: Mon Oct 17, 2005 9:34 am

Post by eostic »

Craig is right --- without having any details on the formal DS errors, it's difficult to tell what might be happening. It would be useful though, if you could clarify what this job is doing --- you posted here in the RTI section, but this error is one that would more likely occur from one of the Web Services Pack stages...... is your situation using both? (ie.. an RTI job exposed as a web service that also calls a web service?)...where does this error show up? in the DS Director detail log?

Ernie
Post Reply