Hi.

When I add the module to a page, under settings (not Form and List configuration) the Max. Records per User is empty, but if I set it to ten (10) it triggers an Page Exception and a Module Exception, if I leave the field empty and save, the error goes away. Both exceptions are listed at the end.

I'm not an expert using that module, it's late and I'm tired so, my first assumption is that it's a DNN error, it's a 5.6.1 version. There is nothing strange with the page since it's the homepage and has a little contact form.

Here the errors were activated by a monitoring service but as a regular user the error is displayed too.

Thanks for your help!

---

AssemblyVersion: 5.6.1
PortalID: 0
PortalName:
UserID: -1
UserName:
ActiveTabID: 41
ActiveTabName: Home
RawURL: /
AbsoluteURL: /default.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/5.0 (compatible; Wasitup monitoring; http://wasitup.com)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 159183da-b5f7-4718-99cb-bef6f83c6518
InnerException: Object reference not set to an instance of an object.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Modules.UserDefinedTable.Security.ModuleSecurity.HasAddPermissonByQuota
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: 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.UserDefinedTable.Security.ModuleSecurity.HasAddPermissonByQuota(DataTable FieldsTable, DataTable DataTable, Int32 userRecordQuota, String username) at DotNetNuke.Modules.UserDefinedTable.EditForm.HasAddPermissonByQuota() at DotNetNuke.Modules.UserDefinedTable.EditForm.CheckPermission(Boolean isUsersOwnItem) at DotNetNuke.Modules.UserDefinedTable.EditForm.Page_Load(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---
Source:
Server Name:

---

ModuleId: 436
ModuleDefId: 123
FriendlyName: Free Consultation
ModuleControlSource: DesktopModules/UserDefinedTable/Default.ascx
AssemblyVersion: 5.6.1
PortalID: 0
PortalName: Prospect Focus
UserID: -1
UserName:
ActiveTabID: 41
ActiveTabName: Home
RawURL: /
AbsoluteURL: /default.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/5.0 (compatible; Wasitup monitoring; http://wasitup.com)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: bea8c729-5967-45a0-8e61-f4d9fef68acd
InnerException: Object reference not set to an instance of an object.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Modules.UserDefinedTable.Security.ModuleSecurity.HasAddPermissonByQuota
StackTrace:
Message: 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.UserDefinedTable.Security.ModuleSecurity.HasAddPermissonByQuota(DataTable FieldsTable, DataTable DataTable, Int32 userRecordQuota, String username) at DotNetNuke.Modules.UserDefinedTable.EditForm.HasAddPermissonByQuota() at DotNetNuke.Modules.UserDefinedTable.EditForm.CheckPermission(Boolean isUsersOwnItem) at DotNetNuke.Modules.UserDefinedTable.EditForm.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---
Source:
Server Name:

---

Sebastian, yes I tried that twice: by changing the web.config and by restarting from the host control panel and still no luck.

Today I'll use a fresh installation to replicate the error and discard it's my production installation.