SQL Server - uninstalling sql server express 2005 problem

Asked By Dinesh Sanwal on 06-Jan-10 10:10 AM

Dear Sir,

When i am uninstalling sql server 2005 express through add remove program in control panel, my system reboots without uninstalling sql server. This occurs every time i uninstall sql server.

Pls help me how to uninstall sql server from my pc.


Jonathan VH replied to Dinesh Sanwal on 06-Jan-10 10:22 AM
You'll probably need to http://support.microsoft.com/kb/909967.

re - Santhosh N replied to Dinesh Sanwal on 06-Jan-10 10:23 AM

There could be some programs which might be dependent ad also there is possibility that .net redistrible might be there which might be stopping it from uninstalling..
you could check http://geekswithblogs.net/mrnat/archive/2004/10/17/12760.aspx for more info and issues related to uninstall problems if express edition of sql server

uninstalling sql server express 2005 - Sagar P replied to Dinesh Sanwal on 06-Jan-10 10:24 AM

SEE THIS INFO:              

Under normal circumstances, all versions of SQL Server 2005 can be uninstalled using Add/Remove Programs and following these steps http://msdn2.microsoft.com/en-us/library/ms143412.aspx in SQL Server BOL. However, sometimes automated uninstall attempts do not work. http://support.microsoft.com/?kbid=909967 details the process of performing a manual uninstall.

Some installation problems are actually caused by a failure to fully uninstall other versions. If a beta or CTP version of SQL Server 2005 is not fully uninstalled before attempting an installation of SQL Server 2005, the installation may fail until the previous version is completely uninstalled. Additionally, an incomplete uninstall of SQL Server 2005 Express can cause problems when attempting to install one of the other versions of SQL Server 2005.

http://msdn.microsoft.com/en-us/library/ms143505(SQL.90).aspx

http://blogs.msdn.com/petersad/archive/2009/01/20/sql-server-2005-sp3-sql-server-2005-sp2-cus-or-sql-server-2008-may-cause-xp-sp2-to-restart.aspx

MS solution to uninstall - Sakshi a replied to Dinesh Sanwal on 06-Jan-10 10:28 AM

How to uninstall a stand-alone instance of SQL Server 2005 manually

loadTOCNode(2, 'moreinformation'); Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
http://support.microsoft.com/kb/322756/  (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows

Step 1: Make sure that the Microsoft SQL Server Setup Support Files component is installed

loadTOCNode(3, 'moreinformation'); In Add or Remove Programs, make sure that Microsoft SQL Server Setup Support Files appears in the list of installed programs. If Microsoft SQL Server Setup Support Files appears in the list, go to the "Step 2: Run the command to uninstall the SQL Server components" section.

If Microsoft SQL Server Setup Support Files does not appear in the list, install this component before you continue. To install this component, follow these steps:
  1. Locate the original SQL Server 2005 installation media.
  2. To install the support files, double-click the Servers\setup\sqlsupport.msi file.
Note In the "Step 5: Uninstall the Microsoft SQL Server Setup Support Files component" section, you uninstall this component.

Step 2: Run the command to uninstall the SQL Server components

loadTOCNode(3, 'moreinformation'); At a command prompt, run the following command:
"%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\ARPWrapper.exe /Remove"
Uninstall the SQL Server components one at a time until all the SQL Server components are uninstalled.

Note Add or Remove Programs also runs the ARPWrapper.exe program by using the /Remove option. However, the reference to the ARPWrapper.exe program may have been deleted.

