I'd like you to think about this a Little differently:

a. Do the Contents of test.bat contain Windows-based scripts? If so, would it not be better to create a Scheduled/On-Demand Job from within Windows?

OR

b. Does the script contain SQL code? If so, would it not be better to runn it under the SQL Server Agent?

As for your error message itself, it is clear that the stored procedure cannot find the file under that path. To that end, have you:

a. Connected to a remote instance using another Server? If so, the calling instance is looking for the file on the wrong Server.

OR

b. checked that the calling account is being denied Access to the file because of incorrect Permissions (even at the NTFS-Level) or is the calling user a member of a role that does not allow browsing for files? I think this solution is less likely but still worth investigating maybe!