Having trouble getting your ADO.NET Data Service running? Getting cryptic error codes in your browser, for instance HTTP error 500? Here is an article on debugging ADO.NET Data Services. In short, it tells you how to get more informational messages in your browser, so that you can find out what is really going wrong. In my case, it was nothing more than the ASP.NET worker process did not have permissions in SQL Server--easily resolved once I knew what was actually going wrong.
Note there are two steps, and you may need to do both:
1) Set UseVerboseErrors to true in the ServiceConfiguration, and
2) Configure your Servicebehavior with the IncludeExceptionDetailInFaults attribute.
No comments:
Post a Comment