A while back, I posted an item describing a possible package load failure when installing the Reporting Add-in on a system that has Visual Web Developer 2005 Express Edition to a non-default path. At the time I wrote that blog post, I confirmed that there was a setup bug in the Reporting Add-in MSI that caused this issue. I also contacted the team at Microsoft that created the Reporting Add-in and they indicated that there would be a new MSI for the Reporting Add-in with a fix for this issue and it would be released with SQL Server 2005 SP1.
This past weekend, I heard from a customer who ran into this exact same error, even though SQL Server 2005 SP1 has been available for several months now. I looked into this further, and I found that there is an updated Reporting Add-in package that has a fix for the setup issue that causes problems if Visual Web Developer 2005 is installed to a non-default path. However, the Visual WebDev downloads page still contains a link to the old, broken Reporting Add-in setup package.
I’m trying to get the team that manages the content of the Express Edition pages on MSDN to update this link, but in the meantime, I want to post it here to hopefully help folks avoid this issue – click on the link to download the updated version of the Reporting Add-in.
If you have already installed the older version of the Reporting Add-in and are receiving package load failures for it as a result, you can simply download and install the updated version to fix the package load failure errors on your system.