During installation, the MSI returns the following error message:
Setup has encountered an error during installation and must close, for more information see the wppacker.log.
No associated entry is recorded in the error log.
In most cases, this is due to SharePoint being extended onto a site using a host header. There is a known issue with Microsoft's .msi not working well with host headers. When an installation attempts to locate your web sites using the Configuration Database, it will simply fail without an error being generated.
**This issue has been resolved in the current releases. Please go to the storefront and download the latest version at http://store.bamboosolutions.com/
Install the Web Part manually using the provided stsadm.exe utility.
The stsadm.exe utility is located at C:\Program Files\Common Files\Microsoft Shared\web server extensions\60\BIN.
Form the command line with the following line and associated arguments:
stsadm.exe -o addwppack -filename (path to file) -force [-url (URL)] [-globalinstall]
- (path to file) specifies the path to the CAB file and the CAB file name that was contained in the downloaded installation package.
- -force instructs stsadm.exe to overwrite an existing Web Part package with a new version. Use this for upgrades or if previous installation attempts were unsuccessful.
- (URL) specifies the optional URL of the virtual server on which to upgrade the Web Parts. If -url is omitted, Stsadm.exe upgrades the Web Parts in the Bin folder of every virtual server on the server. On servers where the Web Parts were not installed, this is equivalent to a new installation.
- -globalinstall specifies installation of the Web Parts in the global assembly cache (GAC) rather than in the Bin directories of each virtual server.