Troubleshooting

Recovering from Abnormal Terminations

Occasionally an unforeseen event, such as a server problem or power outage, can shut down Aumentum in the middle of a task. The table below shows some problems that can occur and the effect on the data and your work.

Scenario Event Effect Action
1 You click the Internet Explorer Close button instead of the Aumentum Close button to exit Aumentum. All of the your active Aumentum tasks are closed and you could lose any changes in progress you have not saved. Go to Configuration > System > Concurrency to check for record locks. (A system administrator may need to do this.) Clear the locked records for the user. Re-do tasks that were interrupted.
2 Workstation loses power before saving data for a task. Same as Scenario 1. Same as Scenario 1.
3 Network connection is lost before saving data for a task. If the network connection is restored before the IIS session timeouts, you will not lose any data and you will be able to continue on from where you were in Aumentum. (Timeout values of jurisdictions using Aumentum vary from the default of 20 minutes to several hours.) None, if the connection is restored within the IIS server timeout period. If the timeout is exceeded, perform the actions of scenario 1.
4 Batch server loses power during a batch process. The batch process ends in error. Any pending database transactions are lost.

Action depends on the particular batch process. Consult your Aumentum Support representative.

For example, a batch process may need to update 1000 records. Assume that after processing 600 records the connection was lost or power went out. If the records are updated independently, then the 600 updates will be committed and 400 records would not have been updated. If the business rules state that all 1000 records must be updated at the same time, the changes to the first 600 would automatically be rolled back by the database itself.
5 Network connection is lost during a batch process. The batch process eventually times out and ends in error. Pending database transactions are lost. Same as scenario 4.
6 Workstation loses power during a batch process. Batch processes that are initiated at a workstation are performed on the batch server. A loss of power at only the workstation after the batch process is initiated would not affect the outcome of the processing. None. The batch process is not affected and runs as expected.