Reinstalling isn't likely to help.

What I would do is to configure a feed from another source, making sure it's another domain. If you get the same problem, that would indicate that the problem is on your end. If that's the case, you'll want to look at your hosting and make sure that it is configured correctly.

You're right... reinstalling did nothing but it was worth a shot.

I've tried other news feed sources. In fact, I tried all the ones that work on my other DNN installations (all with the same hosting provider) but get the same error.

The provider is GoDaddy. I have 11 sites hosted with them, all have the same type of hosting plan. About half of them have news feeds. This is the only time I've run into this problem.

I'll contact them.

AH! A new error message:

News Feed Is Not Available At This Time. Error message:Request for the permission of type 'System.Net.WebPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.

Does this have any bearing with DNN?

Got a reply from GoDaddy. I've generally found that when I ask to 'escalate' a support question to the next level, they'll do it particularly when it involves DNN.

There's nothing wrong on their end, which is what I expected since I have other DNN installations with them that aren't having this problem.

One other thing I'm going to try. This particular site is one that I had taken offline for reasons I won't state here. It is now a live test site for me. When I uninstalled the original DNN installation, I noticed that not all of the directories were removed. I'm going to uninstall again and then go in via FTP, delete the leftovers, and try again.

The reinstallation created another problem (off topic) but I have enough other DNN installations to determine this:
This problem only occurs in my DNN 4.5.1 or 4.5.3 installations. The older ones that are 4.4.1 do not have this problem. I've submitted this at the DNN forum. We'll see.

I'm really in a bind. So pardon me if I border on ranting. It's not directed at anyone here.

I'm not the only one having this effing problem. Here's a link to my post at DNN:
http://www.dotnetnuke.com/tabid/795...fault.aspx

I tried what the other poster tried: putting the news feed URL in an I-frame module. I can see the feed but my formatting options are literally nil. Using I-frame is not an option. This also tells me that my hosting provider is not the problem, particularly since I can see the news feed in I-frame (in my 4.5.x installations) and that the news feed module is working fine in my 4.4.1 installations.

It is extremely aggravating to go to the DNN site with a valid issue just to be ignored. It's not the first time it's happened to me and it's not the first time I've cruised through their forum and seen other people left hanging in the wind.

That's why I come here. At least Lee & Joe will acknowledge when a post has been made even if they don't have an immediate answer. (Thanks guys. I really do appreciate that).

So can anyone offer any enlightenment or at least some moral support [laugh] for the error message I posted 05 Aug 2007 2:12 AM?

Hello,

I've just run a test of the news feed module using an RSS feed from DNN Creative with DotNetNuke version 4.5 .5 and this version works okay. I would suggest testing in the latest version as they fixed quite a few bugs over the earlier point releases.

Hope that helps.

Thanks,

I'm experiencing the same problem with DNN 4.5.5. If I point the Newsfeed module at an internal Announcements module I get the error. If I point the same Newsfeed at another site's Announcement module (running DNN 4.5.1) it works OK. ???

Thanks Lee for your your response (nad yours, too, Joe).

J.strugnell,

Who is your hosting provider?  I won't get into a lengthy post but despite what I sad before about my hosting provider, my dillema is beginning to point back to them.

More later.

We are a hosting provider, we design, develop, host etc. It turns out that the url I use to access the site (currently hosted on a development server) is inaccessible from its own server. Not sure why yet but that's the reason for my error. So at this point I'm 99% confident this isn't DNN error. The feed I got working was from a live site on a different server.