Hello. I've noticed that in my Event Viewer, that my Announcements module is throwing an error, although there is seemingly no impact on the site. I was wondering if anyone using 4.9.1 had ever expierienced this, and if so if there are any potential remidies. Included is the error detail of the event log:

ModuleId: 399
ModuleDefId: 110
FriendlyName: In the News
ModuleControlSource: DesktopModules/Announcements/Announcements.ascx
AssemblyVersion: 04.09.01
PortalID: 0
PortalName: Nature's Avenger - Organic Weed Killer, Natural Bed Bug Killer, Natural Bug & Insect Killer
UserID: 1
UserName: NAOHost
ActiveTabID: 37
ActiveTabName: Home
RawURL: /Home/tabid/37/Default.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://naturesavenger.com/Home/tabid/37/Default.aspx
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; Tablet PC 2.0; .NET CLR 3.5.30729; OfficeLiveConnector.1.3; OfficeLivePatch.0.0; .NET CLR 3.0.30618)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 3cca939f-0c5e-4805-b467-09fd612890cd
InnerException: Must specify valid information for parsing in the string.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Enum.Parse
StackTrace:
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Must specify valid information for parsing in the string. ---> System.ArgumentException: Must specify valid information for parsing in the string. at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase) at DotNetNuke.Modules.Announcements.Announcements.get_viewType() at DotNetNuke.Modules.Announcements.Announcements.bindData() at DotNetNuke.Modules.Announcements.Announcements.OnLoad(EventArgs e) --- End of inner exception stack trace ---
Source:
Server Name: DNPWEB2-TX2

Sorry Donny. The issue persists and I haven't had anyone else offer a suggestion. This error happens almost daily.

This is a bug in module announcements. It is still there in version 04.00.03. You can see it if you are logged in view mode and try to press any button wich lead to a postback of the page (example : try to turn in edit mode). If you check "Use Custom Error Messages" in host settings, you won't see this error again. This option traps the error, shows a friendly message, and let the code continue to a response.redirect(), which performs correctly. If it is not checked, the exception is thrown and response.redirect() cannot perform.