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 ForumsAuthenticationAuthenticationActive Directory 01.00.02 Beta Version 2Active Directory 01.00.02 Beta Version 2
Previous
 
Next
New Post
1/31/2008 6:48 AM
 

Thanks for the 01.00.02 beta, it solved all the Javascript errors we were getting in our 500 PCs intranet.

But now we are experiencing another little problem: DNN log shows many Exception errors (about 200 a day, on 500 clients * 8 working hours = 4000 calls to DNN), all like this:

AssemblyVersion: 04.08.00
PortalID: 0
PortalName: Intranet 2.0
UserID: -1
UserName:
ActiveTabID: 36
ActiveTabName: Home
RawURL: /Dnn/default.aspx
AbsoluteURL: /Dnn/default.aspx
AbsoluteURLReferrer: http://civiweb/
UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; InfoPath.1)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: e4c80074-cf33-4f4f-bae6-50cede08c18c
InnerException: Error processing AD login
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Threading.Thread.AbortInternal
StackTrace:
Message: System.Exception: Error processing AD login ---> System.Threading.ThreadAbortException: Thread was being aborted. at System.Threading.Thread.AbortInternal() at System.Threading.Thread.Abort(Object stateInfo) at System.Web.HttpResponse.End() at System.Web.HttpResponse.Redirect(String url, Boolean endResponse) at System.Web.HttpResponse.Redirect(String url) at DotNetNuke.Authentication.ActiveDirectory.HttpModules.AuthenticationModule.OnAuthenticateRequest(Object s, EventArgs e) --- End of inner exception stack trace ---

I have no clue on what is causing this. Any ideas?

 
New Post
1/31/2008 12:27 PM
 

It's a "sort of" bug that will be fixed in the next release. I added a try/catch to catch AD login failures where there had not been one before. Unfortunately I didn't notice the error on my dev system initially and just ran into it on my live deployment last week. Essentially what is causing the error is the Response.Redirect to windowssignin.aspx. I'm working on a fix for the IIS7 Integrated Pipeline mode and once that's fixed I'll be making another release.

 
New Post
2/1/2008 9:47 AM
 

Thanks for the explanations. Please fix this issue as soon as possible, since it is filling my DNN log with exceptions that hide those more significant. I was thinking to modify the source package directly, wondering if I am able to do it, but I prefer to wait for a more refined release by you.

Thanks again for your hard work and keep in mind that for every DNN administrator like me that (sometimes) writes in these forums there are hundrends out there too shy to do the same, but are willing to see news from you project leaders!

Ciao.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationActive Directory 01.00.02 Beta Version 2Active Directory 01.00.02 Beta Version 2


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