[Webinar] Streamline your web hosting managementRegister Today


Using Sharepoint, getting 401.3 error for crossdomain.xml file

Posted on 2010-01-11
Medium Priority
Last Modified: 2012-05-08
For an application I wrote I needed to put a crossdomain.xml file on my sharepoint site.  To do this I used sharepoint designer to copy the file into the root directory.  After that I was able to access it by typing:


I updated the file several times and suddenly IIS started giving me the error: HTTP Error 401.3 - Unauthorized: Access is denied due to an ACL set on the requested resource.

This site is a publishing site with workflow.  Though it's not giving any control with publishing files in the root directory I think it's a issue related to that.  The file is accessible through the backend of the site.  

I've tried a number of things without success.  If I delete the file I can't access it through the backend, but I get the 401.3 error on the front end.  Copying the file back in allows me to view it through the backend.  I've also tried checking the file out and back in.  I tried accessing permissions from the front end of the site as well as the backend but couldn't find any directly related to the file.  When I looked in the sharepoint error logs the only message I found related to this was:

SmtEcbMenu.TrimEcbMenu.TrimEcbMenuDocumentOperations - Trimming doc operations for 'crossdomain.xml' encountered exception: 'The object specified does not belong to a list'

I'm stumped at this point.  Any ideas on how to fix this?
Question by:marcprog
LVL 15

Accepted Solution

Tray896 earned 2000 total points
ID: 26286027
Sounds like a file permissions issue based on the error.  I would try using Process Monitor.
 Generate the error and then search the log for ACCESS DENIED.  

Alternatively you could turn on failure audits and then any permission errors would be written to the security log on your server.

Author Comment

ID: 26286462

I was able to find out that it was trying to access a crossdomain file I placed in the sharepoint root directory.  (The one IIS points to, not SPD).  I gave ISR_server user read permissions and bang... solved the problem.  I'm not sure why deleting it doesn't fix the file access through SPD's directory tree but that's something to pursue another day.


Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

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.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

We had a requirement to extract data from a SharePoint 2010 Customer List into a CSV file and then place the CSV file into a directory on the network so that the file could be consumed by an AS400 system. I will share in Part 1 how to Extract the Da…
These days socially coordinated efforts have turned into a critical requirement for enterprises.
As many of you are aware about Scanpst.exe utility which is owned by Microsoft itself to repair inaccessible or damaged PST files, but the question is do you really think Scanpst.exe is capable to repair all sorts of PST related corruption issues?
The video will let you know the exact process to import OST/PST files to the cloud based Office 365 mailboxes. Using Kernel Import PST to Office 365 tool, one can quickly import numerous OST/PST files to Office 365. Besides this, the tool also comes…
Suggested Courses

612 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question