Design-time query not available (WIS 00000) by using BW Query in WebI 4.1

[Former Member]

Hello,

when I create a new Report in WebI (4.1 SP1 Patch1) on a Bex Query  (BW 7.3) with prompts, I get the following error.

Design-time query not available (WIS 00000)

How can I fix this issue?

Thanks

Andreas

[abhinav_shrivastava1 · Accepted solution]

Hi Andreas,

Please apply below correction note in BW System and test the behavior:

Note: 1798297 and 1817482

In addition, as workaround you can add the below parameter in the Command line of APS which has DSL Bridge service.

-Dsap.sl.bics.useDesignTimeServices=false

Hope this will help.

Regards,

Abhi

[former_member186489 · Accepted solution]

Hi Abhinav,

What are the consequences of disabling this service? I mean...what's the main reason to have this service activated?

Thanks in advance,

Pablo

[abhinav_shrivastava1 · Accepted solution]

Hi Pablo,

To my understanding DesinTimeQuery is new integration in BI4.1 using BICS layer, which is not getting loaded with some specific BW version.

So we are just disabling it and trying to load Query Panel in the way it get called in BI4.0.

For more information please check SAP Note 1940100.

-Abhi

[Henry_Banks · Accepted solution]

Correct, this note is new 1940100 - Error "Design-time query not available (WIS 00000)" using BICS connectivity with WebI in B...

and is discussed in this blog here: http://scn.sap.com/community/businessobjects-web-intelligence/blog/2013/11/15/bi-41--design-time-que...

Regards,

H

[Former Member · Accepted solution]

Hi Abhinav. Could you help me with my question please?

[Henry_Banks]

Hi,

can you tell from DSL_bridge + Webi Proc Server  TraceLogs if this problem comes from BW ?

You should also use RSTT in the bw backend, to get the comparison of the same workflow.

regards,

H

[Former Member]

Hi,

we have the same issue, after upgrade our enviroment to BO 4.1 SP01 we get the same error, and we haven't seen anything in the webi tracelogs.

any idea?

Thanks.

Joaquin Cheto

[Henry_Banks]

how about the DSL and RSTT traces?

[Former Member]

Hi,

nothing, we don't find nothing about the problem in any of log's files neither at the RSTT.

The problem happens when we modify the BEx query, then the query, at "query panel", shows the error

"Caused by: com.businessobjects.sdk.core.server.ServerException: Design-time query not available

          at com.businessobjects.sdk.core.server.common.CommonRequestHandler.newServerException(CommonRequestHandler.java:260)

          at com.businessobjects.sdk.core.server.common.CommonRequestHandler.createAllServerExceptions(CommonRequestHandler.java:238)

          at com.businessobjects.sdk.core.server.common.CommonRequestHandler.afterProcessing(CommonRequestHandler.java:121)

.... "

Our SAP BI enviroment it's SAP BI 7.3 SP09 and we use SAP Business Explorer client it's 7.3 SP04 Patch 1 to modity the BEx Queries.

Thanks.

Joaquin

[elke_zeimetz]

Hello,

we have the same issue.

I have installed a new system with BO 4.1 SP01 Patch 1.

When creating a new Webi with an existing BEx query (BW 7.3) we get the same error: Design-time query not available (WIS 00000)

Any idea?

Best regards,

Elke

[abhinav_shrivastava1]

Hi Henry,

Here is the DSL and logs which we captured in-house:

DSL trace:

|33E2AA37C77B4C8C8E23E6B1360008BC103d|2013 10 24 10:05:15.657|-0700|Error| |>>|E| |aps_BIPW08R2.AdaptiveProcessingServer1|12784|201498|DT Query Wrapper Factory| ||||||||||||||||||||||Exception in thread "DT Query Wrapper Factory" com.sap.ip.bi.base.application.exceptions.AbortMessageRuntimeException: Termination message sent 

|33E2AA37C77B4C8C8E23E6B1360008BC103e|2013 10 24 10:05:15.658|-0700|Error| |>>|E| |aps_BIPW08R2.AdaptiveProcessingServer1|12784|201498|DT Query Wrapper Factory| ||||||||||||||||||||||ABEND RS_EXCEPTION (000): The argument YCIC cannot be interpreted as a number

|33E2AA37C77B4C8C8E23E6B1360008BC103f|2013 10 24 10:05:15.658|-0700|Error| |>>|E| |aps_BIPW08R2.AdaptiveProcessingServer1|12784|201498|DT Query Wrapper Factory| ||||||||||||||||||||||  MSGV1: The argument YCIC cannot be interpreted as a

