500 just means your app is breaking.
There is some error in logic, or an uncaught exception, or something.
Otherwise troubleshoot and debug as any app error.
Eg, invoke the same logic from an ASP.NET webpage (not webservice) and you
should be able to see the errors (if the page is local).
-Dino
"JP" <an*******@discussions.microsoft.com> wrote in message
news:79**********************************@microsof t.com...
I have a web service that returns a XML dataset, but when i invoke the WS,
i get the http 500 internal server error msg
The stored procedure retrives data just fine in .NEt environment and in
Enterprise Manager. The user in the connection string has permission to
execute the SP.
Any ideas?