Salesforce

Is there a tool to fix registry corruption?

« Go Back

Information

 
TitleIs there a tool to fix registry corruption?
URL Name000030562
Article Number000151606
EnvironmentProduct: OpenEdge
Version: 10.1A, 10.1B. 10.1C, 10.2A, 10.2B, 11.x
OS: Windows
Question/Problem Description
Is there a tool to fix registry corruption?
What is the Registry Corruption Tool?
How can I fix registry corruption after installing OpenEdge?
How can I fix registry corruption where the OpenEdge version in the registry has 10.2Ax, 10.2Bx, 11.0x?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
There is an unsupported tool available called the Registry Corruption Tool which will fix registry corruption where an OpenEdge version has an extra character after it, such as 10.2Bu or 10.2Aw. Also, part of the registry information is under the correct key, such as 10.2B, and part is under the corrupt one, such as 10.2Bu. The tool will correct the key name and move the registry information from both keys to the correctly named key.
 
It has been tested on all supported Windows Operating Systems. The tool works 10.1A, 10.1B, 10.1C, 10.2A, 10.2B, and 11.0 for 32-bit OpenEdge as well as 64-bit OpenEdge.
 
There are separate tools for 32-bit and 64-bit OpenEdge.  The tool is located in the following directories:
 
The 32-bit application fixes the registry issue in 32-bit OpenEdge installed on a 32-bit OS or 64-bit Windows OS.
The 64-bit application fixes the registry issue only for 64-bit OpenEdge installed on a 64-bit Windows OS.
 
NOTE:  The command should be run "as Administrator" or the registry may not be updated.
Right Click the Proenv executable or shortcut icon and select "Run as Administrator" even if the account logged in is an Administrator account.

To run the 32-bit tool from a "proenv" environment, use the command syntax shown below (In Windows 10, proenv has to be started "as administrator"):
 
OERegFix32bit.exe  <OEVersion>
 
Where <OEVersion>: Open edge version (For example 10.1A, 10.2B, etc).
This is case sensitive.

Example:
 
OERegFix32bit.exe  10.2A  (works)
OERegFix32bit.exe  10.2a (doesn't work)
 
To run the 64-bit tool from the "proenv" environment and use the command syntax shown below:
 
OERegFix64bit.exe  <OEVersion>
 
Where <OEVersion>: Open edge version (For example 10.1A, 10.2B, etc).
This is case sensitive.

Example:
 
OERegFix64bit.exe  10.2A  (works)
OERegFix64bit.exe  10.2a (doesn't work)

Before fixing the registry issue, the  tool will make a registry Backup File:

<System-Drive>\Windows\PSC_HKLM_REG_KEY64_RegBackupXXX.reg (64bit open edge)
<System-Drive>\Windows\PSC_HKLM_REG_KEY32_RegBackupXXX.reg (32bit open edge)
<System-Drive>\Windows\PSC_HKCU_RegBackupXXX.reg (Both 32bit and 64bit)
 
Where XXX is Year Month Day Hour Minute Second
 
Logging information:
 
A log File will be created under: <System-Drive>\Windows\OERegFix.log
 
The tool returns the following in the OERegFix.log file:
 
0 – success
1 - normal failure scenario
2 - failed for insufficient arguments
3 - Error in finding registry or opening registry
4 - Failed to create/open log file
5 - Failed to find the log file location to create Windows directory
Workaround
Notes
This tool is not officially supported by Progress.
The tool will not recreate any missing Openedge registry keys.

How to use this tool from another installer application:
 
Create a sample application for an installscript project and use the following line of code to launch the tool silently:
 
szProram = "C:\\CCoding\\OERegFix32bit.exe"; //location and tool name
szCommand = "10.2B"; //commandline argument i.e open edge version
LaunchAppAndWait(szProram, szCommand, LAAW_OPTION_WAIT | LAAW_OPTION_HIDDEN);
 
To create a sample application for a Microsoft Installer (MSI) project use these steps to launch the tool silently:
 
Step 1: Write a custom function under installscript (setup.ru) with this line of code:
 
szProram = "C:\\CCoding\\OERegFix32bit.exe"; //location and tool name
szCommand = "10.2B"; //commandline argument i.e open edge version
LaunchAppAndWait(szProram, szCommand, LAAW_OPTION_WAIT | LAAW_OPTION_HIDDEN);
 
Step 2: Create a custom Action to call this installscript function.
 
To Do:  Create a custom action for this entry-point function:
1.  Right-click on "Custom Actions" in the Sequences/Actions view.
2.  Select "Custom Action Wizard" from the context menu.
3.  Proceed through the wizard and give the custom action a unique name.
4.  Select "Run InstallScript code" for the custom action type, and in
     the next panel select "MyFunction" (or the new name of the entry-
     point function) for the source.
5.  Click Next, accepting the default selections until the wizard
     creates the custom action.

References to Other Documentation:

Progress Article(s):
 Unable to launch Openedge products and install Service Pack on Windows
Keyword Phrase
Last Modified Date11/20/2020 7:19 AM

Powered by