堆栈内存溢出
  简体   繁体   English

ApplicationSettingsBase.Save：无法将配置保存到文件

[英]ApplicationSettingsBase.Save: Unable to save config to file

 原文  2020-10-14 14:54:13  5   1    winforms/ configuration/ citrix/ file-access/ xenapp

问题描述

What could cause ApplicationSettingsBase.Save to fail with the error "Unable to save config to file "?什么可能导致 ApplicationSettingsBase.Save 失败并显示错误“无法将配置保存到文件”？

if (Settings.Default.CallUpgrade)
{
    Settings.Default.Upgrade();
    Settings.Default.CallUpgrade = false;
    Settings.Default.Save();
}


Exception Type: System.Configuration.ConfigurationErrorsException

Exception Message: Konfiguration konnte nicht in Datei "C:\Users\u00001\AppData\Roaming\CompanyName\ApplicationName.ex_StrongName_4vozv12n21s5wt5tg4h44jakrs6m65xy\3.0.0.1\user.config" gespeichert werden.

Stack Trace:
   bei System.Configuration.Internal.WriteFileContext.ReplaceFile(String Source, String Target)
   bei System.Configuration.Internal.WriteFileContext.Complete(String filename, Boolean success)
   bei System.Configuration.Internal.InternalConfigHost.StaticWriteCompleted(String streamName, Boolean success, Object writeContext, Boolean assertPermissions)
   bei System.Configuration.Internal.InternalConfigHost.System.Configuration.Internal.IInternalConfigHost.WriteCompleted(String streamName, Boolean success, Object writeContext, Boolean assertPermissions)
   bei System.Configuration.Internal.DelegatingConfigHost.WriteCompleted(String streamName, Boolean success, Object writeContext, Boolean assertPermissions)
   bei System.Configuration.ClientSettingsStore.ClientSettingsConfigurationHost.WriteCompleted(String streamName, Boolean success, Object writeContext)
   bei System.Configuration.UpdateConfigHost.WriteCompleted(String streamName, Boolean success, Object writeContext)
   bei System.Configuration.MgmtConfigurationRecord.SaveAs(String filename, ConfigurationSaveMode saveMode, Boolean forceUpdateAll)
   bei System.Configuration.Configuration.SaveAsImpl(String filename, ConfigurationSaveMode saveMode, Boolean forceSaveAll)
   bei System.Configuration.ClientSettingsStore.WriteSettings(String sectionName, Boolean isRoaming, IDictionary newSettings)

In addition to user.config, the folder contains another file named a2rx2s4u.newcfg.除了 user.config 之外，该文件夹还包含另一个名为 a2rx2s4u.newcfg 的文件。 The user running the application has full control on the folder.运行应用程序的用户可以完全控制文件夹。

The application is run on a Windows 2019 Server with Citrix XenApp.该应用程序在带有 Citrix XenApp 的 Windows 2019 服务器上运行。

I've logged the activity of the app with Sysinternals Process Monitor.我已经使用 Sysinternals Process Monitor 记录了应用程序的活动。 As far as I understand, the application tries to rename a2rx2s4u.newcfg to user.config replacing the existing user.config, and that seems to fail:据我了解，该应用程序尝试将 a2rx2s4u.newcfg 重命名为 user.config 以替换现有的 user.config，这似乎失败了：

Operation: IRP_MJ_SET_INFORMATION
Result: 0xC0000369
Path: C:\Users\u00001\AppData\Roaming\CompanyName\ApplicationName.ex_StrongName_4vozv12n21s5wt5tg4h44jakrs6m65xy\3.0.0.1\a2rx2s4u.newcfg
Type: SetRenameInformationFile
ReplaceIfExists: True
FileName: C:\Users\u00001\AppData\Roaming\CompanyName\ApplicationName.ex_StrongName_4vozv12n21s5wt5tg4h44jakrs6m65xy\3.0.0.1\user.config

Stack trace from Process Explorer:来自 Process Explorer 的堆栈跟踪：

    "Frame","Module","Location","Address","Path"
