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 ForumsAuthenticationAuthenticationAny suggestions on how to fix this?Any suggestions on how to fix this?
Previous
 
Next
New Post
5/23/2007 8:25 AM
 

I am truly starting to believe that 4.5.1 has a serious flaw in it that is causing this problem when certain conditions are met.  There seem to be more and more people posting with the same symptoms as I'm seeing (this thread is just one example).  

The first hint I had was when I was originally upgrading from 4.5.0 to 4.5.1.  I would install the update, everything stopped working.  I restored 4.5.0, everything started working again.  I went back and forth like this about a dozen times, and it was consistent that the upgrade simply wasn't working.  I'd still be running 4.5.0 if I didn't accidently lose my backup, but that is a different story... *grumble*

The clincher was when I purchased a larger module a couple of weeks ago from a third-party vendor, and they had major warning about installing it on 4.5.1, complete with a diagnostic of what functions were not working right.  About that time I finally started thinking that it wasn't my install that was the problem.

I set aside some time today to get a second copy of DNN up and running today, I'll do some more testing.

 

 

 
New Post
5/24/2007 8:14 AM
 

Danball,

I agree to the certain conditions. I have another site that I upgraded first and had no problems. That site did NOT have any child sites. I upgraded [ one of ] my main sites with several child portals and this problem started. I restored to 4.5.0 and the problem went away. I did the upgrade again and once again, authentication broke.

I'm still at 4.5.1 on that site and receiving a lot of flack. With there being so many child sites involved resorting back to the previous version after an extended troubleshooting period would prove detrimental to my existence.

I am so thankful Mike Horton joined the team because he really has excellent AD integration for previous versions. I can't wait till he breaks it out into a seperate provider independent of the core upgrade heartbeat.  That can't happen soon enough Mike!  

 
New Post
5/24/2007 9:22 AM
 

PaskettJ wrote

I agree to the certain conditions. I have another site that I upgraded first and had no problems. That site did NOT have any child sites. I upgraded [ one of ] my main sites with several child portals and this problem started. I restored to 4.5.0 and the problem went away. I did the upgrade again and once again, authentication broke.

I am so glad I'm not the only one experiencing this!  *grin*

 

 
New Post
5/24/2007 6:36 PM
 

Goes without saying, but I'll say it anyway: Misery loves company!

 
New Post
5/29/2007 3:13 PM
 

I was hoping for an honorable mention in the 4.5.2 list!

Hey Alex, you come across anything on this issue in Gemini? If not I'll submit an issue. Danball, you say you have seen several versions of this issue, any of them reported in Gemini other than the AD provider?

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAny suggestions on how to fix this?Any suggestions on how to fix this?


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