Trouble with ODBC import scheduled script

Discussion created by dreed on Jan 17, 2013
Latest reply on Mar 7, 2013 by dreed

I've read that SQL server sources used as ESS need to have the following domain setup to work for files hosted on server





Since my company only allows windows accounts (not sql server accounts) to access SQL server, I can't seem to get ESS to work on FMS files, since I've not been able to convince IT to configure domain accounts as shown in the link.


Unfortunately, this also appears to carry over to importing ODBC from that source when using a server side script. I received an 802 error when trying the script on the server.



These ESS and ODBC imports work fine when run on a client, but I can't figure out a way to keep updated data available on a hosted file without using a robot client to periodically run the import.


Has anyone else run into problems when SQL server only allows authentication via Windows domain accounts?