Troubleshooting

 

Downloading WSDL - Wrong Host Name

WSDL contains URLs that link to schema information that describes eBusiness Web Services. Internet Information Services uses the full computer name of the server hosting eBusiness Web Services as the host name in these URLs. When the full computer name does not match the common name on the SSL certificate, or when the full computer name is not accessible from the internet, WSDL will fail to download.

This issue can be diagnosed by checking the host name returned by Internet Information Services. Point a browser to https://<host name>/<virtual directory>/<entry point>.

For example:
https://www.sage.com/ebusinesswebservices/masservice.svc

An informational page is displayed that contains a line similar to the following:

svcutil.exe https://www.sage.com/eBusinessWebServices/
MasService.svc?wsdl

When the host name on the informational page’s URL is incorrect, the issue can be resolved by changing the full computer name of the server hosting eBusiness Web Services. If the full computer name cannot be changed, then SSL host headers can be used to resolve the issue.

Setting SSL Host Headers

The SSL host headers for Internet Information Services 8 can be set through the Bindings settings for the web site using Internet Information Services Manager. Internet Information Services version 6 and 7 do not allow SSL host headers to be set from the Internet Information Services Manager; therefore, special steps must be performed.

Internet Information Services 7

SSL host headers may be set by using notepad to edit applicationHost.config located in %windir%\System32\inetsrv\config. A backup copy of the applicationHost.config should be made before editing.

To set SSL host headers for the web site

Set the bindingInformation attribute for the web site’s https protocol by adding the proper host name after the SSL port number. Add a colon
( : ) between the port number and host name.

For example:

<site name="Default Web Site" id="1">

<application path="/">

<virtualDirectory path="/" physicalPath="%SystemDrive%\inetpub\wwwroot" />

</application>

<application path="/eBusinessWebServices" applicationPool="eBusinessWebServices" enabledProtocols="https">

<virtualDirectory path="/" physicalPath="C:\Sage\eBusiness Web Services" />

</application>

<bindings>

<binding protocol="http" bindingInformation="*:80:" />

<binding protocol="https" bindingInformation="*:443:www.sage.com" />

</bindings>

</site>

Downloading WSDL - XSD not Available

The WSDL download can fail while downloading an XSD file.

To diagnose this issue

1. Verify that the issue is not a wrong host name. For more information, see Downloading WSDL - Wrong Host Name.
2. Verify that the main WSDL page can be read by pointing a browser to:

   https://<host name>/<virtual directory>/<entry point>?wsdl

   For example:

   https://www.sage.com/ebusinesswebservices/masservice.svc?wsdl

3. Verify that the XSD fails to display by pointing a browser to:

   https://<host name>/<virtual directory>/<entry point>?xsd=xsd0

   For example:

   https://www.sage.com/ebusinesswebservices/masservice.svc?xsd=xsd0

   If all three items above are true, restart Internet Information Services. If the issue still occurs, change the permissions for the %windir%\Temp directory to Full Control for the eBusiness Web Services user account, and restart Internet Information Services.

Error 404 with Internet Information Services (IIS) version 6

Under certain conditions, when eBusiness Web Services is installed in Internet Information Services version 6, web services calls may fail and the entry point will display an error 404 when accessed from a browser. For example:

https://www.sage.com/ebusinesswebservices/masservice.svc

To correct the error 404

1. Ensure that the ASP.NET v4.0.30319 web service extension is set to Allowed.

   Allow the ASP.NET v4.0.30319 Web Service Extension through Internet Information Services Manager.

2. If the ASP.NET v4.0.30319 web services extension is not listed, install it by running the following command from the command prompt:

   %windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis -i

3. Restart Internet Information Services after issuing the above command.
4. Verify that the ASP.NET v4.0.30319 is the ASP.NET version specified for the eBusiness Web Services application.

   In Internet Information Services Manager, right-click the eBusiness Web Services virtual directory, click Properties, and then click the ASP.NET tab.

Could Not Load Type "System.ServiceModel.Activation.HttpModule" in IIS 7

Under certain conditions, when eBusiness Web Services is installed in Internet Information Services version 7, web services calls may fail and the entry point will display an error referencing System.ServiceModel.Activation.HttpModule when accessed from a browser.

To correct the error

Run the following command from the command prompt using administrative privileges:

%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis –i

General Errors

An error that occurs in eBusiness Web Services, but does not occur when accessing the same data directly from the Sage 100 system, may be caused by a permissions issue.

The most common permissions issue occurs when an alternate data directory is created after eBusiness Web Services is installed. The eBusiness Web Services user account must explicitly be given full control to the alternate directory. For more information, see Permissions.

Internet Information Services (IIS) must be restarted after correcting permissions issues.