We have a SQL Server Agent job running daily on our test org. After Salesforce Winter ‘26 was applied to the org, we started getting the following failure message. How can we resolve this?
OLE DB provider “DBAmp.DBAmp” for linked server “SALESFORCE” returned message “Error 5103 : Error: Zipped response from salesforce was missing valid zip header.”.
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider “DBAmp.DBAmp” for linked server “SALESFORCE”.
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?
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 DBAmpSupport@CData.com.
You can find release notes here to see what has changed with this version: DBAmp - Release Notes
Another thing to note is that the two versions have a different syntax to their serial numbers - you will want to make sure you have your v22+ serial number for this installation. Both will have been included in the usual email with your serial numbers.
If you have any difficulties with the installation, please let us know, we are happy to help!
@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 skipMigrate 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?
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!
This website stores cookies on your computer. These cookies are used to collect information about how you interact with our website and allow us to remember you. We use this information in order to improve and customize your browsing experience and for analytics and metrics about our visitors both on this website and other media.
Review section III of our Privacy Policy for more information on cookies.
To opt out of “sale” or “sharing” of non-cookie data, visit our Privacy Rights Request Form.