You searched for the word(s): userid:604886

More Search Options

RSS Available

• Re: User Accounts is currently unavailable

  This post seemed to be on point with my problems, but the SQL failed to locate any faulty users. This modification did the trick for me (including aspnet_profile in the test): Like above: Use this SQL at your own risk. --First run this to see if the tables are out of Sync: select u.userid, au.username as a_user, u.username as u_user, u.email ,ap.propertyvaluesstring from aspnet_Users au left outer join Users u on au.UserName = U.UserName left join aspnet_profile ap on ap.userid = au.userid where

  Posted to DotNetNuke (Forum) by McMolar on 8/17/2005

• Re: Windows Authentication Signin module

  McMolar wrote: David, My configuration is similar to yours, but with only 3 trusted domains. I could not get the previous version 3.00.12 to work very well, but I will relate what I have done with 3.00.13 to get it almost working here. First I did a fresh install, (I also recompiled, but I dont believe that is required). I installed both of the components, and followed the instructions for setting them up. In the web.config, I gave the ADSIAuthenticationProvider a rootdomain="mdomain1". When updating

  Posted to DotNetNuke (Forum) by McMolar on 4/20/2005

• Re: Windows Authentication Signin module

  David, My configuration is similar to yours, but with only 3 trusted domains. I could not get the previous version 3.00.12 to work very well, but I will relate what I have done with 3.00.13 to get it almost working here. First I did a fresh install, (I also recompiled, but I dont believe that is required). I installed both of the components, and followed the instructions for setting them up. In the web.config, I gave the ADSIAuthenticationProvider a rootdomain="mdomain1". When updating the Authentication

  Posted to DotNetNuke (Forum) by McMolar on 4/19/2005

• Re: Windows Authentication Signin module

  Thank you Tam! I have installed both of the new 3.00.13 modules. This version works much better in my environment (3 trusted domains with no AD). But I have one problem. When the user selects logoff , and then close and re-open the browser,and go to the site, they are presented with Register/Logon instead of First Last/Logoff. If they delete their cookies and refresh, then it works correctly (showing their name and logoff). If they never logoff, they never have this problem. Does anyone else see

  Posted to DotNetNuke (Forum) by McMolar on 4/19/2005

• Re: How can I change width of Left Pane?

  The quick and dirty way to make any module wider is to edit the module title, and add a string of non breaking spaces to the text that is there. Ex: "     " Of course this only works if you are displaying the module title.

  Posted to DotNetNuke (Forum) by McMolar on 4/14/2005

• Re: Windows Authentication for DNN3.0

  Thanks for the reply. I do intermittently get errors, just above the content pane: A critical error has occurred. Object reference not set to an instance of an object. I have done several installs, and this only occurs after the addition of the authentication component. You say this due to LDAP access failures? Is there anything that can be done about this? Thanks, ~McMolar

  Posted to DotNetNuke (Forum) by McMolar on 4/7/2005

• Re: Windows Authentication for DNN3.0

  Does anyone have this module working in a non Active Directory environment? We do not have Active Directory running. The authentication module seems to mostly work, but it will not display the user name on most machines. When a users accesses the page, they are added to the users table. I have manually updated the first and last name in this table, as well as in the aspnet_profile table by updating the information in Admin - User Accounts. I only have one machine where it shows the username (it is

  Posted to DotNetNuke (Forum) by McMolar on 4/6/2005