Last updated May 2008.

This readme contains important updates and information about Microsoft® Commerce Server 2007 Service Pack 2 (SP2). Because Commerce Server 2007 SP2 is an update to Commerce Server 2007 and is not a stand-alone release, this document does not duplicate the information that is contained in the readme for Commerce Server 2007 (http://go.microsoft.com/fwlink/?LinkID=79888) and the readme for Commerce Server 2007 SP1 (http://go.microsoft.com/fwlink/?LinkID=120249). The information in these readmes still applies unless otherwise stated.

This Readme contains instructions for installing and removing Commerce Server 2007 SP2, a list of issues that Commerce Server 2007 SP2 fixes, and known issues with Commerce Server 2007 SP2.

In This Document

Installation Instructions

Use the appropriate procedure for the operating system to install Commerce Server 2007 SP2.

Notes about the SP2 installation:

  • Commerce Server 2007 SP2 includes updated binaries in English only. Each business management application that Commerce Server 2007 provides is available in English only. This does not affect your ability to develop a multilingual Commerce Server Web site.

  • We do not support the installation of Commerce Server 2007 SP2 on non-English versions of Commerce Server 2007.

  • After the installation of SP2 is complete, the account that was used to start the Commerce Server Staging service will be reset to NT Network Service. Follow the instructions in step 24 in the following section to set it back to its original value.

  • If you install SP2 on a computer that is a member of a domain, the computer must be connected to the domain during the installation process.

  • The release version of Commerce Server 2007 and Commerce Server 2007 Service Pack 2 (SP2) can be run on Windows Server 2008, with Internet Information Service (IIS) 7.0.

  • To install Commerce Server 2007 SP2 in a multiple computer environment, you can take the Web servers out of the Web farm one at a time and update them one by one. Do not update the databases until after you have updated the last Web server. Alternatively, you can update the databases after you have updated half of the Web servers.

To install Commerce Server 2007 SP2 on Microsoft Windows Server 2003 and Microsoft Windows XP
  1. Follow the instructions to install Commerce Server 2007. You can download the installation instructions from http://go.microsoft.com/fwlink/?LinkID=79888. If you install the Developer Edition of Commerce Server 2007, you can follow the simpler installation instructions that you can download from http://go.microsoft.com/fwlink/?LinkID=79888. If you are installing the full Commerce Server 2007 product and not only the business management applications, do not configure Commerce Server 2007 or install the CSharpSite at this point.

  2. Download SP2 and extract the files. For Commerce Server 2007 SP2 Enterprise Edition, see http://go.microsoft.com/fwlink/?LinkID=120270. For the SP2 Standard Edition, see http://go.microsoft.com/fwlink/?LinkID=120269.

  3. Back up the catalog, marketing, and marketing lists databases for all Commerce Server sites. This includes the CSharpSite or Starter Site.

  4. If Commerce Server Staging is installed, make a copy of all registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CSS to use if you uninstall SP2. For instructions about how to back up the registry keys, see http://go.microsoft.com/fwlink/?LinkID=93198.

  5. Double-click the file SP2setup.exe in the folder to which you extracted the files.

    Note
    The installation wizard will install the pieces of SP2 for the pieces of Commerce Server 2007 that are installed on the computer. If you have not installed the Business Management applications, for example, the Business Management application pieces of SP2 will not be installed. Install all pieces of Commerce Server 2007 that you will use before you install Commerce Server 2007 SP2.

  6. On the Welcome page, click Next.

  7. Accept the license agreement, and then click Next.

  8. Click Next to continue the installation.

  9. A dialog box that lists the services that will be stopped might appear. Click OK to accept the services being stopped.

    Important
    Installing Commerce Server 2007 SP2 will stop any Web applications that are running on the computer. If this is unacceptable, click Cancel and schedule another time to install Commerce Server 2007 SP2.

  10. If a message that Commerce Server was unable to create a registration marker in Active Directory appears, click OK. The absence of a registration marker does not affect Commerce Server.

  11. If you are installing SP2 on a computer that has only the Commerce Server business management applications or the Commerce Server Adapters for BizTalk Server, click Finish and skip steps 11 through 23.

  12. If you are installing SP2 on a computer that already has Commerce Server sites, make sure that Launch Commerce Server Upgrade Wizard is selected, and then click Finish. The Commerce Server upgrade wizard starts. The upgrade wizard migrates catalog and marketing data to the new database format.

  13. On the Welcome page of the Commerce Server 2007 upgrade wizard, click Next.

  14. On the Select Options page, either accept the default location for the log file or enter a new location, and then click Next.

  15. Select the Commerce Server site whose data you want to migrate.

    Note
    You can only migrate the data for one site at a time. To migrate data for more than one site, rerun the upgrade wizard.

  16. On the Upgrade Site Resources page, select the Product Catalog resource, and then select the Migrate action.

  17. Select the Marketing resource, and then select the Migrate action.

  18. Click Next.

  19. On the Upgrade Summary page, click Next.

  20. When the upgrade is complete, click Next.

  21. On the Summary page, click Next.

  22. Click Finish.

  23. To migrate another site, click Start, point to All Programs, point to Microsoft Commerce Server 2007, point to Tools, and then click Upgrade Wizard. Repeat steps 11 through 20 to run the upgrade wizard.

  24. If you installed Commerce Server Staging, the account that was used to start the service will be reset to NT Network Service after SP2 installation is complete. You will have to change it to its previous value by rerunning the Commerce Server Configuration Wizard. Rerunning the Commerce Server Configuration Wizard will also set the default authentication account to the service account. If the previous default authentication account was different from the service account, change it to its previous value by using the MMC snap-in. Rerun the Commerce Server Configuration Wizard by typing the following line in a Command Prompt window and following the instructions in the wizard:

    "%commerce_server_root%\CSConfig.exe" /r Feature.MS.CS.CsStaging
To install SP2 for Commerce Server 2007 on Windows Vista or Windows Server 2008
  1. Follow the instructions to install Commerce Server 2007. You can download the installation instructions from http://go.microsoft.com/fwlink/?LinkID=79888. If you install the Developer Edition of Commerce Server 2007, you can follow the simpler installation instructions that you can download from http://go.microsoft.com/fwlink/?LinkID=79888. If you are installing the full Commerce Server 2007 product and not only the business management applications, do not configure Commerce Server 2007 or install the CSharpSite at this point.

  2. Download SP2 and extract the files. For Commerce Server 2007 SP2 Enterprise Edition, see http://go.microsoft.com/fwlink/?LinkID=120270. For the SP2 Standard Edition, see http://go.microsoft.com/fwlink/?LinkID=120269.

    Important
    During the installation process the Commerce Server Configuration Wizard may appear. Run the wizard to proceed with the installation.

  3. Double-click SP2setup.exe in the folder to which you extracted the files.

    Note
    The installation wizard will install SP2 for the installed components of Commerce Server 2007. If you have not installed the Business Management applications, for example, the Business Management applications of SP2 will not be installed. Install all parts of Commerce Server 2007 that you will use before you install SP2 for Commerce Server 2007.

  4. In the User Account Control dialog box, click Allow.

  5. On the Welcome page, click Next.

  6. Accept the license agreement, and then click Next.

  7. Click Next to continue the installation.

  8. A dialog box that lists the services that will be stopped might appear. Click OK to accept the services being stopped.

    Important
    Installing Commerce Server 2007 SP2 will stop any Web applications that are running on the computer. If this is unacceptable, click Cancel and schedule another time to install Commerce Server 2007 SP2.

  9. If a message that Commerce Server was unable to create a registration marker in Active Directory appears, click OK. The absence of a registration marker does not affect Commerce Server.

  10. If an option to start the Commerce Server Configuration Wizard is displayed when the installation wizard finishes, make sure that the option is selected, and then click Finish.

  11. If you will not use Commerce Server 2007 to develop a site, skip the rest of this procedure.

  12. If you want to develop a Commerce Server site, follow the installation instructions for Commerce Server 2007 to configure Commerce Server 2007 and install the CSharpSite.

Registering Commerce Server 2007 Help with Visual Studio 2008

Microsoft Visual Studio 2008 may not automatically detect the contents of Commerce Server 2007 Help. If not, use the following procedure to display Commerce Server 2007 Help in Visual Studio 2008.

To display Commerce Server 2007 Help in Visual Studio 2008
  1. In Visual Studio 2008, from the Help menu, click Index.

    Document Explorer opens.

  2. In the Filtered By drop-down list, click unfiltered.

  3. In the Look for box, type Collection Manager.

  4. Below the Collection Manager heading, double-click Help.

  5. Below the Collections available for inclusion in VSCC heading, select Commerce Server Documentation.

  6. Click Update VSCC.

  7. Restart Visual Studio if you are prompted to do so.

Removing Commerce Server 2007 SP2

Use the appropriate procedure for the operating system to remove Commerce Server 2007 SP2.

To remove Commerce Server 2007 SP2 from Microsoft Windows Server 2003 or Microsoft Windows XP
  1. Click Start, point to Settings, and then click Control Panel. (On Microsoft Windows XP, click Start, and then click Control Panel.)

  2. In Control Panel, double-click Add or Remove Programs.

  3. In the Add or Remove Programs window, select the Show Updates checkbox, then select Microsoft Commerce Server 2007 SP2, and then click Change/Remove.

  4. Click OK to confirm that you want to uninstall Commerce Server 2007 SP2.

  5. Restore the backups of the catalog and marketing databases that you created when you installed Commerce Server 2007 SP2.

  6. When you remove Commerce Server 2007 SP2, the value of the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Commerce Server 2007\UnsafeAuthenticatedConnectionSharing registry key is set to 0 (zero). If you changed the value of this registry key, reset it to its previous value.

  7. If you installed Commerce Server Staging, the values of all registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CSS are set to their default values. Reset these registry keys to their previous values by following the instructions at http://go.microsoft.com/fwlink/?LinkID=93198. After resetting these keys, rerun the Commerce Server Configuration Wizard by typing the following line in a Command Prompt window and following the instructions in the wizard:

    "%commerce_server_root%\CSConfig.exe" /r Feature.MS.CS.CsStaging 
To remove Commerce Server 2007 SP2 from Windows Vista or Windows Server 2008
  1. Click Start, and then click Control Panel.

  2. In Control Panel, click Uninstall a Program. (Double-click Programs and Features if you are using the classic view.)

  3. In the Programs and Features window, select the View installed updates option, then right-click Microsoft Commerce Server 2007 SP2, and then click Uninstall/Change.

  4. In the User Account Control dialog box, click Continue.

  5. Click OK to confirm that you want to uninstall Commerce Server 2007 SP2.

Note
If you uninstall SP2 without uninstalling Commerce Server 2007, firewall settings modified by SP2 are not automatically rolled back to their original settings. This issue does not occur if the entire Commerce Server 2007 application is uninstalled (which also removes all service packs).

Fixed Issues

This release of Commerce Server 2007 SP2 fixes the following issues:

List of fixed issues in SP2

For a list of fixed issues in Commerce Server 2007 SP2, see http://go.microsoft.com/fwlink/?LinkID=120248.

Data Warehouse resource fails to unpack on SQL Server 2008 Express CTP

When attempting to unpack the Data Warehouse resource on SQL Server 2008, you may receive the following error in the PuP log file:

"Failed to create olapStore schema.[timestamp] Error: Could not create the global resource. This error may occur because a global resource with the same name already exists. See the trace information (above) for more details."

Note
This issue applies only to SQL Server 2008 Express CTP.

To resolve this problem, you must install the redistributable client components for SQL 2005 Service Pack 2, Cumulative Update 6 or later. You can get the components from http://go.microsoft.com/fwlink/?LinkID=114099.

You must install the redistributable components in the following order:

  1. Microsoft SQL Server Native Client (sqlncli.msi)

  2. Microsoft SQL Server 2005 Management Objects Collection (SQLServer2005_XMO.msi)

  3. Microsoft ADOMD.NET (SQLServer2005_ADOMD.msi)

Known Issues

This release of Commerce Server 2007 SP2 contains the following known issues:

Commerce Server 2007 SP1 hotfix KB 952150 requires SP2 QFE hotfix

If you installed Commerce Server 2007 SP1 and are upgrading to SP2, and you installed hotfix KB 952150 for SP1, you will have to install the corresponding QFE hotfix for SP2, otherwise you will encounter problems similar to those that were fixed by the SP1 hotfix. For more information, contact your Microsoft support representative. For information about the SP1 hotfixes, see http://go.microsoft.com/fwlink/?LinkID=118781.

Default documents setting does not get copied when staging from IIS 7.0 to IIS 7.0 or from IIS 7.0 to IIS 6.0

The Commerce Server Staging (CSS) System relies on the IIS metabase to get all the Web site's information before staging that information to the destination server. When setting the default document in IIS 7.0 by using either the IIS Manager or appcmd.exe, the default document's information isn't copied over to the metabase. When CSS tries to query for it, some or all of the default documents are missing. This results in the destination server either missing default documents, or routing to the server's defaults (default.htm, default.asp, default.aspx, and so on).

There are two possible solutions:

  1. Stage the site(s) as is, and then manually add the missing default documents to the destination servers.

  2. Use the following example script to copy all default documents from ABO to the metabase by using the IIS 7.0 APIs, and then update the metabase by using adsutil.vbs before staging. After running the example code, when CSS pulls information from the metabase, the default documents will be available:

    Note
    This example code and could potentially not work on all setups. You should be aware of what the code is doing, and modify it if necessary to fit your business needs.

    using System;
    using System.Collections.Generic;
    using Microsoft.Web.Administration;
    using System.IO;
    
    
    namespace IIS7ConfigToMetabase
    {
        class Program
        {
            private const string Usage = @"Usage:  IIS7ConfigToMetabase <sitename>
        <sitename> : the name of the site for which the default documents setting should be committed to the legacy IIS6 metabase.
    ";
    
            static void Main(string[] args)
            {
                if (args.Length != 1)
                {
                    Console.WriteLine(Usage);
                    return;
                }
    
                string siteName = args[0];
                string adsUtilPath = Path.Combine(
                    Path.GetPathRoot(Environment.SystemDirectory),
                    "inetpub\\adminscripts\\adsutil.vbs");
    
                if (!File.Exists(adsUtilPath))
                {
                    Console.WriteLine("Error:  could not locate the file {0}", adsUtilPath);
                    return;
                }
    
                ServerManager iisManager = new ServerManager();
                // Replace the "Default Web Site" with the appropriate value for your website.
                // Sites[] also allows you to specify the site's ID.
                Configuration config = iisManager.Sites[siteName].GetWebConfiguration();                        
                ConfigurationElementCollection documents = config.GetSection("system.webServer/defaultDocument").GetCollection("files");
    
                // Exit if this site does not have custom default documents.
                if (documents.Count == 0)
                {
                    Console.WriteLine("No custom default documents setting to commit.");
                    return;
                }
    
                //Create a list to temporaraly store the default docs
                List<string> myDocuments = new List<string>();
    
                // Iterate through the default documents and add them to the list.
                foreach (ConfigurationElement doc in documents)
                {
                    myDocuments.Add((string)doc["value"]);
                }
    
                // Empty IIS default documents to not cause any conflicts when
                // re-adding them in adsutil.vbs
                documents.Clear();
                iisManager.CommitChanges();
    
                //Get the website's ID to input in adsutil.vbs' arguments.
                string siteID = iisManager.Sites[siteName].Id.ToString();
    
                //Build a string that will be given as an argument for adsutil.vbs.
                string arguments = string.Format(
                    "{0} set w3svc/{1}/DefaultDoc \"{2}\"",
                    adsUtilPath,
                    siteID,
                    string.Join(",", myDocuments.ToArray()));
    
                //Finally, add the default documents to the metabase using adsutil.vbs
                System.Diagnostics.Process proc = new System.Diagnostics.Process();
                proc.StartInfo.FileName = "cscript.exe" ;
                proc.StartInfo.UseShellExecute = true;
                proc.StartInfo.RedirectStandardOutput = false;
                proc.StartInfo.Arguments = arguments;
                proc.Start();            
                proc.WaitForExit();
    
                //Reset the servermanager
                config = iisManager.Sites[siteName].GetWebConfiguration();
                documents = config.GetSection("system.webServer/defaultDocument").GetCollection("files");
    
                //Re-add the default documents to IIS7 configuration.
                ConfigurationElement ce = null;
                foreach (string defaultdoc in myDocuments)
                {
                    ce = documents.CreateElement();
                    ce["value"] = defaultdoc;
                    documents.Add(ce);
                }            
                iisManager.CommitChanges();
    
                Console.Write("Done.");
            }
        }
    }
    

Issue with metabase staging between IIS 6.0 and IIS 7.0

The Commerce Server Staging System uses IIS 6.0 metabase compatibility components to configure IIS 7.0. This can result in the creation of legacy metabase keys at the site level in the IIS 7.0 applicationHost.config file, under the customMetadata element. A known issue in IIS 7.0 prevents the site-level customMetadata element from being deleted when the site is deleted through IIS Manager. The next time the IIS 6.0 metabase compatibility components are used to change IIS settings, these orphaned customMetadata elements will cause new sites to be created, named "SITE_N" where N is the site ID. These sites pose no risk and are not needed.

If you remove the orphaned customMetadata elements after you delete the site through IIS Manager, the sites created by this issue will not appear. You can use the following script to remove all orphaned customMetadata elements:

' VBScript source code
Option Explicit

Call Main()

Sub Main
       Dim adminManager, sitesSection, customMetadataSection
       Set adminManager = CreateObject("Microsoft.ApplicationHost.WritableAdminManager")
       
       Set sitesSection = adminManager.GetAdminSection("system.applicationHost/sites", "MACHINE/WEBROOT/APPHOST")
       Set customMetadataSection = adminManager.GetAdminSection("system.applicationHost/customMetadata", "MACHINE/WEBROOT/APPHOST")
       
       Dim i, path
       For i = (CInt(customMetadataSection.Collection.Count)) - 1  To 0 Step -1
              path = customMetadataSection.Collection.Item(i).Properties.Item("path").StringValue
           
              'Make sure it starts with "LM/W3SVC/"
              If (Len(path) > 9) Then
                     if Mid(path, 1, 9) = "LM/W3SVC/" AND IsNumeric(Mid(path, 10, 1)) Then
                           Dim siteID
                           siteID = Val(Mid(path, 10))
                           If FindSite(sitesSection.Collection, siteID) = -1 Then
                              customMetadataSection.Collection.DeleteElement(i)
                           End If
                     End If
              End If
       Next
       
       adminManager.CommitChanges()
End Sub

Function Val(data)
   Dim i
   For i = 1 To Len(data)
      if (Not IsNumeric(Mid(data, i, 1))) Then
                     Exit For
      End If
   Next
   Val = CInt(Mid(data, 1, i - 1))
End Function

Function FindSite(collection, siteID)
    FindSite = -1
    
    Dim i, element
    For i = 0 To CInt(collection.Count) - 1
              Set element = collection.Item(i)
       if (CInt(element.Properties.Item("id").Value) = siteID) Then
           FindSite = i
           Exit Function
       End If
    Next
End Function

Timezonereference.sql file not run automatically after installing SP2

After you update to SP2, the timezonereference.sql file does not automatically run against your existing Data Warehouse. This causes a miscalculation in times on Data Warehouse activities. You must run the timezonereference.sql file manually. The file is located in the root folder of the Commerce Server 2007 directory.

SP2 MSI installer issue

When you try to install Commerce Server 2007 SP2 on a computer that has certain Commerce Server 2007 SP1-based hotfixes installed, the SP2 installation fails and backs out any SP2 changes. To resolve this issue, uninstall any Commerce Server 2007 SP1 hotfixes prior to installing SP2. You may also obtain the CS2007SP1QFERemover.exe tool by opening a PSS Support case with the Commerce Server Support team. The CS2007SP1QFERemover will automatically uninstall any SP1 hotfixes to establish a clean environment so you will be able to install SP2 successfully. For more information, see http://go.microsoft.com/fwlink/?LinkID=120773.

Windows Server 2008 logo certification issues

Commerce Server 2007 is now certified for and supported on Microsoft Windows Server 2008. You can run the release version of Commerce Server 2007 and Commerce Server 2007 Service Pack 2 (SP2) on Windows Server 2008, with Internet Information Service (IIS) 7.0 configured to Classic mode.

The following Microsoft Knowledge Base articles identify Windows Server 2008 Logo Certification issues with Commerce Server 2007, Commerce Server 2007 SP1, and Commerce Server 2007 SP2. None of the Windows Server 2008 Certification issues cause operational problems or failures in Commerce Server 2007:

-----------------------------------------------------------------------------------------------

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2008 Microsoft Corporation. All rights reserved.

Microsoft, Commerce Server, BizTalk, Visual Studio, Windows, Windows Vista, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

All other trademarks are property of their respective owners.