What to do if you don’t get your Daily Update Results as expected:
- Check the dpsvc.log - The dpsvc.log, located in your ExecuTrax directory, shows a history of DataPro stop and start times. Confirm “DataPro Startup” and “Exiting the DataPro Process” as expected.
If there is no start time, confirm DataPro is activated to run as a service and the DataPro service is running.
If there is start time and no exit time, DataPro is either still processing or the process was interrupted by a server reboot or other event. More investigation needs to be done.
If both start and stop times are present, continue to check dpresults.
- Copies of both the most recent Daily Update Result that was emailed as well as the most recent DataPro error message are saved to the ExecuTrax directory as dpresults-institution.html and dpresults-error.institution.html. If you did not receive the emailed version for any reason, confirm the date of the most recent successful run/error here.
Some common error types:
HHold_C is in use -- an extra exlibrary.exe is open in the task manager on the server and holding tables open. There should be only one instance of exlibrary.exe for DataPro. Any additional instances are due to users being in the software or not having fully exited out of the software using the Exit menu option after last connection.
‘PCIMPNAME’ is not found – Typically caused by an import file formatting issue. Confirm that source files to be imported by DataPro were generated correctly.
Arithmetic overflow converting data type – This will typically be a data related issue. An updated value is too large for the field being updated, frequently a calculated value such as an annualized number. Further investigation is needed. Check the exlibrary.log in the ExecuTrax folder for more detailed error messaging.
Alias DPRES_CAM is not found – Need to confirm all expected columns exist for the named table exist in the Daily database. Check the exlibrary.log in the ExecuTrax folder for more detailed error messaging.
Cannot bulk load. The file “xxxxxxxx.txt” does not exist – Need to confirm correct permissions on the application server.
Maximum Account Types Exceeded – the number of new lookup values being imported exceeds the Maximum Lookup Increase % as set in DataPro. Frequently this is due to shifting in the files. If the listed lookup values in the error are not legitimate, review the import files to confirm they generated correctly. If the lookup values are legitimate, consider increasing the Maximum Lookup Increase setting.