0

I have an odd issue with Excel 365 v16.0.16827.20278 installed on a host machine. When trying to access an ODBC source, used successfully by several other individuals, Excel throws the error

An error occurred but no ODBC error information was available

This error can only be triggered from Excel on this single computer from this users profile. Knowing that there are some heavy handed solutions to this e.g., rebuild local computer profile and possibly reinstall Office. I was curious if there was more surgical options.

On the same computer I can do the following without issue:

  • Perform a source test successfully from odbcad32.exe
  • Run a PowerShell Script to pull one record using the odbc source as the troubled user
  • Use Microsoft Access for 365 and use the same ODBC source to pull data
  • Run Excel as myself in my own profile on the same computer to use the ODBC connection

I attempted to run a trace using odbcad32.exe under the Tracing tab with Machine-wide tracing for all users identities checked but no log was created. This is in contrast to the tracing test I did on other computers.

Using this ODBC source requires a VPN connection to be established. What is interesting is that the error is the same whether or not the VPN is connected.

My conclusion using the above information is that Excel is the issue under this one local user profile. However, I don't know where to go with that information. The application itself appears to be working fine so repair/reinstall doesn't seem like a viable approach. Rebuilding the local profile is a last resort that I am trying to avoid for the time being.

10
  • 1
    Check the Event Viewer for error messages, perhaps the ODBC driver has put a message in there. If not, try to find an update to the driver - which one is it?
    – harrymc
    Commented Dec 12, 2023 at 16:16
  • Good point. I should have mentioned that I did check event viewer and no correlating events were found. The deployment instructions we have are for using v17 of the SQL Server driver to match the 2017 sql server version we are using as that is the environment the report were developed in. I might be able to find another version just to try. Not a crazy idea. I wanted some sort of cache to clear for this but I am not aware of any that exists.
    – Matt
    Commented Dec 12, 2023 at 16:54
  • Something else to consider (that has bitten me in the past) is that there are 64 bit and 32 bit odbc drivers that are configured completely separately. I am not saying this is related to your problem but it might be. Commented Dec 12, 2023 at 16:56
  • One tool I have used in the past is to enable tracing for the ODBC driver. See this example link.
    – harrymc
    Commented Dec 12, 2023 at 16:59
  • Appreciate the consideration. That is not the issue here. We are using x64 to match the office installation and odbc. The exposure to application to the source hasnt been the problem. Excel using it has.
    – Matt
    Commented Dec 12, 2023 at 16:59

0

You must log in to answer this question.

Browse other questions tagged .