FIX: A new user profile may not be created and you may receive an exception when you try to create a new user profile in Commerce Server 2007

Hotfix Download Available
View and request hotfix downloads

View products that this article applies to.

SYMPTOMS

When you try to create a new user profile in Microsoft Commerce Server 2007, a new user profile may not be created. Additionally, you may receive the following exceptions in the Application event log.

Exception 1

An exception occurred in the 'ProfilesWebService' Web service. Exception details follow: System.Runtime.InteropServices.COMException (0x8007202F): A constraint violation occurred. (Exception from HRESULT: 0x8007202F)
at Microsoft.CommerceServer.Interop.Profiles.IProfileObject2.Update()
at Microsoft.CommerceServer.Internal.Profiles.ProfileStorage.UpdateOnProfilePIA(IProfil eObject2 piaProfileObject, ProfileErrorContext ctxt)
at Microsoft.CommerceServer.Internal.Profiles.ProfileStorage.UpdateProfile(XmlElement profileXml, Boolean forceOverwrite, Boolean inAdapterContext)
at Microsoft.CommerceServer.Profiles.WebService.ProfilesWebService.UpdateProfile(XmlEle ment& profileXml, Boolean forceOverwrite, Boolean inAdapterContext)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Exception 2

Microsoft.CommerceServer.ServerFaultException: A constraint violation occurred. (Exception from HRESULT: 0x8007202F) --->
System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: A constraint violation occurred.
(Exception from HRESULT: 0x8007202F) --->
Microsoft.CommerceServer.ServerFaultException: A constraint violation occurred.
(Exception from HRESULT: 0x8007202F)
--- End of inner exception stack trace ---
at Microsoft.CommerceServer.Profiles.WebService.ProfilesWebService.PropagateOrLogExcept ionInternal(Exception ex)
at Microsoft.CommerceServer.Profiles.WebService.ProfilesWebService.PropagateOrLogExcept ion(Exception ex)
at Microsoft.CommerceServer.Profiles.WebService.ProfilesWebService.UpdateProfile(XmlEle ment& profileXml, Boolean forceOverwrite, Boolean inAdapterContext)
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsoft.CommerceServer.Internal.Profiles.ProfilesServiceProxy.AuthorizedInvoke(Str ing methodName, Object[] parameters) --- End of inner exception stack trace ---
at Microsoft.CommerceServer.ServiceAgent.TryHandleWebMethodException(Exception ex, SoapHttpClientProtocol serviceProxy) at Microsoft.CommerceServer.Internal.Profiles.ProfilesServiceProxy.AuthorizedInvoke(Str ing methodName, Object[] parameters)
at Microsoft.CommerceServer.Internal.Profiles.ProfilesServiceProxy.UpdateProfile(XmlEle ment& profileXml, Boolean forceOverwrite, Boolean inAdapterContext)
at Microsoft.CommerceServer.Profiles.ProfileManagementContext.UpdateProfile(XmlElement profileXml, Boolean forceOverwrite, Boolean inAdapterContext)
at Microsoft.CommerceServer.Profiles.ProfileManagementContext.UpdateProfile(XmlElement profileXml, Boolean forceOverwrite)
at Microsoft.CommerceServer.UI.CustomerAndOrdersManager.ProfilesManagementProxy.TryUpda teProfile(XmlElement profileXml, Boolean forceOverwrite)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

This problem occurs if the following conditions are true:

You use a centralized profile store to maintain credentials in Active Directory Application Mode (ADAM).
You try to set a password for the unicodePwd attribute.

Note This problem may not occur if the unicodepwd attribute is blank.

Back to the top

RESOLUTION

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart Microsoft Internet Information Services (IIS) after you apply this hotfix. To restart IIS, run the following command at a command prompt.

IISRESET  /RESTART

Note This option stops and then restarts all IIS services.

Hotfix replacement information

This hotfix does not replace any other software updates.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Collapse this tableExpand this table