Monitoring Performance Counters
Microsoft Windows Server provides a system monitoring tool that you can use to view and analyze site performance. You can add Commerce Server performance counters to the System Monitor to view and analyze data that is specific to key components of your site. You can then use the results to fine-tune your site for optimal performance.
For more information about System Monitor, see Windows Server 2003 Help or Windows Server 2008 Help.
Note the following when you monitor Commerce Server performance counters:
To monitor performance on a single site in a multi-site configuration, you must use the Site Name token in all Profile Service objects' connection strings for every installed site. For example, if you have three sites, A, B, and C, and you want to monitor performance on site A, you must include the "Site Name=" token with the appropriate site name for all sites. Otherwise, sites B and C will increment all site performance counters that include site A. For information about the Profile Service object connection string, in the Commerce Server Manager expand Global Resources, and then expand Profiles.
You cannot monitor certain performance counters that are specific to Commerce Server from a remote computer. These include Custom Resources, Data Warehouse, Targeting, and User Profile Management counters. Loading these performance counters requires a connection to the Administration database. By default, performance counters run under the Remote Registry Service as LocalService when they are loaded remotely. By default, the account does not have permissions to access the Administration database if you have not modified access for the Remote Registry Service. If you load Commerce Server performance counters remotely, you might see errors in your Commerce Server computer's event log. These errors include the following:
Error in Commerce Administration Object: Description - 'GlobalConfig:Initialize: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.'
CSPerfCounters Component: Error - 'Calling GetSites'
CSPerfCounters Component: Failed to create - 'Init from registry.'