"0","FLTMGR.SYS","FLTMGR.SYS + 0x555d","0xfffff8058039555d","C:\Windows\System32\drivers\FLTMGR.SYS"
"1","FLTMGR.SYS","FLTMGR.SYS + 0x50bc","0xfffff805803950bc","C:\Windows\System32\drivers\FLTMGR.SYS"
"2","FLTMGR.SYS","FLTMGR.SYS + 0x4c28","0xfffff80580394c28","C:\Windows\System32\drivers\FLTMGR.SYS"
"3","FLTMGR.SYS","FLTMGR.SYS + 0x4a1e","0xfffff80580394a1e","C:\Windows\System32\drivers\FLTMGR.SYS"
"4","ntoskrnl.exe","ntoskrnl.exe + 0x38109","0xfffff8016c0db109","C:\Windows\system32\ntoskrnl.exe"
"5","ntoskrnl.exe","ntoskrnl.exe + 0x10b343","0xfffff8016c1ae343","C:\Windows\system32\ntoskrnl.exe"
"6","ntoskrnl.exe","ntoskrnl.exe + 0x11a4ac","0xfffff8016c1bd4ac","C:\Windows\system32\ntoskrnl.exe"
"7","ntoskrnl.exe","ntoskrnl.exe + 0x1c8605","0xfffff8016c26b605","C:\Windows\system32\ntoskrnl.exe"
"8","ntdll.dll","ntdll.dll + 0x9fc44","0x7ffb5408fc44","C:\Windows\System32\ntdll.dll"
"9","wow64.dll","wow64.dll + 0x14a35","0x7ffb53ca4a35","C:\Windows\System32\wow64.dll"
"10","wow64.dll","wow64.dll + 0xa507","0x7ffb53c9a507","C:\Windows\System32\wow64.dll"
"11","wow64.dll","wow64.dll + 0x7783","0x7ffb53c97783","C:\Windows\System32\wow64.dll"
"12","wow64cpu.dll","wow64cpu.dll + 0x1783","0x775f1783","C:\Windows\System32\wow64cpu.dll"
"13","wow64cpu.dll","wow64cpu.dll + 0x1199","0x775f1199","C:\Windows\System32\wow64cpu.dll"
"14","wow64.dll","wow64.dll + 0xcfda","0x7ffb53c9cfda","C:\Windows\System32\wow64.dll"
"15","wow64.dll","wow64.dll + 0x17dfd","0x7ffb53ca7dfd","C:\Windows\System32\wow64.dll"
"16","wow64win.dll","wow64win.dll + 0x2e0f","0x7ffb53ee2e0f","C:\Windows\System32\wow64win.dll"
"17","ntdll.dll","ntdll.dll + 0xa34b4","0x7ffb540934b4","C:\Windows\System32\ntdll.dll"
"18","ntoskrnl.exe","ntoskrnl.exe + 0x672ae5","0xfffff8016c715ae5","C:\Windows\system32\ntoskrnl.exe"
"19","win32kfull.sys","win32kfull.sys + 0x65ff7","0xfffff4df95065ff7","C:\Windows\System32\win32kfull.sys"
"20","win32kfull.sys","win32kfull.sys + 0x65d20","0xfffff4df95065d20","C:\Windows\System32\win32kfull.sys"
"21","win32kfull.sys","win32kfull.sys + 0x65796","0xfffff4df95065796","C:\Windows\System32\win32kfull.sys"
"22","win32kfull.sys","win32kfull.sys + 0x652dc","0xfffff4df950652dc","C:\Windows\System32\win32kfull.sys"
"23","win32kfull.sys","win32kfull.sys + 0xa033e","0xfffff4df950a033e","C:\Windows\System32\win32kfull.sys"
"24","win32kfull.sys","win32kfull.sys + 0x5a972","0xfffff4df9505a972","C:\Windows\System32\win32kfull.sys"
"25","win32kfull.sys","win32kfull.sys + 0x5a020","0xfffff4df9505a020","C:\Windows\System32\win32kfull.sys"
"26","win32kfull.sys","win32kfull.sys + 0xec27c","0xfffff4df950ec27c","C:\Windows\System32\win32kfull.sys"
"27","win32kfull.sys","win32kfull.sys + 0xce961","0xfffff4df950ce961","C:\Windows\System32\win32kfull.sys"
"28","ntoskrnl.exe","ntoskrnl.exe + 0x1c8605","0xfffff8016c26b605","C:\Windows\system32\ntoskrnl.exe"
"29","wow64win.dll","wow64win.dll + 0xf5b4","0x7ffb53eef5b4","C:\Windows\System32\wow64win.dll"
"30","wow64win.dll","wow64win.dll + 0x36d2","0x7ffb53ee36d2","C:\Windows\System32\wow64win.dll"
"31","wow64win.dll","wow64win.dll + 0x19fe","0x7ffb53ee19fe","C:\Windows\System32\wow64win.dll"
"32","wow64.dll","wow64.dll + 0x7783","0x7ffb53c97783","C:\Windows\System32\wow64.dll"
"33","wow64cpu.dll","wow64cpu.dll + 0x1783","0x775f1783","C:\Windows\System32\wow64cpu.dll"
"34","wow64cpu.dll","wow64cpu.dll + 0x1199","0x775f1199","C:\Windows\System32\wow64cpu.dll"
"35","wow64.dll","wow64.dll + 0xcfda","0x7ffb53c9cfda","C:\Windows\System32\wow64.dll"
"36","wow64.dll","wow64.dll + 0xcea0","0x7ffb53c9cea0","C:\Windows\System32\wow64.dll"
"37","ntdll.dll","ntdll.dll + 0xd5c7d","0x7ffb540c5c7d","C:\Windows\System32\ntdll.dll"
"38","ntdll.dll","ntdll.dll + 0xc38b9","0x7ffb540b38b9","C:\Windows\System32\ntdll.dll"
"39","ntdll.dll","ntdll.dll + 0x756c3","0x7ffb540656c3","C:\Windows\System32\ntdll.dll"
"40","ntdll.dll","ntdll.dll + 0x7566e","0x7ffb5406566e","C:\Windows\System32\ntdll.dll"
"41","ntdll.dll","ntdll.dll + 0x7090c","0x7767090c","C:\Windows\SysWOW64\ntdll.dll"
"42","KernelBase.dll","KernelBase.dll + 0x121517","0x76341517","C:\Windows\SysWOW64\KernelBase.dll"
"43","KernelBase.dll","KernelBase.dll + 0x121338","0x76341338","C:\Windows\SysWOW64\KernelBase.dll"
"44","Sfrhook.dll","Sfrhook.dll + 0x2ae7","0x730a2ae7","C:\Program Files (x86)\Citrix\System32\Sfrhook.dll"
"45","System.Configuration.ni.dll","System.Configuration.ni.dll + 0xa427d","0x6d92427d","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Configuration\727d61c30dcf1fe944a3c6110c244de8\System.Configuration.ni.dll"
"46","System.Configuration.ni.dll","System.Configuration.ni.dll + 0xc4c31","0x6d944c31","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Configuration\727d61c30dcf1fe944a3c6110c244de8\System.Configuration.ni.dll"
"47","System.Configuration.ni.dll","System.Configuration.ni.dll + 0xc4bbd","0x6d944bbd","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Configuration\727d61c30dcf1fe944a3c6110c244de8\System.Configuration.ni.dll"
"48","System.Configuration.ni.dll","System.Configuration.ni.dll + 0xc49c3","0x6d9449c3","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Configuration\727d61c30dcf1fe944a3c6110c244de8\System.Configuration.ni.dll"
"49","System.Configuration.ni.dll","System.Configuration.ni.dll + 0xc42c2","0x6d9442c2","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Configuration\727d61c30dcf1fe944a3c6110c244de8\System.Configuration.ni.dll"
"50","System.Configuration.ni.dll","System.Configuration.ni.dll + 0xc4334","0x6d944334","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Configuration\727d61c30dcf1fe944a3c6110c244de8\System.Configuration.ni.dll"
"51","System.ni.dll","System.ni.dll + 0x75e36e","0x705ee36e","C:\Windows\assembly\NativeImages_v4.0.30319_32\System\9d718786e2ea160f395d8ee3d2488791\System.ni.dll"
"52","System.Configuration.ni.dll","System.Configuration.ni.dll + 0xc225c","0x6d94225c","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Configuration\727d61c30dcf1fe944a3c6110c244de8\System.Configuration.ni.dll"
"53","System.Configuration.ni.dll","System.Configuration.ni.dll + 0xb6d07","0x6d936d07","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Configuration\727d61c30dcf1fe944a3c6110c244de8\System.Configuration.ni.dll"
"54","System.Configuration.ni.dll","System.Configuration.ni.dll + 0xab5cd","0x6d92b5cd","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Configuration\727d61c30dcf1fe944a3c6110c244de8\System.Configuration.ni.dll"
"55","System.ni.dll","System.ni.dll + 0x6423f0","0x704d23f0","C:\Windows\assembly\NativeImages_v4.0.30319_32\System\9d718786e2ea160f395d8ee3d2488791\System.ni.dll"
"56","System.ni.dll","System.ni.dll + 0x643fcf","0x704d3fcf","C:\Windows\assembly\NativeImages_v4.0.30319_32\System\9d718786e2ea160f395d8ee3d2488791\System.ni.dll"
"57","<unknown>","0xccf4cde","0xccf4cde",""
"58","System.ni.dll","System.ni.dll + 0x646425","0x704d6425","C:\Windows\assembly\NativeImages_v4.0.30319_32\System\9d718786e2ea160f395d8ee3d2488791\System.ni.dll"
"59","System.ni.dll","System.ni.dll + 0x64624f","0x704d624f","C:\Windows\assembly\NativeImages_v4.0.30319_32\System\9d718786e2ea160f395d8ee3d2488791\System.ni.dll"
"60","System.ni.dll","System.ni.dll + 0x641636","0x704d1636","C:\Windows\assembly\NativeImages_v4.0.30319_32\System\9d718786e2ea160f395d8ee3d2488791\System.ni.dll"
"61","<unknown>","0x9e7637a","0x9e7637a",""
"62","<unknown>","0x9e75ff5","0x9e75ff5",""
"63","System.Windows.Forms.ni.dll","System.Windows.Forms.ni.dll + 0x8b8b0c","0x60988b0c","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\bf4d479ac30cbf95afe4c0d4de1fc37b\System.Windows.Forms.ni.dll"
"64","System.Windows.Forms.ni.dll","System.Windows.Forms.ni.dll + 0x8bcc03","0x6098cc03","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\bf4d479ac30cbf95afe4c0d4de1fc37b\System.Windows.Forms.ni.dll"
"65","System.Windows.Forms.ni.dll","System.Windows.Forms.ni.dll + 0xc43fe4","0x60d13fe4","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\bf4d479ac30cbf95afe4c0d4de1fc37b\System.Windows.Forms.ni.dll"
"66","<unknown>","0xa4b0385","0xa4b0385",""
"67","System.Windows.Forms.ni.dll","System.Windows.Forms.ni.dll + 0x1c2ff3","0x60292ff3","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\bf4d479ac30cbf95afe4c0d4de1fc37b\System.Windows.Forms.ni.dll"
"68","System.Windows.Forms.ni.dll","System.Windows.Forms.ni.dll + 0x1c2f85","0x60292f85","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\bf4d479ac30cbf95afe4c0d4de1fc37b\System.Windows.Forms.ni.dll"
"69","System.Windows.Forms.ni.dll","System.Windows.Forms.ni.dll + 0x1c28c0","0x602928c0","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\bf4d479ac30cbf95afe4c0d4de1fc37b\System.Windows.Forms.ni.dll"
"70","<unknown>","0x32dd446","0x32dd446",""
"71","user32.dll","user32.dll + 0x45cab","0x77495cab","C:\Windows\SysWOW64\user32.dll"
"72","user32.dll","user32.dll + 0x367bc","0x774867bc","C:\Windows\SysWOW64\user32.dll"
"73","user32.dll","user32.dll + 0x3635a","0x7748635a","C:\Windows\SysWOW64\user32.dll"
"74","user32.dll","user32.dll + 0x4312f","0x7749312f","C:\Windows\SysWOW64\user32.dll"
"75","ntdll.dll","ntdll.dll + 0x72aed","0x77672aed","C:\Windows\SysWOW64\ntdll.dll"
"76","user32.dll","user32.dll + 0x37b5f","0x77487b5f","C:\Windows\SysWOW64\user32.dll"
"77","uxtheme.dll","uxtheme.dll + 0x32dca","0x74342dca","C:\Windows\SysWOW64\uxtheme.dll"
"78","uxtheme.dll","uxtheme.dll + 0x32418","0x74342418","C:\Windows\SysWOW64\uxtheme.dll"
"79","user32.dll","user32.dll + 0x37dd3","0x77487dd3","C:\Windows\SysWOW64\user32.dll"
"80","user32.dll","user32.dll + 0x45cab","0x77495cab","C:\Windows\SysWOW64\user32.dll"
"81","user32.dll","user32.dll + 0x367bc","0x774867bc","C:\Windows\SysWOW64\user32.dll"
"82","user32.dll","user32.dll + 0x35d0f","0x77485d0f","C:\Windows\SysWOW64\user32.dll"
"83","System.Windows.Forms.ni.dll","System.Windows.Forms.ni.dll + 0x1c35d7","0x602935d7","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\bf4d479ac30cbf95afe4c0d4de1fc37b\System.Windows.Forms.ni.dll"
"84","System.Windows.Forms.ni.dll","System.Windows.Forms.ni.dll + 0x1cca34","0x6029ca34","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\bf4d479ac30cbf95afe4c0d4de1fc37b\System.Windows.Forms.ni.dll"
"85","System.Windows.Forms.ni.dll","System.Windows.Forms.ni.dll + 0xc4180c","0x60d1180c","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\bf4d479ac30cbf95afe4c0d4de1fc37b\System.Windows.Forms.ni.dll"
"86","System.Windows.Forms.ni.dll","System.Windows.Forms.ni.dll + 0x1cc9c1","0x6029c9c1","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\bf4d479ac30cbf95afe4c0d4de1fc37b\System.Windows.Forms.ni.dll"
"87","System.Windows.Forms.ni.dll","System.Windows.Forms.ni.dll + 0x1cdae3","0x6029dae3","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\bf4d479ac30cbf95afe4c0d4de1fc37b\System.Windows.Forms.ni.dll"
"88","System.Windows.Forms.ni.dll","System.Windows.Forms.ni.dll + 0x8bd542","0x6098d542","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\bf4d479ac30cbf95afe4c0d4de1fc37b\System.Windows.Forms.ni.dll"
"89","System.Windows.Forms.ni.dll","System.Windows.Forms.ni.dll + 0xc43ea9","0x60d13ea9","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\bf4d479ac30cbf95afe4c0d4de1fc37b\System.Windows.Forms.ni.dll"
"90","<unknown>","0xa4b0385","0xa4b0385",""
"91","System.Windows.Forms.ni.dll","System.Windows.Forms.ni.dll + 0x1c2ff3","0x60292ff3","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\bf4d479ac30cbf95afe4c0d4de1fc37b\System.Windows.Forms.ni.dll"
"92","System.Windows.Forms.ni.dll","System.Windows.Forms.ni.dll + 0x1c2f85","0x60292f85","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\bf4d479ac30cbf95afe4c0d4de1fc37b\System.Windows.Forms.ni.dll"
"93","System.Windows.Forms.ni.dll","System.Windows.Forms.ni.dll + 0x1c28c0","0x602928c0","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\bf4d479ac30cbf95afe4c0d4de1fc37b\System.Windows.Forms.ni.dll"
"94","<unknown>","0x32dd446","0x32dd446",""
"95","user32.dll","user32.dll + 0x45cab","0x77495cab","C:\Windows\SysWOW64\user32.dll"
"96","user32.dll","user32.dll + 0x367bc","0x774867bc","C:\Windows\SysWOW64\user32.dll"
"97","user32.dll","user32.dll + 0x358fb","0x774858fb","C:\Windows\SysWOW64\user32.dll"
"98","user32.dll","user32.dll + 0x356d0","0x774856d0","C:\Windows\SysWOW64\user32.dll"
"99","System.Windows.Forms.ni.dll","System.Windows.Forms.ni.dll + 0x225f1d","0x602f5f1d","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\bf4d479ac30cbf95afe4c0d4de1fc37b\System.Windows.Forms.ni.dll"
"100","System.Windows.Forms.ni.dll","System.Windows.Forms.ni.dll + 0x1d34e3","0x602a34e3","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\bf4d479ac30cbf95afe4c0d4de1fc37b\System.Windows.Forms.ni.dll"
"101","System.Windows.Forms.ni.dll","System.Windows.Forms.ni.dll + 0x1d30d1","0x602a30d1","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\bf4d479ac30cbf95afe4c0d4de1fc37b\System.Windows.Forms.ni.dll"
"102","System.Windows.Forms.ni.dll","System.Windows.Forms.ni.dll + 0x1d2f23","0x602a2f23","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\bf4d479ac30cbf95afe4c0d4de1fc37b\System.Windows.Forms.ni.dll"
"103","System.Windows.Forms.ni.dll","System.Windows.Forms.ni.dll + 0x893c13","0x60963c13","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\bf4d479ac30cbf95afe4c0d4de1fc37b\System.Windows.Forms.ni.dll"
"104","System.Windows.Forms.ni.dll","System.Windows.Forms.ni.dll + 0x8bbf5d","0x6098bf5d","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\bf4d479ac30cbf95afe4c0d4de1fc37b\System.Windows.Forms.ni.dll"
"105","System.Windows.Forms.ni.dll","System.Windows.Forms.ni.dll + 0x8bbc0d","0x6098bc0d","C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\bf4d479ac30cbf95afe4c0d4de1fc37b\System.Windows.Forms.ni.dll"
"106","<unknown>","0x9f6225b","0x9f6225b",""
"107","<unknown>","0x9d89434","0x9d89434",""
"108","<unknown>","0x822b0f7","0x822b0f7",""
"109","<unknown>","0x3411f66","0x3411f66",""
"110","clr.dll","clr.dll + 0xf036","0x7200f036","C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll"
"111","clr.dll","clr.dll + 0x122da","0x720122da","C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll"
"112","clr.dll","clr.dll + 0x1859b","0x7201859b","C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll"
"113","clr.dll","clr.dll + 0x1bb11b","0x721bb11b","C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll"
"114","clr.dll","clr.dll + 0x1bb7fa","0x721bb7fa","C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll"
"115","clr.dll","clr.dll + 0x1bb727","0x721bb727","C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll"
"116","clr.dll","clr.dll + 0x1bb8a8","0x721bb8a8","C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll"
"117","clr.dll","clr.dll + 0x1bb9ce","0x721bb9ce","C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll"
"118","clr.dll","clr.dll + 0x1b7305","0x721b7305","C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll"
"119","mscoreei.dll","mscoreei.dll + 0xfa84","0x7294fa84","C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll"
"120","mscoree.dll","mscoree.dll + 0xe80e","0x74bee80e","C:\Windows\SysWOW64\mscoree.dll"
"121","mscoree.dll","mscoree.dll + 0x143f8","0x74bf43f8","C:\Windows\SysWOW64\mscoree.dll"
"122","ntdll.dll","ntdll.dll + 0x666ed","0x776666ed","C:\Windows\SysWOW64\ntdll.dll"
"123","ntdll.dll","ntdll.dll + 0x666bd","0x776666bd","C:\Windows\SysWOW64\ntdll.dll"

