Software Delivery › Tasks › Moving the OSIM Job Information › Diagnosing an Error during a Computer Move Operation

Diagnosing an Error during a Computer Move Operation

The event log lists the reasons for the failure of a computer move operation. You must check the event log to know why the computer move operation has failed. If you find that the computer move operation has failed because of the failure of the OSIM move operation, you can configure the Computer move: OSIM Move Postpone codes configuration policy parameter accordingly.

For example, consider the following sequence of steps to detect and analyze an error that occurs during a computer move operation. In this example, the OSIM job movement fails with an error code 5:

1. Make sure that the Computer move: OSIM move enabled configuration policy is enabled on the computer.
2. Make sure that the list of error codes defined for the Computer move: postpone codes configuration policy is as follows:

   1,2,3,4,5,6,8,12,13,45,211.

3. Attempt a computer move operation for a target computer from domain manager 1 (DM1) to domain manager 2 (DM2). This attempt tries to initiate the movement of the OSIM job records for the target computer. In this example, transfer of the OSIM job records fails with the error code 5.
4. Check that the error code 5 is present in the list already defined for the Computer move: postpone codes configuration policy. In this example, the error code 5 is available in the list, so the SD move (movement of the installation records) is postponed and the computer move operation fails.
5. Open the event viewer (Windows event console) and check the reason for this failure. If you find that this error is not going to be corrected on subsequent retries, you can remove the error code 5 from the list. Any further failure with the error code 5 does not postpone the SD move operation.