PRB: Secure and Nonsecure Host Name Must Contain Non-Standard Port Numbers (277330)


The information in this article applies to:

  • Microsoft Commerce Server 2002
  • Microsoft Commerce Server 2000
This article was previously published under Q277330

SYMPTOMS

If an application uses non-standard ports in a site, and the application's nonsecure host name is set to myserver, when you browse to the application from http://myserver (for example, http://myserver/bizdesk for a Business Desk application), Microsoft Internet Information Server (IIS) returns a "File not found" (404) error.

CAUSE

This error occurs because the request is made to the server on the standard port, and the application uses non-standard ports. The solution sites use the Secure host name and Nonsecure host name configuration settings to build URLs.

RESOLUTION

When an application uses non-standard ports in a site, you must include the non-standard ports in the Nonsecure host name setting and, if you are using Secure Sockets Layer (SSL), in the Secure host name setting.

For example, to set the nonsecure host name for RetailBizDesk, perform the following steps:
  1. Start the Commerce Server Manager.
  2. Click to expand the Commerce Server Manager, Commerce Sites, Retail, and Applications folders.
  3. Right-click ServerName/RetailBizDesk, and then click Properties.
  4. On the General tab, in the Nonsecure host name list box, type the server name and nonstandard port in the following format:

    servername:nonstandardport

  5. Click Apply, and then click OK to save the changes.
  6. At a command prompt, type the following command to reset IIS:

    IISRESET

REFERENCES

For more information on secure and nonsecure host names, see the "Renaming an Application" topic in the Commerce Server Documentation.
Modification Type:MajorLast Reviewed:10/22/2003
Keywords:kbpending kbprb KB277330
©2003 Microsoft Corporation. All rights reserved.