Unfortunately, I don't have a 32-bit Windows at hand, and as the application is x86, Process Explorer cannot resolve symbols.不幸的是，我手头没有 32 位 Windows，而且由于应用程序是 x86，Process Explorer 无法解析符号。

It might be interesting that the stack trace contains "Sfrhook.dll" which is the "Citrix Special Folder Hook DLL".有趣的是，堆栈跟踪包含“Sfrhook.dll”，即“Citrix 特殊文件夹挂钩 DLL”。 I think this DLL implements Special Folder Redirection in Citrix.我认为这个 DLL 在 Citrix 中实现了特殊文件夹重定向。

According to the Windows Error Codes reference, the error code 0xC0000369 means STATUS_INVALID_DEVICE_OBJECT_PARAMETER:根据 Windows 错误代码参考，错误代码 0xC0000369 表示 STATUS_INVALID_DEVICE_OBJECT_PARAMETER：

The device object parameter is either not a valid device object or is not attached to the volume that is specified by the file name.设备对象参数不是有效的设备对象，或者未附加到文件名指定的卷。

I do not understand this - the source and the target of the rename is in the same directory.我不明白这一点 - 重命名的源和目标在同一目录中。

How to further narrow down this problem?如何进一步缩小这个问题的范围？

[EDIT1] The user profile seems to reside in an FSLogix profile container: https://docs.microsoft.com/en-us/fslogix/configure-profile-container-tutorial [EDIT1] 用户配置文件似乎驻留在 FSLogix 配置文件容器中： https ://docs.microsoft.com/en-us/fslogix/configure-profile-container-tutorial

