Migrating to SSAS cubes error
Earlier this week I got the chance to do some SSAS work for the first time in a long time which made me very happy. My task was to migrate some cubes from Analysis Services 2000 to SSAS 2008. I was given a new Windows 2008 R2 Server with SQL Server 2008 SP1 (Slipstream installed) to work on and when I got started I got an error pretty much right away. I did a quick search on the internet and didn’t find much info on the error at all so I decided to cancel out and redo the steps so that I could document the problem. When I went to recreate the problem I found inadvertently kicked off the process from my local machine instead of the server like I had the time before and this time everything worked; no error. I knew right away what the problem was and was shocked that my search hadn’t turned up anything.
I received this error on the server but not on my local machine:
“ Source server: The Migration Wizard cannot continue because the DSO client is not installed on this computer. Close the current Migration Wizard, install the DSO client on the computer, and then try running the Migration Wizard again. ”
Like muscle memory I knew that I had forgotten to install the Backwards Compatibility kit onto the new server that I was working with. Now most of you may not get this error because you’ve already had to install this pack to migrate or work with DTS packages, but for those of you that may not have needed to touch a DTS package from inside of SQL Server Management Studio (SSMS) you will end up right where I was with this server.
Here’s the article to install the Backwards Compatibility:
And you’ll want to go down the page until you get to:
“Microsoft SQL Server 2005 Backward Compatibility Components
The SQL Server Backward Compatibility package includes the latest versions of the Data Transformation Services 2000 runtime (DTS), SQL Distributed Management Objects (SQL-DMO), Decision Support Objects (DSO), and SQL Virtual Device Interface (SQLVDI). These versions have been updated for compatibility with both SQL Server 2005 and SQL Server 2008 and include all fixes shipped through SQL Server 2000 Service Pack 4 (SP4) and SQL Server 2005 SP2.
And here’s a screenshot of what installing this component looks like:
So, Lesson learned. Use a checklist when installing new servers even if you think you have it all memorized.