Thanks to Chad for directing me down some potential paths and responding to my free flowing email!
Here is what I have found:
- Short version: Having DNN Masters Multi Portal User Sharing Pro installed on the same DNN instance as Dynamic Registration 3.0 results in Password resets executed through Dynamic Registration failing. Uninstalling DNN Masters MPUS Pro and installing DNN Masters MPUS Xtreme resolves this "conflict".
- Long Version: Due to the problem being isolated to the password reset process I wanted to ensure the problem was not the result of my DNN Version (4.5.5). In his first response Chad indicated he had just validated the problem was not occurring on their beta site which had DNN 4.5.3 so I decided to start from that point. I upgraded a dev environment from 4.4.1 to 4.5.3 then installed Dyn Reg 3.0 and found everything worked as expected. I then upgraded to DNN 4.5.5 and found once again that everything worked as expected (unable to replicate my original password reset problem). At this point it appeared the problem was likely a conflict related to a module installed on my primary site and suspected the greatest risk would be with MPUS due to the nature of the modules. Immediately upon proper installation of MPUS 2.0.20 the password reset issue in Dyn Reg 3.0 appeared. Hoping it was isolated to the version of MPUS (there are later versions recommended for DNN 4.5.5) I upgraded MPUS through each available version to determine if the conflict was resolved with a later release. I found 2.0.20, 2.0.26 and 2.0.43 MPUS Pro releases all resulted in password resets in Dynamic Registration 3.0 failing. I then uninstalled MPUS Pro and installed a MPUS Xtreme (cannot upgrade to this product from MPUS pro, must uninstall/install) and found the problem was resolved with both Dynamic Registration 3.0 and MPUS Xtreme functioning as expected with the password reset issue being resolved(though I have not yet completed full testing so there may possibly be other/new conflicts)
MPUS Pro and Extreme each require modifications to the web.config file, specifically changing the members, roles, and profiles providers to utilize MPUS providers. My suspicion is that MPUS PRO is doing something different enough with password resets that it resulted in errors in Dynamic Registration3.0. Of additional note is that the default DNN password reset still works properly when MPUS Pro is in place...very odd.
I would definitely like to thank Chad for being so responsive and offering numerous suggestions of areas to focus on.
Chris