Dave,

This question really relates to a much larger issue than what you presnt.  Now, to be fair, in your post you give the DNN version info, but don't really give the module's version.  Unfortunately, the latest version could mean different versions depending on the moment in time someone views this post.

The short answer here is that there is no standard API RSS news generator required of the DNN project module developers.  Some DNN projects use the internal methods, while others have gone their own way with syndicating content.  Further, there is no guarantee that the methods use pass validation for the syndication spec that the module uses.  See my blog for my rant on the subject.

Still, if you can provide the versions for the modules you are using, I'll take a deeper look into the issue for you.  Most of these are due to the strict compliance requirements that came with the new RSS Newsfeeds (RSS) module, which requires valid RSS v2.0 elements.  Some of this compliance was lifted in the newer v4.0.1 version, but there are some RSS v2.0 specs that still require strict compliance from incoming news sources providers, even from internal DNN syndication.

Cheers

Dave,

I could not reproduce the error on my test XP Pro DNN v04.06.02 site.  The closest I could come to getting an error was using the News Feeds(RSS) v04.00.00, which gave me errors due to the invalid date format being used in the newest version of the DNN Forums module v.04.04.03.  The Forums module uses it's own syndication method to generate news feed, and though it says it's RSSv2.0, the actual feed does not follow RSSv2.0 formatting for a number of elements that include dates and emails. It's the issue I talked about in my blog.

Now, I'm not sure where exactly you are getting the error from because when I use the v04.00.01 version of the News module, it actually displays the feed generated from the Forums module.

As, an alternative, you could try using the XML/XSL module to display the news feed, but you will need a custom xsl to do it.  If you need help with that part, just let me know.

There may be something that is causing the error due to a different configuration setup you are using.  My test XP Pro box would not be able to duplicate everything a site may encounter when it's publicly hosted.