Event Viewer log is flooded with IsolatedStorageException errors

  • 26 January 2016
  • 0 replies
  • 10 views


Symptoms

Numerous errors in Event Viewer logs all of which mention the following exception:

"System.IO.IsolatedStorage.IsolatedStorageException"

Diagnoses

Full sample error message:

Exception on YYYY-MM-DDTHH:MM

 

Addtional: FileUtility.PurgeIsolatedStore: = %STORE%
Exception: System.IO.IsolatedStorage.IsolatedStorageException: Unable to delete, directory not empty or does not exist.
at System.IO.IsolatedStorage.IsolatedStorageFile.DeleteDirectory(String dir)
at SourceCode.Forms.AppFramework.FileUtility.PurgeIsolatedFiles(TimeSpan purgeAge)

WindowsIdentity.GetCurrent(): IIdentity(Name=DOMAINUser, AuthenticationType=Kerberos, IsAuthenticated=True, Type=System.Security.Principal.WindowsIdentity)
WindowsIdentity(.ImpersonationLevel=None)
WindowsIdentity.Token(.Level=-1) ClaimsIdentity(Name=DOMAINUser, Label=, NameClaimType=http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name, RoleClaimType=http://schemas.microsoft.com/ws/2008/06/identity/claims/groupsid
[http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name] = [DOMAINUser]
[http://schemas.microsoft.com/ws/2008/06/identity/claims/primarysid] = [S-1-5-21-4214580827-704355652-3576521324-2619]
[http://schemas.microsoft.com/ws/2008/06/identity/claims/primarygroupsid] = [S-1-5-21-4214580827-704355652-3576521324-513]
[http://schemas.microsoft.com/ws/2008/06/identity/claims/groupsid] = [S-1-5-21-4214580827-704355652-3576521324-513]
[http://schemas.microsoft.com/ws/2008/06/identity/claims/groupsid] = [S-1-1-0]
[http://schemas.microsoft.com/ws/2008/06/identity/claims/groupsid] = [S-1-5-32-544]
[http://schemas.microsoft.com/ws/2008/06/identity/claims/groupsid] = [S-1-5-32-568]
[http://schemas.microsoft.com/ws/2008/06/identity/claims/groupsid] = [S-1-5-32-559]
[http://schemas.microsoft.com/ws/2008/06/identity/claims/groupsid] = [S-1-5-32-545]
[http://schemas.microsoft.com/ws/2008/06/identity/claims/groupsid] = [S-1-5-3]
[http://schemas.microsoft.com/ws/2008/06/identity/claims/groupsid] = [S-1-2-1]
[http://schemas.microsoft.com/ws/2008/06/identity/claims/groupsid] = [S-1-5-11]
[http://schemas.microsoft.com/ws/2008/06/identity/claims/groupsid] = [S-1-5-15]
[http://schemas.microsoft.com/ws/2008/06/identity/claims/groupsid] = [S-1-2-0]
[http://schemas.microsoft.com/ws/2008/06/identity/claims/groupsid] = [S-1-5-82-3018530703-221508303-1617001795-1521473063-2240421750]

Thread.CurrentPrincipal: IPrincipal(Type=System.Security.Principal.WindowsPrincipal) IIdentity(Name=Safe handle has been closed, AuthenticationType=NTLM, IsAuthenticated=True, Type=System.Security.Principal.WindowsIdentity)
WindowsIdentity(.ImpersonationLevel=FAILED System.ObjectDisposedException: Safe handle has been closed
at System.Runtime.InteropServices.SafeHandle.DangerousAddRef(Booleanand success)
at Microsoft.Win32.Win32Native.GetTokenInformation(SafeTokenHandle TokenHandle, UInt32 TokenInformationClass, SafeLocalAllocHandle TokenInformation, UInt32 TokenInformationLength, UInt32and ReturnLength)
at System.Security.Principal.WindowsIdentity.GetTokenInformation(SafeTokenHandle tokenHandle, TokenInformationClass tokenInformationClass)
at System.Security.Principal.WindowsIdentity.GetTokenInformation(TokenInformationClass tokenInformationClass)
at System.Security.Principal.WindowsIdentity.get_ImpersonationLevel()
at SourceCode.Forms.AppFramework.Logging.LogIdentity(StringBuilder builder, IIdentity identity)
at SourceCode.Forms.AppFramework.Logging.LogPrincipal(StringBuilder builder, IPrincipal principal)
at SourceCode.Forms.AppFramework.Logging.LogException(Exception exception, String additional, Boolean asWarning, Boolean generateStackTrace)
HttpContext.Current.User:

StackTrace: at SourceCode.Forms.AppFramework.FileUtility.PurgeIsolatedFiles(TimeSpan purgeAge)
at SourceCode.Forms.AppFramework.FileUtility.OnPurgeFiles(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireNextTimers()

 

Resolution

This is known issue in K2 4.6.11 (internal ID 604534) with coldfix available upon request from K2 support. This issue is resolved in 4.7 release. Fix for this issue included in K2 SF rollup 4611.9 or newer.


0 replies

Be the first to reply!

Reply