MSCRM

When you try to create a new appointment, It shows the error message "General Scheduling error" . If trace is enabled, the below error is recorded in the trace.      "Inner Exception: System.Data.SqlClient.SqlException: Violation of UNIQUE KEY constraint 'UQ_PrincipalObjectAccess'. Cannot insert duplicate key in object 'dbo.PrincipalObjectAccess'." The solution for this is to install the hotfix . http://support.microsoft.com/kb/956129 In our case, the above hotfix has resolved the issue.

Error Description Could not find any resources appropriate for the specified culture or the neutral culture. Make sure "AjaxControlToolkit.Properties.Resources.resources" was correctly embedded or linked into assembly "AjaxControlToolkit" at compile time, or that all the satellite assemblies required are loadable and fully signed Solution : Add the Toolscript Manager

Regular Expresssion for a password validation is   ^(?=.*\d)(?=.*[a-z])(?=.*[A-Z]).{4,8}$ The description for the above expression is  Password matching expression. Password must be at least 4 characters, no more than 8 characters, and must include at least one upper case letter, one lower case letter, and one numeric digit. Lots of regular expresssion available at http://regexlib.com/DisplayPatterns.aspx

nav = document.all.navProds will break in MSCRM 4.0 because the element for navProds has changed to navProducts in version 4. Also, note nav = document.all.navSalesProcess is no longer required (The Sales Process has been removed in version 4) and should be commented out.

In MSCRM 3.0 , it does not automatically set the asterisk if fields are set to mandatory using the below clientside script crmForm.SetFieldReqLevel(" ", 1); we need to explicitly append the asterisk using the client side script, crmForm.all. .innnerText += "*"; When we upgrade from MSCRM 3.0 to MSCRM 4.0, it shows two asterisks appended to the label. It is because MSCRM 4.0 automatically appends the asterisk when you call crmForm.SetFieldReqLevel(" ", 1); After upgradation, we need to remove the line of code --- crmForm.all. .innnerText += "*";

While upgradation from MSCRM 3.0 to 4.0, one of the common error we find is the changes in the names of the query string params. In MSCRM 3.0, the name of the query string for id of the record is "oId" and for typename it is "oTypeName". Where as in MSCRM 4.0, the name of the query string for id of the record is "Id" and for type name it is "TypeName". "oId" in MSCRM 3.0 is changed to "Id" in MSCRM 4.0. "oTypename" in MSCRM 3.0 is chnaged to "Typename" in MSCRM 4.0. All the custom code. which reads these query strings might require a changes to query string param names. 

Error : -------------- 'Microsoft.Crm.WebServices.Crm2007.MultipleOrganizationSoapHeaderAuthentica­tionProvider, Microsoft.Crm.WebServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' doesn't exist. Parameter name: Microsoft.Crm.WebServices.Crm2007.MultipleOrganizationSoapHeaderAuthenticat­ionProvider, Microsoft.Crm.WebServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Solution: Register the DLL Microsoft.Crm.WebServices into the GAC