I totally agree that UNC paths would be better. My takeaway from this, for debugging purposes, is:
[INDENT]If you have data access problems, look for suspicious drive letters like Y: instead of the typical C: 😧 and E: . It usually implies that a network drive has been mapped and the mapping no longer exists, or cannot be found by the scheduled task. You can either change the script or model being run to use a UNC path instead of a drive letter, or, as an alternative when modifying the model or script is difficult, use the NET USE stuff...[/INDENT]