Sage 100

SQL not enabled when running windows batch files for VI jobs. Worked on our last test server, moved everything over to new server, made sure path and everything looks good, can run the VI jobs from within Sage (version 5.0 Premium). We've seen the SQl not enabled 3 or 4 times for multiple reasons, typically seems to be a rights/premissions/path issue and we've been able to resolve in every case but this. Found the sage article about this and have checked the MAS_user and everything looks good. Everything is full permissions under the sage server and workstation folders. SQL not enable seems to be a very generic error message that can mean one of twenty possible things from what I can tell. Any ideas?

If you are executing a batch file with the VI command line using a sql script, SQL cannot reference a mapped drive... must be a unc path.

had to switch from sotapgm.ini to sota.ini in the bat file - not sure what the difference is but it works now (not sure why sotapgm.ini worked on the other server but not this one)