I was going to ask ... but didnt want to push it.. ;)

Gemini 884 and / or 891 might give the code but not sure if that is another bug related or the fix itself ...

so .. I'd like the fix too if possible .. thanks...

(also the templates were changed too from what I hear ...)

I'm getting a child portal error. I have a portal that was originally created with DNN 3.0.9. It has since been upgraded to 3.0.11. There were two child portals (all portals created with built in Club/Oragnization template) which were deleted, leaving the portal with no child portals. In attempting to create a new child portal, the following error occurs:

Error: Signup is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Services.Log.EventLog.EventLogController.AddLog(Object objCBO, PortalSettings _PortalSettings, Int32 UserID, String UserName, EventLogType objLogType) at DotNetNuke.Modules.Admin.PortalManagement.Signup.cmdUpdate_Click(Object sender, EventArgs e) --- End of inner exception stack trace ---

make sure you are not using a userid that you used previously .. that issue should be fixed in .12

When you say userid, are you referring to the SQL userid that is in the web.config file? If so, changing that still gives the same error.

no... your child portal admin id and password .... must be unique .. never ever used before in any 3.x child portal or user in general...


(if you changed your web.config ... how did anything work unless you changed the db too.. oh well...forget that)

Trying to catch up here, work has been keeping me from the forums.

>> I dont think Dave above got key 478 error..

I think it was a different key id then 478, but the rest of the error message fit the origional one posted above.

I am looking through some backups to see if I still have these templates around as I don't see them currently where I copied them, so I must have wiped them out. I guess I figured
its been reported, Ill try a couple ideas next release. e.g. export .11 then upgrade .11 to .12 & export to a different template. then fresh install test time.

Hopefully I made a backup close to then though as it may have been in between.
I will dig through these tonight and report back.

Cheers,
Dave

I don't have the .10 templates laying around so I exported a .11 one and started importing and debuging a fresh install with the modules installed that are not core ones.

Ok, I did some more digging and here is what I can tell you so far.
1) the module it complains about has 2 view controls that are added to the page from one definition in the admin dropdown. This module uses IMC to talk back and forth and update displays based on this. When it bombs here and I go to the page this module is on, both views are there along with the content.

I can't get to far debuging without the page timing out, and ideas here?

I did trace this down to around line 1350...

If Not IsInstance Then


                                                'Add new module


                                                intModuleId = objModules.AddModule(objModule)


                                                If templateModuleID > 0 Then


                                                    hModules.Add(templateModuleID, intModuleId)


                                                End If


                                            Else

If I add a try catch block around hModules.Add, the wizard finishes, but the page also has 2 copies of the module now, so 4 controls in all. and this is logged...

AssemblyVersion: 03.00.11
Method: System.Collections.Hashtable.Insert
FileName:
FileLineNumber: 0
FileColumnNumber: 0
PortalID: 0
PortalName: DNN30
UserID: 1
UserName: host
ActiveTabID: 51
ActiveTabName: Site Wizard
AbsoluteURL: /Dnn30/Default.aspx
AbsoluteURLReferrer: http://localhost/DNN30/Admin/SiteWizard/tabid/51/Default.aspx
ExceptionGUID: dc2b38af-6d68-48bd-b01a-43155251c97a
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
InnerException: Item has already been added. Key in dictionary: "434" Key being added: "434"
Message: Item has already been added. Key in dictionary: "434" Key being added: "434"
StackTrace: at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add) at System.Collections.Hashtable.Add(Object key, Object value) at DotNetNuke.Entities.Portals.PortalController.ParsePanes(XmlNode nodePanes, Int32 PortalId, Int32 TabId, PortalTemplateModuleAction mergeTabs, Hashtable hModules) in C:\Inetpub\wwwroot\DotNetNuke\components\Portal\PortalController.vb:line 1354
Source: mscorlib
Server Name: BAMF


My exception is a bit different, but simular, so I will add that also...


