Hi Hajarussa,

Based upon your description, you're likely missing an entry in UserPortals to associate a particular user with a portal.

However, in virtually all conceivable circumstances, this sort of approach is the incorrect one.  For several reasons (including upgrade-compatibility, the ability to interact with multiple authentication providers, and data consistency) you should rarely -- if ever -- interface directly with the membership persistence layer directly.  Instead, you should be interacting with the DotNetNuke API (e.g., the UserController) itself for registration.

While it remains possible to roll-your-own registration in the data layer, this is going to be an approach that will be fraught with peril.  Few will be able to assist with any problems that will surely arise.  Be sure this is what you really want to do!

Brandon

Hi Hajarussa,

Quirks like these are exactly why I recommend only interfacing with DotNetNuke membership via the API.  You are certain to run into many issues that result in inconsistent behavior, and when you do run into these problems, there will be little that others will be able to do to help you.

Your best bet at this point, if you choose not to utilize the API, will be to attach a debugger to your process and step through the membership provider(s) to see why the framework is not recognizing your registered users.

I really strongly suggest you consider utilizing the API!

Brandon