clientaccesspolicy.xml reportservice2006.asmx
-
Wednesday, December 02, 2009 8:26 PMDoes anyone know how to answer this?
http://forums.silverlight.net/forums/t/147986.aspx
Basically when SSRS is hosted in a windows service how can I make it use a clientaccesspolicy.xml or crossdomain.xml so Silverlight app from another domain can access the service.
Answers
-
Friday, December 04, 2009 8:10 AMModerator
Hi dob_xml,
Please try the following workaround:
1.Install Internet Information Server(IIS) on the SQL Server Reporting Services server.
2.Copy these files to the root path.
The port of the SSRS is 80 which is same to IIS. The native HTTP.SYS supports port sharing for HTTP.
If you have any more questions, please feel free to ask.
Thanks,
Jin Chen
Jin Chen - MSFT- Marked As Answer by Jinchun ChenMicrosoft Employee, Moderator Wednesday, December 23, 2009 8:46 AM
All Replies
-
Friday, December 04, 2009 8:10 AMModerator
Hi dob_xml,
Please try the following workaround:
1.Install Internet Information Server(IIS) on the SQL Server Reporting Services server.
2.Copy these files to the root path.
The port of the SSRS is 80 which is same to IIS. The native HTTP.SYS supports port sharing for HTTP.
If you have any more questions, please feel free to ask.
Thanks,
Jin Chen
Jin Chen - MSFT- Marked As Answer by Jinchun ChenMicrosoft Employee, Moderator Wednesday, December 23, 2009 8:46 AM
-
Wednesday, June 22, 2011 7:51 PM
Jin,
I tried this but it still gives me the same error as below. Am I supposed to do anything else except putting the clientaccesspolicy.xml in the root IIS directory ? Please help.
An error occurred while trying to make a request to URI 'http://myserver/ReportServer/ReportService2005.asmx'. This could be due to attempting to access a service in a cross-domain way without a proper cross-domain policy in place, or a policy that is unsuitable for SOAP services. You may need to contact the owner of the service to publish a cross-domain policy file and to ensure it allows SOAP-related HTTP headers to be sent. This error may also be caused by using internal types in the web service proxy without using the InternalsVisibleToAttribute attribute. Please see the inner exception for more details.
Thanks,
Dev

