Greetings all, I hope someone may provide some light on this annoying problem we are having.

We recently upgraded our DNN 4.8.1 site (4.8.1 > 4.8.2 > 4.9.1) to 4.9.1.  Upgrade went without problems and life was great until we tried to add a child portal (which worked until the 4.9.1 upgrade).

When we try to create a child portal, we get an unhelpful "Error: Unable to create child portal" message on the portal creations screen.  Nothing shows up in the logs (DNN or system logs) that gives us any information.

We run on Windows Server 2003, SQL 2005, IIS 6.  Permissions are set correctly.  Network Service has full control over DNN directory.  We've even reapplied the permissions thinking this might be the problem.  Still unable to create child portals.

Thanks for any help, suggestions, ideas....we are at  total loss here!

I would check to see that permissions are set correctly. Can you create a parent portal?

Unable to create parent portal either.  We get the same "Error creating portal" message with no log data to be found.

Permissions are set properly on the root folder and all child folders.  We have reapplied the permissions as well (several times) with no success.

Network Service has full control.

I haven't run into this.

You might want to start by making a backup of your database, truncating the event log table, and freeing up space in the database. I suggest this only because most of the new stuff is added in the database.

You should also look at the Portals directory in your web directory. Are new directories being created? It's possible that there are some directories there that might need to be removed.

I'd suggest asking for assistance at the DotNetNuke forums, too. And, please let us know how/if this is resolved. If you don't get any help there, please ask again.

Did you find a solution? Could this possibly be a prob. with dnn 4.9.1? If you have a backup it might be worth upgrading to 4.9 on a localhost test area and see if it has the same problem

Hi Lee,

Cathal Connolly has been providing assistance.  So far, it is not a permissions error as I can create files via the Host > Files interface.  I can add and delete module (Module Definitions) to my heart's content.  My users can add data to their sites, create new pages and so forth.  Still working on this and hopefully it will be fixed soon! 

As a quasi-backup, every time I upgrade my DNN installation, I create a new folder labeled with whatever version of DNN I am upgrading to and "point" IIS to that new directory as the home directory.  I use a virtual server for my DNN database and make snapshots of the virtual server before doing any upgrades as well. 

I can regress to earlier versions of both but my faculty will kill me if the files they have added to their sites since the upgrade disappear.  Haven't figured out how to move child portal data between installations yet.

>Cathal Connolly has been providing assistance

You aren't going to do much better!  Please let us know the problem and how it was fixed.

I agree about Cathal's assistance.  I could not ask for better!

I will be happy to let everyone know what the problem was and how it was fixed.  Knowledge is power.

Cheers,
Ezara