Clearly if you read my blog, you will see that as a development team we could have done a better job of testing all of the various installation combinations with SQL Server on ‘test servers’. Unfortunately, our limited test time was focused on production configurations; not on single demo machines. So as a result you can see some of our installation issues that have arisen. Recently we ran into another installation problem when a previous SQL Server installation has been done on a machine prior to installing PowerPivot.
SQL Server stores it files in “instance” folders and a “Shared” folder of tools, SDK, and installation files. Normally the shared folder is specified in:
C:\Program Files\Microsoft SQL Sever\100\
but it does not have to . . . Many times DBAs specify a folder to a different location (off of the system drive) when you do your first SQL Server installation. However if you do this, you will find that PowerPivot will return errors, either:
Object reference not set to an instance of an object.
Or: (if you look at details.txt installation file)
2010-08-17 16:56:29 AS: The location is C:\Program Files\Microsoft SQL Server\100\SDK\Assemblies\Microsoft.AnalysisServices.SharePoint.Integration.DLL.
2010-08-17 16:56:29 AS: Microsoft.AnalysisServices.SharePoint.Integration.DLL not present in SDK
So how do you fix it? A quick workaround is to copy the file from the folder that you specified to its default location:
C:\Program Files\Microsoft SQL Server\100\SDK\Assemblies\Microsoft.AnalysisServices.SharePoint.Integration.DLL
The issue is that the SQL installer copies the file to shared folder but it will look for it in C: in its default location (this is a registry key/directory sync problem). So the workaround is to just copy it there. Smart huh?