Timeline for HTTP 503 error accessing Sharepoint excelservice.asmx through SOAP
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 30, 2013 at 19:03 | comment | added | Jesus Shelby | I would do a fiddler trace and see what is preceding this 503. If that doesn't yield any results then a network trace on both ends to view the entire communication period. The service is running, so I'm thinking you have an authentication issue possibly obscuring the situation. | |
| Aug 16, 2012 at 14:19 | comment | added | Briton.W | I have checked this option as well. I can access all of the UDF's I've created, the problem only occurs in the UDF that attempts to call the OpenWorkbookForEditing() function and as the stack trace indicates, the error occurs on the SOAP call. | |
| Aug 16, 2012 at 5:45 | comment | added | ArkoD | In Excel services application ,when you create trusted data locations settings you can also check the option "children trusted" and have the trusted location to be your site collection. This authorizes all child sites and lists to use user defined functions. | |
| Aug 14, 2012 at 15:00 | comment | added | Briton.W | I have done the above. The problem isn't with the excel service in general, but only when I try to access it through a SOAP call. Additionally, I can access the WSDL both programmatically and through the browser but making a call to any of the listed functions is when it fails. | |
| Aug 14, 2012 at 9:49 | history | answered | ArkoD | CC BY-SA 3.0 |