Downgrading From PowerPivot v2 to v1

OK, let’s say you already installed v2, whether inadvertently or…  advertently.

And now you need to downgrade to v1, so that your workbooks function on your server, or can be opened by other people running v1 on their desktops.

So… how to do that?

The Obvious Thing Works for Most People

Simple:  just uninstall v2 (from Windows Control Panel) and then install v1.

But if you see this error when you try to build a new workbook, or open an old one, well, it’s not working out:

An operation that uses the database driver could not be completed - seen after downgrading PowerPivot v2 to v1.

What to do if you get that error?

1) Open Start Menu

2) Find “Command Prompt” – it is under Accessories

3) Right Click on Command Prompt, choose Run as Administrator

4) Once in the cmd window (looks like the old DOS window), type the following:

regsvr32 “C:\Program Files\Microsoft Analysis Services\AS OLEDB\10\msolap100.dll”

You may need to correct for your actual folder location – that’s the location on my machine.  The quotes ARE required.

Rob Collie

One of the founding engineers behind Power Pivot during his 14-year career at Microsoft, and creator of the world’s first cloud Power Pivot service, Rob is one of the foremost authorities on self-service business intelligence and next-generation spreadsheet technology.

This Post Has 7 Comments

  1. Pozuelo

    Hi there

    Thanks for your post. Overall your website rocks !

    I’ve succesfully done what you described regarding the command prompt.
    But the issue is still the same when opening a spreadhseet created with powerpivot V1 but unfortunatelly upgraded with Powerpivot V2 (before uninstalling V2). Any idea ?


    1. powerpivotpro

      I am sorry to say that a workbook upgraded to v2 cannot be downgraded to v1. If you need to continue to work with v1, you will have to re-create your workbook :(

      1. Pozuelo

        yep…shit happens they say…

  2. Pozuelo

    May I ask you what are the major risks to work with V2. I have to say that our databases / servers are on SQL 2005 actually (sorry I’m not an IT guy, but just an user of powerpivot for my job)

    1. powerpivotpro

      There actually is not much real danger here other than compatibility. Check this other blog post for the details:

  3. Pozuelo

    Thanks a lot Powerpivot Master
    May I ask you what kind of compatibility issues you’re talking about. Say I’m the only one in my company using powerpivot, with links to a datawarehouse under SQL 2005, what kind of troubles might I be exposed to ?

    Thanks for any info

    1. powerpivotpro

      That’s covered in the post I linked in my last comment :)

Leave a Comment or Question