FRX Report Date is not setting.

frx report date not setting

frx report date not setting

In this situation the FRX dates are not sticking to newer periods.  The fiscal periods at Dynamics GP has been created, the old period has been closed.  The problem was associated to only one user. The sticky situation was resolved as follows:

1) The sysdata directory was backed up.

2) All users using FRX were requested to log off.

3) All G32 files at the SYSDATA folder was deleted.

4) Logged as user who did not have the did not have the sticky date issue.

5) Created indexes.

The issue was resolved of all users.

Cheers!
Sanjay

 

FRX – Cannot find GL Index database – [path].G32

Frx index not found

Frx index not found

Though FRX is retired, it is still used in production. There are situations where index files (*.G32 at sysdata folder) needs to be deleted, for example the date is not setting properly when running the report. Once the index files are deleted, it needs to be re-created.

Indexes for the company can be created by making the logged in company the default company @ Company -> Information -> Set as default.

However the indexes for the forecaster company is not created when the logged in company is set at default. In order to create the indexes for the forecaster company, first identify the forecaster company from the Company -> Information screen of the logged in company. Next select the forecaster company and make it default. Indexes for the forecaster company is created.

Select the company to be logged in make it the default company to revert back to the reporting company.

At this point indexes for the company and the forecaster company is generated and all set for reporting.

PS: Always backup the sysdata folder before any operation deletion or rebuild operation in FRX.

Cheers!
Sanjay

The GL Index for the company is currently being rebuild by user…

The GL Index for the company is currently being rebuild by user…

GL Index is being rebuild

GL Index is being rebuild

Cause:

When Frx is rebuilding the GL index file, it create a .LCK file in the sysdata directory to track who is building the file.  If FRx is terminated abnormally while this process occurs the .LCK file is left in sysdata directory preventing further attempts to rebuild the index file.

Resolution:

  1. Request all FRX users to log out of FRX.
  2. Locate and delete the .LCK file at the Sysdata folder.

Additional references:

  1. Microsoft KB article 964735