When executing SharePointCommerceServicesConfiguration.exe wizard, you may encounter an error below error .
|
= SHAREPOINT WEB FEATURE ACTIVATION ========== The job creating the profile encryption key has timed out. STACK: at Microsoft.Commerce.Portal.Setup.CommandObjects.CreateProfileKeyCommand.Execute() |
By seeing the exception, we can says the exception has occurred while creating asymmetric encryption keys for the profile system. Wizard next final step is to create commerce server applications (web services) and associate them to the site. If you would have observed now, your commerce site is created with all resources but the applications will be missing. I encountered the issue and I am able to fix this with the below work around.
1. Create a commerce server site using commerce server manager.
2. Use SharePointCommerceServicesConfiguration.exe wizard, create a IIS web site and select the commerce server site created in step 1 (instead of creating new commerce site).
3. At the end of wizard execution, you will get above error again – ignore the error. Create profile keys manually with the below command.
| ProfileKeyManager.exe /kn /0 |
The above commend generates a new pair of public and private keys.
Writing to file C:\Program Files\Microsoft Commerce Server 2007\Tools\NewKeyPair _2010_9_15_20_46_14_35.xml
Now execute following command to insert the above keys in registry.
| ProfileKeyManager /ke /kf "NewKeyPair_2010_9_15_20_46_14_35.xml" /reg "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Commerce Server 2007 Keys\DefaultSite" /f |
Note: You can get the registry location in the generated site web.config (under <profiles> <encryption> tag)
That’s all, your site starts working. I am not sure whether there is a bug in SharePointCommerceServicesConfiguration.exe as the same wizard is working fine on other machines. May be you can check latest commerce server hot fixes to get rid of this work around.
If you like this post, please click on our sponsor advertisement.

I think you meant : ProfileKeyManager.exe /kn /o
With on “o” not a zero.
Thanks Danny. Its typo and I corrected that
.