Views:

Summary



Restarting Starwind service can take up to 5 minutes and produces a Microsoft error message.

Symptoms



The Starwind process start progress bar takes at least 3-4 minutes to complete followed by a Microsoft error message stating that the process couldn't be started. Starwind then remains in the "Starting" state for about 30 seconds and then starts.

This can occur with no IA maps but it more often occurs when large IA mapped drives exist that were not unmapped and the Starwind service is then started at that point. Also, this occurs more often when IA mapping to the same primary client that was backed up or where the primary client still has an existing iSCSI initiator connection but no IA mapped drive exists for the client.



Resolution



This issue does not prevent the Starwind service from starting, it only causes a delay. However, the following workarounds will resolve this issue and allow Starwind service to be restarted properly without delay:

  1. IA Unmap volumes that exist.
  2. Restart iSCSI initiator on clients that still have iSCSI connections to the secondary server with no mapped drives existing.