Arrgghhh where's the "Pulling Hair Out" emoticon? And if you look at my pic on the project page you'll see how useless that emoticon would really be.

I have a feeling this one is going to be a real pain to sort out as there doesn't seem to be any real rhyme or reason to it. Initially I thought it might be because of multiple portals on one install as that seemed to be the common denominator for those having problems. But now you're not having the problem on a fresh install with multiple portals but still having probs with your original production installs but only for staff accounts and not student accounts right? That right there is a reason to start beating your head against a wall (don't do it Dan, I've already done it for you. ).

I'm going to spend some time just going through this on paper and try to come up with some ways we can try to narrow down what can be done to test the broken installs against working installs.

Some additional information. I logged in with my DOMAIN\UserName and password and selected the save password. Closed my browser and estarted IIS. Browsed to the site and it generated the following error that I hope can be useful. Logging in manually still works.

AssemblyVersion: 04.05.01
PortalID: 0
PortalName: Network Control Center
UserID: 14
UserName: GA-DOMAIN\Jon.Paskett
ActiveTabID: 36
ActiveTabName: Home
RawURL: /Admin/Security/WindowsSignin.aspx?tabid=36
AbsoluteURL: /Admin/Security/WindowsSignin.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: f8b63279-d092-40a3-9968-2bd1f5de8638
InnerException: An operations error occurred.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.DirectoryServices.DirectoryEntry.Bind
StackTrace:
Message: System.Runtime.InteropServices.COMException (0x80072020): An operations error occurred. at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) at System.DirectoryServices.DirectoryEntry.Bind() at System.DirectoryServices.DirectoryEntry.get_AdsObject() at System.DirectoryServices.PropertyValueCollection.PopulateList() at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName) at System.DirectoryServices.PropertyCollection.get_Item(String propertyName) at DotNetNuke.Security.Authentication.ADSI.Domain.PopulateInfo() at DotNetNuke.Security.Authentication.ADSI.Domain..ctor(String Path) at DotNetNuke.Security.Authentication.ADSI.Domain.GetDomain(String Path, String UserName, String Password, AuthenticationTypes AuthenticationType) at DotNetNuke.Security.Authentication.ADSI.Utilities.GetRootDomain()
Source:
Server Name: SERVER01

Dan, Mike,

Shawn's fix posted in Gemini will be included in version 4.5.4. Do you suspect this is the culprit we are fighting with? If you haven't seen the post it is here: http://support.dotnetnuke.com/issue/ViewIssue.aspx?ID=5829

Jon