UtterAccess.com
X   Site Message
(Message will auto close in 2 seconds)

Welcome to UtterAccess! Please ( Login   or   Register )

Custom Search
> Inconsistent State Error On Windows 10, Any Versions    
 
   
BuzyG
post Jun 18 2019, 05:29 AM
Post#1



Posts: 417
Joined: 20-September 12
From: Cornwall UK


Hi All

We have been getting an random Inconsistent State Error, ever since we moved over to Widows 10, typically once or twice a day on our largest access data base. 50+ users typically several logged on at any one time. But also occasionally on databases where only one user is logged in.

databases are:-

Split FE & BE, I do not have access to users C: drives so have created multiple FEs in different folders on the shared drive. But it is possible for more than one user to log in to the same FE. This never once, in 15 years, caused a problem prior to Windows 10.

All users now on MS Access 2016. most on runtime but several with the full version.

The database files where .accdb
I have been through every line of the code, reworked the error trapping, removed previous old code, that was preventing full compile and now all the FE's are compiled .accde files. This was a lengthy but worth while exercise. Alas it appears it made no difference to the error.

With assistance from the package manager, responsible for MSAccess 2016, we have implemented the following on the server and on each user's desktop.

CODE
@echo off
title Babcock Access 2016 Leasing Fix

cls

echo.
echo Applying Microsoft Access 2016 Leasing Registry Keys, please wait...
echo.

REGEDIT /S "%~dp0source\Access2016DB-Fix.reg"

echo Registry Keys applied successfully..
echo.

pause


Alas none of this has had any noticeable affect on the error. So I'm here asking the guys who know Access Best. Any thing else we can try.

--------------------
Live to Surf
Go to the top of the page
 
 
Start new topic
Replies
Phil_cattivocara...
post Jun 18 2019, 05:44 AM
Post#2



Posts: 351
Joined: 2-April 18



QUOTE (BuzyG)
But it is possible for more than one user to log in to the same FE.

This could be the main error cause.
Why this never happened in the past? You were lucky, I think.
It happens even when only one user is logged? The FE should be local, on the hard drive and not in LAN.
There should be a path where a user, in his own pc, can do "everything", with full control. Put the FE there. Ask your IT manager to know it.

--------------------
Please forgive in advance my horrible English.
Go to the top of the page
 
BuzyG
post Jun 18 2019, 07:15 AM
Post#3



Posts: 417
Joined: 20-September 12
From: Cornwall UK


Hi Phil

We have no such accessible hiding place for local use. We did have once, but it went with windows7 implementation, many years ago. Since then users have been able to inadvertently share an FE, though they are informed enough that they should only log into an FE where there is no lock file active. I'm certain they still do though because they are human and they can.

I am working with the IS package manager, so I will ask if there is a way he can repackage this particular FE, to put it on each user C: drive.

Doesn't alter the fact that these issues never showed themselves in any previous version of windows. Therefore windows 10 is certainly playing it's part and quite rightly, IMHO, gets some of the wrap for these errors.


If this is not an option to me, is there anything else that I haven't tried that folk know of, in respect of this error.
This post has been edited by BuzyG: Jun 18 2019, 07:18 AM

--------------------
Live to Surf
Go to the top of the page
 
BuzyG
post Jun 18 2019, 07:28 AM
Post#4



Posts: 417
Joined: 20-September 12
From: Cornwall UK


Hi Daniel

Yes indeed. We have had the error for a good few months ourselves and I have read up much on it. Including some of your own inputs thx. We still have no resolution though, so I thought I would post up here. This is by some way the most knowledgeable Access community I know of and you never know what fresh information, people such as your good self, may have found, since the last internet trawl.

BuzyG

--------------------
Live to Surf
Go to the top of the page
 
DanielPineault
post Jun 18 2019, 07:50 AM
Post#5


UtterAccess VIP
Posts: 6,857
Joined: 30-June 11



Did you implement the Registry Hack?

QUOTE
we are still working on a server 200 miles away

So you are using Access over a WAN?! In that case, you need to use Terminal Services, CITRIX, Remote Desktop, ... Access, with each newer version, is more and more incapable to such feats. Personally, with such a setup, I'd be looking at another back-end immediately (SQL Server, SQL Azure, ...), if not completely switching away from Access to PHP/MySQL, .Net, ...

--------------------
Daniel Pineault (2010-2019 Microsoft MVP)
Professional Help: http://www.cardaconsultants.com
Free MS Access Code, Tips, Tricks and Samples: http://www.devhut.net

