Commerce Server Blog

After successfully installing commerce server site, when you try to open the website, you may encounter following error.

Recently, I fixed database authentication problem by applying a hot fix released by Microsoft.

http://support.microsoft.com/kb/975603

Seems somewhere I have missed the steps mentioned in the document (drop the Microsoft.CommerceServer.Runtime.dll that’s supplied in that hotfix in GAC) and after installing the hot fix, the site started working fine . Thought of sharing the same to fellow commerce server developers.

After deploying couple of pages/web parts/user controls, the site stopped working. I am getting wired error “An unexpected error” on the screen and the event log is clear – no events.

Its very strange to found that SharePoint will hide debugging information and all commerce server developers know that debugging is not easy in commerce server 2009. First my concentration went on WSP package – thinking that there might be some problem with WSP package which is leading some UI problem and SharePoint is not logging any events. But, I have managed to get rid of that error screen completely. The solution is to change a couple of entries in website web.config file. Modify the line <SafeMode MaxControls=“200“ CallStack=“false“… /> to <SafeMode MaxControls=“200“ CallStack=“true“… />

and also we have to set custom errors to ‘Off’ .
<customErrors mode=“Off“/>

That’s it, I stopped getting fancy ASP.NET custom page and able to see full stack trace and also errors in the eventlog. Now my development has got little bit easier!!

After setting up the website using SharePointCommerceServicesConfiguration tool, sometimes you may get following error when you try to open the website.

This error is because the commerce server site name is different than what is mentioned in the application configuration file. To fix this issue, we have to correct the site name value in web.config and channelconfiguration.config file.

After creation registration, if the user try to click on my Account, he may get SPS page with Not authorized exception and was able to find below entry in event log.

when troubleshoot further, I am able to found that the logged in user is not having proper privileges in MOSS site. To fix this, I followed below steps

• Open administrator website (using windows credentials)
• Click on “Site Action” –> “Site Settings” and click on “Modify all Site Settings”.
• Click on “people and groups” under “users and permissions” section.
• Click on “Registered Users” and add newly added user email Id to this group.

Now the end user can can able to access MyAccount page.

One of my friend faced this issue (“Failed in catalog – error ) and forward to us for help. He received this error after creating commerce server site using CS 09 tool “SharePoint Commerce Services Configuration Wizard” and when he tried to open the web page. Unfortunately there is no help available on this error in internet.

We have make sure that it error is not due to configuration issue and cross verified following configuration settings.

1. IIS Security
2. Adman – privileges provided to the windows account in all authorization stores.
3. SQL Server permissions.
4. Profile connection strings (even though the error message shows catalog but the error description shows profile).
5. checked web.comfit file if all settings are fine.

All settings are fine as expected but when we checked profile schema, we found that it was not properly imported by the tool. If you observe below image, you can observe the profile catalog is missing.

The resolution is to import the profile schema again (right click on yellow icon –> import –> select XML to import) and refresh to see the changes on the screen.

To Developer: Check whether installation tool has logged any error. To Microsoft: To make the error more precise – instead of just catalog, they should have mentioned profile catalog in the error.