Problem Initial View and others

[Former Member]

Hi all,

recently we updated to DS 1.4 and our BW to 7.4 SP09.

Now we are facing some problems that did not arise before these updates but until now I am not able to exactly determine the reason and therefore I have no idea how to solve these.

Maybe one of you have any idea.

My first problem is the following:

In my application I have serveral datasources. For them you are normally able to select the displayed measures and keyfigures within the "initial view" tab.

Inside this tab it seems to work as normal but when closing it, the view in my application does not change.

It is like DS is not able to save the selected view but I don't understand why.

WDesign Studio I get this error message:

Could not bind a reference of component com.sap.ip.bi.base.application.DeclaredServiceActivator. The reference is: Reference[name = IActivatorBase, interface = com.sap.ip.bi.base.bundle.IActivatorBase, policy = dynamic, cardinality = 0..n, target = null, bind = addRICActivator, unbind = removeRICActivator]

I just looked in the path: C:\Program Files\SAP BusinessObjects\Design Studio\plugins

and there is no such "com.sap.ip.bi.base.application.DeclaredServiceActivator" - should there be one and this is the problem?

------------------------------------------------------------

---UPDATE----

I just created a totally new dashboard with only one new Datasource.

Now DesignStudio gives me no error message at all but I still cannot change the shown keyfigures in the initial view tab.

After closing the initial view selection, Design Studio will always show ALL keyfigures from the query in the crosstab.

When using this data source with a chart component, I am able to select the shown keyfigures in the chart poperties.

------------------------------------------------------------

In other dashboards I had a conversion routine in some queries and now DS is no longer able to load these.

Then I get following messages:

eclipse.buildId=@qualifier@

java.version=1.7.0_55

java.vendor=SAP AG

BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE

Framework arguments:  BusinessObjects Design Studio

Command-line arguments:  -os win32 -ws win32 -arch x86_64 BusinessObjects Design Studio

Error

Mon Jan 12 11:04:21 CET 2015

ERROR [f65382e7-dff1-4a74-8f78-345dc1115107]: Termination message sent

ABEND RS_EXCEPTION (000): Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER ist aufgetreten, wurde aber weder lokal behandelt noch durch eine RAISING-Klausel deklariert.

  MSGV1: Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER

  MSGV2: ist aufgetreten, wurde aber weder lokal behandelt

  MSGV3: noch durch eine RAISING-Klausel deklariert.

ABEND RS_EXCEPTION (000): Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht als Zahl interpretierbar.

  MSGV1: Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht

  MSGV2: als Zahl interpretierbar.

ABEND RSBOLAP (000): Programmfehler in Klasse SAPMSSY1 Methode : UNCAUGHT_EXCEPTION

  MSGV1: SAPMSSY1

  MSGV3: UNCAUGHT_EXCEPTION

ERROR

"DATAPROVIDER" of type "QUERY_DATA_SOURCE" could not be generated

com.sap.ip.bi.webapplications.runtime.impl.page.Page Page_0013

DATAPROVIDER

QUERY_DATA_SOURCE

"DATAPROVIDER" of type "QUERY_DATA_SOURCE" could not be generated

com.sap.ip.bi.webapplications.runtime.impl.page.Page Page_0013

DATAPROVIDER

QUERY_DATA_SOURCE

ABEND RS_EXCEPTION (000): Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER ist aufgetreten, wurde aber weder lokal behandelt noch durch eine RAISING-Klausel deklariert.

  MSGV1: Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER

  MSGV2: ist aufgetreten, wurde aber weder lokal behandelt

  MSGV3: noch durch eine RAISING-Klausel deklariert.

ABEND RS_EXCEPTION (000): Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht als Zahl interpretierbar.

  MSGV1: Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht

  MSGV2: als Zahl interpretierbar.

ABEND RSBOLAP (000): Programmfehler in Klasse SAPMSSY1 Methode : UNCAUGHT_EXCEPTION

  MSGV1: SAPMSSY1

  MSGV3: UNCAUGHT_EXCEPTION

com.sap.ip.bi.base.application.exceptions.AbortMessageRuntimeException: Termination message sent