[ArgumentException: Item has already been added. Key in dictionary: "433" Key being added: "433"]
System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add) +955
System.Collections.Hashtable.Add(Object key, Object value) +11
DotNetNuke.Entities.Portals.PortalController.ParsePanes(XmlNode nodePanes, Int32 PortalId, Int32 TabId, PortalTemplateModuleAction mergeTabs, Hashtable hModules) +1548
DotNetNuke.Entities.Portals.PortalController.ParseTab(XmlNode nodeTab, Int32 PortalId, Boolean IsAdminTemplate, PortalTemplateModuleAction mergeTabs, Hashtable hModules) +1461
DotNetNuke.Entities.Portals.PortalController.ParseTabs(XmlNode nodeTabs, Int32 PortalId, Boolean IsAdminTemplate, PortalTemplateModuleAction mergeTabs) +132
DotNetNuke.Entities.Portals.PortalController.ParseTemplate(Int32 PortalId, String TemplatePath, String TemplateFile, Int32 AdministratorId, PortalTemplateModuleAction mergeTabs) +1141
DotNetNuke.Modules.Admin.PortalManagement.SiteWizard.Page_FinishWizard(Object sender, WizardEventArgs we) +228
DotNetNuke.Services.Wizards.Wizard.OnFinishWizard(WizardEventArgs e) +26
DotNetNuke.Services.Wizards.Wizard.Finish(Object sender, CommandEventArgs e) +52
System.Web.UI.WebControls.LinkButton.OnCommand(CommandEventArgs e) +110
System.Web.UI.WebControls.LinkButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +115
System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +18
System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +138
System.Web.UI.Page.ProcessRequestMain() +1292

[PageLoadException: Item has already been added. Key in dictionary: "433" Key being added: "433"]
DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) +346
DotNetNuke.Framework.PageBase.Page_Error(Object Source, EventArgs e) +363
System.Web.UI.TemplateControl.OnError(EventArgs e) +109
System.Web.UI.Page.HandleError(Exception e) +68
System.Web.UI.Page.ProcessRequestMain() +2100
System.Web.UI.Page.ProcessRequest() +218
System.Web.UI.Page.ProcessRequest(HttpContext context) +18
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() +179
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +87


HTH's,
Dave

It looks like it has been a while since anyone posted on this subject, but I am getting the same error using 3.1

I export a new portal template with the new blog module included in it, and then when I try to create a new parent portal I get the following error :

Error: Signup is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Item has already been added. Key in dictionary: "367" Key being added: "367" ---> System.ArgumentException: Item has already been added. Key in dictionary: "367" Key being added: "367" at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add) at System.Collections.Hashtable.Add(Object key, Object value) at DotNetNuke.Entities.Portals.PortalController.ParsePanes(XmlNode nodePanes, Int32 PortalId, Int32 TabId, PortalTemplateModuleAction mergeTabs, Hashtable hModules) at DotNetNuke.Entities.Portals.PortalController.ParseTab(XmlNode nodeTab, Int32 PortalId, Boolean IsAdminTemplate, PortalTemplateModuleAction mergeTabs, Hashtable& hModules, Hashtable& hTabs, Boolean IsNewPortal) at DotNetNuke.Entities.Portals.PortalController.ParseTabs(XmlNode nodeTabs, Int32 PortalId, Boolean IsAdminTemplate, PortalTemplateModuleAction mergeTabs, Boolean IsNewPortal) at DotNetNuke.Entities.Portals.PortalController.ParseTemplate(Int32 PortalId, String TemplatePath, String TemplateFile, Int32 AdministratorId, PortalTemplateModuleAction mergeTabs, Boolean IsNewPortal) at DotNetNuke.Entities.Portals.PortalController.CreatePortal(String PortalName, String FirstName, String LastName, String Username, String Password, String Email, String Description, String KeyWords, String TemplatePath, String TemplateFile, String HomeDirectory, String PortalAlias, String ServerPath, String ChildPath, Boolean IsChildPortal) at DotNetNuke.Modules.Admin.PortalManagement.Signup.cmdUpdate_Click(Object sender, EventArgs e) --- End of inner exception stack trace ---

