SAP Disclosure Management MSOLAP Driver Issue

[Former Member]

Hello experts,

We're facing an issue when trying to create a new Datasource connection, using the MSOLAP driver. Basically we enter all the information, but once entered, the Catalog dropbox and Ok button doesn't activate, as is shown in the following screenshot:

The components we've installed are:

Microsoft Office Excel 2010 (x86)

SAP DM

Build: 10.1.3.14

Version: 10.1.3

Any suggestions please? We've no clue about this, any help is highly appreciated.

Thanks!

PS: Is there any way to create manually a connection? An editable .xml or something? Would be a workaround while it's fixed.

[Marc_Kuipers · Accepted solution]

Hello Andres

Any particular reason why you use MSOLAP?

This should connect to MS Analysis Server, and the catalogs are the ones created on that instance

It appears your server has no catalogs....

The name of your server is SQLDEV, which seems more like a MS SQL server, not Analysis Server

Anyway, the connections (local ones) are stored in:

C:\Users\<user>\AppData\Roaming\cundus AG\cundusBIPublisher\config20.xml

You can add a section like this (it's an example for SQL server)

<DataSource>

      <Type>Disclosure Management</Type>

      <SqlDialect>None</SqlDialect>

      <Name>Disclosure Management 10.1SP1 Basic Auth</Name>

      <Description>Current Dev 10.1SP1 (Port: 10110)</Description>

      <Locked>0</Locked>

      <SaveInside>0</SaveInside>

      <Credentials>

        <URL><![CDATA[http://mo-8fe9d2668.mo.sap.corp]]></URL>

        <Timeout><![CDATA[60000]]></Timeout>

        <PORT><![CDATA[10110]]></PORT>

        <User><![CDATA[ADMIN]]></User>

        <AuthType><![CDATA[Basic]]></AuthType>

      </Credentials>

    </DataSource>

Thanks

Marc

[Former Member · Accepted solution]

Hello Marc

Right now we're storing our source information to use with DM in BPC MS 10.0. Basically the information we need to read from DM are group nodes in our hierarchy in BPC. Since the data in SQL Server is stored at the lowest level in the fact table available, we need to use a the Analysis Services layer, where we can read the information already grouped by the existing hierarchy, so that's main reason for us to use MSOLAP.

About the name of the connection, sorry, I just published an example, but when we enter the entire name <SERVER>\<INSTANCE> all the correct information, the behavior is the same (I've already connected from SSAS and there are the available catalogs working).

Any ideas?

Thanks for the connections location, will be very useful.

[Marc_Kuipers · Accepted solution]

Hi Andres,

I reproduce the behavior you describe - the OK button remains inactive.

I am checking this internally with some people, will let you know.

Marc

[Marc_Kuipers · Accepted solution]

Andres

Whilst we wait for a real solution.....here's a rather crude workaround, but it appears to work.

- create an SQL connection, but when defining the connection string, select an OLAP driver

- Provide name of server and the catalog

- save it

- open the config20.xml file (with Notepad or some editor)

- change the type from "SQL Server" to "MSOLAP"

- close Excel/re-open it and connect to DSM and select this datasource

--> it behaves as an OLAP source !

Marc

[Marc_Kuipers]

Andres

This has been confirmed as a bug - I expect a fix in SP06

marc