SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have some applications in Sharepoint that rely on Custom Webservices. The asmx are hosted on a specific path inside the webapplication (and not on the contentdb), and the websites were toplevel, so they worked like charm. Example url:


But we have a new application here that is not a top-level one, and we're not succeding in using it like that.

  1. It gives the following error: "The file you are attempting to save or retrieve has been blocked from this Web site by the server administrators."

  2. When I disable the limitation for ASMX on Central Administration, it gives another error:

[COMException (0x80004005): Cannot complete this action.

Please try again.] Microsoft.SharePoint.Library.SPRequestInternalClass.OpenWebInternal(String bstrUrl, ....

So it looks like that it's trying to open the dir that contains the asmx as a web.

My questions would be:

  1. Why does it work when it's top level? (even with the rule to block asmx on central administration enabled)

  2. Is there a way to make it work with this flag on central administration?

  3. Is there a way to make it work without the flag on CA?

Any kind of help appreciated.


share|improve this question
up vote 1 down vote accepted

I would suggest to drop your ASMX in the ISAPI folder of your SharePoint environment... You should access it from any SharePoint structure, because it's a virtual directory. That way, you would access it by : http://server/_vti_bin/ws.asmx ans even from http://server/subsite/_vti_bin/ws.asmx.

share|improve this answer
That's right - I believe you will need to modify the .disco and .wsdl files to support service virtualization. See – Benjamin J Athawes Dec 16 '10 at 23:11
is this strictly necessary? or just the asmx and the assembly in GAC will work ok? – Tiziani Dec 18 '10 at 15:55
It is not necessary, but highly recommended, I would say... Because those pages are quite special, you could have that kind of problems... Is there a specific reason to it that way ? – Sébastien Levert Dec 18 '10 at 16:19
as it involves a server-wide change, the less files the better (IT team of the client is very restrict regarding deploy packages). Thanks, I'll run some tests on monday. – Tiziani Dec 19 '10 at 15:02

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.