Improving Error Messages for Batch Jobs when using Volume GUIDs

[ob_server]

I use Volume GUIDs for both the Left and Right Sides, with several batch jobs running through Task Scheduler. Occasionally, when these batch jobs run, I receive an error if an external hard drive is not plugged in. However, it’s difficult to determine which batch job caused the error since the Volume GUIDs aren’t easily readable.

If we could add the current drive letter or custom message to the error content, I believe this would help resolve the issue.

[Zenju]

I believe the drive must be accessible in order to determine the drive letter from a given volume GUID.