Error message when you start Microsoft FRx Report Server: "Error 3709 - The connection cannot be used to perform this operation"

Applies to: Microsoft Dynamics AX 4.0Microsoft Dynamics AX 3.0Microsoft Dynamics NAV 5.0

Symptoms


When you start Microsoft FRx Report Server, you receive the following error message:

Error 3709 - The connection cannot be used to perform this operation

Cause


This problem occurs for one of the following reasons.

Cause 1

The workstations do not have the same version of Microsoft FRx Designer or of Microsoft FRx Report Server. See Resolution 1 in the "Resolution" section.

Cause 2

The necessary Microsoft FRx folders have incorrect user permissions. See Resolution 2 in the "Resolution" section.

Cause 3

The building block is corrupted, the specification set is corrupted, or the .f32 files are corrupted. See Resolution 3 in the "Resolution" section.

Cause 4

The FRxQue32.mdb file is corrupted. See Resolution 4 in the "Resolution" section.

Resolution


Resolution 1

To resolve this problem, check the version of Microsoft FRx on every computer that has Microsoft FRx code. To do this, follow these steps.

Microsoft FRx Designer

  1. Click Start, click Search, and then type FRx32.exe.
  2. Right-click FRx32.exe, and then click Properties.
  3. Click the Version tab, and then note the file version.

Microsoft FRx Report Server

  1. Click Start, click Search, and then type RptSvr32.exe.
  2. Right-click RptSvr32.exe, and then click Properties.
  3. Click the Version tab, and then note the file version.
These file versions must be identical on every workstation on the network. If the file versions are not identical, you must apply the appropriate service pack to the application that does not have the same file version.


You can also update to the latest service pack. For more information, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer.

PartnersCustomers

Resolution 2

Set the correct permissions

Set the correct permissions to all folders that Microsoft FRx must access. To do this, follow these steps.
  1. Log on to the computer as the local administrator or as the domain administrator.
  2. Click Start, click Search, and then click All files and Folders.
  3. Search for the following folders:
    • The FRx code folder. By default, the path is C:\Program Files\FRx Software
    • The IO_Data folder.
    • The SysData folder.
    • The Temp folder.
    • The MSInfo folder.
    • The System32 folder.
  4. For each folder that is listed in step 3, follow these steps:
    1. Right-click the folder, and then click Properties.
    2. In the Properties dialog box, click the Security tab.
    3. Make sure that the Administrator user and all the Microsoft FRx users have the following permissions:
      • For the FRx code folder: Full Control
      • For the IO_Data folder: Full Control
      • For the SysData folder: Full Control
      • For the Temp folder: Full Control
      • For the MSInfo folder: Full Control
      • For the System32 folder: A minimum of "Read & Execute"
    4. If there are users who are set up in different security groups, make sure that those users have the same permissions as the groups in step 4c.

Resolution 3

To resolve this problem, correct the building block, correct the specification set, or correct the .f32 files. To do this, follow these steps:
  1. If the error is limited to one catalog, one row, one column, or one tree, re-create that particular building block.
  2. If the error occurs for multiple building blocks, create a new specification set that contains a new .f32 file. To do this, follow these steps:
    1. Start Microsoft FRx, click Company, and then click Specification Sets.
    2. Select the specification set that the company is using.
    3. Click Export, and then select all the items on each tab.
    4. Click Export again. A .tdb file is created.
    5. To create a new specification set, click New, and then type a new file name for the .f32 file in the
      Location box.
    6. Save the new specification set.
    7. Click Import, and then select the .tdb file that was created in step 2d earlier in this section.
    8. Save the specification set.
    9. Click Company, click Information, and then select the new specification set in the Specification Set list. Save the company record.
    10. Set the company as the default company.

Resolution 4

To resolve this problem replace the FRxQue32.mdb file. To do this, follow these steps:
  1. Stop the Microsoft FRx Queue Monitor. To do this, click the Stop/Shutdown button.

  2. Rename the FRxQue32.mdb file in the Microsoft FRx queue directory. For example, rename the file as FRxQue32.old.
  3. Make a copy of the FRxQue32.tpl file, and then rename the copy to FRxQue32.mdb. The FRxQue32.tpl file is located in the SysData directory.
  4. Double-click the RptSvr32.exe file to restart the Microsoft FRx Queue Monitor. To find the RptSvr32.exe file, follow these steps:
    1. Right-click Start, and then click Explore All Users.
    2. Locate the Microsoft FRx Report Server code folder. By default, the path is as follows:
      C:\Program Files\FRx Software\FRx 6.7 Report Server
      The RptSvr32.exe file is in this folder.
    NoteYou may experience the following problem:
    • Files that have an .ldb file name extension or an .lck file name extension remain in the Microsoft FRx SysData folder even when no users are logged on to Microsoft FRx.
    If you experience this problem, opportunistic locking may be corrupting the Microsoft Jet database. This problem may occur if the server that is hosting the Microsoft 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
    • Windows Server 2003 Terminal Server together with Citrix
    To prevent opportunistic locking from corrupting the Microsoft Jet database, install the latest Windows Server service pack. However, if this problem 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 PC Ext: 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.