You could try adding the following to the execution command line:

    >> some_error_file_path_and_name.txt 2>>&1

This will capture any standard output from the command in addition to any error text thrown.

I would also temporarily comment out the @ECHO OFF just to see how things are actually excuting.

Environment variables, PATH particularly, can be bothersome depending on the environemtn and user. I would also add a SET statement right after the @ECHO statement.

One final point - one of the lesser known Windows things, the file qualifier of .BAT causes the OS top execute the file as a 16 bit application in a shared 16 bit pool. Changing the file qualifier to .CMD tells the OS to execute as aq 32 bit application with all of the address and memory protections not afforded to a 16 bit application.