DetailPage-MSS-KB

Microsoft Knowledge Base

Article ID: 857402 - Last Review: December 26, 2014 - Revision: 3.0

This article has been archived. It is offered "as is" and will no longer be updated.
Microsoft Business Solutions-Axapta 3.0 is now part of Microsoft Dynamics AX 3.0. All references to Microsoft Business Solutions-Axapta and Microsoft Axapta pertain to Microsoft Dynamics AX.

TechKnowledge Content

Checklist to Troubleshoot FRx ExpressLink Errors

1. The IIS user (anonymous access user) doesn't have full control to the sysdata directory and cannot create a *.ldb file.

To check:

a. Check the security permissions on the sys data folder.

b. Make sure the anonymous access user has full control on the sysdata.

If the above is verified, then:

a. Log into the web server machine as the anonymous access user.

b. Browse out to the shared sysdata.

c. Try pasting a file into the sysdata and then delete it.

2. The IIS user doesn't have permissions to the LIB directory to save map files.

To check:

a. Check the security permissions on the LIB folder.

b. Make sure the anonymous access user has full control on the LIB folder.

If the above is verified, then:

a. Log into the web server machine as the anonymous access user.

b. Browse to the LIB folder.

c. Try pasting a file into the LIB folder then delete it.

3. The Reporter directory is not in the system PATH therefore cannot locate dependant FRx dlls.

To check:

a. Right click on My Computer on the desktop of the web server machine.

b. Go to Properties | Advanced.

c. Click on Environment Variables.

d. Select Path and then click Edit.

e. Verify the path to FRx Financial Reporter exists in the Variable Value.

Note - If it is not and you need to add it, make sure to press End to add it to the end of the variable.

4. The actsys32.mdb in the shared sysdata does not represent the correct OFSI's that are installed on the web server.

To check:

a. Open the actsys32.mdb file in the shared SysData.

b. Open the actsys32.mdb file in the sysdata on the web server.

c. Verify in the System_Settings table that the same OFSI(s) are marked ‘YES’.

5. The OFSI that is registered on the web server is not the same as what appears in the Actsys32.mdb file in the shared sysdata.

To check:

a. Open the Actsys32.mdb file in the shared SysData.

b. Verify in the System_Settings table that the OFSI(s) marked with ‘YES’ are the same OFSI(s) registered on the web server.

6. The FRx32.cfg file does not have the correct path to the sysdata folder.

To check:

a. Open the FRx32.cfg file in the LIB folder on the webs server.

b. Verify the path to the sysdata folder is valid.

7. The OFSI or any of the other dependant DLLs not being registered on the server.

To check:

Using regserver32 register the OFSI(s) and the FRxGL.dll on the web server.

8. The FRxGL.dll and the FRxSWII.dll versions are not the same in both FRx Forecaster and FRx Financial Reporter.

To check:

Verify the dates of both the FRxGL.dll and FRxSWII.dll are the same in both the FRx Forecaster LIB folder and the FRx Financial Reporter folder.

Note - With the FRx Forecaster SP2 installation, these files are going to be installed and registered to c:/Program Files/Common Files/FRx.

Common Issues with scheduling or running the FRx ExpressLink load (Forecaster 6.5 ONLY)

1. The ExpressLinkMgr.dll is not properly set up in COM+ (The COM+ user is not an administrator).

To check:

a. Go to Start | Programs | Administrative Tools | Component Services.

b. Expand the Component Services.

c. Right click on the FRx ExpressLink Manager and go to Properties.

d. Click on the Identity tab and verify the user is a local machine administrator.

2. The IIS scheduling service is not running on the machine.

To check:

a. Verify the user that is setup in COM+ (# 1 above) the same user must be defined in the registry key authUser found in: HKEY_LOCAL_MACHINE\SOFTWARE\FRx Software\FRx Forecaster\ExpressLink.

3. The scheduled task is running under a user that does not have access to write to the database.

To check:

a. Have Control panel | Scheduled Task open in windows explorer on the web server.

b. From another workstation (not the web server) go through the ExpressLink Wizard.

c. When you click on Finish in the wizard, go to Scheduled Task window and press F5 (to refresh) and you will see the task ExpressLink is scheduling.

d. Right click on it and go to Properties.

e. The Run as user should have access to Write to the database.

Note - Theoretically this should be running under the anonymous access user of the FRx Forecaster site. However, it could be calling the IUSER_(SERVERNAME). If this is the case make sure the IUSER_(SERVERNAME) has rights to write to the FRx Forecaster database. It may also be calling the user of the default website. If it is not the same as the FRx Forecaster anonymous access user, either change the default web site’s user to the FRx Forecaster anonymous access user or give the calling user rights to write to the FRx Forecaster database.

5. The Scheduled task is not getting created.

To check:

a. Have Control panel | Scheduled Task open in windows explorer on the web server.

b. From another workstation (not the web server) go through the ExpressLink Wizard.

c. When you click on Finish in the wizard, go to Scheduled Task window and press F5 (to refresh) and you will see the task ExpressLink is scheduling.

Note - If it is not getting created, we may have an issue with permissions regarding creating scheduled tasks.

Keywords: express link

This article was TechKnowledge Document ID: 27528

APPLIES TO
  • Microsoft Business Solutions for Analytics–Forecaster 6.7
  • Microsoft Dynamics GP 9.0
  • Microsoft Business Solutions–Great Plains 8.0
  • Microsoft Business Solutions–Great Plains 7.5
  • Microsoft Dynamics SL 6.5
  • Microsoft Business Solutions–Solomon 6.0
  • Microsoft Dynamics AX 3.0, when used with:
    • Microsoft Business Solutions for Analytics–Forecaster 6.7
Keywords: 
kbnosurvey kbarchive kbsolomonfrx kbgreatplainsfrx kbaxaptafrx kbmbsmigrate KB857402
Condividi
Altre opzioni per il supporto
Forum del supporto di Microsoft Community
Contattaci direttamente
Ricerca di un partner certificato Microsoft
Microsoft Store