2018年5月CU之后丢失到日志目录的权限 [英] Permissions lost to log directory after May 2018 CU

查看:37
本文介绍了2018年5月CU之后丢失到日志目录的权限的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

有没有人因为CU安装后因权限问题而导致SharePoint日志目录被锁定? 我们正在较低环境服务器场上测试May CU,我们注意到,当他们从重新启动回来时,SharePoint日志目录上的权限
已经消失,因此任何人(包括管理员帐户)都无法访问它们 这会导致SharePoint出错,直到恢复权限(通常我必须更改日志文件夹的权限才能从父级继承
)。

Has anyone ever experienced the SharePoint log directory being locked due to permissions issues after a CU install?  We are testing the May CU on our lower environment server farms, and we are noticing that when they come back from reboot the permissions on the SharePoint log directory are gone so that no one, including the administrator accounts, can access them.  This causes SharePoint to error out until permissions are restored (typically I have had to change the permissions on the log folder to inherit from parent).

任何想法为什么会这样做?来自SharePoint v 15.0.5015.1002 to v 15.0.5031.1000如果重要。

Any ideas why this is happening? Going from SharePoint v15.0.5015.1002 to v15.0.5031.1000 if that matters.

推荐答案

这可能是2018年5月CU内的一个错误。因为在没有在非生产环境中对其进行彻底测试的情况下更新到CU也为时尚早。 

It might be a bug within the May 2018 CU. as it's still too early to update to that CU without thoroughly testing it in a non-prod environment. 

这是您在2018年5月CU注意到的唯一问题吗?

Was that the only issue you noticed with the May 2018 CU?


这篇关于2018年5月CU之后丢失到日志目录的权限的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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