You receive error messages, and FRx Designer does not start when Microsoft FRx tries to access FRx database files

Applies to: Microsoft Dynamics AX 4.0

Symptoms


You may experience unexpected behavior when Microsoft FRx tries to access one or more of the following FRx database files:
  • Frxsys32.mdb
  • Frxque32.mdb
  • Files that have an .f32 file name extension
For example, you may experience the following symptoms:
  • You receive one of the following error messages.
    Error message 1
    Run-time error '-2147467259 (80004005)': Unrecognized database format.
    Error message 2
    Run-time error '3343': Unrecognized database format.
    Error message 3
    Error 3709. The connection cannot be used to perform this operation. It is either closed or invalid in this context.
  • FRx Designer may not start. When you to try to start FRx Designer, the startup screen briefly appears. Then, it disappears.
  • When you generate a report in Microsoft FRx Report Designer, you receive the following error message:
    The Microsoft Jet Database Engine cannot find the input table or query 'Active Users'. Make sure that it exists and is spelled correctly.
When you experience these symptoms, you can no longer use Microsoft FRx. After you perform a compact and repair operation on the database, Microsoft FRx operates as expected. However, you may receive the same error message again a short time later.

Cause


This problem may occur if the Microsoft Jet databases that are used by Microsoft FRx are corrupted. The following issues may cause database corruption:
  • Outdated system files
  • Mismatched Microsoft FRx service packs
  • Network connectivity issues
  • Issues with environment settings

Resolution


To prevent this problem, use one or more of the following methods as appropriate.

Method 1: Regularly perform a compact and repair operation on the database

  1. Start Microsoft FRx. You can start Microsoft FRx on a workstation. Or, if Microsoft FRx is installed on a server, you can start Microsoft FRx on the server.
  2. Click File, point to Compact FRx Database, and then click Current Spec Set Database.
  3. Click Yes, and then click OK when the operation is complete.
  4. Click File, point to Compact FRx Database, and then click FRx System Database.
  5. Click Yes, and then click OK when the operation is complete.
  6. Click File, point to Compact FRx Database, and then click FRx Queue Database.

    Note The FRx Queue database will only be available if FRx Report Server is installed.
  7. Click Yes, and then click OK when the operation is complete.
If you continue to receive one of the error messages that are mentioned in the "Symptoms" section, perform Method 2.

Method 2: Make sure that all the workstations that have FRx Designer installed are up to date

Follow these steps on each workstation that has FRx Designer installed:
  1. Use Microsoft Update to install the latest Microsoft Windows service pack. For more information about Microsoft Update, visit the following Microsoft Web site:
  2. Obtain and install the latest Microsoft Jet service pack. To obtain Microsoft Jet service packs, visit the following Microsoft Web site: To find the latest Microsoft Jet service pack, click All Downloads in the Search list, type Jet updates, and then click Go.
  3. Configure exclusions in the antivirus and antispyware programs to prevent these programs from reading the FRx SysData folder.

    For information about how to configure exclusions, see the antivirus and antispyware program configuration instructions.

    Note When you install Microsoft FRx, make sure that the antivirus and antispyware programs are disabled. This will prevent installation files from being corrupted or from being blocked during the installation.
If you continue to receive one of the error messages that are mentioned in the "Symptoms" section, perform Method 3.

Method 3: Disable opportunistic locking on the server that hosts the FRx SysData folder

If you experience the following behavior, opportunistic locking may be causing corruption in the Microsoft Jet database:
  • After you perform Method 1 and Method 2, you continue to receive one of the error messages that are mentioned in the "Symptoms" section.
  • Files that have an .ldb or .lck file name extension remain in the FRx SysData folder even when no users are logged on to FRx.
This behavior may occur if the server that is hosting the FRx SysData folder is running any of the following programs:
  • Microsoft Windows Server 2003 or Windows Server 2003 Terminal Server
  • Microsoft Windows 2000 Server or Windows 2000 Server Terminal Services
  • Citrix Server
To prevent opportunistic locking from causing corruption in the Microsoft Jet database, install the latest Windows Server service pack. However, if the behavior that is mentioned in this section continues to occur after you install the latest Windows Server service pack, disable opportunistic locking. For more information about how to disable opportunistic locking, click the following article numbers to view the articles in the Microsoft Knowledge Base:

296264 Configuring opportunistic locking in Windows

129202 Explanation of opportunistic locking on Windows NT

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.