How to Ensure that Vizit is Completely Uninstalled

Under certain circumstances, the Vizit solution can fail to retract properly. This usually occurs when files are modified in the Vizit installation directories, a Web Front End is not properly connected to the farm, or some other configuration problem exists in the farm that prevents SharePoint from properly retracting the Vizit solution. Follow the steps below on each Web Front End in your farm to ensure that Vizit is completely removed.

Ensure that Vizit is Retracted

Before any installed Vizit files should be modified you must be sure that the solution is fully retracted and all Vizit features have been deactivated and uninstalled.

For this section of the KB, you must have access to the command line tool, STSADM. It is located in the BIN of the SharePoint directory on any one of your Web Front End servers. For the purpose of this KB, perform the following operations on the server that is running the Central Administration Web Application.

Complete these steps to ensure that Vizit is retracted:

  1.  In a command prompt, navigate to C:\Program Files\Common Files\Microsoft Share\web server extensions\15\BIN
    The above path would end in 14\BIN for SharePoint 2010 and 12\BIN for SharePoint 2007.
  2.  List the solutions that are currently installed on the farm using the following command:
    stsadm -o enumsolutions
  3. If Vizit appears in that list, attempt to retract the solution using the following command:
    stsadm -o retractsolution -name vizit.wsp -immediate -url http://webapplicationurl:port
  4. Repeat step three for each Web Application that Vizit was deployed to.
  5. If any of the retractions fail, you may have to deactivate and uninstall any features that are part of the solution.
    1. Use the following command to deactivate the Vizit features from any Site Collections that may have caused any Web Applications to fail retraction:
      stsadm -o deactivatefeature -name FEATURE_NAME -url http://path/to/site/collection
    2. Repeat this for each of the Vizit features.
    3. For SharePoint 2013 and SharePoint 2010, they are: Vizit, and Vizit.Scanning
      For SharePoint 2007, they are: Vizit, VizitListIntegeration, VizitSearchIntegration, and VizitScanning
    4. After the Vizit features are deactivated, they must be uninstalled using the following command:
      stsadm -o uninstallfeature -name FEATURE_NAME
    5. Repeat this for each of the Vizit features listed above as well as the Vizit.Admin feature (VizitAdmin in SharePoint 2007).
  6. Continue to repeat steps 2 through 5 until the Vizit solution is not listed when running the enumsolutions operation of STSADM. If deactivating or uninstalling features fail in the steps above, it may be necessary to run the command with the force flag. See STSADM's documentation for more infomration:
  7. Once the solution is successfully retracted from each of the Web Applications, run the following command to remove the solution:
    stsadm -o deletesolution -name vizit.wsp

Delete All Remaining Vizit Files

In certain circumstances, files may be left behind even after the solution has been retracted and any/all features are deactivated and uninstalled. Follow the steps below to ensure that all of the files installed with Vizit have been removed from each of your Web Front End servers as well as your Central Administration server:

  1. In a Windows Explorer window, navigate to C:\Program Files\Common Files\Microsoft Shared\web server extensions\15
    The above path would end in 14 for SharePoint 2010 and 12 for SharePoint 2007
  2. Navigate to the Resources directory and delete all files that start with "Vizit".
  3. Navigate to TEMPLATE\ADMIN
    1. Delete the Vizit folder.
    2. Delete the admin.sitemap.vizitsp.xml file.
      1. You may have to run stsadm -o copyappbincontent on each of your Web Front Ends to ensure that all sitemap information has been removed.
      2. If you are still receiving errors relating to "sitemap", you may have to navigate to the _app_bin directory of each of your Virtual Directory folders in inetpub to remove lines referencing "vizit" in the admin.sitemap file.
  4. Navigate to TEMPLATE\FEATURES and delete any folders starting with "Vizit".
  5. Navigate to TEMPLATE\CONTROLTEMPLATES and delete all files that start with "Vizit".
  6. Navigate to TEMPLATE\LAYOUTS and delete the Vizit folder.

Delete Vizit Assemblies

The last step that must be completed is deleting the assemblies that are installed in the Global Assembly Cache (the GAC) when the Vizit solution is deployed.

  1. Navigate to C:\Windows\assembly
  2. Delete all assemblies that start with "Vizit", "Atalasoft", and "Aspose". "Aspose" and "Atalasoft" are third-party libraries that maybe used by other products you have installed on your server. It is important to know what is using each of the assemblies you are deleting before they are removed.
    Due to the introduction of User Account Control (UAC) in Windows Vista, Windows 7 and Windows Server 2008, you may need additional permissions to remove assemblies from the GAC. In some cases, it is easiest to disable UAC while performing this step of the uninstallation process via the Control Panel. A restart may be required to make this change.

After all of these steps are completed on each Web Front End and the Central Administration server, Vizit has been completely removed from the Farm.

Deleting Caches

In addition to making sure that the files added to your SharePoint farm when Vizit is installed are deleted, you may also want to remove the files that are created by Vizit when it is in use. Caches for Vizit Essential and Vizit Pro are created opportunistically along with locations for storing annotations for Vizit Pro. Follow the instructions in these KB articles for removing these additional directories:

Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk