![]() | Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||
Solution Type Sun Alert Sure Solution 1143914.1 : Installation of Microsoft Security Update KB980232 on Windows Systems That Access ST5210/5220/5310/5320 NAS Systems May Cause Loss of File Access/File Descriptors
In this Document
Applies to:Sun Storage 5320 NAS ApplianceSun Storage 5210 NAS Appliance Sun Storage 5220 NAS Appliance Sun Storage 5310 NAS Appliance Generic Windows ________________________________ SUNBUG:6945065 Date of Workaround release: 06-May-2010 Date of Resolved release: 07-Jul-2010 ________________________________ DescriptionInstallation of Microsoft Security Update KB980232 on Windows systems that access Sun StorageTek ST5210/5220/5310/5320 NAS systems may cause a loss of access to files or file descriptor data and/or the inability to edit/save existing files. OccurrenceThis issue can affect the following platforms:
for all NAS OS releases up to and including 4.22M1, where Microsoft Security Update KB980232 is installed on a Windows system that accesses those NAS systems. se5320-b > version SymptomsIf Microsoft Security Update KB980232 has been applied to a Microsoft Windows system which accesses a Sun StorageTek NAS appliance, users and Domain Administrators will not be able to see or set security permissions for files served by the StorageTek NAS appliance. Users and Domain Administrators will not be able to access security descriptor information for such files but will instead see an error message similar to the following: "Unable to display security information." If a user attempts to write to a pre-existing file stored on the StorageTek NAS appliance, the attempt will fail with an error message similar to the following: "There has been a network or file permission error. The network connection may be lost" or: "Document not saved." WorkaroundTo address this issue, download and install Microsoft Hotfix 983458 on the Windows client that is being served by the StorageTek NAS appliance. For a detailed explanation of this issue and Hotfix download instructions, please see: History06-May-2010: Date of Workaround release Attachments This solution has no attachment |
||||||||||||||||||||
|