Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 633
  • Last Modified:

How can we fixe 401.2 Access Denied errors on .Net Framework 2.0 Applications?

We have several websites and Virtual Directories under the websites both external facing and internal facing.  We have begun developing in the .Net Framework 2.0. Our systems are all W2003 Server OS. Our internal applications that were developed on .Net Framework 1.1 are working fine.  The .Net 2.0 Applications are producing the 401.2 Access Denied errors.  Internal Applications are running on the same system whether it is .Net 1.1 or .Net 2.0.  We are seeing this problem in one of our testing environments. I do not see it in our Production nor Virtual Environments.  I have verified that all the settings are the same in each environment.  We are using applicaton pools for the apps, using a domain asp service account and windows integrated authentication.  In the problem environment, I had set the authentication in both the config file and IIS manager to disable the windows authentication and use anonymous.  This worked for a while, but has quit working altogether now.  Anyone have any suggestions?
0
TStechsupport
Asked:
TStechsupport
  • 2
1 Solution
 
TStechsupportAuthor Commented:
I have been able to get the application to work again.  Some of the suggestions in the articles was useful.  Final solution, removed the Virtual Directory and all files associated with it.  Verified that IE was not set for "Enable Windows Authentication", re-deployed the Virtual Directory and files. verified that Windows Integrated was set for the VD Security.  All seems to be working again. Thanks for the assistance.
0
 
TStechsupportAuthor Commented:
I have been able to get the application to work again.  Some of the suggestions in the articles was useful.  Final solution, removed the Virtual Directory and all files associated with it.  Verified that IE was not set for "Enable Windows Authentication", re-deployed the Virtual Directory and files. verified that Windows Integrated was set for the VD Security.  All seems to be working again. Thanks for the assistance.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now