I have had my DNN 4.4 portal for a few days now, and its been working fine. I have been installing new modules, enhancing it, and trying out skins.

But alas, I just managed to bust some kind of configuration somewhere while changing a skin. My main portal is now only displaying empty pages without any content at all. Not even the header or footer. I dont know which skin exactly I was changing to, I have a total of 5, where 4 are from Snowcovered and 1 is from Skincovered. They have all worked fine for days so perhaps something went wring while it was being changed?

I am using the PageBlaster 2 caching module, but uninstalling it has not changed anything, so I dont believe that is the problem.

I have a child-portal which is still working, as long as I dont attempt to use that account to change the skin of the portal. If I do, the pages go blank until I log into the child portal again.

Can anyone point me in a direction that solves this issue? Perhaps a file where I can manually configure these settings, or overwrite it with the standard file without loosing the content stored in my database?

My installation is using Windows 2003, MS SQL 2000, newest MDAC, IIS 6, and no other software on the server to interfere with DNN.

brgds

- Jesper

Yes I did remove it from the config file :-) And I uninstalled the PageBlaster module using the host account through the child portal. So the PageBlaster module is all gone. I even double-checked that the binaries are no longer in my DNN directory structure by doing a file search.

I tried restarting IIS. When that didnt work I rebooted the entire server (just to be sure). The problem is still there.

The child portal still works fine, and I can create new child portal without problems.

My next step will be to uninstall all skins and containers except the default ones, and hope that removes the faulty configuration somehow. I'll post the result here. If someone has a better idea, please post it. :-)

brgds

- Jesper