iSerg


Hi All,

I could see that that question already arised more than once... but I didn't find the following problem:

Request:

< xml version="1.0" encoding="UTF-8" ><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns8256="http://tempuri.org"><SOAP-ENV:Header><ApiUserAuthHeader xmlns="http://adcenter.msn.com/syncapis">
<UserName>XXXXX</UserName>
<Password>XXXXX</Password>
<UserAccessKey>XXXXX</UserAccessKey>
</ApiUserAuthHeader>
</SOAP-ENV:Header><SOAP-ENV:Body><RequestBIReport xmlns="http://adcenter.msn.com/syncapis"><APIFlags>0</APIFlags><request xsi:type="KeywordPerformanceReportRequest"><StartDate>2006-12-07</StartDate><EndDate>2006-12-07</EndDate><ReportDates><dateTime>2006-12-07</dateTime><dateTime>2006-12-07</dateTime></ReportDates><ReportLanguage>English</ReportLanguage><Format>CSV</Format><AllNone>false</AllNone></request></RequestBIReport></SOAP-ENV:Body></SOAP-ENV:Envelope>

Response:

"Server was unable to process request. ---> |-400001|-1|API unauthorized access|"

While the login is correct... 100%...

Can anybody help with this problem

Thank you

Serg




Re: Reporting Service again...

Nitin Hegde


If you are using v3 please change your namespace from http://adcenter.msn.com/syncapis to http://adcenter.microsoft.com/syncapis and that should fix your problem.





Re: Reporting Service again...

iSerg

I have changed the namespace as a result of that I have got the error: Server was unable to process request. ---> Object reference not set to an instance of an object






Re: Reporting Service again...

Ludo-R

Are you using JAVA Do you have the SSL certificate for the reporting system




Re: Reporting Service again...

Thai_edmunds

I use Apache Axis on Linux, and i ran into the same problem.

Here is the errors that I got:

Exception in thread "main" javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: No trusted certificate found
at com.sun.net.ssl.internal.ssl.BaseSSLSocketImpl.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SunJSSE_az.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SunJSSE_az.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SunJSSE_ax.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.j(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.b(DashoA12275)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(DashoA12275)
at sun.net.www.protocol.https.HttpsClient.afterConnect(DashoA12275)
at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(DashoA12275)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(DashoA12275)
at com.edmunds.adcenter.client.ReportServiceClientKeyword.main(Unknown Source)
Caused by: sun.security.validator.ValidatorException: No trusted certificate found
at sun.security.validator.SimpleValidator.buildTrustedChain(SimpleValidator.java:304)
at sun.security.validator.SimpleValidator.engineValidate(SimpleValidator.java:107)
at sun.security.validator.Validator.validate(Validator.java:202)
at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(DashoA12275)
at com.sun.net.ssl.internal.ssl.JsseX509TrustManager.checkServerTrusted(DashoA12275)

I already updated the CA.

Please help





Re: Reporting Service again...

Ludo-R

Did you take the certificate from the reporting service It is not the same as the certificate to access the wsdl.



Re: Reporting Service again...

iSerg

I use PHP + NuSOAP.

Any ideas





Re: Reporting Service again...

iSerg

Anybody has response to this question



Re: Reporting Service again...

Nitin Hegde

Hi iSerg,

Can you please let me know if this is on the sandbox environment or the production environment. If this is on the sandbox environment we may have to check your login details.
Please send an email to the support team so that we can get more detail and troubleshoot in more depth.

Thanks.
NH