"Runtime error 429: Active X component can't create object", when generating a report in FRx

Entry type: Informational

Product: FRx

Application: FRx Desktop

Version reported: 6.0, 6.5.152

Subject:
"Runtime error 429: Active X component can't create object", when generating a report in FRx

Possible resolution:
FRx for all versions:
In the Catalog on the Output tab uncheck option: Prompt for Output Type at Run Time

If the problem persists:

The link below to RegFiles-v2.3.bat file may be used to register all FRx DLLs and several common system files that might cause the 429 error.

  1. Close all FRx applications.
  2. Place this file in the root directory of FRx (where the executables are located), and then double-click to execute.

Note any .DLL files that do not register; they must be registered manually. See the instructions below.

FRx version 6.5.152:
This error can be caused if FRx version 6.5.152 is installed in a Thin-Client environment and Internet Explorer version 5.50 or lower is being used.

  1. Install Internet Explorer 6.0
  2. If IE 6.0 cannot be installed, download the following files:
    1. FRx (both the CD and the service pack) installs msxml4.dll and some dependencies, but it does not install MSXML 3.0.  This means either IE 6.0 or MSXML 3.0 must be installed.  FRx recommends Internet Explorer 6.0 for 6.5.152 and later - this is the best way to ensure that MSXML 3.0 is installed.  If for some reason it is not possible to upgrade to Internet Explorer 6.0, Internet Explorer 5.5 may be used, but the MSXML 3.0 components must be installed.  MSXML 3.0 SP4 can be downloaded from: http://msdn.microsoft.com/library/default.asp?url=/downloads/list/xmlgeneral.asp
    2. Because msxml4.dll is installed with the service pack or full installation, most workstations do not get it in a thin client environment.  Therefore, it may be necessary to install Internet Explorer 6.0 (or MSXML 3.0) and MSXML 4.0 on most workstations. MSXML 4.0 SP2 can be downloaded from: http://msdn.microsoft.com/library/default.asp?url=/downloads/list/xmlgeneral.asp

To manually register DLL files:
There are several methods for registering DLL files in Windows. This document details four different ways to register a DLL. Each method yields the same result, so use the one that is easiest for you.

Method One

  1. Double-click the DLL. An Open With dialog appears.
  2. Click the Other button, and then browse to the Windows system directory
  3. Click the REGSVR32.exe file, click Open, and then click OK.

Method Two

  1. Click the Start button, and then click Run.
  2. In the Open dialog box, type regsvr32 "c:\path\to\DLLname.dll" (include quotes around the path and filename).
  3. Click OK.

Method Three

  1. Open a DOS prompt.
  2. Change to the directory where the DLL resides, and then type regsvr32 DLLname.dll

Method Four

In Windows Explorer, drag the icon for the DLL file and drop it on top of the regsvr32.exe file (located in the Windows system directory).

If the problem persists:

Search the workstation for SQLDMO.DLL. If one file is found, register it. If two copies of this file are found, examine the version of the files (right-click the file, select Properties, and then click the Version tab). Register the file with a version of 2000.80.xxx.x. Use one of the methods above to manually register the .DLL.

If the SQLDMO.DLL file was found, do not perform any of the remaining steps in this article.

If the SQLDMO.DLL file was not found in the steps above, proceed with the following steps:

  1. Click the link below, and save the SQLDMO.EXE file to the hard drive.
  2. Log on to the workstation as an administrative user.
  3. Double-click the SQLDMO.EXE file. A WinZip Self-Extractor window appears. The Unzip to folder field defaults to C:\Program Files\Common Files\System\Ole DB . If the Program Files directory is located on a different drive, change the drive letter. Otherwise, click the Unzip button.
  4. Register the \Program Files\Common Files\System\Ole DB\SQLDMO.DLL file.
  5. From the Catalog window in the FRx Designer, reselect the Prompt for Output Type at Run Time check box.
  6. Generate the report. The error should no longer occur.

Related Files: