Unanswered how to uninstall BIDS R2?

  • lunes, 30 de abril de 2012 19:46
     
     

    I installed SQL 2008 R2, databas engine only but seem to have also installed SQL 2008 R2 BIDS. Now i can't deploy an SSAS build to a SQL 2008 server.. I get "Error loading D:\Cube Deployments\.......asdatabase: Deserialization failed: The 'ProcessingState' element in the 'http://schemas.microsoft.com/analysisservices/2010/engine/200' namespace is unexpected."

    I notice in my Visual Studio 2008 SSAS design session under my "About Micorosft Visuao Studio":

    Microsoft SQL Server Analysis Services Designer
    Version 10.50.1600.1

    I don't want to uninstall SQL 2008 and start over. I did uninstall 2008 R2 database engine, however my SQL 2008 R2 client is still  there. To uninstall it there were tons of warnings of depenecies to SQL 2008.

    Any ideas?

Todas las respuestas

  • lunes, 30 de abril de 2012 23:26
     
     

    Hi Dave,

    No need to uninstall BIDS. Both SQL Server 2008 and SQL Server 2008 R2 run with the VS 2008 Shell. There is a deployment option in the SSAS project properties window that determines the target version. You'll need to change that to 10.0 to deploy to SQL Server 2008. 10.5 correlates to 2008 R2.

    HTH, Martin


    http://martinmason.wordpress.com

  • martes, 01 de mayo de 2012 0:33
     
     

    First off, thank you Martin for responding.

    I kind of figured there had to be a way to state the release of build since with Reporting Services you are able to do that.

    I did notice and saw in the drop down 10.0 and 9.0. I did not see 10.5.

    During the SSAS builds, it appears to be using 10.0. But when I take the files from the build and copy them over to the SSAS server (SQL2008) for deployment, that is when I get the deployment error: "Error loading D:\Cube Deployments\.......asdatabase: Deserialization failed: The 'ProcessingState' element in the 'http://schemas.microsoft.com/analysisservices/2010/engine/200' namespace is unexpected.". 

    I assume that the build used the R2 version but now confused when it does show 10. for the target. I have tried several times since uninstalling R2 on my local.

    However, tomorrow at work I will look at this again. I did not copy over all the files and maybe one of them was still under the old build. I will try again.

    Please stay tuned....

    Thanks again,

    Dave

  • martes, 01 de mayo de 2012 12:09
     
     

    I came int his morning to try one more thing and that being I dd not copy over all the latest files from the build. One of the componets is from an assembly that never changes so I never bring that over. And now I remember htat I never brught it over even after a build from R2. But even after a total copy over of all the files from the build, I still had the error.

    This is intertesting, when I go into Visual Studio I see under About Micorosdft Visual Studio and when I click on SQL Server Analysis Services Designer, Microsoft SQL Server Analysis Services Designer
    Version 10.50.1600.1

    which i beleive to be R2. Since unstalling R2 and repairing 2008 9which failed), I was expecting:

    Microsoft SQL Server Analysis Services Designer
    Version 10.0.5500.0

    which I believe to be 2008 version.

    Now at a lost other than to totally uninstall and install 2008 .

    I do have a work around in that is too copy the total project onto the target server and do build from there.

    Thanks again,

    Dave

  • miércoles, 02 de mayo de 2012 7:36
    Moderador
     
     

    Hi Dave,

    Just as Martin said, you should select proper version for deploy the build to a SQL Server 2008 server. To do it, right click on the solution in BIDS and select Properties, in the properties window, click "Build" and choose "10.0" for the Deployment Server Version. Then, you can deploy the build to SQL 2008 server.

    By default, it is 10.50 which correlates to 2008 R2. The error you have seen will occur if the build with 10.50 version is deployed to SQL 2008 server.

    Regards,
    Jerry

  • miércoles, 02 de mayo de 2012 12:39
     
     

    Version 10.0 is the default showing up and when a build is done with that version it still fails. 

    10.5 is not even in the dropdown list. There is just 10.0 and 9.0.  Using 9 fails as well.

    What concerns me is that I see the below version showing in the popup window when the "help - About Microsft Visual Studio"  is viewed. "Microsoft SQL Server Analysis Services Designer  Version 10.50.1600.1"

    My work around is to copy the whole project over to the dev target server and build there.

    I still havenot gone through the pains of uninstalling and reinstalling 2008. I am not sure if I would have to do the same with my Visual Studio environment.

    Dave