Skip to Content

Which is the right log to trace failed attempts when accesing a QaaWS/BIWS?


One of our developers is trying to consumea WebI report published as a web service (BIWS). When he tries to read it it receives following error message

“There was no endpoint listening at https://bi.f4eda.local/dswsbobje/qaawsservices/biws?.. that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: The remote server returned an error: (403) Forbidden.”

This error usually occurs when brad credentials are not accepted by the server. Question is: how could we determine which credentials are submitted to the server.

We have started by increasing the level of tracing log of the web service application to HIGH but even after that we are not able to notice any failed attempt login on the log.

Do you think that the log mentioned here could do the trick?

1384988 - How to enable log4j tracing for Query As A Web Service (QAAWS) / Live Office in BO XI 3.x and Bi 4.x

Has anyone faced a similar need of tracing login attempts when using QaaWS/BIWS?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Apr 26, 2018 at 02:05 PM

    the address doesn't look right, unless you have changed the ports on web app server or are using non-default tomcat....
    so, are you sure this url is correct ?
    what happens when you go to https://bi.f4eda.local/dswsbobje ?

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 27, 2018 at 02:50 PM

    As Denis said, the port of the web service does not seem to be correct. Check which ports are configured (in the CMC under Applications / Web Services)

    Also, under Servers / WebApplicationContainerServer, make sure that the port is bound to the correct host name / IP of the BI server.

    Finally, check the web service properties of the published web service (BIWS) (WSDL URL, ....)


    You can see the login error / warning in the file


    and it will look like this (if you have wrong login information)

    |7B1B48D0FB3449FBB1F38804B9C2E0432|2018 04 27 17:28:56.906|+0200|Error| |>=|E| |wacs_WIN2012R2B42SP5.WebApplicationContainerServer| 6956|  77|http-bio-| |0|0|0|0|-|-|-|-|-|-||||||||||com.businessobjects.qaaws.internal.webi.WISessionMgr||makeSession() userName=xxxxxx auth=secEnterprise timeout=300 locale=de_DE
    com.crystaldecisions.sdk.exception.SDKServerException: Die Enterprise-Authentifizierung konnte Sie nicht anmelden. Überprüfen Sie, ob Ihre Anmeldedaten korrekt sind. (FWB 00008)
    Add comment
    10|10000 characters needed characters exceeded