Loading...
Recommendations
Explore
View Error Files or Logs
View Error Files or Logs
To view the
NextGenDebugLog.txt
text file, do the following:
Navigate to the main NextGen directory.
Open the file using Notepad.
To view the ODBC Error Log, access the location specified in the [ODBC-API] section of your ngconfig.ini file.
The ErrorLog file entry specifies the location of the log.
To view the Application Event Log, Select
Control Panel
>
Administrative Tools
>
Event Viewer
.
Select the Application event log.
Items with a source of NextGen.BBP.Engine are messages from the
NextGen® Background Business Processor
Engine.
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 User Guide
View Error Files or Logs
To view the NextGenDebugLog.txt text file, do the following: Navigate to the main NextGen directory. Open the file using Notepad. To view the ODBC Error Log, access the location specified in the [ODBC-API] section of your ngconfig.ini file. The ErrorLog file entry specifies the location of the log. To view the Application Event Log, Select Control Panel > Administrative Tools > Event Viewer. Select the Application event log. Items with a source of NextGen.BBP.Engine are messages from the NextGen® Background Business Processor Engine.
NextGen® Background Business Processor User Guide
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 User Guide
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
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: 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 Troubleshooting