ABEND RS_EXCEPTION (000): Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER ist aufgetreten, wurde aber weder lokal behandelt noch durch eine RAISING-Klausel deklariert.

  MSGV1: Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER

  MSGV2: ist aufgetreten, wurde aber weder lokal behandelt

  MSGV3: noch durch eine RAISING-Klausel deklariert.

ABEND RS_EXCEPTION (000): Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht als Zahl interpretierbar.

  MSGV1: Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht

  MSGV2: als Zahl interpretierbar.

ABEND RSBOLAP (000): Programmfehler in Klasse SAPMSSY1 Methode : UNCAUGHT_EXCEPTION

  MSGV1: SAPMSSY1

  MSGV3: UNCAUGHT_EXCEPTION

ERROR

"DATAPROVIDER" of type "QUERY_DATA_SOURCE" could not be generated

com.sap.ip.bi.webapplications.runtime.impl.page.Page Page_0013

DATAPROVIDER

QUERY_DATA_SOURCE

"DATAPROVIDER" of type "QUERY_DATA_SOURCE" could not be generated

com.sap.ip.bi.webapplications.runtime.impl.page.Page Page_0013

DATAPROVIDER

QUERY_DATA_SOURCE

ABEND RS_EXCEPTION (000): Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER ist aufgetreten, wurde aber weder lokal behandelt noch durch eine RAISING-Klausel deklariert.

  MSGV1: Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER

  MSGV2: ist aufgetreten, wurde aber weder lokal behandelt

  MSGV3: noch durch eine RAISING-Klausel deklariert.

ABEND RS_EXCEPTION (000): Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht als Zahl interpretierbar.

  MSGV1: Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht

  MSGV2: als Zahl interpretierbar.

