Troubleshooting Common Issues

NextGen® Background Business Processor Help 8

NextGen® Background Business Processor Error Tracking

When NextGen® Background Business Processor launches NextGen® Enterprise PM and the Report Server during normal job processing: The NextGen® Background Business Processor Engine writes error messages to the ODBC Error Log if possible. If it is not possible for the NextGen® Background Business Processor Engine to write to the ODBC Error Log, it writes to the Application Event Log. The NextGen® Background Business Processor application logs application errors from NextGen® Enterprise PM and Report Server in the NextGen® Background Business Processor package history table and displays the error messages in the history details portion of the History List window in BBP Manager. The NextGen® Background Business Processor application writes database errors from NextGen® Enterprise PM and Report Server to the standard NextGen ODBC Error log. The NextGen® Background Business Processor application logs job success or failure in the NextGen® Background Business Processor package history. When a j

NextGen® Background Business Processor Help 8

Running NextGen® Background Business Processor in Debug Mode

You can run NextGen® Background Business Processor in a "debug" mode. The debug mode tells the NextGen® Background Business Processor Engine service and the NextGen® Enterprise PM and Report Server applications to log debug messages: Turning on "debug" mode: In NextGen® Background Business Processor Manager, if the NextGen® Background Business Processor Engine is not yet running, go to Engine > Start/Continue (debug mode). In NextGen® Background Business Processor Manager, if the NextGen® Background Business Processor Engine is already running, go to Engine > Restart (debug mode) Turning off "debug" mode: In NextGen® Background Business Processor Manager, if the NextGen® Background Business Processor Engine is not yet running, go to Engine > Start/Continue In NextGen® Background Business Processor Manager, if the NextGen® Background Business Processor Engine is already running, go to Engine > Restart The NextGen® Background Business Processor Engine, the NextGen® Enterprise PM applicat

NextGen® Background Business Processor Help 8

Logging SQL Commands

You can set NextGen® Background Business Processor to record SQL Server® commands for: All NextGen® Background Business Processor Manager and NextGen® Background Business Processor Engine operations All NextGen® Enterprise PM or Report Server operations performed during a job NextGen® Background Business Processor records the commands in the NextGen install folder in a file called allsql.log. The main purpose of recording NextGen® Background Business Processor SQL commands is to help debug an error that occurs with NextGen® Background Business Processor. You should not activate the Log All SQL option unless instructed to do so by NextGen Customer Support. Log SQL Commands for Engine Operations Log SQL Commands During a Job Parent topic: NextGen Background Business Processor Troubleshooting

NextGen® Background Business Processor User Guide

Troubleshooting Common Issues

The following list contains some of the most common problems associated with NextGen® Background Business Processor: If a job fails with an exit code of 50000, the failure is likely due to a SQL error that should be reflected in the ODBC Error Log. Analyze the log for that time period to determine the error. If running against a local database on the same machine, and you get a "SQL Server does not exist or access denied" message, but you can connect via NextGen® Enterprise PM, then check the SQL Server aliases.

NextGen® Background Business Processor Help 8

Troubleshooting for SQL Server 2000

Open Start > Programs > Microsoft SQL Server > Client Network Utility. Go to the Alias tab. Remove any entries that have a Server alias value that is the same as the local computer's name. The printer offsets for paper claims printed via NextGen® Background Business Processor live in the ngconfig.ini file on the machine where the NextGen® Background Business Processor Engine is running. For example, [1500Settings] XOffSet=0.28 YOffSet=0.30 [UB92Settings] XOffSet=0.30 YOffSet=0.15 If you get an Error #70 – Permission Denied message when trying to export an Excel file, you may be able to run the DCOM Configuration Utility and set up custom launch permissions for Microsoft Excel for the user that the NextGen® Background Business Processor Engine runs as. Parent topic: Troubleshooting Common Issues

NextGen® Background Business Processor Help 8

NextGen® Background Business Processor Troubleshooting

This chapter provides information on troubleshooting errors in the NextGen® Background Business Processor application. NextGen Background Business Processor Error Tracking Running NextGen Background Business Processor in Debug Mode Logging SQL Commands Troubleshooting Common Issues

Troubleshooting Common Issues

Recommendations

NextGen® Background Business Processor Error Tracking

Running NextGen® Background Business Processor in Debug Mode

Logging SQL Commands

Troubleshooting Common Issues

Troubleshooting for SQL Server 2000

NextGen® Background Business Processor Troubleshooting

NextGen® Background Business Processor Error Tracking

Running NextGen® Background Business Processor in Debug Mode

Logging SQL Commands

Troubleshooting Common Issues

Troubleshooting for SQL Server 2000

NextGen® Background Business Processor Troubleshooting