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 ForumsAuthenticationAuthenticationUpgraded to 4.5.1, and now site is down!Upgraded to 4.5.1, and now site is down!
Previous
 
Next
New Post
5/23/2007 11:41 AM
 

1.  I was asking about the EventQueue because I have one entry in there that has completed=false, and got me wondering if that was tying up things.

2.  I finally got another test server up and running today to test authentication.  A clean install of 4.5.1 DOES work with the exact same settings in the Authentication page.   So.... It's related to that one server and the 4.5.1 upgrade...  Still no further ahead!

 

 
New Post
5/23/2007 9:21 PM
 

Dan:

I cannot give you specific recommendations about your issues, I need to get more experience with the AD integration, but, I would like to offer you a tool I found that may help.  It is a stored procedure that will allow you to search for a string in all the text fields in all the tables of a given database.  I talked about it in this post: http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/111/threadid/121639/scope/posts/Default.aspx.

Based on the results of your last test with a fresh install of 4.5.1, it seems that there may be some left over junk in your production database that is causing the trouble.  For instance you could search for the string "comic" in all tables to see where it appears.  I know you added the module again but remember that the new install of that module would have a different ModuleID than the old one.  So, the old instance of the module could give you problems whereas the new version with its new ModuleID would not.

I don't know if this makes a lot of sense to you, just trying to help.

Carlos

 

 
New Post
5/24/2007 9:42 AM
 

I agree with you, there is definitely something hosed.  I've been upgrading the same website for years now, and with every upgrade something seems to get leftover.  I've gone through the site several times over the last couple of years, weeding out old files, and quite often just removing some of the older files cleared up some issues.  This time it is a bit more complex, as it appears that there is possibly something in the database itself that is corrupted.

Your stored procedure might help "if" I knew what I was looking for.  Following Mike's recommendation, I was finally able to remove the DailyComic error, but I don't know what else is wrong.  Since I don't know the program inside-and-out, I don't know what to look for or how to trouble-shoot this issue.

 
New Post
6/7/2007 10:27 PM
 

You're not going to believe this, but I think I stumbled across a fix for this!

The problem appears to be in the user account information, which is why some people were working and some weren't.  To put it simply, if you delete the account from DNN, and then log into DNN again it will create a new account and everything is neato-cool-and-groovy, everything works just like it is supposed to!  (well, logging in does... I'll have to do more trouble-shooting on the other issues.

Anyways, tomorrow I'm going to figure out the table structures and then run SQL queries to "unathorize" all the domain users so I can then delete all unathorized accounts.  Then I'll be able to let the accounts re-create themselves.  Of course, that means I'll also have to spend time making duplicate AD groups to match the DNN security roles so everyone gets into the proper places in DNN.... 

Come to think of it, that sounds like a lot of work...  But, if it gets everything working again, it will be worth it!

 

 

 

 
New Post
6/8/2007 1:41 PM
 

Could catch Dan. I was able to confirm this when I was testing the 4.5.3 AD Fix this morning. Now the question is why???  I was not able to find anything at all that should cause that in the AD code itself. Once the user is logged in, which is evident by looking at the Eventviewer the next section of code calls a NavigateURL to force a page refresh.

I'll investigate further and keep you posted on what I find out.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationUpgraded to 4.5.1, and now site is down!Upgraded to 4.5.1, and now site is down!


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