I know it doesn't sound like this post belongs here, but I have a reference to the localization module in a stack trace, so I thought I'd post it here.  I'm getting a failure of my file system synchronization scheduled job.  Here's the trace:

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()

Notice towards the top it talks about the Localization.GetString() function.  Has anyone else here had trouble with this?

Thanks in advance...

Marc

It's the default job.

*bump*

I was browsing through the bug/issue database for DNN, and I noticed there were a number of localization issues addressed in the upcoming release (3.3 I think).  I hope that we get to see this release sooner than later.  Perhaps this thing that Maury and I have encountered has already been addressed?

One can always hope...

Marc