Default DNN Portal install works very well. But, when I try to create a Parent or Child (eg, www.domain.com/portal ) I get this error.

"An Error Was Encountered During The Creation Of Your Portal. This May Have Been Caused By Specifying An Incorrect Password For An Existing User Account. Please Verify Your Details Before You Try Again."

I have tried creating unique new users (with valid pwds) in addition to trying admin and host logins. I left the "Home Directory" field untouched with the grayed out default. No joy.

I run my own web server (IIS 5 with MSDE). Permissions seem to be proper. This is a live site and I created a Portal subfolder (maybe I shouldn't have?)

I saw a similar (but not exact) problem posted yesterday
http://forums.asp.net/912129/ShowPost.aspx
There were no final solutions?

Should I upgrade to 3.1.0 or would that make it worse?
Thanx,
John

 

You do not need to create the sub-folder for the child portal, DNN does that for you (that is why the ASPNet user has to have List/Read/Execute/Write/modify permissions on the root) .  It might be failing becuase the folder already exists, but it is just not reporting the correct error.

As far as upgrading is concerned, it never hurts to update.  3.1.0 contains quite a few bug fixes.

Smehaffie, thanx very much for your prompt reply! I did do a fresh clean install of 3.1.0 (new database also). However, neither parent or child portals install as I understand the documentation. I can see where the Portal \0, \1 , \2 etc, folders are being created and in fact I can see the sample pix and .css in the folders (using the Club template). But, the portal folder is NOT created in the actual web ( www.website.com/portal ) where I would expect. It's my own web server machine and I have double checked all the ASPNet user etc. and everthing seems to check out, permission-wise.

I will keep working on this and maybe I'll trip over something or clarify a better question, but wanted to say thanx for the attempt.
john

Please post any additional information you find, and I will help in any way I can.  A couple of questions.

1) After install 3.1, so you still get an error when creating a new child portal?

2) Are you only having problems creating child portals?

3) DNN is installed to the www.website.com/portal directory, correct?  Or is DNN stored at the root of www.website.com/portal  and you are trying to create the portal as a child?  

Server environment: W2000 server with MSDE.
This is my own machine and I have a single IP address with about 20 virtual domains.
These virtual domains are resolved by a third party running DNS for me.
All websites are running smoothly.

In my attempt to create parent/child portals and based on smehaffie's comments, I decided to go back to square one and start over with fresh database and a clean install of DNN 3.1.0. Since I have a "live" website that I use for testing, I cleared it out and copied the DNN files into that empty folder (making sure ASPNet account modify/read/write permissions, etc. were retained)

However it dawned on me that I wasn't sure what to put in the connection string "Server=xxxx" section of the web.config. I left it as Server=(local);  Maybe this is my problem? I have included the following error.
Thank you for any assistance.
john

---

Server Error in '/' Application.

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: ?

Source Error:

Line 256: <add assembly="System.EnterpriseServices, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/> Line 257: <add assembly="System.Web.Mobile, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"/> Line 258: <add assembly="*"/> Line 259: </assemblies> Line 260:

Source File: c:\winnt\microsoft.net\framework\v1.1.4322\Config\machine.config    Line: 258

Assembly Load Trace: The following information can be helpful to determine why the assembly 'DotNetNuke.Caching.BroadcastPollingCachingProvider' could not be loaded.

=== Pre-bind state information === LOG: DisplayName = DotNetNuke.Caching.BroadcastPollingCachingProvider (Partial) LOG: Appbase = file:///C:/web/sites/robotipster LOG: Initial PrivatePath = bin Calling assembly : (Unknown). === LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind). LOG: Post-policy reference: DotNetNuke.Caching.BroadcastPollingCachingProvider LOG: Attempting download of new URL file:///C:/WINNT/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/root/958994c5/dc8c9da/DotNetNuke.Caching.BroadcastPollingCachingProvider.DLL. LOG: Attempting download of new URL file:///C:/WINNT/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/root/958994c5/dc8c9da/DotNetNuke.Caching.BroadcastPollingCachingProvider/DotNetNuke.Caching.BroadcastPollingCachingProvider.DLL. LOG: Attempting download of new URL file:///C:/web/sites/robotipster/bin/DotNetNuke.Caching.BroadcastPollingCachingProvider.DLL. LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind). LOG

I'm having the exact same problem with creating new portals (child or parent).  This started happening to me when I upgraded to 3.0.13 and is still happening after I upgraded to 3.1.0.  I figured that 3.1.0 had many fixes and that hopefully it would fix the problem.  Unfortunately it didn't.

I consider myself a pretty advanced user and can guarantee that the generic message that shows up (about the account details) is not because I'm trying to add a user that already exists.  I've checked the database directly and can guarantee that.  Unlike one of the other posters here, I am not seeing any directories created at all when the error occurs.

Here's a little background:

• I have 7 portals total with my installation (4 parent, 3 child)
• I have been running this setup for a while (back since v2.x, upgrading with each release)
• I've never had any problems like this until I moved to v3.0.13

I've tried to hit the log viewer right after each portal creation fails but either A) don't see anything related to this specific action or B) the log viewer just times out and does not let me view it.  B) is another problem all together, which I've posted on the forums about in the past.  Somebody suggested I clear out the log files becaues they may be too large for the log viewer to return.  I've done that and still get a timeout when I try to open the log viewer every 4 out of 5 times.

Anyway, I've posted a few times on the main forum about this portal creation problem too and haven't gotten any help towards solving it yet.  Hopefully this time can be different.  I'd be happy to provide any additional information that I can if you tell me what you'd need to help resolve the problem.

Thanks!