I assume that if you choose a portal name like xyz987 you get the same error?

It might be worthwhile to look around in your Portals directory to see what is there. This might also happen if you don't have write permission in that directory.

I am currently getting this error whenever I create a child portal. I have amended the message so that is actually displays the pathanme it is checking, so I get an error like this:

The Child Portal Name You Specified Already Exists. Please Choose A Different Child Portal Name.
Portal Name = \\Richtest\aaa8

The child portal creation takes an absolute age to complete, but what I do know is that this folder is created almost immediately as are the portal table entry, the userid entry and the new tabs.

What does sometime happen is that the PortalAlias is not created.


So my question is why is DNN reporting that the child portal already exists when it created this folder successfully when it first started the child protal creation?????

 

Can you create a child portal with another name?   Or is this a case of not being able to create any child portal?

Which version of DotNetNuke are you using?

Can you create a child portal with another name?   Or is this a case of not being able to create any child portal?

Which version of DotNetNuke are you using?

Hi,

I am using 4.9.0 and it doesn't matter what I call the child portal, the same thing happens every time

If there are other errors related to the database, I would start by looking there.  This could be something as simple as a timeout.

First, is an error posted to the event log?  If so, please post it here.

Second, look into doing some maintenance on your database.

• Back it up first
• TRUNCATE the event log and the site log
• Clear out the site log (ou can do this easily as part of a full backup process with SQL Management Studio, and you should be doing regularly scheduled backups frequently.)

With your fairly large number of users, you might want to tune-up your database.  Hal Hayes has several blog posts related to DotNetNuke and database issues here.

1. There are no errors reported in the logs
2. I have been through the process of truncating logs etc and it has made no difference.
3. We are running on an industrial strenght SQL server with over 7gb of memory and the db's are all finely tuned. I have had my DBA run performance monitoring during the portal creation process and he is very happy that the SQL Server can cope with the workload easily.
4. The issue I firmly believe is connected to the SQL Server process. I had my DBA also run a SQL Server trace and it created 1,000's and 1,000's of lines. Being so large it is difficult to interogate, but it would appear to be doing something with every child portal on the site??????

Can anyone tell me where the code is that is run when creating a child portal? I have downloaded the DNN Source code, but I haven't been able to trace the exact code that is executed.

Thanks in advance for your help.
Rcih.

Since you have other issues with installing modules, etc. I believe that you are correct that it's a SQL server process.  I'm afraid that I don't know enough about the code to point you in the right direction on that one.

If you want to contact me privately (jncraig at yahoo dot com) I can put you in touch with some people who might be able to help.

A quick update on my situation.

I still have BIG problems creating Child portals, installing new modules and updating host settings.

After much debugging using the full DNN Source code, the problem appears to be with the removal of cache that is performed when creating a child portal (I expect the same process is run when installing a new module?).

This process goes through every single module on every single tab within every single portal.

So as we have over 200 child portals, all with at least 10 pages and most having numerous modules you can understand that this takes a very long time and this is what results in us experiencing timeouts.

This is what is causing our probelm.

However over on the main DNN forum I have a thread running () and on here Mitch Sellers (he of the DNN module programming book fame - I would certainly recommend this book!) states that he has one client who has over 1,600 child portals!

Has anyone else got close to 200 child portals?
Have you experienced these timeout issues?

We haven't discussed your hardware configuration, or your server software.

What servers are you using?  Memory, processor speed, etc.

Are SQL Server and web server on different machines?  Which versions of these are you using?

Any other details?


Also, how many users?

You might want to look here for information on tuning your database.

We host the site here at work on industrial size server (they have about 7gb of memory to give you an idea of their config).

We are using SQL Server 2005 and it is on a different server to the web server. I don;t know off the top of my head which OS we are using on the servers.

Our DBA's have carried out loads of analysis on the server and DB are they are very happy with everything so I don't believe tuning is necessary.

User database is about 20,000 although the majority of these (~16,000) are for a single company and most of them (~90%) will be dormant

My recollection is that the link that I sent you discusses rebuilding indexes after adding large number of users.  I don't recall the specifics, but it won't hurt to check it out.

Can you tell if the slowdown is related to the DB, to the load on the DB server, or somewhere else?

I don't think the problem is caused by a DB problem.

I think it is the fact that DNN attempts to clear down cache and the fact that this takes SO long to do because of the number of child portals. This causes a timeout. Whether it is a DB timeout I don't know

Have you tried asking about this on the DotNetNuke forums?  There are some people there who understand the inner workings and performance-related issues much better than I do.

Yes I have posted several threads on the DNN forum but to no avail unfortunately.

We have even taken out a support contract with PowerDNN in the hope that they would be able to help us, but so far no luck.

I just can't understand how other DNN users don't have this issue. We can't be the only DNN users who have 100+ child portals within one installation??

Hello,

I can't offer any advice on the problem, but I recall meeting people at the DNN conferences who were running several hundred portals on one install without problems. Hopefully powerdnn will be able to look through your account and work it out.

thanks,