Troubleshoot
April 5, 2011 | 
Author We have production site and staging site in different IIS servers. Last week, we have a production issue where we are facing issue in pushing the data from staging server to production server (where it was working before). In the event log, we see below exception.
Failed to export business data for ‘Catalog’ resource for project ‘PushData2Prod’.
Cannot open database "MSCS_Admin" requested by the login.
We figured out that it is happening because the staging service is attempting to connect to MSCS_Admin database using anonymous. After troubleshooting, we figured out that the staging service is running in Network service rather than domain account. Running the service under network account is attempting to the connect to the database anonymously. After making the service run under the domain account the staging service started working fine and we are able to push the data from staging server to production server.
The domain account to the service is normally set when running the configuration wizard after the installation of Commerce Server. It is important to note that you must also re-run the configuration tool after installing Commerce Server service packs . Mostly we might of missed this.
If you like this post, please click on our sponsor advertisement.
Posted in 
Tags: 
We have production site and staging site in different IIS servers. Last week, we have a production issue where we are facing issue in pushing the data from staging server to production server (where it was working before). In the event log, we see below exception.
Failed to export business data for ‘Catalog’ resource for project ‘PushData2Prod’.
Cannot open database "MSCS_Admin" requested by the login.
We figured out that it is happening because the staging service is attempting to connect to MSCS_Admin database using anonymous. After troubleshooting, we figured out that the staging service is running in Network service rather than domain account. Running the service under network account is attempting to the connect to the database anonymously. After making the service run under the domain account the staging service started working fine and we are able to push the data from staging server to production server.
The domain account to the service is normally set when running the configuration wizard after the installation of Commerce Server. It is important to note that you must also re-run the configuration tool after installing Commerce Server service packs . Mostly we might of missed this.
If you like this post, please click on our sponsor advertisement.
Today, my team is deploying commerce server application on a fresh server. After installing and configuring commerce server site, when we tried to open the internal or external site, we are getting a wired exception “The requested performance counter is not a custom counter, it has to be initialized as ReadOnly”. Nothing is written in to the event log.
Google/Bing didn’t provide much information on this problem but finally I am able to figured out the fix to this error. Here are the things I have done to fix this error and hope this will resolve your issue.
First thing I found is that while installing “commerce server – performing counter feature”, the installation is logging some exception into the log and this is coming due to some security issue. So, I make sure I provide valid security permission to my service account on following folders.
- Full permission on Windows\temp folder.
- Full permission on Temporary Asp.NET files folder (c:\Windows\Microsoft.NET\Framework64\v2.0.50727).
- Full permission on C:\Program Files (x86)\Microsoft Commerce Server 2007 folder.
After these changes, the installation went good and simultaneously the site is working fine.
If you like this post, please click on our sponsor advertisement.
After installing new SharePoint commerce service site in SPS 2010, we are facing issues while logging into the application. We are getting typical profile exception – failed to retrieve the profile (as shown below).
With the stack trace, it is clearly seen that while fetching profile information, the exception is thrown and this call is done by SharePointCommerceDataWareHouseAuthenticationModule (which in turn calls CS2007 CommerceDataWareHouseAuthenticationModule). After some analysis, we found that CommerceDataWareHouseAuthenticationModule class is used for analytics click-stream reports generation for the site and the PreRequestHandlerExecute (where exception has happened) event obtains the username from the CommerceContext.Current.UserId and creates an encrypted Ticket string. MSDN also says that, if the Commerce Server Authentication is being used, then the Data Warehouse Authentication Module should not be listed in the http modules section of web.config.
The remedy worked for me. We have removed CommerceDataWareHouseAuthenticationModule module from web.config and the site stared working fine.
If you like this post, please click on our sponsor advertisement.
We have unpacked the pub file in production environment and OOB application is working fine. We have some profile data exist in staging commerce server and want to bring it to production server. Since profile data can’t be moved through staging service, we have taken the backup and restored the database in the production. Everything worked fine but after database restore the commerce server manager is not behaving properly. Through MMC, we are not able to modify the profile connection strings. On edit link click, MMC is showing as blank screen. As a work around, we went to soursedef table in profile DB and modify the connection string but it didn’t worked.
To fix this issue (it’s a shot in the dark and it worked), we have exported the profile xml from staging server and imported that xml file in the production. After import, the MMC started working properly. I am not sure the logic behind that but it has fixed my issue. So, thought of sharing this to the community.
If you like this post, please click on our sponsor advertisement.
