Error message when you start Microsoft FRx: "Invalid SysData directory"

Symptoms

When you start Microsoft FRx, you receive the following error message:
"Invalid SysData directory. Check the directory keyname in the [SYSDATA] section of your FRx32.cfg file. Make sure you have read/write permissions to the network directory."

Cause

This problem may occur for one of the following reasons.

Cause 1

The permissions to one or more folders are incorrect. To resolve this problem, see Resolution 1.

Cause 2

The FRx32.cfg file or the System.cfg file has incorrect path information. This problem occurs if the Microsoft FRx program is moved, if the Microsoft FRx data is moved, or if the mapped drives are changed. This problem occurs in Microsoft FRx 6.7 Service Pack 8 and in earlier versions of Microsoft FRx 6.7. To resolve this problem, see Resolution 2.

Cause 3

The FRxConfig.xml file in the user profile for Microsoft FRx 6.7 Service Pack 9 and for later versions contains the incorrect SysData path. To resolve this problem, see Resolution 3.

Cause 4

The FRxSys32.mdb file or the FRxRpts.f32 file is corrupted. To resolve this problem, see Resolution 4.

Resolution

Resolution 1

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.
Note In addition to these steps, verify that all users have Full Control permissions to the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\FRx Software
Additionally, if you use a shared SysData folder, verify that the folder is shared. To do this, follow these steps:
  1. Log on as the local administrator to the server where the SysData folder is. Right-click the shared SysData folder, and then click Properties.
  2. Click the Sharing tab, and then verify that Share this folder is selected.
  3. If Share this folder is not selected, click Share this folder, and then click Apply.

Resolution 2

Step 1: Verify the path of the FRx32.cfg file

  1. Locate the Microsoft FRx folder that contains the program.
  2. Right-click the FRx32.cfg file, click Open With, and then click Notepad.
  3. Copy the path from the following line of code.
    Directory=
    Note This path contains the path of the SysData folder. This path should contain a trailing backslash. By default, the SysData folder has the following path:
    C:\Program Files\FRx Software\FRx 6.7\SysData\
    If the SysData folder is located on another computer, you must use a Universal Naming Convention (UNC) path. For example, use the following path:
    \\ Server_Name\FRx67\SysData\
  4. Click Start, click Run, paste the path that you copied into the Open field, and then click OK.
  5. Verify that the path that you pasted in step 4 exists, and then verify that you can see the contents of the SysData folder.
Note
  • If the SysData folder does not exist in the default location, change the directory to the actual location of the SysData folder.
  • If you do not have access to the location of the SysData folder, contact the system administrator.

Step 2: Verify the path of the System.cfg file

  1. Locate the System.cfg file in the SysData folder.
  2. Right-click the System.cfg file, click Open With, and then click Notepad.
  3. If the System.cfg file contains the following line of code, delete this line of code.
    MoveTo=
  4. Click File, click Save, and then close the file in Notepad.

Resolution 3

Verify the SysData path in the FRxConfig.xml file for Microsoft FRx 6.7 Service Pack 9 and for later versions. To do this, follow these steps:
  1. Right-click Start, and then click Explore.
  2. Locate the FRxConfig.xml file in the "FRx 6.7" folder under each user profile.
    • The following path is the default path for this file in Windows XP, in Windows Server 2003, in Windows Server 2000, and in Windows 2000:

      C:\Documents and Settings\user_name\Local Settings\Application Data\FRx Software\FRx 6.7\FRxConfig.xml
    • The following path is the default path for this file in Windows Vista:
      C:\Users\user_name\AppData\Local\FRx Software\FRx 6.7\FRxConfig.xml

  3. Right-click the FRxConfig.xml file, and then click Edit.
  4. Verify that the SysData path is for the correct shared SysData folder.

Note When you update the SysData path, keep the <sysdataPath> tag at the beginning of the path and at the end of the path.

Resolution 4

Restore the FRxSys32.mdb file and the FRxRpts.f32 file from the backups. To do this, follow these steps:
  1. Locate the FRxSys32.mdb file in the SysData folder. To do this, follow these steps:
    1. Click Start, point to All Programs, point to FRx 6.7, and then click Report Designer.
    2. Click Admin, click Organization, and then click SysData.

      The path of the SysData folder is in the Current directory box.
  2. Rename the FRxSys32.mdb file as FRxSys32.bak.
  3. Restore the FRxSys32.mdb file from the backup, and then put the file in the SysData folder.
  4. Repeat step 1 through step 3 for the FRxRpts.f32 file.
Properties

Article ID: 871831 - Last Review: 24 Jul 2011 - Revision: 1

Feedback