Solution Sites Are Not Unpackaged with the Fully Qualified Domain Name (274497)

SYMPTOMS

When you use the Commerce Site Packager to unpackage sites, the site is not accessible by using their Fully Qualified Domain Name (FQDN).

For example, if you use http://www.microsoft.com, you may not be able to access the sites, but you can access the sites by using the NetBIOS name http://myserver.

RESOLUTION

Before a site can be accessible with its FQDN, you must modify the non-secure host name by using the Commerce Server Manager in the Commerce Server Microsoft Management Console (MMC). If your site supports SSL, you need to modify the secure host name as well.

To modify the non-secure host name, perform the following steps:

Start Commerce Server Manager from Microsoft Commerce Server Program group (MMC).
Expand the Commerce Server Manager snap-in.
Expand Commerce Sites.
Expand the Commerce site that you want to modify.
Expand the Applications folder.
Select the properties for the Application.
Enter the FQDN in the Nonsecure host name text box.
Click OK, and then close the properties.
From a command prompt, run the IISRESET command to restart the Web services for the changes to take effect.

MORE INFORMATION

The Commerce Site Packager defaults the non-secure host name to the local server name. This is intended as a placeholder until an Administrator opens the MMC and types in the appropriate FQDN for the non-secure host name. The site is not meant to be available over the Internet until this change is made.