Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationError when loggin in with an AD User not in DNN databaseError when loggin in with an AD User not in DNN database
Previous
 
Next
New Post
3/11/2008 4:55 PM
 

My DNN is configured with the AD Provider and it works except for one thing. When I log in for the first time with a user that exists only in my AD and not in the DNN database, I get this error (and I am not signed in):

A critical error has occurred.
Unknown UserCreateStatus value encountered Parameter name: UserRegistrationStatus

When I log in again with the same user, I get this error (but this time I stay logged in):

A critical error has occurred.
Redirect URI cannot contain newline characters.

And then, I don't have any connection problem with this user. Does anyone know how to solve this ???

Thanks

 
New Post
3/11/2008 9:26 PM
 

Maxime can you post more information about your DNN setup (DNN version, Server/IIS version, AD Provider version, etc). Also is this the error displayed on the user screen? Can you post whatever is posted to the DNN Eventviewer?

 
New Post
3/27/2008 5:01 PM
 

Mike,

I am getting the same error. Here is the info you requested...

DNN version: 04.08.02

Server/IIS version: Windows 2003 Ent R2 SP2/IIS 6

AD: Windows 2003 using default DNN ADSIAuthenticationProvider

Event Viewer:

UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.0.04506; InfoPath.2)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 46d74374-b293-46d7-ac04-d7f9de44ad2a
InnerException: Unknown UserCreateStatus value encountered Parameter name: UserRegistrationStatus
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Entities.Users.UserController.GetUserCreateStatus
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: Unknown UserCreateStatus value encountered Parameter name: UserRegistrationStatus ---> System.ArgumentException: Unknown UserCreateStatus value encountered Parameter name: UserRegistrationStatus at DotNetNuke.Entities.Users.UserController.GetUserCreateStatus(UserCreateStatus UserRegistrationStatus) at DotNetNuke.Authentication.ActiveDirectory.Login.WindowsAuthorization(UserLoginStatus& loginStatus, String IP) at DotNetNuke.Authentication.ActiveDirectory.Login.cmdLogin_Click(Object sender, EventArgs e) at System.Web.UI.WebControls.Button.OnClick(EventArgs e) at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---
Source:
Server Name: WEB

 
New Post
3/27/2008 5:50 PM
 

Thanks Lester. One more questions. Is this portal the main portal (PortalID =0) or a sub portal. I haven't run into that error on the same configuration so I'm trying to narrow it down as much as possible so that I can try to recreate the error.

 
New Post
3/28/2008 10:20 AM
 

It's the main Portal. I do have subportals though... in which, if I disabled all login providers in the Host Settings except for Active Directory, I get the following exception when i try to access the login page or I add "ctl=login" to any page:

DotNetNuke.Services.Exceptions.PageLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Modules.Admin.Authentication.Login.DisplayLoginControl(AuthenticationLoginBase authLoginControl, Boolean addHeader, Boolean addFooter) at DotNetNuke.Modules.Admin.Authentication.Login.BindLogin() at DotNetNuke.Modules.Admin.Authentication.Login.ShowPanel() at DotNetNuke.Modules.Admin.Authentication.Login.Page_Load(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(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.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---

I'm sure this is a different error and has nothing to do with the previous one, but since we are debugging this it's worth mentioning. Note that I do not get the exception when I access the login control on the main portal.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationError when loggin in with an AD User not in DNN databaseError when loggin in with an AD User not in DNN database


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out