Before you can use Web Parts, you must enable the Channel Configuration feature, and specify a default catalog and channel name. The following procedures provide instruction about how to enable the Channel Configuration feature when using WSS or MOSS.

Features in Commerce Server 2009 require Microsoft .NET Framework 3.5 Service Pack 1. Therefore, development with Visual Studio requires Visual Studio 2008 with Service Pack 1.

The SharePoint Commerce Services Configuration Wizard runs Commerce Server Site Packager to create a Commerce Server site for the SharePoint Default site. When the SharePoint Commerce Services Configuration Wizard runs Site Packager, it checks the process exit status code. If Site Packager encounters any problems, it returns -1 and the SharePoint Commerce Services Configuration Wizard then stops processing.

To troubleshoot this issue, see the Site Packager log, usually stored in C:\pup.log. The log file will show the "Exit status code for this session: -1" message. You can see a more descriptive error message higher in the log file. Clear the error, and run the SharePoint Commerce Services Configuration Wizard again.

In some cases, the problem may be benign, for example, a problem with IIS. Site Packager looks at IIS and sets the error status if there is a problem, but that would not prevent the SharePoint Commerce Services Configuration Wizard from creating the site because it does not deploy any Web applications (such as the Web services) that require IIS services.

Commerce Server 2009 does not support, but does not prohibit, the use of Microsoft Windows Communication Foundation (WCF).

If you choose not to use SharePoint (WSS or MOSS), you can only conduct catalog searches. If you use SharePoint, you can conduct content searches.

As recommended by the Payment Card Industry (PCI) Security Standards Council (SSC), the persistence of the CreditCardPayment.ValidationCode property has been disabled by default in Commerce Server 2009. If you require this property to be persisted for Commerce Server 2007 parity, it can be added.

All Commerce Server sites need a way to identify the encryption keys that will be used to encrypt and decrypt sensitive data, for example, credit card numbers. The Commerce Server site configuration will look for these keys in the registry. The tool that manages the creation and loading of the keys is the ProfileKeyManager.exe.

When you use the SharePoint Commerce Services Configuration Wizard to create a Commerce Server site, the wizard will create a key pair and load the pair into the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Commerce Server 2007 Keys\SiteName; where SiteName is the name of the Commerce Server site that you have either selected or that you want to create as your default site. Note that the SharePoint Commerce Services Configuration Wizard will create the key pair and store the keys in a file called ProfileKeys_SiteName.key under Site directory under the Commerce Server 2009 install folder.

It is a good security practice to keep the key file in a safe place. You will use the key file with the ProfileKeyManager.exe tool to load the keys into the registry for other nodes of a farm since the SharePoint Commerce Services Configuration Wizard does not do this for Web farms.

To use the Project Creation Wizard in Visual Studio 2008, you must register it.

To use Microsoft.SharePoint.ApplicationPages.dll, you must add a reference to it. Use the following procedure to add the reference.

If you want to build the SharePoint Commerce Services Extensibility Kit in an environment where WSS is installed, see the procedures in "Using the SharePoint Commerce Services Extensibility Kit with WSS" in the Commerce Server 2009 Installation and Configuration Guide at http://go.microsoft.com/fwlink/?LinkID=139462.

Developers can easily modify the validation expression for a phone number format. In the following example from the user control Billing.ascx, it is set to "[-() 0123456789]{6,20}". When changed, you do not need to restart the Web application; the new validation expression will be active immediately after saving the user control.

.
.
.
<td>
      *&nbsp;<asp:Label ID="lblContactPhone" runat="server" Text="<%$ Resources:OrderResources, ContactPhone %>"></asp:Label>
</td>
<td>
      <asp:TextBox ID="txtContactPhone" runat="server" MaxLength="50" />
</td>
<td>
      <asp:RequiredFieldValidator ID="RequiredFieldValidator1" runat="server" ControlToValidate="txtContactPhone"
      ErrorMessage="<%$ Resources:OrderResources, ContactPhone_Required %>" Display="Dynamic" Text="*" ValidationGroup="Billing" Enabled='<%# radioEnter.Checked %>'>
</asp:RequiredFieldValidator>
<asp:RegularExpressionValidator ID="PhoneNumberFormatValidator" runat="server" ControlToValidate="txtContactPhone" ValidationExpression="[-() 0123456789]{6,20}"  
      ErrorMessage="<%$ Resources:OrderResources, ContactPhone_Invalid %>" Display="Dynamic" Text="*" ValidationGroup="Billing" Enabled='<%# radioEnter.Checked %>'/>
</td>
.
.
.

