Export (0) Print
Expand All

Uninstall Duet Enterprise

 

Applies to: Duet Enterprise for Microsoft SharePoint and SAP

Topic Last Modified: 2011-08-05

This article describes how to uninstall Duet Enterprise solutions. The uninstall procedures explain the following processes:

  • How to uninstall a specific Duet Enterprise solution from a specific Web application

  • How to uninstall all Duet Enterprise solutions at the same time

  • How to remove all Duet Enterprise files from the front-end Web servers

  • How to restart IIS and SharePoint services, which is necessary after uninstalling one or more solutions

In this article

When you uninstall specific Duet Enterprise solutions, you must uninstall the solutions from the Web application to which the solutions were deployed. The names of solutions that you use to uninstall solutions are case-sensitive so you must pay attention to capitalization and follow the exact solution name.

This section explains how to uninstall a specific Duet Enterprise solution from a specific Web application in a SharePoint Server farm. If you want to delete the same solution from multiple Web applications, you must complete these steps separately for each Web application that contains the solution that you want to uninstall.

There are two ways to uninstall a Duet Enterprise solution. We recommend that you first use DuetConfig to uninstall a solution because it is the easier of the two ways. In some cases, DuetConfig might not completely remove the solution. If this occurs, you will see an error message that resembles the following when you attempt to reinstall the solution.

A feature with ID <ID number>has already been installed in this farm. Use the force attribute to explicitly re-install the feature.

If this occurs, use the Stsadm -o uninstallfeature command of stsadm as shown later in this article.

noteNote
You must be a member of the farm administrators group to uninstall Duet Enterprise solutions from SharePoint Server 2010.
To uninstall a specific solution by using DuetConfig
  1. Log on to any Web front-end server or application server in the SharePoint Server farm.

  2. Open a Command prompt window and locate the <systemdrive>:\Program Files\Duet Enterprise\1.0 folder.

    This folder contains the DuetConfig.exe.config file.

  3. At a prompt type DuetConfig /removesolution “SolutionName” /webappurl http://URL

    Where:

    • <SolutionName> is the name of the Duet Enterprise solution to be removed

    • <URL> is the URL of the Web application where the solution is deployed

    tipTip
    The solutionname is case-sensitive. Type the exact name of the solution that you want to uninstall. For a list of solutions that are provided with Duet Enterprise, see List of solutions (http://go.microsoft.com/fwlink/p/?LinkId=205306).
  4. Press Enter. When you run this command, the server that is running SharePoint Server creates a job request, puts it in the job queue, and then starts this job. This may take several minutes depending on how busy the server is at the time when you run this command.

  5. If the uninstall command is successful the command returns the following message:

    The solution <solutionname::solution ID> was successfully removed.

  6. To ensure that SharePoint Server will not use the old .dll files if the solution is later reinstalled, you must restart IIS and SharePoint services. For more information, see Restart IIS and SharePoint services.

To uninstall a Duet Enterprise solution by using stsadm
  1. Log on to any Web front-end server or application server in the SharePoint Server farm.

  2. Open a Command Prompt window as a farm administrator.

  3. At the prompt, type stsadm.exe -o uninstallfeature -filename <FileName> -name <FolderName> -id <FeatureID> -force and then press Enter.

    Where:

    • <FileName> is the full path and file name of the solution

    • <FolderName> is the name of the solution folder

    • <FeatureID> is the ID of the solution

If you want to remove all Duet Enterprise solutions from all Web applications and also unregister all Duet Enterprise components, there are two commands that you must use:

  • DuetConfig /uninstall removes all solutions from all Web applications and unregisters all Duet Enterprise components, at the same time.

  • setup /uninstall remove all traces of Duet Enterprise.

The following procedure explains how to uninstall all Duet Enterprise solutions that you have deployed to a SharePoint Server farm and also how to remove all traces of Duet Enterprise on each front-end Web server in the SharePoint Server farm. You can run each command alone or consecutively, according to what you want to uninstall.

To uninstall all solutions
  1. Verify that you have the following administrative credentials:

    • You must be a member of the Farm Administrators group to uninstall Duet Enterprise solutions from SharePoint Server 2010.

  2. Open a Command Prompt window on a front-end Web server computer in the SharePoint Server 2010 farm and locate <systemdrive>:\Program Files\Duet Enterprise\1.0.

    This folder contains the DuetConfig.exe.config file.

  3. At the prompt type DuetConfig /uninstall and press Enter.

    noteNote
    This command removes all solutions from all Web applications and unregisters all Duet Enterprise components, at the same time.
  4. If the uninstall command is successful the command returns the following message.

    Duet Enterprise unconfiguration succeeded

  5. Next, at the prompt, go to the folder that contains the setup.exe file for Duet Enterprise. If this file is not in the file system of the server running Microsoft SharePoint Server 2010, you can locate this file on the Microsoft SharePoint and SAP DVD.

  6. Type setup /uninstall and then press ENTER.

    If the setup /uninstall command is successful, the command returns the following message:

    Duet Enterprise setup completed successfully

    Press any key to continue…

    noteNote
    You must run this command on each front-end Web server to completely remove all traces of Duet Enterprise.
  7. When you run these commands, the server that is running SharePoint Server 2010 creates a job request for each, puts each in the job queue, and then starts them. This may take several minutes to complete depending on how busy the server is at the time when you run these commands.

  8. To ensure that SharePoint Server will not use the old .dll files if the solution is reinstalled, you must restart IIS and SharePoint services. For more information, see Restart IIS and SharePoint services later in this article.

To ensure that solutions that have been uninstalled can no longer be run in the SharePoint Server farm, you must restart IIS, the SharePoint 2010 Administration service, and the SharePoint 2010 Timer service.

noteNote
You must be a member of the Windows Administrators group on each front-end Web server in the network load balancing rotation of the SharePoint Server farm to complete these procedures.
To restart IIS
  1. Log on to the front-end Web server of the SharePoint Server farm as a member of the Windows Administrators group.

  2. Open a Command Prompt window as Administrator (Run as administrator).

  3. At the prompt, type iisreset /restart and then press Enter.

  4. After the “Internet services successfully restarted” message appears in the Command Prompt window, close the Command Prompt window.

  5. If you have more than one front-end Web server in the network load balancing rotation for the SharePoint Server farm, repeat steps 1 through 4 for each remaining front-end Web server.

To restart the SharePoint services
  1. Log on to the front-end Web server of the SharePoint Server farm as a member of the Windows Administrators group.

  2. Click Start, point to Administrative Tools, and then click Services.

  3. In the Name column, right-click SharePoint 2010 Administration, and then click Restart.

  4. In the Name column, right-click SharePoint 2010 Timer, and then click Restart.

  5. If you have more than one front-end Web server in the network load balancing rotation for the SharePoint Server farm, repeat steps 1 through 4 for each remaining front-end Web server.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft