BoostSolutions » Installation

Can't get access into SharePoint site after upgrade

Admin — Mon, 31 Mar 2014 19:44:06 +0000

Sometimes, after upgrade BoostSolutions product, user cannot get access into sites. The error message could be "SharePoint Foundation" or "File not found".

Solution:

This issue is caused by the conflict between the old version "sharepointboost" and the new version "boostsolutions" while the old version "sharepointboost" hasn’t been removed completely during the upgrade.

To solve this issue, please follow below steps:

1. Go to Central Administration—>System Settings—>Farm Management—>Manage Farm Solutions to check whether there are wsp with the name "sharepointboost". If so, retract and remove it.

2. Reinstall the upgrade again, choose "Repair" during re-installation.

Applies for: SharePoint 2013, SharePoint 2010, SharePoint 2007

The post Can't get access into SharePoint site after upgrade appeared first on BoostSolutions.

The specified module could not be found. (Exception from HRESULT:0x8007007E)

Admin — Mon, 31 Mar 2014 19:44:03 +0000

During Installing/upgrading/deploying product, there is an error message shows up during the installation procedure as well in the solution status page:
"The specified module could not be found. (Exception from HRESULT:0x8007007E)"

An related log information could be found in SharePoint log file:

Solution:

A possible reason for this is that the WMI (http://msdn.microsoft.com/en-us/library/windows/desktop/aa394582(v=vs.85).aspx) might be corrupted, please test by following the steps below:

Login the server, Start -> Run -> cmd to open command line, then type wbemtest.exe
Click ‘Connect’ on the pop-up window:

3. After it loads the Namespace, click ‘Connect’ again

4. If WMI is running ok, the result will be shown as below:

If any error message shows, there is something wrong with WMI, and you may need to re-register the WMI .dll’s and .exe’s by referring to this link: http://blogs.msdn.com/b/josrod/archive/2011/05/25/corrupt-wmi-causing-sharepoint-search-provisioning-to-fail.aspx

Reference:

http://blogs.msdn.com/b/josrod/archive/2011/05/25/corrupt-wmi-causing-sharepoint-search-provisioning-to-fail.aspx

Applies for: SharePoint 2007

The post The specified module could not be found. (Exception from HRESULT:0x8007007E) appeared first on BoostSolutions.

Cannot add the specified assembly to the global assembly cache: SharePointBoost.Integration.dll

Admin — Mon, 31 Mar 2014 19:43:55 +0000

An error occurs during the product installation:

Error: Cannot add the specified assembly to the global assembly cache: SharePointBoot.Integration.dll.

Solution:

This error might be caused by incomplete uninstallation, here is the step to resolve it:

1. Go to the gac folder:

SharePoint 2013:

C:\Windows\Microsoft.NET\assembly\GAC_MSIL;

SharePoint 2007/2010:

C:\windows\assembly

2. Find the folder named "SharePointBoost.Integration", and delete it.

3. Run the setup.exe again to install the product.

Applies for: SharePoint 2013, SharePoint 2010, SharePoint 2007

The post Cannot add the specified assembly to the global assembly cache: SharePointBoost.Integration.dll appeared first on BoostSolutions.

Could not find the specified solution file 'BoostSolutions.xxxxxx.x.wsp'

Admin — Mon, 31 Mar 2014 19:43:40 +0000

An error message shows up while installing the products:

Could not find the specified solution file ‘BoostSolutions.xxxxxxxxxxxxx14.3.wsp’

Solution:

Please try the steps below:
1. Unzip the file and run setup.exe.
2. Right click setup.exe and choose ‘Run as administrator’.

Applies for: SharePoint 2010

The post Could not find the specified solution file 'BoostSolutions.xxxxxx.x.wsp' appeared first on BoostSolutions.

Conflicting solution detected

Admin — Mon, 31 Mar 2014 19:43:27 +0000

While installing products, in the initial system check stage, a conflicting message shows:

Conflicting solution detected.

Solution:

This is mostly because a package was installed previously in the system while it’s installing a single product instead. Simply just remove the package product and reinstall the single product, the conflict would be gone.

Applies for: SharePoint 2013, SharePoint 2010, SharePoint 2007

The post Conflicting solution detected appeared first on BoostSolutions.

Installation procedure gets stuck

Admin — Mon, 31 Mar 2014 19:43:22 +0000

When installing products, the bar is not processing and installtion gets stuck.

Solution:

Some possible reasons:

One of the WFE servers is not running — please restart the server or related services
Time difference between WFE servers

Applies for: SharePoint 2013, SharePoint 2010, SharePoint 2007

The post Installation procedure gets stuck appeared first on BoostSolutions.

Access denied! Could not add solution to the SharePoint farm.

Admin — Mon, 31 Mar 2014 19:43:21 +0000

Error occurs after system check while installing products:

"Access denied! Could not add solution to the SharePoint farm. Make sure you are logged in as SharePoint Administrator or Domain Administrator on the server. Also, make sure to turn off Windows User Account Control."

Solution:

Please try the steps below:

Make sure you log on the server as SharePoint administrator or domain administrator
Extract the solution folder out of zip file, right-click on the setup.exe file, then choose ‘Run as administrator‘
If persists after the above steps, plesae turn off the UAC controls

Applies for: SharePoint 2013, SharePoint 2010

The post Access denied! Could not add solution to the SharePoint farm. appeared first on BoostSolutions.

Timed out error during deployment procedure

Admin — Mon, 31 Mar 2014 19:43:20 +0000

Timed out error when using the installer to install the product, during deploying procedure

Solution:

Please check the following settings in the sharepoint enviroment which might be the possible causes:

Make sure the servers are time cosistent
Make sure the services related to SharePoint on each server are running
Restart the Timer Services in all server side
VM restoration would be a cause

Applies for: SharePoint 2013, SharePoint 2010, SharePoint 2007

The post Timed out error during deployment procedure appeared first on BoostSolutions.

Failed to create a control from assembly 'SharePointBoost.License'

Admin — Mon, 31 Mar 2014 19:39:57 +0000

There are below error messages in SharePoint log when using BoostSolutions products:

Failed to create a control from assembly ‘SharePointBoost.License, Version=x.x.x.x, Culture=neutral, PublicKeyToken=15fd9ef9a2ec3a95′, class ‘SharePointBoost.License.Management.RedirectControl’: The control with assembly name "SharePointBoost.License, Version=2.0.9.2, Culture=neutral, PublicKeyToken=15fd9ef9a2ec3a95" class name "SharePointBoost.License.Management.RedirectControl" is not allowed for web at URL : http://xxxx. The type is not registered as safe.

Solution:

Reason

BoostSolutions License Management Center hasn’t been deployed to the content web application where customer is using BoostSolutions product.

Solution

For SharePoint 2007:

Go to Central Administration—>Operations—>Global Configuration—>Solutions Management to deploy "boostsolutions.foundationsetup12.x.wsp" to the content web application where customer is using BoostSolutions product.

For SharePoint 2010:

Go to Central Administration—>System Settings—>Farm Management—>Manage Farm Solutions to deploy "boostsolutions.foundationsetup14.x.wsp" to the content web application where customer is using BoostSolutions product.

For SharePoint 2013:

Go to Central Administration—>System Settings—>Farm Management—>Manage Farm Solutions to deploy "boostsolutions.foundationsetup15.x.wsp" to the content web application where customer is using BoostSolutions product.

Applies for: SharePoint 2013, SharePoint 2010, SharePoint 2007

The post Failed to create a control from assembly 'SharePointBoost.License' appeared first on BoostSolutions.

No product feature is found in new site collection

Admin — Mon, 31 Mar 2014 19:35:31 +0000

Product feature cannot be found under the new site collection, it’s not usable.

Solution:

This is due to the SharePoint solution mechanism. Existing wsp cannot be deployed automatically into the new web applications created. The solutions need to be deployed manually.

For new site collection created under existing web application, the features need to be activated manually as well.

Applies for: SharePoint 2013

The post No product feature is found in new site collection appeared first on BoostSolutions.