Skip to Content
Author's profile photo Jonathan Brown

BI 4.1 – Design-time query not available (WIS 00000) Error with some BEx queries

Hey Webi World.

I have been seeing a number of customers reporting the below error after upgrading to BI 4.1 so I wanted to release a few details to help those that experience this issue.

First of all, I want to say that it is quite early on in the investigation and it appears that there could be a few different causes for this high level error from Webi.  This post is more a heads up on the known resolutions and a simple work-around that can be implemented for users that are getting this error on critical reports.

A little background on what Design Time Service is can be read in John Mrozek ‘s great SCN blog post here: BI 4.1 on BW 7x Performance Improvements 


In short, the design time service allows the BICs connector to retrieve metadata about BEx query definition quicker. 

In BI 4.0, we didn’t use the Design Time (DT) service so certain workflows we’re slightly slower, but they worked pretty reliably.  In BI 4.1, we are finding that if a failure occurs in the DT function, then the end user is presented with an error and may not be able to continue.

So, if you do see this issue, I would follow the below steps to resolve it:

  1. Read John’s Blog post above and ensure that your BW system is patched up to the minimum or recommended levels.
    • BW 7.30 SP8 or BW 7.31 SP5+, plus all the SAP notes listed in his blog post OR
    • BW 7.30 SP10, 7.31 SP08 and 7.40 SP05 (versions that contain those notes)
  2. Read KBA –  1940100 – Error “Design-time query not available (WIS 00000)” using BICS connectivity with WebI in BI 4.1 to find out what other options you might have.  This KBA will be updated as new resolutions/issues are discovered
  3. Do an End to End trace by following Toby Johnston ‘s KBA: 1861180 – Customer instructions and best practice for collecting a BI Platform 4.x end to end trace 
    • Review the traces and find out what the cause of the failure is.  The error reported by Web Intelligence is a high level message and does not contain the details needed to actually identify the root cause.  You will want to look for an exception within the APS DSL Bridge logs that contains the stack trace from the BICs/JCO driver.
  4. Contact support and provide the traces. 😉

Hope this helps!

– Jb

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Henry Banks
      Henry Banks

      very important info, thanks for clearing this up for us!

      i closed the loop on this discussion thread here:



      Author's profile photo Former Member
      Former Member

      Hi Henry, could you help me with my problem? Adaptive  Processing Server (DSL Bridge) not found

      Author's profile photo Former Member
      Former Member


      The KBA is still noted as "Active".

      Is this or will this be fixed in any upcoming Service Pack or patch??



      Author's profile photo Jonathan Brown
      Jonathan Brown
      Blog Post Author

      We do have a developer reviewing this to see if there is something we can do at a code level to prevent this error.  In the meantime, disabling the design-time is the easiest solution.

      I will follow-up with the development contacts I have worked with in the past to see if they can provide an update.



      Author's profile photo chandra koduri
      chandra koduri

      Thank you so much Gielen As our problem solved 🙂 🙂

      Author's profile photo Former Member
      Former Member

      Hello Jonathan,

      What is the  "simple work-around that can be implemented"?

      We do not see this error in Dev only when transported to QA do the errors appear.


      Author's profile photo Jonathan Brown
      Jonathan Brown
      Blog Post Author

      Hi Seamus,

      The simple work-around is to add a couple of command line switches to the APS (DSL Bridge) startup command line.   This disables the design-time API for BICS based reports.

      The SAP KBA outlines this work-around in more details