In addition to Breck's comments, it is possible that the connection DSN you are using is an USER DSN. If JitterBit is attempting to use that DSN in the context of a different user, it will not be able to find that DSN. For example, JitterBit could be attempting this through a service which requires a SYSTEM DSN by default - unless the service is configured to use a specific account and in that case the user DSN must be defined for that user.
↧