Need to give a better error on a sharing violation

Storage Explorer Version: 1.14.0
Build Number: 20200624.3
Platform/OS: Windows 10
Architecture: x64
Regression From: unknown

Bug Description

When another program has a file open with exclusive access, ASE gives a confusing error message when uploading.

Steps to Reproduce

1. Open c:\temp\foo.csv in Excel (Excel opens with exclusive access)
2. In ASE, try to upload c:\temp\foo.csv to blob storage

Expected Experience

An error message like "Unable to open c:\temp\foo.csv because another program has it open"

Actual Experience

Transfer of 'C:\temp\foo.csv' to 'datacontainer' failed: error: failed to perform copy command due to error: cannot start job due to error: cannot scan the path \?\C:\temp\foo.csv, please verify that it is a valid. (used SAS, discovery not completed)

Additional Context

I thought since I took a recent update, it was getting confused about this "\?\c:" path format. Instead it was a sharing violation.

Considering Excel is so unfriendly about sharing, this has to happen on occasion.

Start by reproducing the upload from c:\temp\foo.csv while Excel holds the file with exclusive access, using the listed Windows and Storage Explorer versions as context. Trace how the sharing violation becomes the transfer error, and consider the issue done when the upload reports that another program has the file open instead of the confusing scan-path message.