MSCRM

The IE 6.0 window hangs for 5 minutes when a incident is opened for edit. The solution for this is to add the below registry keys to the Client Machine on which IE runs. 1. Start Registry Editor (Regedt32.exe). 2. Locate the following key in the registry: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings 3. On the Edit menu, point to New click DWORD Value, and then add the following registry values: Value name: MaxConnectionsPer1_0Server Value data: 10 Base: Decimal Value Name: MaxConnectionsPerServer Value data: 10 Base: Decimal Note: This happens on IE 6.0 only.

we should not use the web reference to CRM web services. If web references to CRM web references are used, when we run from the second server, plug ins throws error. It says "bad request". If we remove the references to CRM web services, then we cannot access the custom attributes inside the plug ins. We have to use the dynamic entities for accessing the custom attributes.

The below method can be used to check the session time out in MSCRM. Private void CheckSessionTimeOut() { if (Context.Session != null) { if (Context.Session.IsNewSession) { string sCookieHeader = Page.Request.Headers["Cookie"]; if ((null != sCookieHeader) && (sCookieHeader.IndexOf("ASP.NET_SessionId") >= 0)) { Server.Transfer("SessionTimeOut.aspx"); } } }

Error Message : “Could not load file or assembly ‘ Microsoft..Crm.WebSerices ....or one of its dependences. An attempt was made to load a program with an incorrect format." Solution : Check the version of the "Microsoft..Crm.WebServices.dll" file. There are separate versions for 32 bit and 64 bit installations. Use the appropriate dll basded on the operating system type.