If you have uninstalled SQL Server Reporting Services, you must perform the following tasks:
  • Delete the Reporting Services virtual directories
    loadTOCNode(4, 'moreinformation'); Use Microsoft Internet Information Services (IIS) Manager to delete the following virtual directories:
    • ReportServer[$InstanceName
    • Reports[$InstanceName
  • Delete the ReportServer application pool
    loadTOCNode(4, 'moreinformation'); Use IIS Manager to delete the ReportServer application pool.
If you receive the following error message, go to the "If you experience problems" section to uninstall the SQL Server redistributed files and the SQL Server support files:
Registry Enumeration Failed
You may have an instance that has more than one server. For example, you may have an instance that has SQL Server 2005 Database Engine, SQL Server 2005 Analysis Services, and SQL Server 2005 Reporting Services. If you have an instance that has more than one server, the Setup program fails, and you receive the following error message:
The setup has encountered an unexpected error in datastore. The action is RestoreSetupParams.
This error is expected because of refcounting. A refcount is used to track how many programs use the same .dll file or the same .msi file. When a program is uninstalled, the program decrements the refcount for an .msi file by one. When the last program is uninstalled, the .msi file is deleted. In this case, the .msi file is the Microsoft SQL Server Setup Support Files component (SqlSupport.msi). If you receive this error message, use one of the following methods to resolve this error:
  • Reinstall the Microsoft SQL Server Setup Support Files component (SqlSupport.msi) before you uninstall each component in the instance.
  • Temporarily refcount the SqlSupport.msi file to itself. To do this, follow these steps:
    1. Obtain the GUID for the Microsoft SQL Server Setup Support Files component. To obtain the GUID, follow steps 1 and 2 from the "If you experience problems" section.
    2. Use Registry Editor to create or to modify the following registry key with these values:
      Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\Bootstrap\MSIRefCount
      Value: Uninstall
      Type: REG_SZ
      Data: {11111111-1111-1111-1111-111111111111},{GUID}
      Note GUID is a placeholder for the GUID of the SQL Server support files. For example, the GUID of the English x86 SQL Server support files is as follows:
      Data: {11111111-1111-1111-1111-111111111111},{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
If you experience problems
loadTOCNode(4, 'moreinformation'); If you experience problems when you try to uninstall the SQL Server components, follow these steps:
  1. Start Registry Editor, and then locate the following registry key:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
  2. In the left pane, click each GUID. For each GUID that you click, look for a display name in the right pane that includes "Microsoft SQL Server 2005." For example, look for the following names:
    • Microsoft SQL Server 2005
    • Microsoft SQL Server 2005 Analysis Services
    • Microsoft SQL Server 2005 Reporting Services
    • Microsoft SQL Server 2005 Notification Services
    • Microsoft SQL Server 2005 Integration Services
    • Microsoft SQL Server 2005 Tools
    • Microsoft SQL Server 2005 Books Online
    When you see a display name that includes "Microsoft SQL Server 2005," note the GUID that you clicked in the left pane.
  3. For each GUID that you noted in step 2, run the following command at a command prompt:
    start /wait msiexec /x {GUID} /l*v c:\sql_uninstall.log
    Notes
    • In this command, replace GUID with the GUID that you noted in step 2.
    • If you receive the following error message, contact Microsoft Customer Support Services:
      The setup has encountered an unexpected error in datastore.
      For a complete list of Microsoft Product Support Services telephone numbers and for information about support costs, visit the following Microsoft Web site:
      http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
  4. Open the following file:
    C:\Sql_uninstall.log
    Approximately 15 lines from the bottom of the file, locate a line that resembles the following line:
    MSI (s) (EC:F8) [12:52:18:007]: Product: Microsoft SQL Server 2005 Tools -- Removal completed successfully.
    If the uninstallation process was not successful, note the component name and the GUID, and then save the Sql_uninstall.log file.

Step 3: Uninstall the support components

loadTOCNode(3, 'moreinformation'); Use Add or Remove Programs to uninstall the support components in the following order:
  • MSXML 6.0 Parser
  • SQLXML4
  • Microsoft SQL Server VSS Writer
  • Microsoft SQL Server 2005 Backward Compatibility
  • Anything else that is related to SQL Server 2005, except for the Microsoft SQL Server Native Client component and for the Microsoft SQL Server Setup Support Files component
If the uninstallation process fails for any one of the support components, you may receive the following error message:
Setup failed due to missing prerequisites
If you receive this error message, follow these steps:
  1. Start Registry Editor, and then locate the following registry key:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
  2. In the left pane, click each GUID. For each GUID that you click, look for a display name in the right pane that matches the name of the redistributable file. When you see a display name that matches the name of the redistributable file, note the GUID that you clicked in the left pane.
  3. For each GUID that you noted in step 2, run the following command at a command prompt:
    start /wait msiexec /x {GUID} SKIPREDISTPREREQS=1 /l*v c:\sqlredist_uninstall.log
    Note In this command, replace GUID with the GUID that you noted in step 2.
  4. Open the following file:
    C:\Sqlredist_uninstall.log
    At the bottom of the file, locate a line that resembles the following line:
    MSI (s) (EC:F8) [12:52:18:007]: Product: Microsoft SQL Server 2005 Backward compatibility -- Removal completed successfully.
    If the uninstallation process was not successful, note the component name and the GUID, and then save the Sqlredist_uninstall.log file.

Step 4: Uninstall the Microsoft SQL Server Native Client component

loadTOCNode(3, 'moreinformation'); If all the other steps were successful, uninstall the Microsoft SQL Server Native Client component by using Add or Remove Programs.

Note Do not uninstall the Microsoft SQL Server Native Client component if you have SQL Server 2000 components installed.

Step 5: Uninstall the Microsoft SQL Server Setup Support Files component

loadTOCNode(3, 'moreinformation'); If all the other steps were successful, uninstall the Microsoft SQL Server Setup Support Files component by using Add or Remove Programs.
http://support.microsoft.com/kb/909967#top

If these steps did not uninstall all the components

loadTOCNode(2, 'moreinformation'); If the previous steps did not uninstall all the components, follow these steps:
  1. Perform Step 1 in the "How to uninstall a stand-alone instance of SQL Server 2005 manually" section.
  2. In Add or Remove Programs, uninstall all SQL Server 2005 components in the following order:
    • SQL Server 2005
    • SQL Server 2005 Analysis Services
    • SQL Server 2005 Reporting Services
    • SQL Server 2005 Notification Services
    • SQL Server 2005 Integration Services
    • SQL Server 2005 Tools
    • SQL Server 2005 Books Online
    • MSXML 6.0 Parser
    • SQLXML4
    • SQL Server VSS Writer
    • SQL Server 2005 Backward Compatibility
    • Anything else that is related to SQL Server 2005
    • SQL Server Native Client
    • SQL Server setup support files
  3. Download and then install the Windows Installer CleanUp Utility. For more information about this utility, click the following article number to view the article in the Microsoft Knowledge Base:
    http://support.microsoft.com/kb/290301/  (http://support.microsoft.com/kb/290301/ ) Description of the Windows Installer CleanUp Utility
  4. Start the Windows Installer CleanUp Utility.
  5. If any of the components in step 2 are listed, follow these steps:
    1. Select the components, and then click Remove. You can use the CTRL key to select multiple components.
    2. When you receive the following warning message, click OK:
      All products selected will be removed from the Windows Installer database. In order for the products to work properly, you must individually re-install all products selected.
      Note Before you click OK, verify that the components that you selected are correct. These components will be permanently removed after you click OK.
    3. In Add or Remove Programs, uninstall the Windows Installer Cleanup Utility.

If these steps did not uninstall all the components and all the files that are related to the instance of SQL Server 2005, contact Microsoft Customer Support Services.


Thanks and Regards,
http://www.CodeCollege.NET
http://www.InterviewsGuru.info


 

solution 2 - Sakshi a replied to Dinesh Sanwal on 06-Jan-10 10:29 AM

this also has a solution

http://blogs.msdn.com/astebner/archive/2005/09/13/465401.aspx


Thanks and Regards,
http://www.CodeCollege.NET
http://www.InterviewsGuru.info


 

Jonathan VH replied to Sakshi a on 06-Jan-10 10:43 AM
You illegally copied to a public website the copyrighted MSKB article I linked in the first reply. Why?
to directly give the answer instead of giving the link - Sakshi a replied to Jonathan VH on 06-Jan-10 11:04 AM
to directly give the answer instead of giving the link
Jonathan VH replied to Sakshi a on 06-Jan-10 11:18 AM

Because someone using the eggheadcafe website may not have access to web pages?

There is a copyright at the end of every MSKB article, and a http://www.microsoft.com/info/cpyright.mspx#E4B.

yes i agree. gud to follow - Sakshi a replied to Jonathan VH on 06-Jan-10 11:22 AM
yes i agree. gud to  follow
As mentioned by Rob multiple times.... - Perry replied to Sakshi a on 07-Jan-10 02:32 AM
Please donot copy-paste copy-right materials here. Instead provide the link and your understanding. Your account will be disabled if you continue doing this.
Barbara Lolley replied to Jonathan VH on 18-Feb-10 05:48 PM
And How do I do that? I am at my witts end right now. And Copmuter stupid it what i am.