|33E2AA37C77B4C8C8E23E6B1360008BC1040|2013 10 24 10:05:15.658|-0700|Error| |>>|E| |aps_BIPW08R2.AdaptiveProcessingServer1|12784|201498|DT Query Wrapper Factory| ||||||||||||||||||||||  MSGV2: number

|33E2AA37C77B4C8C8E23E6B1360008BC1041|2013 10 24 10:05:15.658|-0700|Error| |>>|E| |aps_BIPW08R2.AdaptiveProcessingServer1|12784|201498|DT Query Wrapper Factory| |||||||||||||||||||||| at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageInternal(MessageManager.java:211)

|33E2AA37C77B4C8C8E23E6B1360008BC1042|2013 10 24 10:05:15.658|-0700|Error| |>>|E| |aps_BIPW08R2.AdaptiveProcessingServer1|12784|201498|DT Query Wrapper Factory| |||||||||||||||||||||| at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageByListener(MessageManager.java:177)

|33E2AA37C77B4C8C8E23E6B1360008BC1043|2013 10 24 10:05:15.658|-0700|Error| |>>|E| |aps_BIPW08R2.AdaptiveProcessingServer1|12784|201498|DT Query Wrapper Factory| |||||||||||||||||||||| at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessage(MessageManager.java:129)

There are continous Query Wrapper calls and later got below details further detial in the logs where request sent to WIPS:

|33E2AA37C77B4C8C8E23E6B1360008BC1057|2013 10 24 10:05:15.661|-0700|Debug| |<<| | |aps_BIPW08R2.AdaptiveProcessingServer1|12784|201497|Transport:Shared-408/34|}|29|11|3|4|BIlaunchpad.WebApp|BIPW08R2:1464:44.1431:1|webiserver_BIPW08R2.WebIntelligenceProcessingServer.getSessionInfosEx|localhost:8596:2004.17015:1|.doIt|BIPW08R2:12784:201497.196555:1|CtQaZ.2YiEIylcrNE2zyuW4595|||||||||||Generating fat universe: 04.922

|33E2AA37C77B4C8C8E23E6B1360008BC1058|2013 10 24 10:05:15.662|-0700|Error| |>>|E| |aps_BIPW08R2.AdaptiveProcessingServer1|12784|201497|Transport:Shared-408/34| |29|12|3|3|BIlaunchpad.WebApp|BIPW08R2:1464:44.1431:1|webiserver_BIPW08R2.WebIntelligenceProcessingServer.getSessionInfosEx|localhost:8596:2004.17015:1|.doIt|BIPW08R2:12784:201497.196555:1|CtQaZ.2YiEIylcrNE2zyuW4595|||||||||||Exception caught in SL Service: Design-time query not available

java.lang.IllegalStateException: Design-time query not available

After this we have errors in WIPS trace file at "10:05:15:666"along with Stack trace :

|f5ad7b12-9343-28c4-392c-e7eb1a6a185d|2013 10 24 10:05:15:666|-0700|Error| |>>|E| |webiserver_BIPW08R2.WebIntelligenceProcessingServer| 8596|2004|| |30|1|2|7|BIlaunchpad.WebApp|BIPW08R2:1464:44.1431:1|Webi SDK.CorbaServerImpl.doProcess()|BIPW08R2:1464:44.1431:6|webiserver_BIPW08R2.WebIntelligenceProcessingServer.getSessionInfosEx|localhost:8596:2004.17015:1|CtQaZ.2YiEIylcrNE2zyuW4595|||||||||||**ERROR:SLProxyBridge:Caught Exception from SL Service:  : Error: Design-time query not available
ErrorCode:
StackTrace:
*** com.businessobjects.mds.olap.protocol.bics.internal.BICSClientImpl.getDtQueryWrapper(BICSClientImpl.java:464)

Design-time query not available

So this problem seems somewhere lying in the QueryWrapper.

@Elke and Andreas: Is this problem even coming with a simple BEX Query too?

-Abhi

[Henry_Banks]

hmm... what's this "YCIC" ?

both these parts of that error message are searcheable for BW  "ABEND RS_EXCEPTION (000)"   and "The argument cannot be interpreted as a number" .  something to do with transformation routines?

IMO - One of you customers should take this to AGS Support as an incident message.

Best of luck

regards,

H