最近出现了不一致状态的 Microsoft Access 数据库文件 [英] Recent rash of Microsoft Access database files in an inconsistent state

问题描述

运行我们构建的拆分前端/后端 Microsoft Access 应用程序的大量客户都遇到了频繁但间歇性的数据库文件损坏问题.当后端文件打开时，出现此消息:Microsoft Access 已检测到此数据库处于不一致状态，并将尝试恢复数据库……"

使用 Visual Basic 代码通过 DAO 打开数据库会导致错误代码 3343，无法识别的数据库格式".

修复尝试成功，我们没有目睹任何数据丢失或主键、索引或关系丢失.大多数情况涉及后端文件位于共享网络驱动器上的位置.一些搜索表明最新的 Windows 10 更新 1803 是可疑的.有没有其他人遇到过这种情况?

解决方案

最近有报道 几个 次数.可以在 此处.

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

移至 Server 2012 导致 Access 数据库损坏

无法访问 Windows Server 2012 或 Windows Server 2012 R2 驱动器上的共享文件或文件夹

评论:

<块引用>

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

我只能这么认为最新的 Windows 10 Build 1803 中的某些内容提出了这个问题再次因为运行该构建的 PC 导致了问题.

修复是将以下条目添加到 Vospers 服务器中2012 R2 注册表:

键:HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServiceslanmanserverparameters值:禁用租赁类型:双字数据:0x1

<块引用>

我们在我们的服务器上对此进行了测试，问题消失了.只要我们再次将禁用租赁"值更改为0"，问题返回.

我还找不到合理的解释来解释为什么会这样上周开始发生，但如果它有效并且不会导致任何其他地方还有其他问题，那么我可以接受.

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 … "

Opening the database with DAO using Visual Basic code results in error code 3343, "Unrecognized database format."

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:

Moved to Server 2012 getting Access Database Corruption

Cannot access shared files or folders on a drive in Windows Server 2012 or Windows Server 2012 R2

Comments:

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.

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.

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

Key:   HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServiceslanmanserverparameters
Value: DisableLeasing
Type:  DWORD
Data:  0x1

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屋！