Does not seem to work on DNN v7.3.1--Critical Error

[boydbadten]

Tried UserAccountmanagement 1.2.0 and 1.2.2 and they both install OK but then the module fails to a "critical error" after installing on a page. Tried it with three different DNN 7.3.1 installs--same result in all three. Running as HOST. Error below:

A critical error has occurred.

AssemblyVersion:7.3.1

PortalID:0

PortalName:The Hearts Center

UserID:1

UserName:Cyclopea

ActiveTabID:922

ActiveTabName:Account Manager module

RawURL:/Servitors/AccountManagermodule/tabid/922/Default.aspx

AbsoluteURL:/Default.aspx

AbsoluteURLReferrer:http://amazonia.heartscenter.org/AscendedMastersandTheHeartsCenterCommunity/tabid/817/Default.aspx

UserAgent:Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0

DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke

ExceptionGUID:54acf288-7604-424a-807e-eb62289e7548

InnerException:Conversion from string "" to type 'Integer' is not valid.

FileName:

FileLineNumber:0

FileColumnNumber:0

Method:Microsoft.VisualBasic.CompilerServices.Conversions.ParseDouble

StackTrace:

Message:

DotNetNuke.Services.Exceptions.PageLoadException: Conversion from string "" to type 'Integer' is not valid. ---> System.InvalidCastException: Conversion from string "" to type 'Integer' is not valid. ---> System.FormatException: Input string was not in a correct format.
at Microsoft.VisualBasic.CompilerServices.Conversions.ParseDouble(String Value, NumberFormatInfo NumberFormat)
at Microsoft.VisualBasic.CompilerServices.Conversions.ToInteger(String Value)
--- End of inner exception stack trace ---
at Microsoft.VisualBasic.CompilerServices.Conversions.ToInteger(String Value)
at Microsoft.VisualBasic.CompilerServices.Conversions.ToInteger(Object Value)
at Connect.Modules.UserManagement.AccountManagement.View.BindRoles()
at Connect.Modules.UserManagement.AccountManagement.View.Page_Load(Object sender, 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.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
--- End of inner exception stack trace ---

Source:

Server Name: AmazoniaFTP

[peppertree]

Can't reproduce this either.Your installation seems to be somewhat different from the ones I tested this with. The only thing I can think of is that role selection of the treeview does not work because any of your roleids is not properly populated (that would also explain the other error you've logged).

Can you access the module settings and set a preselected role?

[boydbadten]

I figured out the problem. I'm betting that you can duplicate it if
you try.
Put the page which contains the User Account module under a menu
item which has restricted view permissions. Your module will go
crazy and you'll see all kinds of mayhem if you do this in DNN
7.3.1. I've seen some references to undesired behavior in DNN 7.3.1
with regards to permissions handling.
My sites usually have a "staff only" menu item with view and access
restrictions so that the general public can't even see the menu
item. And we put all the staff-only "under the hood" controls to
everything in there--controls for people who don't need to be
admins. If you make such a menu item (a disabled page at the root
level) and give it view permissions to a role of "staff" but not
"everyone" your module will greatly misbehave if you place the page
it's on under such a menu item.
Yes, I can access the module settings and I've tried every
permutation on things there all to no avail at fixing the problem
mentioned above.
BoydOn 7/25/2014 12:58 AM, peppertree
  wrote:

  Can't reproduce this either.Your installation seems to be
    somewhat different from the ones I tested this with. The only
    thing I can think of is that role selection of the treeview does
    not work because any of your roleids is not properly populated
    (that would also explain the other error you've logged).
  Can you access the module settings and set a preselected role?
  —
    Reply to this email directly or view
      it on GitHub.

-- 

---

| _ \ | |
| |) | ___ _ _ **| |
| _ < / _ | | | |/ ` |
| |) | () | || | (| |
|/ _/ **, |,|
**/ |
|**/

[peppertree]

I followed your steps to reproduce the issue. Yet everything is working as expected, no such error here. Actually your design is what the module has been made for. Obviously noone would ever use an accounts management module on a page that is visible to the public.

[boydbadten]

I've played with it some more and found that the problems will go
away as long as I install the module on a page, configure the module
and then move the page to another location.  So it may not have to
do with permissions. I was getting this false impressions from
installing and then moving the page from place to place. Now it
seems that if I simply install and then move the page it fixes the
issues. I can't imagine why. I know this sounds crazy and I
appreciate your patience in reading my comments. 
Thank you so much for building this module!!! I have two other
account management modules and have been using DNN since version
3.x. Your module is way better than any others I've ever seen. Good
karma coming your way---
BoydOn 7/25/2014 1:58 PM, peppertree wrote:

  I followed your steps to reproduce the issue. Yet everything is
    working as expected, no such error here. Actually your design is
    what the module has been made for. Obviously noone would ever
    use an accounts management module on a page that is visible to
    the public.
  —
    Reply to this email directly or view
      it on GitHub.

-- 

---

| _ \ | |
| |) | ___ _ _ **| |
| _ < / _ | | | |/ ` |
| |) | () | || | (| |
|/ _/ **, |,|
**/ |
|**/

[iiminov]

If I correctly understood the above issue. That is:

I have a page which is only visible to Staff Admin role (not to be confused with default Administrator role or SuperAdmin).
On this page I have an instance of this module configured to allow members of Staff Admin role to manage certain user accounts.
I don't see any critical errors and everything works right out of the box.

The only time I was presented with critical error was when I didn't have a selection in Allowed roles corresponding to selected role in Preselected role.

I have tested this in two configurations currently running latest release of UserAccountManagement.
DNN 7.2.2 w/ SQL Server 2012 SP1
and
DNN 7.3.1 w/ SQL Server 2008 R2

If it helps :)

[peppertree]

That is expected behaviour because once no role is selected it will default to "registered users". I will make sure that the fallback always defaults to a role that is in "AllowedRoles"

[jyjohnson]

I'm getting the "InnerException:Conversion from string "" to type 'Integer' is not valid" error right after making any edits on the Settings page. Even if I set all options back to the default/blank value I continue to get the exception.

If I move the module to another page, the exception stops, however the previously selected Settings are removed (blank defaults).

[peppertree]

I have fixed a few other issues first to get the next release ready. Will work on this next.