ABEND RSBOLAP (000): Programmfehler in Klasse SAPMSSY1 Methode : UNCAUGHT_EXCEPTION

  MSGV1: SAPMSSY1

  MSGV3: UNCAUGHT_EXCEPTION

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageInternal(MessageManager.java:211)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageByListener(MessageManager.java:177)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessage(MessageManager.java:129)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageInternal(MessageManager.java:207)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageByListener(MessageManager.java:177)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessage(MessageManager.java:129)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageInternal(MessageManager.java:207)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessageByListener(MessageManager.java:177)

    at com.sap.ip.bi.base.application.message.impl.MessageManager.addMessage(MessageManager.java:129)

    at com.sap.ip.bi.base.application.service.RfcService.fillMessages(RfcService.java:358)

    at com.sap.ip.bi.base.application.service.RfcService.doPostProcessing(RfcService.java:307)

    at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.ProviderSelectionObject.doPostProcessing(ProviderSelectionObject.java:1817)

    at com.sap.ip.bi.base.application.service.rfcproxy.base.RfcFunction.execute(RfcFunction.java:97)

    at com.sap.ip.bi.base.application.service.RfcService.doPostProcessing(RfcService.java:316)

    at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.ProviderSelectionObject.doPostProcessing(ProviderSelectionObject.java:1817)

    at com.sap.ip.bi.base.application.service.rfcproxy.base.RfcFunction.execute(RfcFunction.java:97)

    at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.ProviderInfoObject.prepareForSelectionMemberAccess(ProviderInfoObject.java:1698)

    at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.selection.ProviderComponentList.setup(ProviderComponentList.java:145)

    at com.sap.ip.bi.bics.dataaccess.resource.impl.bi.selector.selection.ProviderComponentList.isSingleMemberSelection(ProviderComponentList.java:414)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.selection.ComponentList.isOnlySingleMembersSelection(ComponentList.java:1108)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.Sorting.supportsSortBySelection(Sorting.java:457)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.Sorting.getType(Sorting.java:208)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.Sorting.setSortByMembersPresentation(Sorting.java:251)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseSorting(StateDomParser.java:3243)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseQvSorting(StateDomParser.java:3122)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseQvCharacteristicNode(StateDomParser.java:2016)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseCharacteristic(StateDomParser.java:1645)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.CharacteristicList.setStateFromDom(CharacteristicList.java:92)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.readListObjectDetails(StateDomParser.java:4274)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseSelectorNode(StateDomParser.java:293)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseQueryViewNode(StateDomParser.java:368)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseSelectorNodeBase(StateDomParser.java:253)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseSelector(StateDomParser.java:212)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.base.StateDomParser.parseSelector(StateDomParser.java:165)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.SelectionObject.readStateFromDom(SelectionObject.java:1489)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.SelectionObject.setDefaultStateByXml(SelectionObject.java:1627)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.SelectionObject.initializeState(SelectionObject.java:718)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.queryview.QueryView.initializeState(QueryView.java:182)

    at com.sap.ip.bi.bics.dataaccess.consumer.impl.selector.SelectionObject.initialization(SelectionObject.java:684)

    at com.sap.ip.bi.base.application.impl.ServiceManagement.registerService(ServiceManagement.java:776)

    at com.sap.ip.bi.base.application.impl.ServiceManagement.createService(ServiceManagement.java:397)

    at com.sap.ip.bi.base.application.impl.ServiceManagement.createService(ServiceManagement.java:365)

    at com.sap.ip.bi.base.application.impl.Application.createService(Application.java:491)

    at com.sap.ip.bi.base.application.service.base.BaseServiceDescription.createService(BaseServiceDescription.java:142)

    at com.sap.ip.bi.webapplications.dataproviders.selector.impl.WdpSelector.doInit(WdpSelector.java:325)

    at com.sap.ip.bi.webapplications.runtime.object.page.impl.PageObject.init(PageObject.java:296)

    at com.sap.ip.bi.webapplications.runtime.object.provider.impl.Provider.init(Provider.java:37)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageStateProcessor.initPageObject(PageStateProcessor.java:2798)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageStateProcessor.setupPageObject(PageStateProcessor.java:2104)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageStateProcessor.createPageObject(PageStateProcessor.java:2061)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageCommandProcessor.doCreateDataProviderCommand(PageCommandProcessor.java:819)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.doCreateDataProviderCommand(Page.java:5933)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke(Method.java:606)

    at com.sap.ip.bi.util.MethodInvoker.callMethod(MethodInvoker.java:155)

    at com.sap.ip.bi.webapplications.runtime.service.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:425)

    at com.sap.ip.bi.webapplications.runtime.service.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:340)

    at com.sap.ip.bi.webapplications.runtime.processor.CommunicationProcessor.processCommand(CommunicationProcessor.java:212)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processCommandSuper(Page.java:4910)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processCommand(Page.java:4476)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processCommand(Page.java:1)

    at com.sap.ip.bi.web.runtime.template.impl.items.TemplateAssembler.createPageObjects(TemplateAssembler.java:655)

    at com.sap.ip.bi.web.runtime.template.impl.xml.XmlTemplateAssembler.reloadTemplate(XmlTemplateAssembler.java:182)

    at com.sap.ip.bi.web.runtime.template.impl.xml.XmlTemplateAssembler.doInit(XmlTemplateAssembler.java:94)

    at com.sap.ip.bi.web.runtime.template.impl.items.TemplateAssembler.init(TemplateAssembler.java:162)

    at com.sap.ip.bi.webapplications.runtime.impl.object.template.Template.doInit(Template.java:144)

    at com.sap.ip.bi.webapplications.runtime.object.page.impl.PageObject.doInit(PageObject.java:344)

    at com.sap.ip.bi.webapplications.runtime.object.page.impl.PageObject.init(PageObject.java:296)

    at com.sap.ip.bi.webapplications.runtime.rendering.renderer.ItemRenderer.init(ItemRenderer.java:41)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageStateProcessor.initPageObject(PageStateProcessor.java:2798)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageStateProcessor.setupPageObject(PageStateProcessor.java:2104)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageStateProcessor.createPageObject(PageStateProcessor.java:2061)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.setTemplate(Page.java:5440)

    at com.sap.ip.bi.webapplications.runtime.impl.page.processor.PageCommandProcessor.doSetTemplateCommand(PageCommandProcessor.java:1698)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.doSetTemplateCommand(Page.java:6028)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

    at java.lang.reflect.Method.invoke(Method.java:606)

    at com.sap.ip.bi.util.MethodInvoker.callMethod(MethodInvoker.java:155)

    at com.sap.ip.bi.webapplications.runtime.service.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:443)

    at com.sap.ip.bi.webapplications.runtime.service.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:340)

    at com.sap.ip.bi.webapplications.runtime.processor.CommunicationProcessor.processCommand(CommunicationProcessor.java:212)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processCommandSuper(Page.java:4910)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processCommandInternal(Page.java:4569)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processCommandSequence(Page.java:4729)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.doProcessRequest(Page.java:2574)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page._processRequest(Page.java:780)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processRequest(Page.java:5157)

    at com.sap.ip.bi.webapplications.runtime.impl.page.Page.processRequest(Page.java:5150)

    at com.sap.ip.bi.webapplications.runtime.impl.controller.Controller.doProcessRequest(Controller.java:1244)

    at com.sap.ip.bi.webapplications.runtime.impl.controller.Controller._processRequest(Controller.java:1094)

    at com.sap.ip.bi.webapplications.runtime.impl.controller.Controller.processRequest(Controller.java:1060)

    at com.sap.ip.bi.webapplications.runtime.impl.controller.Controller.processRequest(Controller.java:1)

    at com.sap.ip.bi.server.runtime.sevice.impl.BIRuntimeServerService._handleRequest(BIRuntimeServerService.java:524)

    at com.sap.ip.bi.server.runtime.sevice.impl.BIRuntimeServerService.handleRequest(BIRuntimeServerService.java:907)

    at com.sap.ip.bi.server.execution.engine.runtime.LocalBIExecutionService.executeRequest(LocalBIExecutionService.java:47)

    at com.sap.ip.bi.client.execution.AbstractExecutionServlet.handleRequest(AbstractExecutionServlet.java:146)

    at com.sap.ip.bi.client.servlet.BIPrivateServlet.handleRequest(BIPrivateServlet.java:35)

    at com.sap.ip.bi.client.execution.AbstractExecutionServlet.doPost(AbstractExecutionServlet.java:125)

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:755)

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)

    at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)

    at org.eclipse.equinox.http.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:38)

    at com.sap.ip.bi.zen.webserver.designer.ZenSessionFilter.doFilter(ZenSessionFilter.java:45)

    at org.eclipse.equinox.http.servlet.internal.FilterRegistration.doFilter(FilterRegistration.java:81)

    at org.eclipse.equinox.http.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:35)

    at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:132)

    at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:60)

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)

    at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.service(HttpServerManager.java:386)

    at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)

    at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:501)

    at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:229)

    at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)

    at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)

    at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)

    at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)

    at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)

    at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)

    at org.eclipse.jetty.server.Server.handle(Server.java:370)

    at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:494)

    at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:982)

    at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1043)

    at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865)

    at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)

    at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)

    at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:667)

    at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)

    at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)

    at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)

    at java.lang.Thread.run(Thread.java:812)

