Hi,
Check out these two useful links
Release News for Microsoft Dynamics CRM: Q4 2012 Update & CRM on Windows 8.
http://niiranen.eu/crm/2012/07/dynamics-crm-roadmap-for-fall-2012-release-and-beyond/
Bye.
Hi,
Check out these two useful links
Release News for Microsoft Dynamics CRM: Q4 2012 Update & CRM on Windows 8.
http://niiranen.eu/crm/2012/07/dynamics-crm-roadmap-for-fall-2012-release-and-beyond/
Bye.
Hi,
I had recently uninstalled and then reinstalled the Outlook client for CRM 2011. However when I was running the Configuration Wizard it was not opening up and instead I was getting the below error in the event log.

Removing the registry key MSCRMClient manually resolved the issue. (HKEY_currentuser\SOFTWARE\Microsoft\MSCRM)
http://social.microsoft.com/Forums/eu/crm/thread/97156d82-1491-4518-b6bc-b70b432bd12c
Hope it helps.
Hi,
We had our plugins registered in Sandbox mode (for development we were using on premise and were deploying it on online environment) and the Microsoft Dynamics CRM Sandbox Processing Service was not running.
Starting the service resolved the issue.
Hope it helps.
Hi,
Do check out this informative article that talks about different timeout settings and limits in CRM 2011
http://social.technet.microsoft.com/wiki/contents/articles/12601.crm-2011-timeouts-and-limits.aspx
Bye.
Hi,
While trying to retrieve more than 5000 records using Fetch XML we were getting the above error.
This is the sample code that we were using
http://msdn.microsoft.com/en-us/library/gg328046.aspx
it seems that the value of pagingcookie is not being set there in case of more records
// Check for morerecords, if it returns 1.
if (returnCollection.MoreRecords)
{
// Increment the page number to retrieve the next page.
pageNumber++;
}
Similar sample code for CRM 4
http://msdn.microsoft.com/en-us/library/cc151070.aspx
// Check for morerecords, if it returns true.
if (results.MoreRecords) {
// Increment the page number to retrieve the next page.
query.PageInfo.PageNumber++;
// Set the paging cookie to the paging cookie returned from current results.
query.PageInfo.PagingCookie = results.PagingCookie;
}
So setting the PagingCookie resolved the issue for us.
Bye.
Hi,
We were getting the above error while trying to import our default unmanaged solution from development environment to our staging environment.
It was giving the error for one of the custom entities. But there were no option sets (picklist fields) in that entity. There was one “two options” (bit) field in the entity. Deleting that field from the target staging environment and then retrying the import worked in our scenario.
Hope it helps.