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 ForumsAuthenticationAuthenticationIssues with new Dnn 4.5 install and AD moduleIssues with new Dnn 4.5 install and AD module
Previous
 
Next
New Post
5/14/2007 1:31 PM
 

I got the same error, too.

I have a fresh DNN 4.3.7 Install edition installed. Until I tried impersonation and getting the error of CountryListBox...access is denied, the site authenticated me, but the Users table in the database didn't pull the information correctly from AD prior to the attempted impersonation fix.

The account I am using in the impersonation tag in web.config is my personal domain account, which is a basic user account.

Here's what's happening to my Users table:

  • username pulled fine
  • first name field was populated with my username without the domain prefix
  • last name field populated with the domain name
  • email field populated fine
  • display name field not populated at all

I've been fighting AD integration on DNN for awhile now and haven't had complete success. This is discouraging and not at all a good thing for DNN's future in Intranets, in my opinion. So, current status is 2 problems, possibly unrelated:

  1. Users' table not populating properly
  2. CountryListBox error. Access is denied.

What might be the solution to the incorrect info being pulled or populating the User's table following successful authentication, in particular getting the Display Name field populated? I have a feeling the use of impersonation is not needed to get the User's table to populated properly, so maybe there's a solution unrelated to impersonation.

Dan

 
New Post
5/15/2007 12:37 AM
 

Dan, can you upgrade to 4.5.1? There were some changes after 4.3.7 that I think will solve your problems (I'm don't have the source files here at home to compare them to). If you can't upgrade then possibly the DNN AD Fix for 4.3.7 will work for you (it can be found at http://dnn.gmss.org)

 
New Post
5/15/2007 9:49 AM
 

Hi Mike

 I am currently running 4.4.0 integrating into W2K3 AD and it works fine.  I am now looking to unpgrade to 4.5.1 in a development environment and can confirm that I am seeing the problem of "CountryListBox error. Access is denied" that Dan was complaining of.

Has anyone got any ideas?

Thanks

Glen

 

 
New Post
5/16/2007 5:45 PM
 

Ok, I went to http://dnn.gmss.org/Default.aspx?grm2catid=61&tabid=312 and downloaded the "DNN AD Fix 4.5.1".

I unzipped it on the host web server (W2K3) and followed the steps in the readme.txt. Btw, there is an omission of a dll file in Step 2 that should be backed up.

I commented out the <impersonation> tag in web.config, stopped and started the site, and launched IE 6 on the actual server and got the following:

Compiler Error Message: BC30451: Name 'AssemblyPath' is not declared.

Source Error:

 
Line 247:            HostMapPath = Server.MapPath(HostPath)
Line 248:
Line 249:            AssemblyPath = ApplicationMapPath & "\bin\dotnetnuke.dll"
Line 250:
Line 251:            'Check whether the current App Version is the same as the DB Version

Source File: D:\Inetpub\Internal_Root\DNN Test Site\App_Code\Global.asax.vb    Line: 249

I googled for a more info about it, but got nothing.

I think this could be caused from any number of things, such as needing another global.asax.vb in /app_code/ in this AD Fix, an addition for 4.5.1 that no longer applies to 4.3.7, etc. I don't know.

Dan

 
New Post
5/17/2007 12:34 AM
 

What happens if you remove the fix files and go back to the originals? I've got it running on three or four separate installs and there are however many other installs out there and I haven't seen or heard of that error in the global.asax.vb with the AD Fix

I just did some quick googling and found this post with the same error. https://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/107/threadid/122266/threadpage/1/scope/posts/Default.aspx. When you upgraded to 4.5.1 did you adjust your web.config to match all the changes or did you just use your previous web.config?

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationIssues with new Dnn 4.5 install and AD moduleIssues with new Dnn 4.5 install and AD module


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