At the moment most of our dashboards don't work and I am desperately looking for a solution.

Regards

Steffen

[Karol-K · Accepted solution]

Hi Steffen,

to your issue:

Error

Mon Jan 12 11:04:21 CET 2015

ERROR [f65382e7-dff1-4a74-8f78-345dc1115107]: Termination message sent

ABEND RS_EXCEPTION (000): Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER ist aufgetreten, wurde aber weder lokal behandelt noch durch eine RAISING-Klausel deklariert.

  MSGV1: Eine Exception vom Typ CX_SY_CONVERSION_NO_NUMBER

  MSGV2: ist aufgetreten, wurde aber weder lokal behandelt

  MSGV3: noch durch eine RAISING-Klausel deklariert.

ABEND RS_EXCEPTION (000): Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' ist nicht als Zahl interpretierbar.

is it possible that during the upgrade some queries has been changed? This error message is a clear EXCEPTION on ABAP side in OLAP processor. from the IDs it looks for me like you had an DS application which was based on data source / query and modified via initial view editor. This procedure is saving the query metadata (including all characteristics, keyfigures etc) and on runtime applying so called query view on top of the initial query. In case this is not compatible (eg. query has been changed ans some elements are missing) this can recover or badly break - with similar exception.

Das Argument '00O2TRX36WVOYQSJQVM3B2QOV' seems to be some guid to key figure or other query element which is either missing or changed ith definition on query level.

