Symptom:
Error message "Can not browse sql servers SQLDMO.application is missing" is displayed when restoring deplyment,
Problem:
Error when trying to restore a Planning deployment in Contributor Admin Console (CAC), because it is not possible to browse to the folder on the SQL server for the mdf and ldf files.
Environment:
IBM Cognos Planning 8.4.1
SQLserver 2008
Cause:
DMO support is there but not installed by default in SQL Server 2008 (except for SQL Server Express where it's removed entirely). The files to install DMO support are on the SQL Server install DVD. But it doesn't install via the main installer. You must find the SQLServer2005_BC.MSI file and install it manually..
Solution:
Take the following steps:
1. Look for SQLServer2005_BC.msi which is typically found in a path such as Z:\x86\Setup\x86 (presuming your dvd drive is Z:)
http://www.microsoft.com/downloads/details.aspx?FamilyId=C6C3E9EF-BA29-4A43-8D69-A2BED18FE73C&displaylang=en
2. Updates required for Microsoft SQL server connection string
You need to update the epEAdminSQL7Resources.xml file to accommodate the name of the native client driver that is used in Microsoft SQL Server 2008. This update is required to start the planning service. You must update the epEAdminSQL7Resources.xml file on each machine that has the IBM Cognos 8 Planning server installed.
You can update the epEAdminSQL7Resources.xml file immediately after installing the planning server, prior to opening IBM Cognos Configuration.
Please change from this original Resource ID value:
<Resource ID="DefaultProviderDriverString" Context="Customization" Hint="The default string used in the ADO connection string that is generated for a new Application.">
<![CDATA[SQLOLEDB or SQLNCLI] ]> </Resource>
To this new Resource ID value:
<Resource ID="DefaultProviderDriverString" Context="Customization" Hint="The default string used in the ADO connection string that is generated for a new Application.">
<![CDATA[SQLNCLI10] ]> </Resource>
3. Install the Microsoft SQL Server 2005 Backward Compatibility Components as well.
4. Restart Cognos Planning service and open CAC to test again.
www.cogknowhow.com