InternalServiceFault error when calling SubmitGenerateReport action

Ashwani Chandra 6

From Saturday onwards, while calling the https://reporting.api.bingads.microsoft.com/Api/Advertiser/Reporting/v13/ReportingService.svc?singleWsdl endpoint with the SubmitGenerateReport action, I am getting the following error

{:error=>{:fault=>{:faultcode=>"a:InternalServiceFault", :faultstring=>"The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs."}}}

<Savon::SOAPFault: (a:InternalServiceFault) The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.>

(a:InternalServiceFault) The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.

I haven't changed anything from my end.

We have tried it with the following with https://reporting.api.bingads.microsoft.com/Api/Advertiser/Reporting/v13/ReportingService.svc?wsdl and https://api.bingads.microsoft.com/Api/Advertiser/Reporting/v13/ReportingService.svc?singleWsdl endpoints with similar results.

This is blocking the reporting for our customers. Can you please let us know how we can fix this?

Henry Chan 1 Reputation point

2022-10-24T08:07:17.777+00:00

We also have been encountering this issue starting early Friday morning (BST) and it is effecting several services, including the ReportingService. I've been in contact with support (albeit a bot) and they think it is related to the reporting data issue which still doesn't seem fixed https://status.ads.microsoft.com/.

Posting here to hopefully get some traction as this is having a negative impact on us as a business.

Here's the SOAP log that we are recieving (attached file, seems like there's a character limit on comments):
253748-report-service-logs.txt

We've ruled out that it isn't actually a credential error as this does not occur when we hit CustomerManagementService and the account is active.
Ashwani Chandra 6 Reputation points

2022-10-24T22:57:32.207+00:00

Hi Henry,

the status is up, but we are still facing the same issue. Are you still facing the same issue as well?
Henry Chan 1 Reputation point

2022-10-25T07:38:03.203+00:00

we are still seeing the same error for the ReportingService :(
Ashwani Chandra 6 Reputation points

2022-10-25T07:39:11.433+00:00

Hi Henry,

Are you seeing a:InternalServiceFault error or error related to authentication?
Henry Chan 1 Reputation point

2022-10-25T07:41:48.077+00:00

Yes we are seeing a 105 error. Never used to happen until last Friday. We use the bulk service for uploading offline conversions which also saw a similar issue, but that started working as of the 23rd.
Ashwani Chandra 6 Reputation points

2022-10-25T07:45:44.967+00:00

In the logs that you have shared, it says Invalid client data. Check the SOAP fault details for more information.

It might be that your authentication token or something else in the soap header is wrong.
Henry Chan 1 Reputation point

2022-10-25T07:51:27.783+00:00

seems strange that it's the auth token though, as it works for all the other services except this one (again used to work, haven't made any changes). We are using the bing ads python sdk for making the interactions, might do a log comparsion between a successful call against this.
Ashwani Chandra 6 Reputation points

2022-10-25T07:53:04.29+00:00

Okay.

We seem to be getting a different error. We are using savon_client library in ruby to get the data. worked perfectly till Friday, since when we starting seeing these random errors.
Ashwani Chandra 6 Reputation points

2022-10-25T07:53:38.72+00:00

Would it be possible for you to share a POSTMAN request or something of that sort? We can compare.

I am also trying to convert it to a postman request
Henry Chan 1 Reputation point

2022-10-25T09:16:40.983+00:00

that file that I sent contains the soap request I believe. Our account manager got us through to tech support and it turns out that the xml body is not correct, for whatever reason auth tokens are there twice.

I've played around with it (removing the duplicate) and that seems to have fixed it for us
Ashwani Chandra 6 Reputation points

2022-10-25T09:18:06.607+00:00

Okay.

I'm with tech support now as well.

Can you please share the final soap envelope and what is working for you? That will help us fix the issue
Henry Chan 1 Reputation point

2022-10-25T09:29:55.987+00:00

That's good to here.

I have attached the soap envelope that the sdk generates (bad_soap) and the modified one (good_soap)253829-bad-soap.xml

253727-good-soap.xml
Ashwani Chandra 6 Reputation points

2022-10-25T09:32:51.363+00:00

Thanks a lot. I am checking this out

Share via

InternalServiceFault error when calling SubmitGenerateReport action

Your answer