Commerce Server 2009 has a restriction to make sure that only one Product Query or Product Provider Web Part is on the Web site page at a time. If you want to add more than one, use the Extensibility Kit to remove the restriction. Open the Extensibility Kit and navigate to UI\Catalog\WebParts\ProductQuery\ProductQuery.cs to find the ThereIsOnlyOneProductProvider() method. You can modify this method to remove or alter the restriction.

When you use the SharePoint Commerce Services Configuration Wizard with Windows SharePoint Services (WSS) and Microsoft Search Server 2008, during the configuration process you may notice during the dependency check that a warning icon is displayed on the "Check for SharePoint Search Service". This dependency check only examines the state of the local SPSearch service and does not take into account the state of the Microsoft Search Server 2008 service state. You may ignore this warning. The configuration will continue successfully, following the standard installation instructions.  

In SharePoint, multilingual Web sites are created by using site variations. A site variation is created for each language that is to be supported.  SharePoint will re-direct a shopper to the appropriate site variation based on the shopper's browser language setting. The URL of pages in a site variation are slightly different. Each site variation has its own unique Commerce Server document library, which means they will have their own XSLTs. The site variation name is added as a prefix to the "Pages/" part of the URL. For example, the URL of a product page normally looks like this:

http://<server name>/Pages/Product.aspx?category=Boots&cat=Adventure Works Catalog&id=AW074-04

And on a Japanese site variation:

http://<server name>/Japanese/Pages/Category.aspx?cat=Adventure%20Works%20Catalog&category=Boots

Each site variation has a copy of Web Part templates. You must edit these templates and modify any XSLT that renders URLs. Modify the XSLT to add the site variation prefix.

For the Commerce Server 2009 sample reports to correctly work with SQL Server Reporting Services (SSRS) 2008, you must upgrade the report files (RDL files). To upgrade the reports, open them using SQL Server Business Intelligence Development Studio 2008. The report files are located in the C:\<Commerce Server root>\RDLs folder. You can then upload the upgraded reports to the server using the Report Manager or rs.exe utility. You must also create data sources to connect the reports to the required SQL Server Analysis Server. Consult the SQL Server 2008 documentation for detailed instructions.

If you had the Commerce Server 2007 SP2 Business Applications installed prior to installing Commerce Server 2009, the uninstall process for Commerce Server 2009 reverts these applications to file versions from SP1, not SP2. To restore them to the SP2 version, rerun the Commerce Server 2007 SP2 setup.

When attempting to uninstall the Default Site and the Web Parts by using the command line syntax "SharePointCommerceServicesConfiguration.exe –u", you may get the following error message:

Error: Cannot remove the specified assembly from the global assembly cache: [Assembly].dll.

You get this error because the SharePoint Services Timer (OWSTimer.exe) job has a lock on the assembly that prevents SharePoint from removing the assembly from the GAC. Use the following steps to solve this issue:

1. Click Start, point to Administrative Tools, and then click Services.
   
   
2. Navigate to Windows SharePoint Services Timer and restart it
   
   
3. Run "SharePointCommerceServicesConfiguration.exe –u" again.
   
   
4. Repeat Steps 1-3 if the error occurs again, but for a different assembly.
   
   

If you add the Store Locator Web Part on a new page before you add the Image Viewer Web Part on the same page, the image will not appear on the page. To resolve this issue, you must add the Image Viewer Web Part on the page before you add the Store Locator Web Part.

Use alternate access mappings with your site because there are common Internet deployment scenarios in which the URL of a Web request received by Internet Information Services (IIS) is not the same as the URL that was typed by an end user. For example, the search technology in MOSS 2007 is able to crawl content external to the farm such as file shares and Web sites. If that content is available at different URLs on different networks, search should return results by using the appropriate URLs for the user's current network. By using alternate access mapping's external resource mapping technology, search can remap the external URLs in its search results to match the user's zone. For information about alternate access mapping with MOSS 2007, see http://go.microsoft.com/fwlink/?LinkID=140977.

Under heavy load, shoppers may receive an unexpected error message:

"Error. An unexpected error has occurred."

An event with the message "Exception information:

Exception type: InvalidOperationException

This is caused by a known .NET 3.5 SP1 issue. To resolve this issue, install the  updates to .NET Framework 3.5 SP1 from http://support.microsoft.com/kb/959209.

If you have a Web Part that contains a property that is a link that is outside of the sub site in which you are operating, you cannot modify it by editing the Web Part. To work around this issue, you need to modify the code by using SharePoint Designer. An example of this is the My List Details Web Part on the wishListDetailsPage.aspx page in the MyAccount sub site.

On a MOSS site

