My dnn installs have been subjected to registration attacks. From time to time I also see items such as this which I believe to reflect some type of attack. it does not seem to coincide with any active users actions

I. I am trying to understand the error below.
2. I am looking for a best practices guide to lock down the security on my server

I manage my own 2008 server. (virtual server)

any insights to this would be helpful





AbsoluteURL:/Default.aspx
DefaultDataProviderotNetNuke.Data.SqlDataProvider, DotNetNuke
ExceptionGUID:64730345-cd16-414c-8579-c973be705403
AssemblyVersion:
PortalId:-1
UserId:-1
TabId:-1
RawUrl:
Referrer:
UserAgent:
ExceptionHash:Qfza10Bj8rfGsXz7PECmyg==
Message:Unhandled Error Adding Module to contentPane
StackTrace:
at DotNetNuke.UI.Skins.Pane.InjectModule(ModuleInfo module)
at DotNetNuke.UI.Skins.Skin.InjectModule(Pane pane, ModuleInfo module)
InnerMessage:Not Found
InnerStackTrace:
at DotNetNuke.Modules.Admin.Users.ViewProfile.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.AddedControl(Control control, Int32 index)
at System.Web.UI.ControlCollection.Add(Control child)
at DotNetNuke.UI.Modules.ModuleHost.InjectModuleContent(Control content)
at DotNetNuke.UI.Modules.ModuleHost.CreateChildControls()
at System.Web.UI.Control.EnsureChildControls()
at DotNetNuke.UI.Containers.Container.get_ModuleControl()
at DotNetNuke.UI.Containers.Container.ProcessModule()
at DotNetNuke.UI.Skins.Pane.InjectModule(ModuleInfo module)
SourceotNetNuke
FileName:
FileLineNumber:0
FileColumnNumber:0
Method:
Server Name:

I don't think that particular error is an attack. It appears that DNN is having trouble adding a module to a page. You probably will have to dig around to see if you can determine which one.

Which version of DNN are you using?

Thanks Joe,
this was occurring across several instances of dnn, in the particular case i am working with i moved a website, actually by recreating it, to a fresh instance.

I have observed similar error reports on both instances. these seem to be related to the profile, which is also being targeted by the registration bots at least in the sense that they need to provide profile info to create the bogus registrations.

There were no users logged into the portal that through the error when it occurred which is what gives me cause for suspicion.

BTW this is version 7.4