- #Microsoft office 2002 crashes after update 1803 windows 10#
- #Microsoft office 2002 crashes after update 1803 windows 7#
I can only imagine how much downtime there has been worldwide,Īs this personally has brought my clients to a standstill. I'm flabbergasted that this is taking so long to fix. 2018 " The engineering team is aware of and working to fix this issue.". Is this a kind of self-destruct action by Microsoft to kill off Access?Īccording to the article dated June 14th. I have to confess I'm pretty angry about the whole thing! It's caused much pain for my customers and a lot of sleepless nights for me. There are 10 or so regular simultaneous connections to the database. Since applying the "DisableLeasing" fix above, "touch wood for luck", on Monday afternoon, there have been zero issues. I ended up exporting the tables into a new. Ridiculous! The last time of which badly damaged a table in theīack-end database so that Compact/Repair had to be done several times and a couple of corrupted records removed before the primary index could be re-built. This week, on Monday morning, the error occurred about 5 times within a 2 hour period. The "Access error 3343" strangely began a couple of weeks ago, just once or twice. PCs either use Access 2007 or Access 2013, which has never caused a problem in the past.
#Microsoft office 2002 crashes after update 1803 windows 10#
Around 10 client Windows PCs, 2 with Windows 7, 2 with Windows 8, the rest with Windows 10 (with 1803 release) which I assume is the culprit. The environment is MS Access database back-end (2007 format) on Windows Server 2012 Standard. This fix in the article link above worked for me. Registry settings for Windows Server 2012 or above pertaining to the server side if the fix above does not resolve your problem. You may also review the " DisableLeasing" "FileNotFoundCacheLifetime"=dword:00000000 Copy and save the following text to notepad and save it as "SMBCacheFix.reg" (with quotes) Evidently SMB changes are the culprit in the 1803 update and the following fix (and workstation reboot) worked for me which was applied to all the Windows 10 (1803) workstations in Into the database and performed extensive query and table operations. The backend database became corrupted as the Windows 10 (1803) workstations were introduced
#Microsoft office 2002 crashes after update 1803 windows 7#
For my scenario and many days and hours investigating this issue, the Windows 7 workstations had no issues accessing and sharing the network mapped backend database.