When using Profile Container, both applications and users see the profile as if it's located on the local drive.使用配置文件容器时，应用程序和用户都可以看到配置文件，就像它位于本地驱动器上一样。

[EDIT2] We now have another customer which experiences the same problem. [EDIT2] 我们现在有另一个客户遇到同样的问题。 This time: No Citrix, but "Windows 10 Enterprise multi-session" - also uses FSLogix Profile Containers.这一次：没有 Citrix，而是“Windows 10 Enterprise 多会话” - 也使用 FSLogix 配置文件容器。 https://docs.microsoft.com/en-us/azure/virtual-desktop/windows-10-multisession-faq https://docs.microsoft.com/en-us/azure/virtual-desktop/windows-10-multisession-faq

1 个解决方案

解决方案1
 0  2020-12-08 22:00:25

We have found that in server 2019 it required the UAC virtualization setting needed to be disabled for user level writes.我们发现，在服务器 2019 中，需要为用户级写入禁用 UAC 虚拟化设置。 Using Process Monitor, we found that when the error occurred, it wrote to a UAC event log.使用Process Monitor，我们发现当错误发生时，它写入了一个UAC事件日志。 For legacy applications this issue occurs when the user.config file is being copied from the "user.newcfg" file that is just a temporary file the the .NET code creates.对于遗留应用程序，当从“user.newcfg”文件复制 user.config 文件时会出现此问题，该文件只是 .NET 代码创建的临时文件。

暂无
暂无

声明:本站的技术帖子网页，遵循CC BY-SA 4.0协议，如果您需要转载，请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 无法更新和保存web.config文件 - Unable to update and save web.config file 无法保存Excel文件 - Unable to save Excel file 无法将更改保存到xml文件 - Unable to save changes to xml file 无法将数据保存到数据库 - Unable to save Data into a database 在“保存文件”提示中使用适当的扩展名保存文件 - Save file with appropriate extension in a Save File prompt 将更改保存到C＃中的App.config - Save Changes to App.config in C# 如何将VisualStyleRenderer保存到文件 - How to save a VisualStyleRenderer to a file 将文件保存在特定的文件夹中 - Save file in specific folder 在Winforms中保存文件 - Save File in winforms 保存并打开文件对话框 - Save and Open file Dialogs
相关标签
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM