Financial Reporter Error Messages
Financial Reporter error messages fall into two general categories:
- Error messages printed on financial statements. These messages report problems in formulas and report specifications, such as an account reference with too many account code segments. If Financial Reporter encounters a problem when generating a financial statement, it inserts a message in the report, and then continues to generate (and print) the rest of the statement.
- Error messages displayed by Financial Reporter. These messages appear when you attempt to open Financial Reporter screens, or when report generation is canceled, and may appear under the following conditions:
- If Sage 300 cannot start Microsoft Excel.
- If the computer runs out of memory (RAM).
- If Financial Reporter cannot continue to generate the report. (For example, this may happen if the text or formula in a specification cell is too long.)
The following tables describe these error messages and possible solutions.
Error Messages Printed on Financial Statements
For more information, see About Columns in Report Specifications.
Error Messages when Starting G/L Statement Designer or Running Print Financial Statements
Message |
Description |
---|---|
"Error in creating Excel object." |
Make sure Microsoft Excel is installed. |
"Page Break Preview is not available in Print Financial Statements (GL9100). Please go to Statement Designer (GL9200) to use this function." |
The Print Financial Statements feature does not support Page Break Preview. Use the G/L Statement Designer instead. |
"FileSystemObject object model cannot be initiated. Please make sure that Scripting type library is properly installed in Windows System." |
Cannot find Microsoft Scripting Runtime Object - required when starting FR. |
Error Messages when Starting Financial Reporter
Message |
Description |
---|---|
"cmdStart: <error message>" |
If you receive error messages that are in this format, you may need to reinstall Microsoft Excel, or General Ledger, or System Manager. After reinstalling, restart the system, and then check to see if the problem has been resolved. If the problem cannot be resolved by reinstalling these programs, contact your system administrator. Tip: Before reinstalling Microsoft Excel, confirm that Microsoft Office is installed correctly. From the Programs and Features screen of Windows' Control Panel, right-click Microsoft Office, and then click Change. Select the option to add or remove features, and then confirm that Visual Basic for Applications is installed as part of Office Shared Features. |
"Initializing FR Error (< error id>J): Failure in starting Statement Designer." |
Failure to start Statement Designer. |
"Initializing FR Error (<error id>): Failure in starting Print Financial Statements." |
Failure to start Print Financial Statements. |
"Internal error," "Insufficient memory," or "System error." |
Write down the message, exit applications and Windows, restart your computer, and then try the task again. |
"Incorrect procedure." |
Most error messages pertaining to incorrect procedures arise when other tasks have locked the system or company database. Wait for the other task to complete, and then try again. |