Aha, excellent stuff and thanks for the pointer. I'm not sure how to go about carrying that fix out, but I guess I can postpone it until the other problem is sorted, one way or the other. I've gone and told Webhost4life not to tell ppl to load sql2k db's straight into 2005 and sent them the link too.

ok, so this evening I installed a fresh DNN 4.37 upgrade package (no modules) to an empty folder and attached a backup db from my main instance to it to see if the db was at fault.

The profiles pages worked fine, so I guess that means it's something in the file system.. bin?... any idea on further ways of tracking this error down are veerrryy much appreciated. I could list all the files in my bin perhaps?

In the meantime I'm going host shopping.... the VPS account I just purchased is unbelievably bad... even the cheapie shared account was better overall.

Rob

I sent PowerDNN a request for information last night. They got back pretty quick with a reply to about half of my questions, but one thing in particular makes them unsuitable. They don't seem to let one run multiple independent sites with independent email off a single DNN instance. You have to run seperate instances for each site, which to me pretty much defeats the purpose. I'm using a DNN portal to reduce my work, not multiply it.

I'm definitely really fed up with Webhost4life, but I just can't find another host that offers a similar VPS package. There's always some important component or other missing.

Regarding my buggy site; I've tried it with different copies of the file system and of course the upgrade to 4.37 also refreshed all the essential system files... but the error remained.

So now I've gone all the way back to a backup from 22 November and that works fine. I'm going to have to go with that copy and just try and restore the differences and forum posts manually for each portal.

Then I'll have to step up the backup and test regime even more. The big problem is there's no way of telling if a module has caused trouble unless it does so visibly and on the pages checked after each module install or upgrade.

I'm also going to be a lot more wary of modules that won't export their content.. it's vital when dealing with application or server problems to be able to save off some content for restoring into a backup.

I'll make sure I post the problem item when I come across it again, as I probably will when I begin reinstalling modules.

Thanks for all the posts.

Rob