you can check your query "change log", I suppose it was changed in last days.

Karol

[Former Member · Accepted solution]

Hi Karol.,

thank you for your answer. This helped me a lot to better understand the problem(s).

Ok:

You are right, my DS Apllication is based on a query which was modified via the initial view editor.

But initially this query was not changed, we only updated the BW from 7.4 SP05 to SP09.

After this update two problems arised:

The Design Studio Application was not able to generate a datasource from the query and I had problems with the conversation routine even when executing the query with bex.

In order to resolve this I made some changes in the query but the problems remain.

I understand that this may be the reason for the problem with the argument '00O2TRX36WVOYQSJQVM3B2QOV'.

But additionaly, now I am not even able to make (save) any changes in the initial view editor - not only for the faulty query but for all of my queries (and even if I use InfoCubes as DataSource).

So i cannot just redesign the query and the DS appliction which is a big problem.

Maybe there is some (communication) problem between DS and the OLAP?

Unfortunately I do not know where I can get more detailed error logs to exactly determine the problem.

Regards

Steffen

[Karol-K · Accepted solution]

Steffen,

do you see some visible exceptions in local log file? This behavior is strange, this would mean that BICS accsess to 7.4 SP09 has troubles.

The initial view editor is at the end asking BICS for a Query View Notation XML (like in BEx DataProviderInformation Item, or how this was called) and saving this XML into application. In case there are some ABAP exceptions, can happen that the serialization does not work well. But then something should be still in LOG file, can you check this?

Karol

[Former Member · Accepted solution]

I opened a new apllication and testet to make some chages in the initial view.

I does not work but there are no errors in the workspace log.

Or is there another log file where such an error could be stored?

Steffen

[Karol-K · Accepted solution]

Actually, all issues should be logged in "Error Log" and also in the log file which will be captured by "Collect Support Information".

if it is not there, I am afraid we have to continue on customer incident with this issue.

[Former Member · Accepted solution]

Hi Karol,

I just checked it again and there is nothing in the error log which is strange for me.

I tried to rebuild a quite similar cube and query in another bw system that is not on SP09 but on 740 SP05 and there I have no problem which indicates a problem with the SP09.

But without any entry in the error log it's not easy to determine the problem...

[manfred_schwarz · Accepted solution]

Hi Steffen,

In the meantime i've opened an OSS incident - but nobody has contacted me so far - i will keep you updated. I can confirm that there is also no entry in the logs on my side

I did not face the issue that i could not connect to the query ?!? I just can't make any changes on the initial view regarding measures...

[Former Member · Accepted solution]

Hi Manfred,

thanks for the info.

I assume that I have two different problems/errors that both may have the same reason.

In my case there is one specific query that DS was not able  to load after the system update within an existing application.

When designing a new application, I am able to connect this query but then I have the same problem as you, that I cannot make any changes in the initial view editor which hinders me in simply redesigning my existing apllications.

Ok, I could use the coding but this is only a workaround and has other effects.

I hope that SAP will contact you soon and more importantly fix this problem soon.

PS: Is it useful to open a second oss incident for the same problem? If yes I can do this.

[manfred_schwarz · Accepted solution]

Hi Steffen,

Today i got an answer and was pointed to note 2092810. The note sounds promising but i did not find the time to test it.

http://service.sap.com/sap/support/notes/2092810

But next week i will definitely do

Keep you updated.

[Former Member · Accepted solution]

Thanks Manfred.

It works for me!

Regards

Steffen

[Former Member · Accepted solution]

This message was moderated.

[manfred_schwarz]

OK - i can confirm that this note also works on my side

Take care

[Former Member]

Helo,

i have the same issue.

i try to install a sdk extension to Design Studio 1.4 (colored box) and get the same message:

eclipse.buildId=@qualifier@

java.version=1.7.0_55

java.vendor=SAP AG

BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_CH

Framework arguments:  BusinessObjects Design Studio

