Dossies @ Work: Dynamics 365 CDS

After applying a host header to my MSCRM 4.0 website, I was able to connect to CRM on a client PC, but on the server itself I always received a "HTTP 401.1 - Unauthorized" error. After some searching around, I found the solution to my problem in the following KB article: http://support.microsoft.com/default.aspx?scid=kb;en-us;896861 It seemed that the loopback check security feature on my Windows 2003 server was causing the problem. Kevin Dosseray

Recently I had a problem trying to upload my customizations file (Settings -> Customizations -> Import Customizations -> Upload). I wasn't able to upload the file. After clicking the button "Upload", the button greyed out and nothing else happened. The problem was that my customizations file was too big. The file was about 10MB and apparently CRM doesn't default allow http requests of files bigger than 8MB. Fortunatly you can change this setting: go to your location where you installed the CRM website (default this is "c:\program files\microsoft dynamics crm\crmweb") and open the web.config. In the web.config locate the following line: Change the maxRequestLength to a value big enough to handle your file (in my case this was 11000). Kevin Dosseray

A client was getting an "Invalid Action" error when trying to open their Microsoft CRM 4.0 (on-premise) application. Checking the event log, showed the following: Event Type: ErrorEvent Source: MSCRMKeyGeneratorEvent Category: NoneEvent ... Description: Current active key (KeyType : CrmWRPCTokenKey) is expired. This can indicate that a key is not being regenerated properly. Starting the Microsoft CRM Asynchronous Processing Service on the server solved the problem! Kevin Dosseray

At a client we received an error 'No Attribute' while trying to merge 2 accounts. In the trace logs the error said: 'owninguser field not known in custom entity'. Apparently this was caused by the parental relationship between account and a custom entity. After changing the parental relationship to a referential (restrict delete), the merging worked fine. I did some searching on the internet and it seems that Microsoft is aware of the bug and working on a hotfix, but no release date is yet known. Kevin Dosseray