I ran into the same problem today, unfortunately the sql script does not help, the first query returns no results. I am on 3.1, here's my error trace:
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 _ASP.Users_ascx.__DataBind__control19(Object
sender, EventArgs e) at System.Web.UI.Control.OnDataBinding(EventArgs e) at System.Web.UI.Control.DataBind() at System.Web.UI.Control.DataBind() 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 ---
I have experienced this issue several times. The cause is definitely caused when there is a user that exists in the base DNN User tables and not the aspnet User tables. For the longest time I knew I could fix it by removing the out of synch records from the
aspnet tables, but I couldn't figure out how they were getting out of synch. Finally, I think I figured out it was being caused by a current bug in the system that is actually scheduled to be fixed in the 3.1.1 Maintenance Release.
Delete Child Portal deletes users from others portals
If you delete a child portal, it accidentally deletes all users in the portal in the users table but does not delete it from the aspnet tables. If the user exists in other portals other than the one you deleted, your tables will become out of synch for those
other portals, and you will get the error. The fix to this bug should involve checking to see if a particular user is a member of more than one portal, and only deleting them from that particular Portal (UserPortals table). I look forward to this fix coming
out. Untill then, my tip would be don't delete portals.
Two questions about the 3.1.1 Maintenance release.
Do we have any idea when this will be released?
In addition to fixing the bug that leaves the abandon records, will it remove any abandon records it finds?
Since I haven't had the time to sit down and fix this problem (which prevents me from creating new portals), I'm hoping that the maintenance release will clean up the dirty funky nasty records that exist because of this bug.
Anybody know the answers to both or one of these questions?
I still get this error - can anyone help me out with a quick solution? I ran the query, I doublechecked the user tables and there does not seem to be any inconsistancy. This happened on a production server and I cannot get around it.
Btw. it only occurs in the host portal, while all the child portals run fine.
Server: Msg 512, Level 16, State 1, Line 21
Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.
The statement has been terminated.
(0 row(s) affected)
(0 row(s) affected)
Server: Msg 547, Level 16, State 1, Line 32
DELETE statement conflicted with COLUMN REFERENCE constraint 'FK__aspnet_Me__UserI__76D69450'. The conflict occurred in database 'NukeSqlServer', table 'aspnet_Membership', column 'UserId'.
The statement has been terminated.
Server: Msg 512, Level 16, State 1, Line 21
Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.
The statement has been terminated.
(0 row(s) affected)
(0 row(s) affected)
Server: Msg 547, Level 16, State 1, Line 32
DELETE statement conflicted with COLUMN REFERENCE constraint 'FK__aspnet_Me__UserI__76D69450'. The conflict occurred in database 'NukeSqlServer', table 'aspnet_Membership', column 'UserId'.
The statement has been terminated.
proeder
Member
555 Points
111 Posts
Re: User Accounts is currently unavailable
Jul 27, 2005 12:39 PM|LINK
I ran into the same problem today, unfortunately the sql script does not help, the first query returns no results. I am on 3.1, here's my error trace:
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 _ASP.Users_ascx.__DataBind__control19(Object sender, EventArgs e) at System.Web.UI.Control.OnDataBinding(EventArgs e) at System.Web.UI.Control.DataBind() at System.Web.UI.Control.DataBind() 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 ---
Can thsi have other reasons, too?
Desktopmodules@Portalfabrik :: DotNetNuke Hosting@Portalfabrik
jmcwilliam
Member
70 Points
14 Posts
Re: User Accounts is currently unavailable
Jul 29, 2005 02:46 PM|LINK
If you delete a child portal, it accidentally deletes all users in the portal in the users table but does not delete it from the aspnet tables. If the user exists in other portals other than the one you deleted, your tables will become out of synch for those other portals, and you will get the error. The fix to this bug should involve checking to see if a particular user is a member of more than one portal, and only deleting them from that particular Portal (UserPortals table). I look forward to this fix coming out. Untill then, my tip would be don't delete portals.
CybrEnergy
Member
381 Points
94 Posts
Re: User Accounts is currently unavailable
Jul 29, 2005 04:01 PM|LINK
Do we have any idea when this will be released?
In addition to fixing the bug that leaves the abandon records, will it remove any abandon records it finds?
Since I haven't had the time to sit down and fix this problem (which prevents me from creating new portals), I'm hoping that the maintenance release will clean up the dirty funky nasty records that exist because of this bug.
Anybody know the answers to both or one of these questions?
Thanks!
proeder
Member
555 Points
111 Posts
Re: User Accounts is currently unavailable
Aug 08, 2005 08:33 AM|LINK
Btw. it only occurs in the host portal, while all the child portals run fine.
Desktopmodules@Portalfabrik :: DotNetNuke Hosting@Portalfabrik
BarrierMan
Member
95 Points
19 Posts
Betreft: Re: User Accounts is currently unavailable
Aug 14, 2005 08:00 AM|LINK
The 1st sql-query generates a huge list of accounts.
The 2nd sql-statement does not work for me as it reply that there is an error in the sql-command.
Can someone help me with that?
J7Mitch
Star
13145 Points
2632 Posts
Re: Betreft: Re: User Accounts is currently unavailable
Aug 15, 2005 03:54 AM|LINK
BarrierMan
Member
95 Points
19 Posts
Betreft: Re: Betreft: Re: User Accounts is currently unavailable
Aug 15, 2005 05:35 AM|LINK
J7Mitch
Star
13145 Points
2632 Posts
Re: Betreft: Re: Betreft: Re: User Accounts is currently unavailable
Aug 16, 2005 05:54 AM|LINK
That isn't much to go on. Can you run the query from something other than the Host>Sql window (Like Query Anayzer)?
Do you have a setting for objectQualifier in the web.config? If so you need to add that to the db objects in the query.
BarrierMan
Member
95 Points
19 Posts
Betreft: Re: Betreft: Re: Betreft: Re: User Accounts is currently unavailable
Aug 16, 2005 06:17 PM|LINK
Result:
Server: Msg 512, Level 16, State 1, Line 21
Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.
The statement has been terminated.
(0 row(s) affected)
(0 row(s) affected)
Server: Msg 547, Level 16, State 1, Line 32
DELETE statement conflicted with COLUMN REFERENCE constraint 'FK__aspnet_Me__UserI__76D69450'. The conflict occurred in database 'NukeSqlServer', table 'aspnet_Membership', column 'UserId'.
The statement has been terminated.
Server: Msg 512, Level 16, State 1, Line 21
Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.
The statement has been terminated.
(0 row(s) affected)
(0 row(s) affected)
Server: Msg 547, Level 16, State 1, Line 32
DELETE statement conflicted with COLUMN REFERENCE constraint 'FK__aspnet_Me__UserI__76D69450'. The conflict occurred in database 'NukeSqlServer', table 'aspnet_Membership', column 'UserId'.
The statement has been terminated.
J7Mitch
Star
13145 Points
2632 Posts
Re: Betreft: Re: Betreft: Re: Betreft: Re: User Accounts is currently unavailable
Aug 16, 2005 06:26 PM|LINK
Add "AND PortalId=0" to all the select queries ( and then run it again for any other portals).
You could also create a cursor loop around the one that is there that ran the set for each portal one at a time.