NextGen® Background Business Processor Troubleshooting
This chapter provides information on troubleshooting errors in the NextGen® Background Business Processor application.
Recommendations
NextGen® Background Business Processor Help 8
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 jNextGen® Background Business Processor Error Tracking
NextGen® Background Business Processor Help 8
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 applicatRunning NextGen® Background Business Processor in Debug Mode
NextGen® Background Business Processor Help 8
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: Troubleshooting for SQL Server 2000 Troubleshooting for Window 2000 Operating system Troubleshooting for Windows XP Operating system Other Method for Troubleshooting Troubleshooting for SQL Server 2000 Troubleshooting for Window 2000 Operating system Troubleshooting for Windows XP Operating system Other Method for Troubleshooting Parent topic: NextGen Background Business Processor TroubleshootingTroubleshooting Common Issues
NextGen® Background Business Processor Help 8
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 TroubleshootingLogging SQL Commands
NextGen® Background Business Processor Help 8
You can log all SQL commands for NextGen® Background Business Processor Manager and NextGen® Background Business Processor Engine operations Access NextGen® Background Business Processor Manager. Select the Log All SQL option on the File menu. Parent topic: Logging SQL CommandsLog SQL Commands for Engine Operations
NextGen® Background Business Processor Help 8
You must select a server for NextGen® Background Business Processor to use when it performs automated NextGen® Enterprise PM processes. To create a server that is eligible for NextGen® Background Business Processor to use, install the NextGen® Background Business Processor Engine service on it. On the Server List tab, the NextGen® Background Business Processor Manager lists each server on the network on which the NextGen® Background Business Processor Engine Service exists. The Server List provides the following information for each NextGen® Background Business Processor Engine Service installation: The domain and server name for the server on which the NextGen® Background Business Processor Engine Service is installed If the service is available If the service is running The last time the service was started and stopped The total duration of the package that it had run last The server capacity percentage A Gantt chart of each package based on the time The package server schedule An op