Error: 401.3 even with Full Control NTFS permission to Everyone

Background info:

401.3 error: Unauthorized Due to ACL on Resource

Hi,

I am running into a weird problem. I have a web farm setup with 4 frontend
servers, 2 win2k and 2 win2k3. Last night, the 2 win2k3 servers all of a
sudden started producing this 401.3 error (login box poped up, entered
credential, and got the error).

I then went into the servers to see permission settings for IIS and NTFS and
event viewer, and found no suspicious hacking attempts nor any wrong
permission setting. Whatever I tried (like change the account IIS application
runs as), it just wouldn't work. I then grant Everyone Full Control to the
home directory just to make sure it works with the least restriction ->
again, it didn't help. It just kept throwing this 401.3 error.

I fully understand how 401.3 differs from other 401 errors, and I had never
had to deal with this problem with so much efforts. I think it is probably
something else that manifested as 401.3.

My Win2k3 has SP1 applied with all Windows Update patches applied.
Therefore, this article does not apply:

http://support.microsoft.com/default.aspx?scid=kb;en-us;832911

Thanks for your help in advance!

v-garych
Wed May 03 01:32:29 CDT 2006

Hi,

Thank you posting!

This is a quick note to let you know that I am performing research on this
issue and will get back to you as soon as possible. I appreciate your
patience.

Thanks for your understanding.

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Jeethu
Wed May 03 11:54:14 CDT 2006

Hi,
Why dont you try to trace it using the filemon tool available
from http://sysinternals.com . You can see infact if there is any file
restrictions in access
you can also use Regmon for monitoring registry.Check out the Access
denieds in the log files !!!

Thanks
Jeethu Joseph
IIS/Asp.Net Engineer Microsoft

programmer
Wed May 03 12:38:02 CDT 2006

It turned out to be a Cold Fusion problem. Once I gave proper permission to
the cold fusion user on the cold fusion mx folder on the same drive the
problem went away.

The reason it happened around a day after I made the permission change to
the D drive is because the WPG process cached the permission for around 29
hours or so after the change was made. this is why both servers likely blew
up about a day after and just a couple hours apart.