Hi 67RSSS,

This issue was supposed to have been corrected in 4.8.2.  What version are you experiencing this problem on?  You can read more about the work item here: http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=6862&PROJID=2

That said, I seem to recall some others who are continuing to experience this error.  However, I do not recall if this was before or after 4.8.2 was released, so it's very possible that the fix mentioned above fully resolved the issue.

Brandon

I'm very pleased with the 4.8 release.  Remember that for every person that has a problem, there are many out there that do not.  That said, I can fully understand your apprehension!

I know that I saw a manual fix floating around somewhere in the forums.  I do not recall if it required a core recompile or not, nor do I have a link to the thread.  But you might be able to find it by poking around.

Whichever route you go, good luck!

Brandon