Loading...
Recommendations
Explore
Troubleshooting for Window 2000 Operating system
Open the computer that the
NextGen® Background Business Processor
Engine service is running on.
Open
Start
>
Run
Enter 'dcomcnfg' in the
Run
window and select
OK
.
A list of applications displays.
Double-click on
Microsoft Excel
.
Go to the
Security
>
Launch and Activations Permissions
frame.
Select the
Customize
button.
The
Edit
button becomes enabled in the frame.
Select the
Edit
button.
In the next window, add the user account that the
NextGen® Background Business Processor
Engine uses.
Select
OK
several times to exit.
Troubleshooting for Window 2000 Operating system
NextGen® Background Business Processor Help 8
Troubleshooting for Windows XP Operating system
Open the computer that the NextGen® Background Business Processor Engine service is running on. Select Start > Run. Enter 'dcomcnfg' in the Run window and select OK. Access the following path in the tree view: Console Root > Component Services > Computers > My Computer > DCOM Config. Right-click on the Microsoft Excel Application and select Properties. Go to the Security > Launch and Activations Permissions frame. Select the Customize button. The Edit button becomes enabled in the frame. Select the Edit button. In the next window, add the user account that the NextGen® Background Business Processor Engine uses. Select OK several times to exit. Parent topic: Troubleshooting Common Issues
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
Other Method for Troubleshooting
If you get a "Could not create 'cdo.message' object" message when trying to send a test e-mail from the File à E-mail Settings screen in the NextGen® Background Business Processor Manager, look for the cdosys.dll in the Windows\System32 directory and un-register and re-register it. Try to send the test e-mail again. If you get the same error, try the following procedure: Launch Regedt32.exe from Start > Run. Navigate to HKEY_CLASSES_ROOT\CDO.xxxxxx (CDO.xxxxxx represents a registry item, i.e. CDO.Address), copy down the default value of the key CLSID (i.e. {CD000110-8B95-11D1-82DB-00C04FB1625D}). Navigate to HKEY_CLASSES_ROOT\CLSID\{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} (Note: {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} represents the value you got in Step 2.) The default value of the sub-key InprocServer32 is the path of the target file (usually cdosys.dll). Navigate to the path and file and un-register the file with the command line Regsvr32 -u xxxxx.dll. Re-register the file with the com
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
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
Configure Servers for NextGen® Background Business Processor
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
