Tuesday, July 21, 2009

Thank you MVPs & other Community Members




Way to go!

Monday, July 20, 2009

MSCRMAsync error in Event Viewer

Lately I encountered another interesting error during CRM implementaion. After installing Update Rollup 4, I noticed MSCRMAsync Service in the Event Viewer throwing an error at regular intervals.

Google looked around the world wide web and brought to me that .Net Framework 3.0 SP1 was missing. I downloaded and before it could finish installation, it threw another error and took everything down (including SQL Server 2005). I un-installed Update Rollup 4 for CRM, .Net Framework 3.0 and .Net Framework 2.0. Re-installed them again in this manner
  • .Net Framework 2.0
  • .Net Framework 2.0 SP1
  • .Net Framework 3.0 &
  • .Net Framework 3.0 SP1
  • Update Rollup 4
after which everything seem'd to be perfect. Event viewer was error spotless.

If you've received a similar error but had a different solution, I'm sure you want to share it as a comment.

Friday, July 17, 2009

Microsoft Dynamics CRM Server Setup did not complete successfully

Microsoft Dynamics CRM Server install failed.

Action Microsoft.Crm.Setup.Server.MsiInstallServerAction failed. This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.

I was very close to completing the CRM v4.0 installation on the server during a client implementation when I received a dialog box just as one displayed below. I've done plenty of implementations before but never came across any such error during installation. It made me think for a while, what different did I do during this installation and I noticed it was the recommended update. (The first step during a CRM installation)

Microsoft.Crm.Setup.Server.MsiInstallServerAction
After a while of thought and reading the error over and over again, I thought let me try this.

I simply cleared the IE cache, increased the cache size to almost 2 GB and re-installed CRM from the beginning, including the recommended update during the installation steps. The CRM installation glided to finish.

A happy ending!

Thursday, July 16, 2009

CRM for Outlook cannot be installed on a computer where Exchange Server prior to Exchange Server 2007 are installed

Did you ever happen to see this especially when you are installing CRM client for Outlook?
Microsoft Dynamics CRM for Outlook cannot be installed on a computer where Microsoft Exchange Server versions prior to Exchange Server 2007 are installed.

It showed up today while I was installing Microsoft Dynamics CRM 4.0 Client for Office Outlook on one of the client machine's and this is how I went about solving it.
  • Click Start > Run and type regedit.exe (Registry editing has been disabled by your administrator)
  • Navigate to HKEY_Local_Machine\Software\Microsoft\Exchange
  • Right click Exchange and export it as .reg file
  • Now delete the Exchange folder from the registry
  • Go ahead and install Microsoft Dynamics CRM 4.0 client for Office Outlook and also configure the CRM client.
  • Once through with installation and configuration of CRM client for Office Outlook, restore the Exchange .reg file back into the registry. (Just double click it to add it back into the registry)
Your client user should be happy now!

Saturday, July 4, 2009

How To ? - 3

How do I get rid of
Atleast one of the recepient could not be resolved to a record in the system
  • Click on Settings > Administration > System Settings
  • Click on the E-mail tab
  • Select Yes for "Allow messages with unresolved e-mail recepients to be sent"
  • Click OK