Command-line arguments:  -os win32 -ws win32 -arch x86_64 BusinessObjects Design Studio

Error

Wed Jan 14 16:11:41 CET 2015

Could not bind a reference of component com.sap.ip.bi.base.application.DeclaredServiceActivator. The reference is: Reference[name = IActivatorBase, interface = com.sap.ip.bi.base.bundle.IActivatorBase, policy = dynamic, cardinality = 0..n, target = null, bind = addRICActivator, unbind = removeRICActivator]

[Former Member]

Hi,

so some incompatibilities with sdks may be a reason for these errors?

I have installed some simple Sdks, too (e.g. KPI_Tile).

@Manfred

Do you also have a sdk installed?

Regards

Steffen

[Former Member]

i just try to repeat the example from the sdk documentation

[manfred_schwarz]

Hi Steffen,

No - we don't have them published to the BO-Server - ihave locally some SDKs, but i also tried without them.

What is your database behind BW ? Are you using Oracle, MaxDB, Hana ???

We are on a HANA backend. Perhabs this is the point of failure ?

Best regards

Manfred

[Former Member]

Hi Manfred,

no we are not using Hana.

As far as I know we are using MaxDB.

And we are connecting to NW Portal (where I have three Sdks installed).

I also deleted my local installation of DesignStudio 64bit and tried the 32bit but same error as before.

After editing my dashboard and query it will run again to some extent (thanks to Manfred for the hint with the skript) but I still get the same error-message as Luis :

eclipse.buildId=@qualifier@

java.version=1.7.0_55

java.vendor=SAP AG

BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE

Framework arguments:  BusinessObjects Design Studio

Command-line arguments:  -os win32 -ws win32 -arch x86 BusinessObjects Design Studio

Error

Wed Jan 14 16:31:08 CET 2015

Could not bind a reference of component com.sap.ip.bi.base.application.DeclaredServiceActivator. The reference is: Reference[name = IActivatorBase, interface = com.sap.ip.bi.base.bundle.IActivatorBase, policy = dynamic, cardinality = 0..n, target = null, bind = addRICActivator, unbind = removeRICActivator]

Regards

Steffen

[Karol-K]

hi,

the message "Could not bind a reference of component com.sap.ip.bi.base.application.DeclaredServiceActivator." is coming on startup - it is ugly but not effecting functionality. already reported, hope will be fixed soon.

Karol

[former_member193885]

Steffen,

We had the issues filtering on the initial view with queries which had BEx conditions enabled.  I was not able to remove certain measures from the initial view of the data source but can do it at the chart data selection level (i used this as the work around).

This happened only in 1.4 and not 1.3.

Thanks.

[Former Member]

Hi Deepu,

sounds intereresting. I checked some of the queries but none of them has conditions or exceptions.

For charts it may be a good workaround to do the selection in the chart properties but I need some selection for crosstabs too, and there I do not have that option.

Maybe I should try some scripting...?

Regards

Steffen

[manfred_schwarz]

Hi Steffen,

I have the exact same issue as you. I tried DS 1.3 and 1.4 in combination with BW 7.4 SP9

Something seems to be not working here. As an workaround you can use the BIAL in the Application onStartup Event.:

DS.setFilter(KeyfigureDimension, "Name of the Keyfigure");

That did the trick for overcoming this funny error. If you need multiple keyfigures you can first fill an array and then assign it to the setFilter function.

I will do a search on thursday and if i don't find anything i will open up an oss ticket.

Keep me updated if you find something first

Best regards

Manfred

[Former Member]

Hi Manfred,

this is really interesting!

So it seems that there is a real problem in the combination of these two versions.

Until your post I thought that there is something wrong with our system and I am the only one that is facing this problem.

After searching the reason for this strange beahavoiur in our system (and SAP notes) for now 4 days I was beginning to loose hope in finding a faulty customization or a fix...

I planned to downgrade our Design Studio to 1.3, hoping that it will work again, but after your post I see that this will be useless.

Thanks for your workaround - I will try this today,.

Hopefully we soon can get a solution/fix from SAP with the next SP wich is planned for next week I read...

Regards

Steffen