When a users is removed from a portal, the name is still on the database, and a user with the same name can't be created. Although the name is in the database, nothing can be seen from the users menu of the portal.
I only know of a problem like this after deleting a superuser. That has just been fixed an hour ago.
I have upgraded from DNN 3012 to 3013 and am getting this same error. While the deletion of the "not fully registered" users does resolve the "users accounts not accessible" hard error, it does not resolve the error with registering new users. The SuperUser
account has not been deleted, and rolling back to 3012 does resolve the error. At this point (after upgrading to DNN 3013) new users cannot be added without causing an error.
J.Arctain
-The greatest good you can do for another is not just share your riches, but reveal to them their own.
--Benjamin Disraeli
I have upgraded from DNN 3012 to 3013 and am getting this same error. While the deletion of the "not fully registered" users does resolve the "users accounts not accessible" hard error, it does not resolve the error with registering new users. The SuperUser
account has not been deleted, and rolling back to 3012 does resolve the error. At this point (after upgrading to DNN 3013) new users cannot be added without causing an error.
I don't have any problem adding users to my upgraded sites. It would be interesting to find out what is different about your environment.
Is it possible that someone who is experiencing these problems after upgrading zip up their database and DotnetNuke folder and send it me so I can compare with a standard 3.0.13 version (database) and find out what's happening here ?
Windows 2003 server (with all service packs applied) and also getting the same on a WinXP pro development environment
Have not had a chance to see if the build version 3.0.13.36098 encounters the same issue.
No changes to the Web.Config file other than the original database setup change: add key="SiteSqlServer" value="Server=(local);Database=dbXXX;uid=dbUserXXX;pwd=XXX;" etc...
Thanks!
J.Arctain
-The greatest good you can do for another is not just share your riches, but reveal to them their own.
--Benjamin Disraeli
I have no problem with backing-up the database, zipping it, along with the base DNN folder. Let me know your email, and it will be on the way. If your email account will fail on a >10Meg file, then let me know, and I will set up an alternate download path
for the files and DB. I have done a comparison of the files and database, but a second set of eyes is always appreciated.
Thanks,
J.Arctain
-The greatest good you can do for another is not just share your riches, but reveal to them their own.
--Benjamin Disraeli
At risk of confusing everyone let me add my experience. I upgraded from Dotnetnuke 2.1.2 to Dotnetnuke 3.0.13. Everything went fine. The only problem was that a new user could not register with the site. I logged in as the superuser and started clicking around
everywhere and noticed that when I clicked on user management it would error out (I could not get to user management) So I started looking at the tables and found out my Portal was assigned to a user that had a user id that didn’t belong to anyone. I tried
to assign it to my superusers id but that still caused odd behavior. When I looked in the administration of the portal, the drop-down that contains the administrators name was blank. The solution was to assign the portal to the ID of a admin that already had
an account. Now I was able to log in as that Admin and get to the user management. Now people are able to register with the site. The superuser account still works. I really think the problem was that my superuser was the admin of this portal. All my other
portals did not have this problem.
I would like to thank the posters for the SQL solutions to this problem. I had the exact behaviour in my DNN 3.0.13 portal, and the SQL helped me remove the 4 bad rows in aspnet_Users. The member data seems to be healthy again. Thanks.
DNN will most definitely need some method for SQL jockeys to insert/delete/update user data directly as a single row or string, as well as this useful procedure to de-lintify the data across the DNN and aspnet_* tables.
Administrator manipulation of user data in bulk is one of the great inevitabilities of any portal system of nontrivial size. We might as well get back to the level of flexibilty we had with 2.1.2.
It should be part of the core installation, or at least documented as a HOW-TO:
That is a good call. This is actually a perfect example of a data integrity problem that was introduced during one of the pre-release versions. At one point, it was possible to "promote" a user to SuperUser... it is not now. And while the data works within
the referential integrity issues of the DB itself, it is an unexpected combination from a processing standpoint. Good catch.
Scott
Scott Willhite
Director of Community Relations, DotNetNuke
It is only with the heart that one can see rightly... what is essential is invisible to the eye.
~ Antoine de Saint-Exupéry
Geert
Star
10052 Points
2011 Posts
Re: User Accounts is currently unavailable
May 15, 2005 03:17 PM|LINK
When a users is removed from a portal, the name is still on the database, and a user with the same name can't be created. Although the name is in the database, nothing can be seen from the users menu of the portal.
I only know of a problem like this after deleting a superuser. That has just been fixed an hour ago.
arctain
Member
295 Points
59 Posts
Re: User Accounts is currently unavailable
May 16, 2005 03:41 PM|LINK
All,
I have upgraded from DNN 3012 to 3013 and am getting this same error. While the deletion of the "not fully registered" users does resolve the "users accounts not accessible" hard error, it does not resolve the error with registering new users. The SuperUser account has not been deleted, and rolling back to 3012 does resolve the error. At this point (after upgrading to DNN 3013) new users cannot be added without causing an error.
-The greatest good you can do for another is not just share your riches, but reveal to them their own.
--Benjamin Disraeli
J7Mitch
Star
13145 Points
2632 Posts
Re: User Accounts is currently unavailable
May 16, 2005 05:19 PM|LINK
I don't have any problem adding users to my upgraded sites. It would be interesting to find out what is different about your environment.
Geert
Star
10052 Points
2011 Posts
Re: User Accounts is currently unavailable
May 16, 2005 05:31 PM|LINK
I also keep hearing this problem.
Is it possible that someone who is experiencing these problems after upgrading zip up their database and DotnetNuke folder and send it me so I can compare with a standard 3.0.13 version (database) and find out what's happening here ?
(Or you could compare it yourself of course)
arctain
Member
295 Points
59 Posts
Re: User Accounts is currently unavailable
May 16, 2005 05:42 PM|LINK
DNN 3013 build version 3.0.13.13077
Windows 2003 server (with all service packs applied) and also getting the same on a WinXP pro development environment
Have not had a chance to see if the build version 3.0.13.36098 encounters the same issue.
No changes to the Web.Config file other than the original database setup change: add key="SiteSqlServer" value="Server=(local);Database=dbXXX;uid=dbUserXXX;pwd=XXX;" etc...
Thanks!
-The greatest good you can do for another is not just share your riches, but reveal to them their own.
--Benjamin Disraeli
arctain
Member
295 Points
59 Posts
Re: User Accounts is currently unavailable
May 16, 2005 05:52 PM|LINK
I have no problem with backing-up the database, zipping it, along with the base DNN folder. Let me know your email, and it will be on the way. If your email account will fail on a >10Meg file, then let me know, and I will set up an alternate download path for the files and DB. I have done a comparison of the files and database, but a second set of eyes is always appreciated.
Thanks,
-The greatest good you can do for another is not just share your riches, but reveal to them their own.
--Benjamin Disraeli
adefwebserve...
Contributor
5912 Points
1207 Posts
MVP
Re: User Accounts is currently unavailable
May 16, 2005 06:11 PM|LINK
Open Light Group
LightSwitchHelpWebsite.com | ADefWebserver.com
Geert
Star
10052 Points
2011 Posts
Re: User Accounts is currently unavailable
May 16, 2005 06:15 PM|LINK
Now where would you get version 3.0.13.13077 ???
The official 3.0.13 is build 3.0.13.36098 (DotNetNuke.dll)
I recommend trying that version first !
Jeff_K
Member
270 Points
54 Posts
Re: User Accounts is currently unavailable
May 16, 2005 06:34 PM|LINK
DNN will most definitely need some method for SQL jockeys to insert/delete/update user data directly as a single row or string, as well as this useful procedure to de-lintify the data across the DNN and aspnet_* tables.
Administrator manipulation of user data in bulk is one of the great inevitabilities of any portal system of nontrivial size. We might as well get back to the level of flexibilty we had with 2.1.2.
It should be part of the core installation, or at least documented as a HOW-TO:
mrswoop
Star
11177 Points
2240 Posts
Re: User Accounts is currently unavailable
May 16, 2005 07:57 PM|LINK
Michael ~
That is a good call. This is actually a perfect example of a data integrity problem that was introduced during one of the pre-release versions. At one point, it was possible to "promote" a user to SuperUser... it is not now. And while the data works within the referential integrity issues of the DB itself, it is an unexpected combination from a processing standpoint. Good catch.
Scott
Director of Community Relations, DotNetNuke
It is only with the heart that one can see rightly... what is essential is invisible to the eye.
~ Antoine de Saint-Exupéry