# SDS - Resolving Pending Updates or Errors

Pending updates and data distribution errors are collected and displayed in the SDS Distribution Errors form of the local element where you initiated the Start Sharing operation. You must resolve data distribution errors at the element where the updates were initiated.

When there are errors, a warning message will display after every System Admin Tool login and logout. The message is a reminder to resolve the errors. It goes away when there are no more errors or when the check box to skip the message is selected.

NOTE: The warning applies to the local node (the one that the administrator is logged in to). No such warning is provided when an application reach through is done to another node that has distribution errors.

To resolve distribution errors from the originating element:

1. Go to the SDS Distribution Errors form.

The number of data sharing errors is given in the top left-hand corner of the form.

2. To view all records, in the Display field select all and then click Retrieve. Or, to view a subset of records, select first or last, select the desired number of records, and then click Retrieve. The main frame of the window lists the pending updates and the failed updates.

3. Click on the Action ID field heading to sort the errors by action ID. You can sort the errors based on any of the column headings simply by clicking on the desired heading (for example, Reason).

4. Click the check box next to the update record. In order to retry or delete a record, you must first check its associated box.

   NOTES

   - You can check the boxes of multiple records and the operation that you choose will be applied to the checked records. To select all update records, click Select All.

   - When you select multiple records, the Retry and Force Change operations will only be available if the records selected are of the same type.

5. To resolve the pending update or error:

6. Click Retry to retry the update. "Retrying" appears before the Reason field in the record. If the update is successful the update record disappears from the list. If the update is unsuccessful, the update error record will be updated with the new time stamp.

7. Click Force Change to update the remote node with the record from the local node. (This action only applies to conflict errors)

8. Click Login to launch the system administration tool of the remote system. You can then manually fix the error through the System Administration Tool of the remote element. In order to automatically login from the local element, the User Authorization Profile must share the profile of the logged in administrator with the remote element. If the login ID of the administrator is not defined on the remote element, the login page of the remote element will be displayed instead, and you must login using the user name and password of the remote element.

6. Click Data Refresh to update the main window.

   NOTE: The system automatically retries "transport" errors. Updates that are fixed by the system will disappear from the SDS Distribution Errors window after a Refresh. See About Automatic Retry for details.

7. After you have corrected an error, you may have to delete the error record. Go back to the SDS Distribution Errors form on the local element, select the error record and click Delete. The update error is removed from the main window and the error log is removed from the logs. You can also choose to delete an error record if you understand the error and determine that the update is not required.

NOTE: If an error involving MiCollab persists, try re-syncing to MiCollab.

CAUTION: Deleting an error record could cause data inconsistencies that could cause subsequent retry operations to fail because of a dependency between the records.

## About Automatic Retry

The system automatically retries data updates that are not successfully delivered to the destination element (due to a network or element failure).

Note that the following data updates are not automatically retried

- updates that fail because an application on the destination element was unable to write the data to its database

- updates that fail because the same data was updated concurrently.

The following conditions apply to system initiated automatic retries:

- Automatic retries are started every 30 minutes.

- Updates are retried from oldest to newest based on the initial time stamps of the record.

- Automatic retries yield to manual retries and new updates.

Related Topics

- Viewing Data Distribution Errors

- Troubleshooting Sharing Operations

- Troubleshooting Sync Operations