* Design should never say "Look at me". It should always say "Look at this". -- David Craib
* A user interface is like a joke, if you have to explain it, it's not that good! -- Martin LeBlanc


All code samples, demonstration databases, links,... are provided 'AS IS' and are to be used at your own risk! Take the necessary steps to check, validate ...(you are responsible for your choices and actions)
Go to the top of the page
 
BuzyG
post Jun 18 2019, 08:32 AM
Post#6



Posts: 417
Joined: 20-September 12
From: Cornwall UK


Your replies read like the end of Access as we have known and loved it for 30 odd years.

Thus far we have spent close to 7 figures, just on this site, trying to implement, within a shared world wide, corporate solution, what a few smaller access databases used to do effortlessly, but locally. Current target is to complete within three years. Until then I have the task of keeping them going, with an ever growing list of users and projects and another multinational, Microsoft who clearly don't see a future for Access either frown.gif. I did at least have the pleasure of creating them in the first place. smile.gif

Thx for your replies. I will keep an eye out for any more ideas here.

--------------------
Live to Surf
Go to the top of the page
 
DanielPineault
post Jun 18 2019, 08:43 AM
Post#7


UtterAccess VIP
Posts: 6,857
Joined: 30-June 11



Nothing has truly change on the Access front. It was never meant to be used over a WAN (Albert Kallal has an excellent article on this which has been around for 10-20+ years now) and you're never supposed to share a common copy of a front-end with multiple users. It's absolutely amazing that you didn't encounter serious issues prior to this. But yes, this latest Windows 10 bug is an absolute show stopper if you are impacted by it. The workaround (disable leasing) works, but many experience some network performance reduction.

QUOTE
with an ever growing list of users

This may be part of your issue as well. If the number of users has increased, you may have finally hit the breaking point of Access on your WAN.

Terminal Services and CITRIX remain 2 great options IMHO, or migrating the back-end to SQL Server/SQL Server Express and would give you a lot more stability (well outside of the Microsoft bugs! - <deep breath here/>).

Good luck.

--------------------
Daniel Pineault (2010-2019 Microsoft MVP)
Professional Help: http://www.cardaconsultants.com
Free MS Access Code, Tips, Tricks and Samples: http://www.devhut.net

* Design should never say "Look at me". It should always say "Look at this". -- David Craib
* A user interface is like a joke, if you have to explain it, it's not that good! -- Martin LeBlanc


All code samples, demonstration databases, links,... are provided 'AS IS' and are to be used at your own risk! Take the necessary steps to check, validate ...(you are responsible for your choices and actions)
Go to the top of the page
 

Posts in this topic
- BuzyG   Inconsistent State Error On Windows 10   Jun 18 2019, 05:29 AM
- - Phil_cattivocarattere   QUOTE (BuzyG)But it is possible for more than one ...   Jun 18 2019, 05:44 AM
|- - BuzyG   Hi Phil We have no such accessible hiding place f...   Jun 18 2019, 07:15 AM
|- - cheekybuddha   If each user can't have their own copy of the ...   Jun 18 2019, 07:21 AM
|- - BuzyG   Hi Daniel Yes indeed. We have had the error for a...   Jun 18 2019, 07:28 AM
||- - DanielPineault   Did you implement the Registry Hack? QUOTE we are...   Jun 18 2019, 07:50 AM
||- - cheekybuddha   >> we are still working on a server 200 mile...   Jun 18 2019, 08:01 AM
||- - BuzyG   Your replies read like the end of Access as we hav...   Jun 18 2019, 08:32 AM
||- - DanielPineault   Nothing has truly change on the Access front. It ...   Jun 18 2019, 08:43 AM
||- - BuzyG   Your absolutely right Daniel. I was expecting tro...   Jun 18 2019, 10:34 AM
||- - BuzyG   I received this from our IS Package managed this m...   Jun 20 2019, 02:40 AM
||- - DanielPineault   NAS devices are finicky when it comes to Access da...   Jun 20 2019, 05:02 AM
||- - cheekybuddha   Reading through all this, I think migrating your b...   Jun 20 2019, 05:23 AM
||- - DanielPineault   cheekybuddha brings up a good point. SQL Server i...   Jun 20 2019, 06:52 AM
|- - BuzyG   Hi Cheeky Completely agree with your suggestion a...   Jun 18 2019, 07:32 AM
- - DanielPineault   It's a known bug that is now more than a year ...   Jun 18 2019, 07:01 AM
- - CaptainMilly   QUOTE I do not have access to users C: drives so h...   Aug 14 2019, 06:47 AM



Custom Search


RSSSearch   Top   Lo-Fi    23rd September 2019 - 02:06 AM