How to troubleshoot Commerce Server Staging (CSS) issues in Commerce Server 2007 (921489)

MORE INFORMATION

Enable CSS logging

CSS logging may provide useful information that helps you troubleshoot CSS issues. To enable CSS logging, use the following commands.

CSS setglobal FullLogging=Yes 
net stop css 
net start css 

Note The second command and the third command restart the CSS service. Before you run these commands, make sure that you do not have CSS projects running.

For more information about the CSS log, click the following article number to view the article in the Microsoft Knowledge Base:

Use the general troubleshooting tips

Before you contact Microsoft Product Support Services, use the following general tips to troubleshoot CSS issues:

• If you manage CSS projects, make sure that your user account is a member of the CSS Administrators group.
• Make sure that the CSS service is running. Additionally, make sure that the account that is assigned to the CSS service has administrator-level permissions. To do this, follow these steps:
  1. Click Start, click Run, type services.msc, and then click OK.
  2. Click the Commerce Server Staging service, and then start the CSS service.
  3. Make sure that the account that is assigned to the CSS service has administrator-level permissions.
• Make sure that you have access to the CSS service or to CSS projects. You may want to view the registry to confirm the permissions. To do this, follow these steps:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate the following registry subkey:

     HKEY_LOCAL_MACHINE\Software\Microsoft\CSS

  3. To confirm the permissions, click Permissions on the Edit menu.
• Make sure that the user is part of the lists in the CSS registry value and in the Projects registry value.
  
  Note To verify that the user is part of the lists in the CSS registry value and in the Projects registry value, view the registry. This is more important if you have used many removeuser commands and many grantuser commands.
• If you replicate across trusted domains or across untrusted domains, make sure that the source server and the target server have the same user account and the same password. This is the only way that the session between the source server and the target server can be authenticated in an untrusted domain situation.
• Make sure that the underlying TCP/IP network is working. You can do this by using the Ping command to verify that the source server and the target server have the correct IP address.