Connection error to SSAS 2017

[Commander Cognos]

Hi guys,

After migrating our Analysis Services from 2012 to 2017 we'd like to connect and use the cubes within Cognos 11.1.7. The connection can be established and tested successfully, however we get the following error once we want to open a cube for creating a package at the data source connection:

XOD-CON-0001 Failed to connect to the OLE DB provider (Microsoft Analysis Services 2012) and server (<servername>). The data provider returned and error message {2}

Meaning the connection is fine and we can see the metadata from the analysis services. The Analysis Services run with a compatibilty mode 1100, after the migration. Does it mean we need the 2017 OLE DB client or does it mean we need connecti as 2012 ODBO?

Do you guys have any hints where we can investigate. Is there any specific client required? We followed the tech note, but this didn't solve the issue:

[MFGF]

Hi guys,

After migrating our Analysis Services from 2012 to 2017 we'd like to connect and use the cubes within Cognos 11.1.7. The connection can be established and tested successfully, however we get the following error once we want to open a cube for creating a package at the data source connection:

XOD-CON-0001 Failed to connect to the OLE DB provider (Microsoft Analysis Services 2012) and server (<servername>). The data provider returned and error message {2}

Meaning the connection is fine and we can see the metadata from the analysis services. The Analysis Services run with a compatibilty mode 1100, after the migration. Does it mean we need the 2017 OLE DB client or does it mean we need connecti as 2012 ODBO?

Do you guys have any hints where we can investigate. Is there any specific client required? We followed the tech note, but this didn't solve the issue:

Hi,

Did you update the OLE DB client on your Cognos server to match the new version of SSAS? From the error message you posted, it looks like your Cognos server still has the 2012 version of the OLE DB client installed. As you are now using Analysis Services 2017, this isn't going to work. Try updating your OLE DB client - this should fix the issue.

Cheers!

MF.

[Commander Cognos]

Hi MFGF,

thanks for your quick response. So that means you assume an issue with the client? The point is that we actually set up a fresh installation with only the new OLE DB client. Unfortunately I cannot see a correct matrix which client to use. As far as I can see there is only the latest version available - this is the one we used. We also copied the msolap.dll to the /bin64 folder, but this has no impact. How about the SQL Server OLE DB, it this also required? Meanwhile we also have the error in another environment - so we seemed to be missing a step :-(

Thanks and best regards,
CC

[Commander Cognos]

... one additional note/question. Does it mean we only need to have the Analysis Services OLE DB client or (only/in addition) the SQL OLE DB client? When matching the version, do we need to check the actual SQL Server version (2017) or the compatibility version the Analysis Services are running with (1100 = SQL Server 2012, right?)

Thanks again!

[MFGF]

Hi MFGF,

thanks for your quick response. So that means you assume an issue with the client? The point is that we actually set up a fresh installation with only the new OLE DB client. Unfortunately I cannot see a correct matrix which client to use. As far as I can see there is only the latest version available - this is the one we used. We also copied the msolap.dll to the /bin64 folder, but this has no impact. How about the SQL Server OLE DB, it this also required? Meanwhile we also have the error in another environment - so we seemed to be missing a step :-(

Thanks and best regards,
CC

Hi,

Yes, it looks like a mismatched client issue to me. The Cognos error indicates you are trying to use the 2012 client?

Quick sanity-check. Have you re-configured your data source connection / data server connection to be the 2017 version? I assume you already did this?

... one additional note/question. Does it mean we only need to have the Analysis Services OLE DB client or (only/in addition) the SQL OLE DB client? When matching the version, do we need to check the actual SQL Server version (2017) or the compatibility version the Analysis Services are running with (1100 = SQL Server 2012, right?)

Thanks again!

I would install the SQL Server OLE DB 2017 client too to rule this out.

Cheers!

MF.

[Commander Cognos]

Hi everyone,

first of all, I noticed, that I pasted the wrong error message in the first place, howevere the error was the same.
XOD-CON-0001 Failed to connect to the OLE DB provider (Microsoft Analysis Services 2017) and server (<servername>). The data provider returned and error message {2}

After hours of analyzing we came to the conclusion that while migrating the Analysis Services from 2012 to 2017 the Admin change the case sensitive setting to enabled. That means the Databases and Cubes could not been detected anymore. Disabling the case sensitive setting solved the issue.

Thanks for your support,
CC

[Commander Cognos]

Hi everyone,

just for the record and in case someone runs into the same problem, we eventually found the issue:
The Analysis Services were configured to be case sensitive and this caused the error in combination with the collate language settings. So you better uncheck the option and then it works perfectly.

Best regards,
CC