Problem with Alternate Access Mapping and XML Web Services on SharePoint 2007
I have a problem with Alternate Access Mapping and XML Web Services on SharePoint 2007. I have a Data View Web Part placed on an aspx page (URL: http://servername/sitename/default.aspx) that connects to a web service (with address: http://servername/sitename/_vti_bin/usergroup.asmx?WSDL). When I access the site through http://servername/sitename/default.aspx , everything works ok. However when I enter through http://my-domain.com/sitename/default.aspx (which is added as an Alternate Access Mapping) - the data view shows an error message (on the site: "Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Windows SharePoint Services-compatible HTML editor such as Microsoft Office SharePoint Designer. If the problem persists, contact your Web server administrator." , in Sharepoint Designer: "The server returned a non-specific error when trying to get data from the data source. Check the format and content of your query and try again. If the problem persists, contact the server administrator."). Changing the connection url from absolute to relative (/sitename/_vti_bin/uservroup.asmx?WSDL) gives no effect. However changing it to http://my-domain.comsitename/_vti_bin/usergroup.asmx?WSDL makes it also unavailable on http://servername/sitename/default.aspx . Moreover, I've been unsuccessfull in connecting to web services of other web applications (i.e. from http://servername/sitename/default.aspx to http://servername:15000/sitename/default.aspx ). I'd like to make my Data View Web Part work on the http://my-domain.com address. What should I do?
August 6th, 2010 12:45pm

Make sure you add all servers you are calling from to the alternate access mapping for the application. Please notice that by security design, cross-domain calls in javascript do not carry the same credential obtained in another URI. So, if I understand your environment correctly you cannot do what you plan. The javascript would have to be downloaded from the URL you are trying to access. Adding the FQDN in all your servers in the HOST file can also help resolve the issue (for same farm calls).
Free Windows Admin Tool Kit Click here and download it now
June 2nd, 2011 6:03pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics