If you attempted to perform the uninstall procedure outlined in Using the Uninstall or Add/Remove Programs utility and it failed, you must manually remove the OpenEdge Uninstall folder before reinstalling. The uninstall file records the initial installation and appends additional installations to the file.
This section provides guidelines to manually uninstalling the OpenEdge folder located at C:\Program Files\InstallShield Installation Information\ {CFD926DB-10C8-4CB6-A6B3-49FD8F98262F}and performs other steps related to this task.
To manually uninstall OpenEdge:
1. Log in under the same domain and user name you used when you installed OpenEdge.
2. Make sure that OpenEdge is not running in an open DOS window (or that the current directory is not any OpenEdge-related directory).
3. Stop all OpenEdge processes and close all OpenEdge help files. You can use the Task Manager to ensure that you stop all processes and close all help files.
4. Using the OpenEdge Management or OpenEdge Explorer, shut down all OpenEdge services (brokers, NameServers, and databases).
5. Shut down the AdminServer by following these steps:
a. From the desktop, select Start > Control Panel > Administrative Tools > Services.
b. Highlight the AdminService for OpenEdge, and select Stop.
c. When the service stops, choose Action > Properties. The AdminService dialog box appears.
d. Change the Startup type from Automatic to Manual, and choose OK. (This step is necessary if you reboot your machine before completing the uninstall so that the AdminServer does not start up automatically.)
Note: If these same services will be required for a new installation, be sure to note any configuration settings, agent parameters, and so forth.
6. Shut down some services, as needed. Consider the following situations:
If you are using a Sun Web server (or NSAPI-compatible Web server) that uses the wsnsa.dll, you are not required to shut down a Windows service. You only have to shut down the Web server and the WebSpeed Transaction Server.
If you are using the Microsoft IIS Web server to use the WebSpeed Messenger that uses the wsisa.dll, you must shut down the IIS Admin Service.
7. Remove the C:\Program Files\InstallShield Installation Information\{CFD926DB-10C8-4CB6-A6B3-49FD8F98262F} directory.
8. Run regedit.exe (or regedt32.exe) to edit the Windows registry as follows:
a. Remove the <version> keys that appear under the HKEY_CURRENT_USER location. If there is only one release number identified under PSC, delete the PSC key, as shown:
b. Remove the <version> keys that appear under the HKEY_LOCAL_MACHINE location. Check the release number identified under each product subfolder. If only one release number is identified as installed for all products, delete the PSC key, as shown:
If you have installed 32-bit version of OpenEdge on a 64-bit version of Windows, the keys are located under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PSC\product name(s)\release number(s).
c. Remove the <version> key that appears under the following HKEY_LOCAL_MACHINE location:
9. If you have installed an OpenEdge product for which drivers have also been installed, run regedit.exe (or regedt32.exe) to edit the Windows registry as follows:
a. Go to HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI.
b. Remove the following key(s) (and the values it contains), as needed:
10. Depending on the products you have installed, the following files might have been registered during the install and should be unregistered:
dzocx32.ocx
pstimer.ocx
dzstat32.ocx
prox.dll
duzocx32.ocx
sstree.ocx
cscomb32.ocx
cihttp.ocx
csspin32.ocx
cslist32.ocx
Note: The registered version of some of these files might not be under the OpenEdge installation directory. Check the Windows system, system32, and SysWOW64 directories for these files.
The following example shows how you can unregister one of these OCX files. In the example it is located in the Windows system32 directory:
11. Delete the OpenEdge program directory, including all of its subdirectories. The default OpenEdge directory is C:\Progress\OpenEdge.
12. Delete the OpenEdge folder/group from the Windows Start menu.
13. Shut down your Web server and delete the cgiip.exe and wsisa.dll files from the Web server cgi-bin/scripts directory.
If you are uninstalling WebSpeed and using the Sun Web server that uses the wsnsa.dll, you must return the obj.conf file to its pre-WebSpeed state. If you are upgrading WebSpeed to the same directory, you need not modify the obj.conf file. However, if you intend to change the directory location, then you must modify the obj.conf file to reflect the correct location.
14. Depending on the installation options you chose (that is, Web server type, WebSpeed virtual directory, or having static HTML files copied to your Web server document root directory), you might need to perform either one, or both of the following steps:
a. Delete the WebSpeed directory from your Web server document root directory. For example, on MSIIS the default is: \InetPub\wwroot\webspeed.
b. Delete any virtual directories defined for WebSpeed in your Web server.
If you are using a Sun Web server (or NSAPI-compatible Web server) that uses the wsnsa.dll, you are not required to shut down a Windows service. You only have to shut down the Web server and the WebSpeed Transaction Server.