MS Access (O365) Encountering -3151 Error (ODBC Connection to Salesforce Failed) During Salesforce Data Connection Setup

Anonymous
2024-07-17T21:02:01+00:00

SOLUTION: There is a bug with the recent O365 update. Until Microsoft addresses the issue, you must revert to the previous version, 17726.20126. You can do so programmatically. Here's a command to revert to previous version: "C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe" /update user updatetoversion=16.0.17726.20126

Issue:

I have been using the built-in MS Access Salesforce ODBC driver and have successfully connected to Salesforce for several years without any issues. Recently, when I tried to run a query, I encountered the "ODBC Connection to Salesforce Failed" error.

I have attempted to refresh the link, reimport the tables, and confirmed that my Salesforce token has not changed. I checked my Salesforce login events, and I'm not seeing any attempts to login from the partner product.

Does anyone have any suggestions on how to resolve or troubleshoot this issue?

Thank you.

Microsoft 365 and Office | Access | For business | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2024-09-10T14:38:17+00:00

Hi,

I just downloaded the new build from today and updated the status in our documenting AFo article to this text:

Microsoft planned to release a fix for this problem in the Current Channel on Patch Tuesday, Sep 10. The update is version 2408 build 17928.20156*.*

If you do not receive it automatically, you can retrieve it by choosing Update Nowon File - Account*.*

If you were affected by the bug, please let us know if the update fixes the Salesforce connector problem for you.

Servus
Karl
****************
Access Forever News DevCon
Access-Entwickler-Konferenz AEK - 19./20.10. Nürnberg

Was this answer helpful?

0 comments

41 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. George Hepworth 23,120 Reputation points Volunteer Moderator
    2024-09-03T15:44:24+00:00

    Thank you VERY much for sharing this. I concur that a change of this sort should have followed public notice somewhere.

    Subsequent discussion reveals the claim that the SalesForce connector was discontinued is not true (see Karl's explanation below).

    I apologize for reacting prematurely.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-09-03T15:15:29+00:00

    I received the following response from Microsoft Support regarding the Salesforce connecter no longer working in Access:

    Microsoft has made changes regarding the support of the Salesforce connector in Access. Previously, Access provided native support for connecting to Salesforce without the need for third-party ODBC drivers. However, recent updates and policy changes from Microsoft have altered this support structure.

    Why the Change?

    The shift towards third-party ODBC drivers is part of Microsoft's effort to streamline their services and enhance security and compatibility. Third-party ODBC drivers provide more flexibility, frequent updates, and better support for various data integration scenarios. By leveraging these drivers, users can achieve a more robust and reliable connection to Salesforce.

    Next Steps:

    To continue using Microsoft Access with Salesforce, you will need to install a compatible third-party ODBC driver. We recommend researching and selecting a reliable ODBC driver provider that meets your specific requirements. Detailed installation instructions and configuration guides are typically provided by the ODBC driver vendor and should help you set up the connection seamlessly.

    Additionally, they identified the following as potential options for third-party ODBC drivers:

    1. Salesforce ODBC Driver by CData
    2. ODBC Driver for Salesforce by Devart
    3. ODBC Driver for Salesforce by Simba

    Not sure why this change wasn't announced publicly.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-08-29T14:03:51+00:00

    hello - im even encountering now the working build 17726.20126. is now failing for some people - this is very worrying - do we think that this is not likely to be solved now? we have purchased a salesforce ODBC driver as that then works, but it does ask for credentials more often - but it also means solutions having to be re-written as table names are presented differently

    Was this answer helpful?

    0 comments