SharePoint Experts, Information Architects, Expert Witness

SICG provides a broad array of business and technology consulting from architecture to design to deployment of global systems with a focus on surfacing data in the enterprise. We focus on the "How", not just the possible. Contact me direct: or call 704-873-8846 x704.

Search This Blog

Wednesday, September 16, 2009

HOME FOR SALE! Mooresville, North Carolina

Currently selling a home and golf lots in Mooresville, North Carolina. Nestled inbetween the 4th and 6th holes of the Mallard Head Golf Course. Oustanding Schools, close to shopping and 1.5 miles to Lake Norman! 35 miles from downtown Charlotte.

3 Bedrooms (with oversized master suite), 2 full bath, custom built bar (seats 12), quality oak trim throughout - all appliances less than 1 year old.

For more information please go to :

Contact me directly -

Unable to open the Adventure Works Catalog with Default Site

I've heard of many cases in which using the Commerce Server default data (the Adventure Works Catalog) fails to load after a successful install and several solutions though I've not seen a post regarding Commerce Server 2009 with SharePoint which requires a different fix.

The symptom is demonstrated by error messages when you try to open the Adventure Works Catalog using the Catalog Manager; if you check the System Event Log, you'll see a message similar to this:

Failed to retrieve the AzMan Scope named CatalogScope_Adventure Works Catalog

The CS2009 fix for this is under Start > All Programs > Microsoft Commerce Server 2009 > Tools > Upgrade Wizard. Simply run this utility on the catalog and Viola!

Commerce Server Web Services Connection Failures - Authentication Errors

After installing and configuring Commerce Server 2009, you may encounter connection and permsissions errors when attempting to use the Catalog Manager, etc. While there can be several causes, a few tips:

No permission to connect/General Permissions Errors/Unable to connect to services under Default Site:

The setup documentation for Commerce isn't clear on the SharePoint integration; while it correctly tells you to add the users to the IIS_WPG group, it is necessary to add the same users to the WSS_WPG. The IIS_WPG (Internet Information Services Worker Process Group) is the default group used for running services for IIS/ASP.NET sites. WSS_WPG, added when SharePoint is installed, serves the same purpose but for SharePoint sites Only.

NOTE: One way to avoid the above problem completely is to put all of the Web Services into a single IIS site (provisioned through IIS, not SharePoint) then modify all of your connection strings to point to the new location.

Authentication Errors:

If you get authentication logged in the System Event log, it can indicate that permissions are wrong in the Authorization file for the service (i.e. CatalogAuthorizationStore.xml). You verify this using the azman.msc snap-in to view the settings. Per the documentation, the web service machine groups (CatalogWebSvcGroup, etc.) are added to the Administration Roles using azman.msc; however, in a domain environment, it is often necessary to add the specific Domain User accounts (i.e. \CatalogWebSvc) to the Administrator/Catalog Administrator Roles (same for Orders, Profiles and Marketing).

Tuesday, September 15, 2009

Pipelines: The PCF file 'c:\inetpub\wwwroot\CatalogWebService\pipelines\basket.pcf' does not exist

When deploying a commerce site, you might encounter the following error attempting to use the Catalog Web Service (Catalog Manager, Catalog and Inventory Schema Manager):

Pipelines: The PCF file 'c:\inetpub\wwwroot\CatalogWebService\pipelines\basket.pcf' does not exist

To correct:

1) First check the CSApp.ini files in each of the services to verify they are pointing to the right site and that the path defined is correct
2) Check web.config of the web services to verify the Site name specified is correct

Commerce Server Failed to start monitoring changes to '' because access is denied

A tip for those of you trying to configure Commerce Server 2009 under SharePoint.

After deploying a site then trying to access the Catalog Web Service (or other services), you may encounter the error:

Commerce Server Failed to start monitoring changes to '' because access is denied

The problem here is that the Web Service Accounts in Commerce do not have access to SharePoint - simply add them to the WSS_WPG group (Start > Administrative Tools > Computer Management > Local Users and Groups) in addition to the IIS_WPG as instructed in the documentation.