SAP Knowledge Base Article - Preview

2312762 - Design Studio login to clustered BI platform fails with 400 Bad Request errors


Using Design Studio 1.5/1/6 and login to the BI platform 4.1 SP7 cluster on a secure (SSL) loadbalanced deployment which comprises a loadbalancer and an IIS web server, the design studio login fails with below errors.

  • The deployment comprises of clustered and distributed BI 4.1 SP7 environment with Tomcat web tier and fronted by IIS web server and a standard loadbalancer with SSL implemented.
  • The server side backend processes are all running (Analysis Application designer) and CMC shows the design studio runtime.
  • With Design Studio, login with https loadbalancer URL (https://loadbalancer_FQDN/dswsbobje/services/Session): Failed with below error -
  • ParseError at [row,col]:[1,1] Message: Content is not allowed in prolog. 

  • If you skip on error window and login the second time or if you login without SSL in loadbalancer (http://loadbalancer_FQDN/dswsbobje/services/Session), following error is thrown- SOAP message MUST NOT contain a Document Type Declaration(DTD)

  • The same errors as above are thrown by design studio if we Login using direct Tomcat server HTTP / HTTPS URLS which failed with same error as before. 
  • After applying SAP Kbase 1985014 - Test Connection returns "Error: SOAP message MUST NOT contain a document Type Declaration(DTD)" in CR for Enterprise via HTTPS, error changed to below with https


  • Using the same Design studio, we can login to another standalone environment which also uses a loadbalancer and IIS redirection.
  • DS Support logs show following error details: ParseError at [row,col]:[1,1] Message: Content is not allowed in prolog.
  • HTTP traces using Fiddler or wireshar show following error :

    REQUEST from Design Studio

    POST /dswsbobje/services/BIPlatform HTTP/1.1
    Content-Type: text/xml; charset=UTF-8
    Cookie: JSESSIONID=xxxxxxxxxxxxxxxyyyyyyyyyyy; Path=/dswsbobje/; HttpOnly=null
    SOAPAction: ""
    User-Agent: Axis2
    Transfer-Encoding: chunked

    <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv=""><soapenv:Body><Get xmlns=""><SessionID xmlns="">xxxxxxxxxxxxxxxxxyyyyyyyyyyyyyyyyyyyyyyyzzzzzzzzzzzzzzzzzzzzzzzzzzzz2CSI_TENANT_ID%3D0|en|America/Los_Angeles|ANALYSIS AAD 1.0 </SessionID><Path xmlns="">query://{SELECT SI_NAME FROM CI_INFOOBJECTS WHERE SI_ID='23'}</Path><Options xmlns=""><ExportDependencies xmlns="">false</ExportDependencies></Options></Get></soapenv:Body></soapenv:Envelope>

    Response from Server

    HTTP/1.1 400 Bad Request
    Content-Type: text/html
    Server: Microsoft-IIS/7.5
    X-Powered-By: ASP.NET
    Date: Tue, 26 Apr 2016 16:08:37 GMT
    Content-Length: 11

    Bad Request





SAP BusinessObjects BI Platform 4.1 SP7
SAP Design Studio 1.6
Loadbalanced deployment with Apache Tomcat 7 Web tier.
IIS 7 - Tomcat 7 Redirector / AJP 1.3




SAP BusinessObjects Business Intelligence platform 4.0 ; SAP BusinessObjects Business Intelligence platform 4.1 ; SAP BusinessObjects Business Intelligence platform 4.2 ; SAP BusinessObjects Design Studio 1.5 ; SAP BusinessObjects Design Studio 1.6


Design studio BIP 400 Bad request IIS Tomcat redirect isapi redirect , KBA , bad_request , iis , design_studio , isapi , tomcat , ds , BI-RA-AD-BIP , Business Intelligence Platform Integration , BI-BIP-DEP , Webapp Deployment, Networking, Vulnerabilities, Webservices , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.