Sage 100

I'm trying to get a VI job to run on the same server as Sage 100 as a Windows Scheduled Task but I keep getting the attached ODBC error. The VI job uses a silent ODBC connection (SILENTMAS90) that tests okay. The job works fine when run manually inside of Sage 100. In order to troubleshoot, I tried running the job as a batch file (attached). It runs fine if the line includes the MANUAL switch. However, it fails if the same batch file runs with the AUTO switch. I've also tried this on two separate servers, same Sage 100 install, one a 2003 server, the other 2008 server, both with the same result. I've scoured the KB and community and can only find a reference to ODBC security (which is not enabled). If you've experienced this or can offer any additional assistance it would be appreciated. Details: > Sage 100 Standard 2013 on a Windows 2003 server. > Sage 100 user account ""VI"" has full rights within Sage 100. I logged into Sage 100 as ""VI"" and the job runs fine. > ODBC security is not enabled. > The jobs have been added to the Jobs menu and ""VI"" has rights.

I knowit's no help but I'm experiencing the exact same thing

Sometimes just finding out that ODBC Security is not enabled isn't the final answer. I don't know why but over the years there have been times when I have suspected ODBC Security as a problem and it was turned off. However turning it on and closing out of MAS, then turning it back off and logging out and in again has solved the issue. As Spock said to Stonn, ""it isn't logical but it is often true"". Other than that, assuming your password is ""import"" the only difference I see in my command line than yours is that I am using a different INI file. Mine reads ""....\LAUNCHER\SOTAPGM.INI..

Company maintenance - outside access ON?

@LeeGraham Yes. Checked that. Thanks. @CullenLowe I agree. So in my initial troubleshooting I turned on ODBC security, checked role maintenance, then turned it off again. If it was ODBC, I would think it would also fail when running the job manually within Sage 100. Thanks for the input.

Not sure which version you're working with, but shouldn't the command line be SOTAPGM.INI (instead of Sota.ini)?

Thanks @MarkKotyla I tried both, and no luck with either.

@BillPfahnl it's been a little while since was working on this and I'd all but given up. If I recall, I found a few posts about windows server issues that were causing this. I removed VI/providex from the loop and I couldn't get a simple script to run at all through the scheduler. Scripts run without issue when launched manually.

Thanks @BrettLyder I've tried this on two servers now, 2003 and 2008 so I don't think that's it. I also tried manually as a batch file on the desktop without the scheduler. It works with the MANUAL flag, but not with the AUTO flag. It's very frustrating, to say the least.

Maybe you can post screenshots of the Basic, Logon, and Options tab of the SILENTMAS90 system DSN

Thanks @AlnoorCassim . Here you go.

AUTO run on a V/I ODBC import job using a silent MAS connection through a batch file works okay for me on 4.50, 2013, and 2014 albeit my o/s is Windows 7 instead of a server o/s. Is it possible the Server tab in your DSN has has something in it or the VI user in User Maintenance / Preferences has Use Client/Server ODBC turned on? Another thought is if you pull up your job via DFDM of VI_JobHeader.m4t is Field 26 DataSourceOnHost is it set to Y