Windows 10 1803 的 VFP 网络问题 [英] VFP networking issues with Windows 10 1803

查看:27
本文介绍了Windows 10 1803 的 VFP 网络问题的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们在 Windows 1803 版和 VFP9 SP2 上遇到了多用户网络文件共享的一些重大问题.以下是我们看到的一些问题:

We are experiencing some huge issues with multi-user network file sharing on version 1803 of Windows and VFP9 SP2. Here are a few of the issues we see:

  1. 写入数据库的空白记录.一个系统会写出一个完整的记录,所有字段都有值,但该记录在表格中是空白的.

  1. Blank records written to the database. A system will write a complete record with values in all fields, but the record is blank in the table.

已写入但在表关闭之前不会向其他用户显示的记录.如果会话 A 打开一个表并添加 5 条记录,会话 B 将看到额外的 5 条记录在那里,但它们要么是空白的,要么看起来包含来自前一条记录的数据.一旦会话 A 关闭表格,其他会话的数据就会出现.

Records that are written but don't appear for other users until the table is closed. If session A opens a table and adds 5 records, session B will see that the extra 5 records are there, but they will either be blank or will appear to have data from a previous record in them. Once session A closes the table, the data appears for other sessions.

记录将被附加到表格中,最终只会创建先前记录的副本.

Records will be appended to a table, and will end up just creating a duplicate of a previous record instead.

这些似乎都是缓存或某种延迟写入的问题.

These all appear to be issues with caching or delayed writes of some sort.

在过去几天中,我在数十个安装中非常一致地看到了这些问题的各种组合.唯一的解决方案是让用户回滚到以前的 Windows 版本.

I've seen various combinations of these problems very consistently across dozens of installations in the last couple of days. The only solution has been to have the users roll back to the previous build of Windows.

我们已尝试在客户端和服务器计算机上禁用 oplocks 并验证未启用脱机文件,但尚未找到解决方案.

We've tried disabling oplocks on the client and server machines and verifying offline files are not enabled, but haven't found a solutions.

有没有其他人见过类似的东西?建议?如果我们不弄清楚,这可能是一场灾难.

Has anyone else seen anything similar? Suggestions? This could be a disaster if we don't figure it out.

推荐答案

这就是我们所发现的.这些问题似乎是由 Windows 1803 的 KB4103721 更新引起的.我们能够通过删除该更新作为临时解决方案来解决该问题.

So here is what we have found. The problems seem to be specifically caused by the KB4103721 update to Windows 1803. We were able to resolve the problem by removing that update as a temporary solution.

我们现在通过禁用一些 SMB 缓存参数发现了这一点.

We have now found that by disabling some of the SMB caching parameters.

打开一个 powershell 管理提示.(右键单击开始按钮)

Open a powershell administrative prompt. (right click on the start button)

执行以下两条命令:

set-smbclientconfiguration -DirectoryCacheLifetime 0
set-smbclientconfiguration -FileInfoCacheLifetime 0

然后你可以运行

get-smbclientconfiguration

验证设置的值.

这篇关于Windows 10 1803 的 VFP 网络问题的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