MS Access .mdb database Corruption

%3CLINGO-SUB%20id%3D%22lingo-sub-1203997%22%20slang%3D%22en-US%22%3EMS%20Access%20.mdb%20database%20Corruption%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1203997%22%20slang%3D%22en-US%22%3E%3CP%3EMajor%20issue%3A%3CBR%20%2F%3EWE%20have%20an%20MS%20Access%20database%20application%20(Inventory%20Management%20System)%20that%20was%20developed%20few%20years%20back.%20We%20have%20been%20using%20this%20app%20in%20SBS%202008%20without%20any%20problem%20for%20over%2010%20years.%20The%20DB%20is%20split%20in%20two%20parts%2C%20Front%20End%20(all%20logic)%20which%20is%20linked%20to%20Back%20End%20that%20has%20all%20the%20database%20tables.%20Recently%20(about%20a%20couple%20of%20weeks%20ago)%20we%20have%20migrated%20to%20Server%202019%20VM%20and%20have%20started%20using%20above%20application.%20We%26nbsp%3Bare%20experiencing%20Back%20End%20database%20corruption%20on%20daily%20basis%20(See%20Error%20attached).%20This%20is%20becoming%20a%20major%20issue.%20I%20am%20just%20wondering%20if%20this%20is%20being%20caused%20by%20some%20Server%20Network%20stability%2F%20configuration%20issue.%20Your%20thoughts%2F%20help%20will%20be%20greatly%20appreciated%20to%20resolve%20this%20issue!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1203997%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAccess%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1493821%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Access%20.mdb%20database%20Corruption%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1493821%22%20slang%3D%22en-US%22%3EWe%20are%20seeing%20a%20similar%20issue%20with%20Windows%20server%202016%20and%20access%202016%20databases.%20The%20corruption%20only%20happens%20when%20connections%20are%20initiated%20from%20a%20windows%20server%202016%20desktop.%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Major issue:
WE have an MS Access database application (Inventory Management System) that was developed few years back. We have been using this app in SBS 2008 without any problem for over 10 years. The DB is split in two parts, Front End (all logic) which is linked to Back End that has all the database tables. Recently (about a couple of weeks ago) we have migrated to Server 2019 VM and have started using above application. We are experiencing Back End database corruption on daily basis (See Error attached). This is becoming a major issue. I am just wondering if this is being caused by some Server Network stability/ configuration issue. Your thoughts/ help will be greatly appreciated to resolve this issue!

2 Replies
Highlighted
We are seeing a similar issue with Windows server 2016 and access 2016 databases. The corruption only happens when connections are initiated from a windows server 2016 desktop.
Highlighted