状态不一致的Microsoft Access数据库文件最近发生的故障 [英] Recent rash of Microsoft Access database files in an inconsistent state

问题描述

我们构建的前端/后端Microsoft Access拆分应用程序的大量客户都遇到频繁但间歇性的数据库文件损坏问题.打开后端文件后，将显示以下消息:"Microsoft Access已检测到该数据库处于不一致状态，并将尝试恢复该数据库……"修复尝试成功，并且我们没有目睹任何数据丢失或主数据库丢失的情况.键，索引或关系.大多数情况下，后端文件位于共享的网络驱动器上.一些搜索表明可疑的是最新的Windows 10更新1803.还有其他人遇到过吗?

A large number of our clients operating a split front end/back end Microsoft Access application we built are encountering frequent but intermittent database file corruption issues. When the back end file is opened this message appears: "Microsoft Access has detected that this database is in an inconsistent state, and will attempt to recover the database … " The repair attempt succeeds and we have not witnessed any data loss or dropping of primary keys, indexes, or relationships. Most cases involve where the back end file is located on a shared network drive. Some searches suggest that the latest Windows 10 update 1803 is suspect. Has anybody else encountered this?

推荐答案

最近已被报道时间.可以

It has recently been reported several times. A very thorough coverage of this issue can be found here.

奇怪的是，至少在某些情况下，可以在旧的支持线程中找到治愈方法:

Strangely, the cure can - at least for some cases - be found in old support threads:

评论:

这有点奇怪，因为修复此问题的补丁是在5月. 2014已安装在服务器上.

It’s a bit strange though as the patch to fix the issue is back in May 2014 which is already installed on the server.

我只能认为 最新的Windows 10 Build 1803中的某些内容提出了该问题 再次是因为正在运行该版本的PC导致了 问题.

I can only think that something in the latest Windows 10 Build 1803 has brought up the issue again as it was PC’s that are running that build were causing the problem.

此修复程序将以下条目添加到Vospers Server中 2012 R2注册表:

The fix is adding the following entry into Vospers Server 2012 R2 registry:

Key:   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
Value: DisableLeasing
Type:  DWORD
Data:  0x1

我们在服务器上对此进行了测试，问题消失了.一旦我们 再次将禁用租赁"的值更改为"0"，这是问题所在 回来.

We testing this on our server and the problem went away. As soon as we changed the ‘Disable leasing’ value to ‘0’ again, the problem returned.

我还找不到合理的解释来解释为什么 已于上周开始发生，但如果有效且不会引起任何后果 还有其他问题，我可以接受.

I can’t find a reasonable explanation yet as to why this has started to happen last week but if it works and doesn’t cause any further issues elsewhere then I’m ok with that.

这篇关于状态不一致的Microsoft Access数据库文件最近发生的故障的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！