TechKnowledge Content
Potential Causes
1. CSTEXT32.OCX is not located in the \WINNT\SYSTEM32 directory. See resolution 26354.
2. CSTEXT32.OCX is not registered. See resolution 8674.
3. FRx installation is corrupt. See resolution 7166 for FRx 5.5. See resolution 1 for FRx 6.x.
4. Windows installation is corrupt. See resolution 23772.
Resolutions
Resolution 8674 - Register the *.DLL or *.OCX file using REGSVR32.EXE or REGSVR.EXE.
1. Using Explorer, locate the file indicated in the message and right-click on the file.
2. Select Open With from the menu.
3. Click the Other button at the bottom of the Open With window.
4. Browse to the local drive (most often C:\), and select either REGSVR32.EXE in WINNT\SYSTEM32 or REGSVR.EXE in WINDOWS\SYSTEM.
5. Click Open.
6. Click OK. A message will display indicating whether the file was successfully registered.
OR
1. At a DOS prompt, select the drive where Solomon is installed.
2. Enter REGSVR32 followed by the name of the .DLL to be registered.
Example: REGSVR32 FSFRL32.DLL
3. Press Enter.
Resolution 7166 - Uninstall and reinstall FRx Version 5.5 to the appropriate Solomon IV directory.
WARNING: If custom FRx reports and production companies have been created, make a copy of the current FV\SYSDATA (Advanced Edition) or FX\SYSDATA (Standard Edition) folder and store it outside of the current FRx installation path. Failure to do so will result in the loss of report formats, Company and Spec Set setup information, and software registration data.
Note -
Technical Bulletin 2616- FRx 5.5 Uninstalling/Reinstalling Detailed Process.
1. In Start | Programs, locate the FRx program group and click on Uninstall FRx to remove the program.
2. It will be necessary to delete the files in the \FV (Advanced) or \FX (Standard) directory after the FRx Uninstall program, but before reinstalling FRx.
3. Reinstall FRx to Solomon IV\FV (Advanced Edition) or Solomon IV\FX (Standard Edition).
Note -FRx will not operate correctly in Solomon if any other directory is chosen.
4. Rerun the workstation setup and point to the drive letter that the workstation has mapped to Solomon IV\FV or Solomon IV\FX on the server.
Note - All workstations must be mapped to the server using the same drive letter.
Resolution 1 - Uninstall and reinstall FRx Version 6.x to the appropriate Solomon IV directory.
WARNING: If custom FRx reports and production companies have been created, make a copy of the current FD\SYSDATA (FRx 6.0 Desktop Edition),FP\SYSDATA (FRx 6.0 ProfessionalEdition), FD65\SYSDATA (FRx 6.5 Desktop Edition) orFP65\SYSDATA (FRx 6.5 ProfessionalEdition) folder and store it outside of the current FRx installation path. Failure to do so will result in the loss of report formats, Company and Spec Set setup information, and software registration data.
Additional Resource:
Detailed Process for Uninstalling/Reinstalling FRx 6.x
Correction Steps
1. In Start | Programs, locate the FRx program group and click on Uninstall FRx to remove the program.
2. It will be necessary to delete the files in the \FD (FRx 6.0 Desktop Edition),\FP (FRx 6.0 ProfessionalEdition), \FD65 (FRx 6.5 Desktop Edition) or\FP65 (FRx 6.5 ProfessionalEdition) directory after the FRx Uninstall program, but before reinstalling FRx. It will also be necessary to delete the frx.ini file from the windows directory.
3. Reinstall FRx to Solomon IV \FD (FRx 6.0 Desktop Edition),\FP (FRx 6.0 ProfessionalEdition), \FD65 (FRx 6.5 Desktop Edition) or\FP65 (FRx 6.5 ProfessionalEdition) directory.
Note- FRx will not operate correctly in Solomon if any other directory is chosen.
4. Rerun the workstation setup and point to the correct UNC pathto Solomon IV
\FD (FRx 6.0 Desktop Edition),\FP (FRx 6.0 ProfessionalEdition), \FD65 (FRx 6.5 Desktop Edition) or\FP65 (FRx 6.5 ProfessionalEdition)on the server.
Resolution 23772 - Reinstall the Windows operating system.
Notes
1. Contact Microsoft for assistance if necessary.
2. Errors sometimes occur after upgrading the Windows operating system due to conflicts that occurred during the process. Reinstalling the Windows operating system a second time usually corrects the error.
Resolution 26354 - Copy the missing or corrupt file from another workstation and place it in the appropriate directory.
This article was TechKnowledge Document ID:132018
