DBAmp linked server Error 5103 after Salesforce Winter 2026 release applied to our test org

I’m experiencing this same issue as well, on DBAmp 5.1.9.0.

Same here, I am guessing this is related to the recent changes from Salesforce?  What configuration changes do we need to make?
Connected App Usage Restrictions
Data Loader OAuth 2.0 Device Flow Removal 

The strange thing is it has only impacted our FULL sandbox and not Production?

What version are you on @Brock?

I got a response from CData support, could be time to upgrade DBAmp:

It is a recently known issue we are seeing for some of the customers, and it seems that Salesforce made a change on their side in how they respond to certain API calls, in a way that the older pre-v22 DBAmp cannot handle.
This is part of their Winter '26 release, and for now, it is only affecting non-prod environments

​@gerryaff ​@BrockMcDonald Thanks for your input. In our case, the Salesforce Winter 26 release was applied to our full sandbox on 9/5 and the failure started the next day when the sql server agent job ran. The release will hit our production org in October, so isn’t it logical to assume that prod will also have the issue at that time?  If we have to upgrade DBAmp to resolve this, that’s a heavy lift for us.  

We have the same issue. Look like the ODBC connector uses Salesforce SOAP API, and there’s nothing in the Salesforce release notes about changes to SOAP in Winter ‘26. Does cData know what has changed in the headers to cause this? 

CData has confirmed that upgrade to the latest version of DBAmp is the fix, v2025.

Yes, we are on the older version of DBAmp, had been trying to avoid upgrade due to retiring the Org it is on, looks like this is forcing an upgrade.  

So to fix this we must upgrade to v2025?

Current versions (different Orgs)
V8304 (DBAmpAZ 22.0.8304.0 Copyright c 2021 CData Software, Inc.)
and
V5.1.9

@gerryaff  do you have the link to CData that confirmed the need for the upgrade?

To jump in and clarify a couple of questions on this thread, in no particular order:

This is related to the Winter ‘26 update, which is why it is only affecting sandboxes so far.

It does not seem to be related to the OAuth changes, since DBAmp does not use OAuth.

We do not know exactly what has changed, nor do we know why, unfortunately.

The pre-v22 versions are out of support, and there is unfortunately no configuration change that can be made to get around the change Salesforce made, so if you have v5.1.9 or earlier, you will need to upgrade.

On the bright side, so far, we have not heard from anyone with v22+ of DBAmp having this issue, and we have not seen it ourselves (and man, have we been testing up a storm since Monday!). So upgrading to v22+ should fix this issue entirely. If you already have v22+ (such as your 22.0.8304.0 Brock) then that installation should be fine. If anyone is seeing this error with v22+ specifically, please open a ticket with [email protected].

​@Dani Moran Are there any issues/changes we would have to make with updating from v5.1.9 since production is still on the Summer ‘25 release?

Is it possible to do a side-by-side installation of DBAmp?

​@Dani Moran  - Can you answer a couple of questions regarding running the current, 22+, version in parallel with 5.1.9?

After installing the new version, during configuration, should I skip Migrate Old Settings?
(since I want both versions running separately while I test and configure v22+, and prepare to cut over)

Are there any gotcha’s I should be aware of while configuring v22+ to run in parallel with our existing v5.1.9?

Thanks,

Pat

Absolutely!

Migrate Old Settings will not effect your installation of v5.1.9 (or any pre-v22 version). It only makes a copy of those settings that the old version and the new version have in common into v22+ (as they look when you hit the button), it doesn’t change anything about the old version. 

The main thing to keep in mind, specific to a side-by-side setup, is to note that the stored procedures are completely incompatible between versions. So v22+ will need its own database(s), separate from the database(s) that you might be using with a pre-v22 version. Their linked servers are also set up differently, so v22+ will need its own linked server as well. That shouldn’t interact with your current pre-v22 set up linked server, as long as you don’t delete it yourself!

Its an old one, but wondering what was the link used to download for the upgrade?

You can find the most recent version here: https://www.cdata.com/download/dbamp/