1. In SharePoint Designer, open site and select the NTLM site, for example, http://MACHINENAME:PORT.
   
   
2. Open MyAccount, view Pages.
   
   
3. Check out wishListDetails.aspx.
   
   
4. Right-click Detach from Page Layout.
   
   
5. In the warning dialog box that appears, click OK.
   
   
6. Change the CartUrl and ContineShoppingURL attributes to the URL you want (see the following example).
   
   
7. Check the file in and publish a major version, and approve it.
   
   
8. Right-click wishListDetails.aspx, and then click Attach to Page Layout.
   
   

On a WSS site

1. In SharePoint Designer, open the site and select the NTLM site, for example, http://MACHINENAME:PORT.
   
   
2. Open MyAccount, view Pages.
   
   
3. In SharePoint Designer, right-click wishListDetails.aspx, and then click Open with SharePoint Designer (HTML). 
   
   The file is opens in a separate window in SharePoint Designer.
   
   
4. Change the CartUrl and ContineShoppingURL attributes to the URL you want (see the following example).
   
   
5. Save the changes.
   
   

The following example is the Shopper List Detail Web Part as it appears on the page <WpNs0:SPShopperListDetailWebPart runat="server":

TemplatePath="[Templates]/ShopperListDetail/DefaultSite_WishListDetail.xslt" AllowMinimize="False" 
AllowClose="False" ChromeType="None" AllowEdit="False" 
XslTemplateUri="[Templates]/ShopperListDetail/DefaultSite_WishListDetail.xslt" CartUrl="/Pages/category.aspx" 
Description="Lists Detail Web Part for Commerce Server." 
LineItemColumnNames="DeleteAction;Image;ProductName;ProductId;Availability;Price;AddToCartAction" 
ID="g_d0850820_10f6_442c_80d7_d25469025a0b" ContinueShoppingUrl="/default.aspx" 
UserControlName="ShopperListDetail.ascx" TemplateRepositoryFolderName="ShopperListDetail" Title="My Lists Detail 
Web Part" ErrorMessage="" __MarkupType="vsattributemarkup" __WebPartId="{D0850820-10F6-442C-80D7-D25469025A0B}" 
WebPart="true" __designer:IsClosed="false" partorder="1"></WpNs0:SPShopperListDetailWebPart>

When using the TargetingContext to pass information used in the expression evaluation of advertisements, the "Page Group" attribute on the search model will be ignored.

This occurs because the "Page Group" attribute in the TargetingContext is null.

To resolve this issue, delete the "Page Group" attribute in the TargetingContext in Commerce Server Manager.

1. In Commerce Server Manager, expand the Global Resources node, and locate the Profiles node for your site.
   
   
2. Expand the Profiles node, expand the Profile Catalog node, expand the Profile Definitions node, and then select the Targeting Context node.
   
   
3. Select the "Page Group" property, and then click Remove.
   
   

If you were using this attribute in your TargetingContext, recreate the property with a different "Name" field. Update your code to use the new property name, as well as updating any expressions in Marketing Manager that use this property.

The configuration of the Store Locator Web Part has been updated from what is included in the product documentation. See the Commerce Server 2009 Installation and Configuration Guide at http://go.microsoft.com/fwlink/?LinkID=139462 for the most current information.

If you want to create localized versions of your site, known as site variations in SharePoint, see "Localizing Your Commerce Server 2009 Site Using Site Variations" at http://go.microsoft.com/fwlink/?LinkId=147752. Note that the instructions are only applicable if you are using MOSS.

The Microsoft Office SharePoint Server 2007 (MOSS) error message, "This page has been modified since you opened it" may appear if you attempt to modify a Web part by going into Edit mode for an existing site page. To modify the Web part, you must first reload the page in question and then explicitly edit it by clicking on the Edit Page button on the toolbar on the top of the page. This will then include any existing changes that may already have been incorporated.

When importing multiple profile objects (for example, UserObject, Address, and so on) by using a ProfileDocument in one XML file through BizTalk Profile Adapters, Commerce Server creates only the first profile object. You do not receive an error message that the other profile objects were not created.

To workaround this error, put only one profile object in each ProfileDocument and save it in a separate XML file.

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

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.

© 2009 Microsoft Corporation. All rights reserved.

Microsoft, Active Directory, ActiveX, BackOffice, BizTalk, Developer Studio, Expression Blend, FrontPage, Hotmail, JScript, MSDN, MS-DOS, MSN, Outlook, PivotChart, PivotTable, Silverlight, SharePoint, Virtual Earth, Visual Basic, Visual C++, Visual C#, Visual Studio, Webdings, Win32, Windows, Windows Live, Windows Media, Windows NT, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.