Chad I have resolved this problem.  It was resolved by one of two possibilities.  I did not have Display Name required nor ID'd as core field in the Dyn. Reg.  Or UserName is duplicate of acct in another portal in same db.

Incidentally,  Dynamic Reg returned an error when I attempted to create a new acct with a username that was used in another portal, but, it also returned the Registration Successful message on the same page as the error.

The error was (sic) "username in use.  register again with a different username."

Peter,

Hi. Thanks for your posts. I will probably add them all to the same thread to help other users.

This issue came about with DNN 4.3.x and we have notified the Core team of DotNetNuke about the situation. The problem occurs when you leave out the fields for display name, first name, last name, or email address since these fields are all required within the user accounts area. Since it was posted in a benefactors post I will include the full post here, there are some simple instructions you can do if you don't want to make those fields required (changes to a file within DotNetNuke but not actually have to recompile or anything).

------Post to the benefactors forum here-------

http://www.dotnetnuke.com/Community...fault.aspx

Hi. I have a few issues coming up with the new standard "Admin, User Accounts" area within DotNetNuke 4.3.x. For custom registration modules not everyone wants to use the standard fields (i.e. First/Last Names or DisplayName). Within the new user accounts there are certain fields using the TextColumn control which is throwing and error if a null value is returned for these fields.

Code (within users.ascx under admin\users)






If any custom module creates a user within the system without a first name for example, or a display name then User Accounts returns this error when binding the grid:

Error: User Accounts 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.UI.WebControls.TextColumnTemplate.GetValue(DataGridItem container) at DotNetNuke.UI.WebControls.TextColumnTemplate.Item_DataBinding(Object sender, EventArgs e) at System.Web.UI.Control.OnDataBinding(EventArgs e) at System.Web.UI.Control.DataBind(Boolean raiseOnDataBinding) at System.Web.UI.Control.DataBind() at System.Web.UI.Control.DataBindChildren() at System.Web.UI.Control.DataBind(Boolean raiseOnDataBinding) at System.Web.UI.Control.DataBind() at System.Web.UI.Control.DataBindChildren() at System.Web.UI.Control.DataBind(Boolean raiseOnDataBinding) at System.Web.UI.Control.DataBind() at System.Web.UI.WebControls.DataGrid.CreateItem(Int32 itemIndex, Int32 dataSourceIndex, ListItemType itemType, Boolean dataBind, Object dataItem, DataGridColumn[] columns, TableRowCollection rows, PagedDataSource pagedDataSource) at System.Web.UI.WebControls.DataGrid.CreateControlHierarchy(Boolean useDataSource) at System.Web.UI.WebControls.BaseDataList.OnDataBinding(EventArgs e) at System.Web.UI.WebControls.BaseDataList.DataBind() at DotNetNuke.Modules.Admin.Users.UserAccounts.BindData(String SearchText, String SearchField) at DotNetNuke.Modules.Admin.Users.UserAccounts.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---

A workaround for this would be to simply remove those columns from the .ascx files but thats customization which involves retrofits for upgrades.

So it would look like this instead (assuming you also wanted to remove First/Last names etc...):



Any chance future versions of the CORE could include some error handling that would allow for null values here?


Also, as a follow up Charles replied that there was tracking for this issue within Gemini and it shows fixed but I don't see that it was.

http://support.dotnetnuke.com/issue...px?ID=2913