riceflamingo
New Member
I have moved an intranet site from a server running IIS 6.0 to one running IIS 7.5. That has effectively broken the parts of the site that rely on reading the authenticated user's login info. I've already changed the application pool to use the Classic pipeline, and have enabled the ASP.NET Impersonation in the Authentication for my application. However, I'm getting 500.0 error (System.DirectoryServices.DirectoryServicesCOMException: An operations error occurred.) when I access the page.If I set the ASP.NET Impersonation to use a specific user (my domain login info), then the page works correctly. The application does a database lookup based on the username, though, so obviously that won't work as a final solution; people need to be able to see their own data.Anybody have an idea why forcing the identity works, but having the Impersonation set to "Authenticated User" doesn't?