If you've followed this link and/or otherwise found this post, you are probably dealing with the following error:
"FRx Reporting Engine
The GL Account link in row % combined with the Acct Mask specified in the reporting tree do not make up a valid GL account. Verify that the link in the row format does not include mask characters (such as #, &, or -). If you are subtracting accounts, make sure that the subtracted account is included in parentheses.
Account Mask in the tree: &&&&&????
Link in the row format: %
If you continue, this row will be left blank. Do you want to continue generating the report?"
According to KB966649 This error is caused because the Viewpoint General Ledger is upgraded to Viewpoint 6.0.1 and the version of Microsoft FRx is not compatible with the newer Viewpoint version. Microsoft FRx version 6.7.9111 or above is only certified with Viewpoint 6.0.1.
PROBLEM - my client is already on 6.7.9111
Actual cause... account format mismatch!
1. No Reporting Tree was in use.
2. The error occurred for the first and all subsequent rows in the row format.
3. The Report worked fine for another company/entity.
4. The Account mask referenced by the error was actually &&&?????
For the uninitiated, in FRx, account masks for account components/formats are & and ?
The & character is the substitute for any Main Account character and the ? character is the substitute for an sub-account character (a.k.a. wildcards).
The actual account format for this company should have been ???&&&&&, the first segment being location, the second being the main account; however, when the Account Format was initially configured for this company, the user accepted the default account settings, which made the Location segment the Main segment.
In order to fix this, you need exclusive access to the database. In Tools > Setup > Company > Account Format, choose the actual main account segment in the Main Segment drop-down list. You will be prompted to run Check Links maintenance on the Account Master file. I took the extra precaution of rebuilding the GL index in FRx, as I assumed this would prove necessary. It worked like a charm.