PROGRAM ISSUE ** THIS INFORMATION HAS NOT BEEN VERIFIED **

"Error 5: An invalid character was found in text content" occurs when generating a report in FRx

Entry Type: Informational

Product:
FRx

Application: FRx

Version Reported: 6.7.11027

Subject:

"Error 5: Invalid character was found in text content" occurs when generating a report when the transaction detail posting comments have an invalid character.

Possible Resolution:

1. Save the row as a different name using File/ Save As.
2. Then begin removing accounts from the row to narrow down the account that is causing the error. Once that has been determined.
3. Determine the Account Key for that account number
4. • Expand Modules, Library Master, and Utilities. Double-click Data File Display and Maintenance.
   • Click the File Name lookup button, and select ..\Mas90\Mas_xxx\Glxxx\GL_Account.m4t (xxx = company code).
   • Select KRAWACCOUNT from the Key No list. "Raw Account" appears next to the Key field.
   • Click the Key lookup button, and select the raw account key of the General Ledger account to be corrected.
   • Note the value in the 01-accountkey$ field. (This is the surrogate key)

   4. Locate the invalid character in GL_Detailposting.m4tClick theFile Name lookup button, and select ..\Mas90\Mas_xxx\Glxxx\GL_DetailPosting.m4t (xxx = company code).
   Note: If DFDM was not closed, the lookup should open the same folder that was accessed above.

5. Click the Key lookup button, and enter the General Ledger account key that has the invalid posting comment and scroll through all the records to find the invalid character and remove it from filed 13.
• NOTE: In our case there was a box in the posting comment field
6. Delete the G32 file from the sysdata folder and let the system rebuild it on the next login to FRx.
7. Have all users exit FRx
8. InWindows Explorer locate the Sysdata folder.