Access error when database stored on network

%3CLINGO-SUB%20id%3D%22lingo-sub-688251%22%20slang%3D%22en-US%22%3EAccess%20error%20when%20database%20stored%20on%20network%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-688251%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%20I%20tried%20the%20latest%20workaround%20for%20this%20error%20message%20(see%20below)%20related%20to%20access%20files%20stored%20on%20networks%20and%20used%20by%20multiple%20users%2C%20but%20it%20did%20not%20fix%20the%20problem.%20I%20continue%20to%20get%20the%20error%20message.%20Do%20I%20need%20to%20run%20the%20command%20on%20every%20PC%20that%20has%20used%20it%3F%20Are%20there%20any%20updates%20for%20solving%20this%20problem%3F%20It%20is%20a%20major%20issue%20for%20my%20company%20as%20we%20use%20Access%20in%20this%20manner%20all%20the%20time.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Faccess-reports-that-databases-are-in-an-inconsistent-state-%25EF%25BB%25BF-7ec975da-f7a9-4414-a306-d3a7c422dc1d%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Faccess-reports-that-databases-are-in-an-inconsistent-state-%25EF%25BB%25BF-7ec975da-f7a9-4414-a306-d3a7c422dc1d%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-688251%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAccess%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-699759%22%20slang%3D%22en-US%22%3ERe%3A%20Access%20error%20when%20database%20stored%20on%20network%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-699759%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F359118%22%20target%3D%22_blank%22%3E%40LauraGPA%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAlthough%20not%20a%20fix%20for%20your%20particular%20issue%20you%20may%20wish%20to%20consider%20upgrading%20your%20Access%20data%20to%20SQL%20Server%20or%20SQL%20Server%20Express%2C%20which%20is%20free.%20As%20a%20general%20rule%20we%20recommend%20any%20client%20with%203%20or%20more%20users%20to%20upgrade%2C%20allowing%20you%20to%20leverage%20the%20best%20of%20SQL%20Server%20and%20Access%20together.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20more%20information%20on%20upgrading%20just%20your%20data%20to%20SQL%20Server%2C%20check%20out%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Fmigrate-an-access-database-to-sql-server-7bac0438-498a-4f53-b17b-cc22fc42c979%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Fmigrate-an-access-database-to-sql-server-7bac0438-498a-4f53-b17b-cc22fc42c979%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPlease%20note%3A%20Just%20upgrading%20to%20SQL%20Server%20may%20not%20be%20enough%2C%20you%20may%20need%20to%20create%20views%20and%20stored%20procedures%20in%20order%20to%20get%20the%20performance%20you%20need%2C%20but%20it%20will%20be%20worth%20it%20in%20the%20end%2C%20since%20SQL%20Server%20is%20much%20more%20stable%20and%20has%20many%20other%20benefits%20over%20Access.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1493793%22%20slang%3D%22en-US%22%3ERe%3A%20Access%20error%20when%20database%20stored%20on%20network%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1493793%22%20slang%3D%22en-US%22%3EDid%20you%20ever%20have%20any%20luck%20with%20a%20work%20around%3F%20I%20have%20the%20same%20issue%20and%20disabling%20leasing%20or%20using%20SQL%20are%20not%20an%20option%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1493807%22%20slang%3D%22en-US%22%3ERe%3A%20Access%20error%20when%20database%20stored%20on%20network%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1493807%22%20slang%3D%22en-US%22%3ETo%20do%20this%3A%3CBR%20%2F%3E%3CBR%20%2F%3EClick%20Windows%20Start%20Press%20the%20Windows%20key%20and%20then%20type%20Command.%20Right-click%20on%20Command%20Prompt%20and%20choose%20Run%20as%20administrator.%3CBR%20%2F%3E%3CBR%20%2F%3ECopy%20and%20paste%20the%20following%20commands%20into%20the%20command%20prompt%20window%3A%3CBR%20%2F%3E%3CBR%20%2F%3EREG%20ADD%20HKEY_LOCAL_MACHINE%5CSYSTEM%5CCurrentControlSet%5CServices%5Clanmanserver%5Cparameters%20%2Fv%20DisableLeasing%20%2Ft%20REG_DWORD%20%2Fd%201%20%2Ff%3CBR%20%2F%3E%3CBR%20%2F%3ENET%20STOP%20SERVER%3CBR%20%2F%3E%3CBR%20%2F%3ENET%20START%20SERVER%3CBR%20%2F%3E%3CBR%20%2F%3EClose%20the%20command%20prompt%20window.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1493812%22%20slang%3D%22en-US%22%3ERe%3A%20Access%20error%20when%20database%20stored%20on%20network%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1493812%22%20slang%3D%22en-US%22%3EBut%20-%20I%20am%20using%20a%20split%20database%20scenario%20and%20my%20back%20end%20databases%20(the%20ones%20getting%20corrupt)%20are%20on%20a%20NAS%20server.%3CBR%20%2F%3E%3CBR%20%2F%3EWould%20I%20need%20to%20do%20this%20on%20every%20windows%20desktop%20that%20connects%20to%20the%20back%20end%3F%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

Hi All, I tried the latest workaround for this error message (see below) related to access files stored on networks and used by multiple users, but it did not fix the problem. I continue to get the error message. Do I need to run the command on every PC that has used it? Are there any updates for solving this problem? It is a major issue for my company as we use Access in this manner all the time. 

 

https://support.office.com/en-us/article/access-reports-that-databases-are-in-an-inconsistent-state-...

4 Replies
Highlighted

@LauraGPA 

 

Although not a fix for your particular issue you may wish to consider upgrading your Access data to SQL Server or SQL Server Express, which is free. As a general rule we recommend any client with 3 or more users to upgrade, allowing you to leverage the best of SQL Server and Access together. 

 

For more information on upgrading just your data to SQL Server, check out:

https://support.office.com/en-us/article/migrate-an-access-database-to-sql-server-7bac0438-498a-4f53...

 

Please note: Just upgrading to SQL Server may not be enough, you may need to create views and stored procedures in order to get the performance you need, but it will be worth it in the end, since SQL Server is much more stable and has many other benefits over Access.

Highlighted
Did you ever have any luck with a work around? I have the same issue and disabling leasing or using SQL are not an option
Highlighted
To do this:

Click Windows Start Press the Windows key and then type Command. Right-click on Command Prompt and choose Run as administrator.

Copy and paste the following commands into the command prompt window:

REG ADD HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters /v DisableLeasing /t REG_DWORD /d 1 /f

NET STOP SERVER

NET START SERVER

Close the command prompt window.
Highlighted
But - I am using a split database scenario and my back end databases (the ones getting corrupt) are on a NAS server.

Would I need to do this on every windows desktop that connects to the back end?