Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

2017-10 Cumulative Update KB4041676 breaks DoCmd.TransferSpreadsheet acExport

Posted on 2017-10-12
24
High Priority
?
762 Views
1 Endorsement
Last Modified: 2017-10-18
Experts,

Running into a problem with a legacy application.  Access 2003 runtime on Win 10 pro client PC's.

The method is failing with a run-time error 3275 "Unexpected error from external database driver (1)"

Example:
DoCmd.TransferSpreadsheet acExport, acSpreadsheetTypeExcel8, "[qryObjectName]", "C:\Folder\Filename.xls", True

Trouble began after MS Updates for the 2017-10 Cumulative Update for Windows 10 Version 1703 x64-based Systems (KB4041676)

Rolling back the update resolves the issue for now... but I'm looking for a practical fix.

Thanks in advance
Shawn
1
Comment
Question by:Shawn Cøady
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 5
  • 5
  • +4
24 Comments
 
LVL 9

Expert Comment

by:Anders Ebro (Microsoft MVP)
Probably not what you want to hear, but a practical fix would be to upgrade to a supported runtime, 2010 or newer.

If that fails, you can quite easily write a custom function to export to excel using automation, but that might suffer from the same issues. 2003 has been out of support for 4 or 5 years now, and 2007 is now on the verge of joining those ranks.
1
 
LVL 13

Expert Comment

by:Máté Farkas
Anders is right! It is not a good idea to run a more than 10 years old software on an up to date operating system.
You have to use Office 2003 on Windows XP or Windows 7 but not on Windows 10.
Or you have to upgrade to at least Office 2010.
0
 

Expert Comment

by:Luciano Giaccone
Excuse me,
but the problem is not only for old version of  Office.
For example, after this update, I don't able to attach a file Xls in a db Access 2016!
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
LVL 85
Try changing acSpreadsheetTypeExcel8 to something else, like acSpreadsheetTypeExcel9 (which is the 2000 format). acSpreadsheetTypeExcel8 is the A97 format.

I do agree with the others, however. Access is far too dependent on other bits of Office and the OS to leave an older program in place, especially if it's one that is critical to your business. The old adage of "if it ain't broke don't fix it" doesn't apply to most software!
1
 
LVL 3

Author Comment

by:Shawn Cøady
Thanks for the feedback so far.  The application has been maintained using a static developer platform that's Access 2003 SP3 on a Server 2003 vm... thus prolonging the life beyond reason.  The client environment has steadily upgraded (XP to Win 7 to Win 10) -- and Office 2003 was replaced with Microsoft Office Home and Business 2013 and 2016.  But since those newer versions of Office don't include Access, the Access 2003 has continued to be included in the default computer image.  The application is a compiled .mde but it's the Access program running it.  I'm not sure if we can use a modern Access runtime without also upgrading the MDE... and the Exec team hasn't been willing to fund a development effort.

Scott - I did try changing the Excel version to see if that would resolve... but it didn't.

Related, the DoCmd.OutputTo acQuery, "QueryDef", "MicrosoftExcelBiff8 (*.xls)", "", True, "", 0
Works fine.  In some instances... we can use this as a work around for now... but the TransferSpreadsheet has some functionality that can't be duplicated.  For example... creating multiple tabs.

I was hoping that I might be pointed to a Reference or Registry edit that would solve.  Any thoughts on that?

Thanks,
Shawn
1
 
LVL 85
I don't know of any quick fix for something like this. As mentioned previously, MSFT does no regression testing for non-supported programs, so you're pretty much out of luck with stuff like this.

Have you checked the Event Viewer to see if you can find any clues?

