Troubleshooting: Authentication Settings in IIS for SDL Tridion / SDL Tridion 2013 Web Application
- Access IIS -> Sites -> SDL Tridion 2013 under Features view find Authentication and ensure Windows Authentication alone is enabled
- Access IIS -> Sites -> SDL Tridion 2013 -> webdav under Features view find Authentication and ensure Basic Authentication and Windows Authentication is enabled
- Access IIS -> Sites -> SDL Tridion 2013 -> webservice under Features view find Authentication and ensure Windows Authentication and Anonymous Authentication is enabled.
On the Authentication page, select Anonymous Authentication. In the Actions pane, click Edit to confirm the security principal used for anonymous access.
Could you also check & confirm the permissions of the SDL Tridion web application root path & ensure following permissions exists on the folder:
NETWORK SERVICE (Modify, Read & Execute, List Folder Contents, Read, Write)
IIS_IUSRS (Modify, Read & Execute, List Folder Contents, Read, Write)

1. Identify accounts that could not be resolved to a SID:
From the command prompt, type: FIND /I "Cannot find" %SYSTEMROOT%\Security\Logs\winlogon.log
The string following "Cannot find" in the FIND output identifies the problem account names.
Example: Cannot find JohnDough.
In this case, the SID for username "JohnDough" could not be determined. This most likely occurs because the account was deleted, renamed, or is spelled differently (e.g. "JohnDoe").
2. Use RSoP to identify the specific User Rights, Restricted Groups, and Source GPOs that contain the problem accounts:
a. Start -> Run -> RSoP.msc
b. Review the results for Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment and Computer Configuration\Windows Settings\Security Settings\Local Policies\Restricted Groups for any errors flagged with a red X.
c. For any User Right or Restricted Group marked with a red X, the corresponding GPO that contains the problem policy setting is listed under the column entitled "Source GPO". Note the specific User Rights, Restricted Groups and containing Source GPOs that are generating errors.
3. Remove unresolved accounts from Group Policy
a. Start -> Run -> MMC.EXE
b. From the File menu select "Add/Remove Snap-in..."
c. From the "Add/Remove Snap-in" dialog box select "Add..."
d. In the "Add Standalone Snap-in" dialog box select "Group Policy" and click "Add"
e. In the "Select Group Policy Object" dialog box click the "Browse" button.
f. On the "Browse for a Group Policy Object" dialog box choose the "All" tab
g. For each source GPO identified in step 2, correct the specific User Rights or Restricted Groups that were flagged with a red X in step 2. These User Rights or Restricted Groups can be corrected by removing or correcting any references to the problem accounts that were identified in step 1