Obviously an error with the connection. Are you running this fine on your machine? This will be because you have the driver and authenication set up on your machine. You need to replicate this on the server itself - i.e. it looks like you need to install the driver on the Server. .
Hopefully that will get you up and running.
It could be that Qlikview is authenticating on your username when you run via desktop, but is using the QV administrator account when authenticating via the QMEC. Do all accounts have access to your source?
I'm a little outside my comfort zone here, but I remember suffering a similar issue a couple of years ago myself.
From the error message, I get that SQL Server is refusing your login attempt (no problem with ODBC here) because the domain from which you try to login is not trusted. SQL Server is probably configured to use Windows authentication instead of SQL Server authentication. This means that SQL server uses sort of SSO to let you in.
When you do a desktop reload on the server, you're probably logged in into the same Windows domain (or at least a trusted one) as the SQL server, but QVS isn't. Have the QlikView services been configured to run under a local (e.g. machine) account?
Just a guess.
As Peter pointed out that correctly may be the issue. So do one thing :
- Make sure DSN to the DB is created in your server performing the reload
- The credentials used in the DSN must be the one which is used to run the qlikview services.
- On the server open a new qlikview document and try to Connect to the SQL DB using ODBC connection. (obviously use the same credentials which is used in the DSN to connect to the SQL DB i.e. the one which is running the qlikview services).
- If the connection is successful, then copy this Connection string into the qlikview document where you are getting the error and this time I am sure it will connect.
- If the connection is unsuccessful then make sure that the qlikview service account has authentication to connect to the SQL DB.