I've noticed my server's CPU is periodically getting pinned, and after a 24 hour perfmon run, I've narrowed the problem down to DNN. I checked the history logs for each of my scheduled jobs (first time in months I've done that...) and found that the File Synchronization job has been bombing for quite some time. The stack trace that it pukes up is:
File System Synchronization failed. System.NullReferenceException: Object reference not set to an instance of an object.
at DotNetNuke.Services.Localization.Localization.GetString(String name)
at DotNetNuke.Common.Utilities.FileSystemUtils.UpdateFile(String strSourceFile, String strDestFile, Int32 PortalId, String HomeDirectory, Boolean isCopy, Boolean isNew, Boolean ClearCache)
at DotNetNuke.Common.Utilities.FileSystemUtils.SynchronizeFolder(Int32 PortalId, Int32 AdministratorRoleId, String HomeDirectory, String physicalPath, String relativePath)
at DotNetNuke.Common.Utilities.FileSystemUtils.SynchronizeFolder(Int32 PortalId, Int32 AdministratorRoleId, String HomeDirectory, String physicalPath, String relativePath)
at DotNetNuke.Common.Utilities.FileSystemUtils.SynchronizeFolder(Int32 PortalId, Int32 AdministratorRoleId, String HomeDirectory, String physicalPath, String relativePath)
at DotNetNuke.Services.FileSystem.SynchronizeFileSystem.Synchronize()
at DotNetNuke.Services.FileSystem.SynchronizeFileSystem.DoWork()
Can anyone shed some light on debugging the scheduled file synch job? I'm in a bit over my head...
Marc