If you have not already noticed that CrmXpress has always been run by BlogEngine.Net then well... know that it has been powered by BlogEngine.Net. As the new year arrives [Gujarati New Year is generally the next day of Diwali]. There were some unexpected problems during the upgrade and it brought this blog down for almost 3 days and I hope that it did not affect any one. If it did, sorry for the trouble caused and I would like to assure you all that in future we will not do an in-place upgrade without putting in effort to make sure that everything is working as per the expectations. Anyways now things are in control except our CrmXpress theme which shall be up and running soon.
Wish you all Happy Diwali and a Very Happy New Year!!! Stay tuned we have many gifts lined up for you.
I recently observed a scenario where a CRM 4.0 database was upgreaded to CRM 2011 and after upgrade process uses were not able to perform any kind of operation within CRM. The exception that we found was :
A potentially dangerous Request.Form value was detected from the client (crmFormSubmitXml="<iteasy_postcode><it...").;Hash='1073421037'
This is because ASP.Net 4.0 now has a different behvaior and it inspects all request data. Rather that being the cookies, urls, headers, etc. This behavior is controlled by RequestValidationMode property.
Now to override this behavior for CRM 2011, all you need to do is set <httpRuntime requestValidationMode="2.0" /> in your web.config. This setting will enforce request validation in .Net 2.0 mode i.e. only Form's input fields are checked for invalid HTML input.
Recently I was asked what exactly Application File Privilege found under Core Records affects within CRM. After some research on the topic I found that it holds Schemas and Templates as mentioned below :
One of the practical usages of AdHocReportTemplate is to apply changes to your Ad Hoc Reports by modifying this template. Here is a link that demonstrates how to do so : http://blog.sonomapartners.com/2008/11/customizing-the-report-wizard-template.html
This one is a well known error for people who have worked with CRM 4.0 and an easy fix was to restart CRM Async Service.
The key specified to compute a hash value is expired, only active keys are valid. Expired Key : CrmKey(Id:a06a2c71-e96a-e011-ae0c-000c29ce8648, ScaleGroupId:00000000-0000-0000-0000-000000000000, KeyType:CrmStaticVersionScaleGroupKey, Expired:True, ValidOn:04/20/2011 00:59:35, ExpiresOn:06/19/2011 00:59:35, CreatedOn:04/20/2011 00:59:35, CreatedBy:CRM\Administrator.
The same error when it comes to CRM 2011, you might have to restart
Microsoft Dynamics CRM Asynchronous Processing Service
Microsoft Dynamics CRM Asynchronous Processing Service (maintenance)
followed by an IIS Reset.