brian_c wrote:

grrrrr. The Host Settings are set to Host PhpDupe. The Site Settings have all skins/containers set to Host and all to DNN Blue. That is almost another bug to me. How can Site Settings indicate Host skins/containers that are different than Host Settings.

The host / site radion button just tells the program whether you want a list of shared skins (host) or non-shared skins (site).  In the Host setting you are setting up the skins that will be used by default for any new sites created.  You can then go into site settings and set the site up to use a different skin if you want.

Bump...

I'm currently working with 3.1.1 and getting this error trying to create a new child portal via a template created from the parent in this installation.  I have also tried using a new username and an existing known username to eliminate this as a possibility as mentioned earlier in the thread.  Has anyone been able to resolve this issue short of a new install?

Thanks!

Error: Signup is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Item has already been added. Key in dictionary: "495" Key being added: "495" ---> System.ArgumentException: Item has already been added. Key in dictionary: "495" Key being added: "495" at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add) at System.Collections.Hashtable.Add(Object key, Object value) at DotNetNuke.Entities.Portals.PortalController.ParsePanes(XmlNode nodePanes, Int32 PortalId, Int32 TabId, PortalTemplateModuleAction mergeTabs, Hashtable hModules) at DotNetNuke.Entities.Portals.PortalController.ParseTab(XmlNode nodeTab, Int32 PortalId, Boolean IsAdminTemplate, PortalTemplateModuleAction mergeTabs, Hashtable& hModules, Hashtable& hTabs, Boolean IsNewPortal) at DotNetNuke.Entities.Portals.PortalController.ParseTabs(XmlNode nodeTabs, Int32 PortalId, Boolean IsAdminTemplate, PortalTemplateModuleAction mergeTabs, Boolean IsNewPortal) at DotNetNuke.Entities.Portals.PortalController.ParseTemplate(Int32 PortalId, String TemplatePath, String TemplateFile, Int32 AdministratorId, PortalTemplateModuleAction mergeTabs, Boolean IsNewPortal) at DotNetNuke.Entities.Portals.PortalController.CreatePortal(String PortalName, String FirstName, String LastName, String Username, String Password, String Email, String Description, String KeyWords, String TemplatePath, String TemplateFile, String HomeDirectory, String PortalAlias, String ServerPath, String ChildPath, Boolean IsChildPortal) at DotNetNuke.Modules.Admin.PortalManagement.Signup.cmdUpdate_Click(Object sender, EventArgs e) --- End of inner exception stack trace ---

I think this issue is that whatever key that module is .. it has multiple definitions.   DNN portal creation from a template cannot handle modules with multiple definitions.

Can you check and see if that is your issue.

I came to this thread after having a similar problem while creating a new child portal using a template I created (export it from a current site). I got the same error but with a key = 12548

While reading the thread I understood that its a module ID.

I looked inside the created template file and found out that the module is UltraPhotoGallery. I removed it from the original site, created the template again and now I can produce new child portals using this template :

http://www.dotnetnuke-portal.com/ClubSite

Hope it helps

liorlustig,

You're right.  I got the same error but with key = 395.  This was the ID for the View_Blog module.  I deleted this and created another portal, but got error with key = 396.  I deleted the Blog_List (ID = 396), New_Blog (ID = 397), Search_Blog (ID = 398) and Blog_Archive (ID = 399) modules.  Now, I can create portals using this template.

brian_c wrote:

tried a new one .. exact same error ... now I have two portals which both created subdirs on the root, subdirs under Portals and show up under Portals. If I try to edit the portal to delete it ... upon clicking edit.. the details including delete option are not visible .. just Error: Site Settings is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Modules.Admin.PortalManagement.SiteSettings.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---

brian_c or anybody else,

I have the same problem.  I created portals using an exported template which created errors (caused by certain module IDs and not by duplicate usernames).  Now I have these portals that I cannot delete.  Have you figured out how to delete them?

Good Question
I have some portals I can't delete as well. (Not sure if from the same reason).