Maybe run ProcMon from SysInternals (https://docs.microsoft.com/en-us/sysinternals/) to see what's failing?
1
 
LVL 3

Author Comment

by:Shawn Cøady
Found an article on ComputerWorld site related to KB4041676

I've further tested and can produce the same problem trying to import an .xls file via [File] [Get External Data] -- something we do quite frequently.  Saving the .xls as a .csv is one work around... but clumsy.

ComputerWorld - Woody On Windows

Problems importing XLS files
If you’re seeing problems importing XLS files into your applications, you aren't alone. See this anonymous post on AskWoody:
I have to report a bug, or is it a “feature” maybe, with the 2017-10 Security Monthly Quality Rollup for Windows 7 for x64-based Systems KB4041681 and 2017-10 Security Only Quality Update for Windows 7 for x64-based Systems KB4041678.
Yesterday we got bombarded with the problem that we can not import an xls file into our application, which we have been doing since forever. It gives an error: Unexpected error from external database driver (1). We dug deeper and discovered
Provider=Microsoft.Jet.OLEDB.4.0;Data Source={0};Extended Properties=\”Excel 8.0;HDR=Yes;IMEX=1\”
Doesn’t work anymore. After we removed both updates, everything was back to normal.
2
 

Expert Comment

by:Wesley Ronka
I'm having the same problem related to the same update when trying to join a table into arcmap. Uninstalling the update fixes the problem but the update comes back almost immediately and next time I reboot it's there. I guess I could stop it from installing but.... it's a security update.

EDIT: My only "work-around" is to save my excel file as a text file or csv and then import that but when dealing with around 40 xls files this quickly grows into a burden. I'm thinking of keeping this machine offline and uninstalling the update for good while this either gets fixed or ends up being the way things are for now.
1
 
LVL 1

Expert Comment

by:Marcus Taylor
Similar issue do me,
0
 
LVL 1

Expert Comment

by:Marcus Taylor
I have a similar issue, w10pro64 and w7pro64 using office 2003sp3 access which is linked to excel , I too have uninstalled the update and system restore on some computers, also tried detect and repair, within access but not excel, so might try that too. The database is OK on the server as when you uninstall the update on each PC it works OK again. I have contacted Microsoft but I am sure they will do nothing about it as 2003 is not supported esp from w8.1 onwards, yet still it effect my windows 7 computers as well.

I might try a test PC with a fresh install with this update on first then install office,  if this works I will let you know,

I have paused the update for 35days
0
 

Expert Comment

by:Wesley Ronka
I'm on Office 365 and it's the same issue. I tried it on my office computer which is running argis 10.5 isntead of 10.2 (which is where I first experienced this) and the same thing happened. I might have to pause the update. Changing it to csv works fine but for importing many files it becomes a big nuisance.
0
 
LVL 1

Expert Comment

by:Marcus Taylor
Did fresh install on new hard-drive w10pro64 and let it do the kb4048186  then put on office 2003sp3 and still the database fails,  so rolled it back and it's working again, as we all know.

I then connected the old hard-drive as a slave to copy documents etc accross and while that drive was on I tried it again and it failed,  and I thought I wonder if the update slipped through before I paused it, anyway it had not reinstated the bad update, I shut down removed that drive and and when I open the data base it worked again. Very Strange, Remember the database is on the server,  Hope Microsoft does a fix or I will have to avoid this update forever,

There are more threads appearing on line now about similar problems but no positive cures.
0
 
LVL 9

Expert Comment

by:Anders Ebro (Microsoft MVP)
How many are experiencing problems on office 2010 or newer?
0
 
LVL 1

Expert Comment

by:Marcus Taylor
I believe even office 2016 as the same issue,  I tried it on a test PC yesterday at work and says database not found except this time the runtime error message is a different number to what's on office 2003,
0
 
LVL 85
I tested on my Access 2016, and had no issues. This worked fine:

DoCmd.TransferSpreadsheet acExport, acSpreadsheetTypeExcel8, "qTestQry", "C:\Folder\Filename.xls", True

I note that you had square brackets around your query name. I tried that as well, but Access could not find the query name [qTestQry]. If I remove the brackets, the transfer worked every time.

I did confirm my machine has update KB4041676, installed 10-11-2017.

On this machine, I ONLY have Access 2016. I don't have any other versions installed. I'm curious if those who are having issues have multiple versions of Access?
0
 
LVL 1

Expert Comment

by:Marcus Taylor
No multiversions on any computers of mine,
IMAG1548.jpg
0
 
LVL 85
Hi Marcus,

You're Importing, whereas the original poster here indicated they were having troubles Exporting. Looks like a mixed bag, since others seem to have troubles with importing as well.  Wonder if you could try to Export and see if the process is still broken.

My previous test was done with an .accdb database, so I decided to try it with an older legacy .mdb. I was able to export from that .mdb database as well.

Scott
1
 
LVL 1

Accepted Solution

by:
Marcus Taylor earned 3000 total points
OK got one PC working so will do the rest before the paused updates 35days is up

PC was w764pro free upgraded to w10 etc

Office 2003sp3 with no other versions

You need a PC before the Oct  2017 update
And copy the file msexcl40.dll and replace the one in c:\Windows\syswow64\ on the PC with the bad microsoft update , and reboot the PC, you might need to do as administrator, or put the file elsewhere and edit the registry instead

Hkey_local_machine\software\wow64node\microsoft\4.0\jet\engines\excel\win32old\repacement folder
2
 
LVL 3

Author Comment

by:Shawn Cøady
I'm working on the solution suggested by Marcus and that seems promising.  I've got to get around the SysWOW64 TrustedInstaller permissions issue.
0
 
LVL 3

Author Closing Comment

by:Shawn Cøady
Replacing the msexcl40.dll in the C:\Windows\SysWOW64 folder did the trick.  I had to modify the permissions of the file (replacing TrustedInstaller) and that took some trial and error... but once the permissions were changed I was able to rename the file and copy the older version of the .dll into the folder.  My Access Import and TransferSpreadsheet acExport work again.

Thanks again for all the feedback on this question.
0
 

Expert Comment

by:Wesley Ronka
Ahh shoot, I just had done upgrading my three main machines to the "fall creators update". I'll go look for a friends computer that I know is not updated and try this method. I will report back once I reach him in a couple of days maybe a week at most, hopefully it works.
0
 
LVL 3

Author Comment

by:Shawn Cøady
Wesley... we were able to roll back the update on one machine and grab the msexcl40.dll file.  That's the dll we have been copying where needed.
1
 

Expert Comment

by:Wesley Ronka
Understood. Doing that right now.

EDIT: Success finally. Thank you all for your help.
1
 

Expert Comment

by:Wesley Ronka
Downloading this also helped me, tested in another machine, both methods work: https://www.microsoft.com/en-us/download/details.aspx?id=54920

Also this thread details some fixes, including the one provided here by Marcus Taylor, link: https://blogs.msdn.microsoft.com/dataaccesstechnologies/2017/10/18/unexpected-error-from-external-database-driver-1-microsoft-jet-database-engine-after-applying-october-security-updates/
1

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Join & Write a Comment

Traditionally, the method to display pictures in Access forms and reports is to first download them from URLs to a folder, record the path in a table and then let the form or report pull the pictures from that folder. But why not let Windows retr…
Cancel future meetings from user mailboxes in Office 365 using Remove-CalendarEvents
This Micro Tutorial will demonstrate how to use a scrolling table in Microsoft Excel using the INDEX function.
Finds all prime numbers in a range requested and places them in a public primes() array. I've demostrated a template size of 30 (2 * 3 * 5) but larger templates can be built such 210  (2 * 3 * 5 * 7) or 2310  (2 * 3 * 5 * 7 * 11). The larger templa…

636 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question