I don't learn well. Or so it would seem. So let me tell you what I did this time.
I am working on a project that requires me to install the CRM Online Email Router. I really didn't think too much about uninstalling the router for on-premise CRM, which I did, and the CRM Online Router worked just like it was supposed to.
I also did not think very much about the fact that I was installing a CRM Online component on the same server where CRM on-premise was loaded.
This morning, I was going to continue work on a CRM on-premise project but when I fired up CRM, I get this:
Hmm. In my line of work, we call this, "Bad."
I was wrong about that too. It wasn't just bad, it was really, really bad.
I assumed that I had inadvertently created a conflict between the on-premise vs. Online versions of one or more DLLs. Deciding that it should be a simple fix to just uninstall the CRM Online router and reinstall the on-premise version, that is what I did.
The uninstall operation worked, the reinstall didn't.
No problem, I thought. I'll just do a repair on the CRM on-premise software and we'll be good.
Nope. That didn't work either.
Since I wasn't really sure what was happening, and I really didn't care ( since this was a development box ), I just uninstalled and reinstalled CRM – connecting to the existing installation.
And the point of your story was what?
Don't mix components from CRM on-premise with CRM Online. That's what virtual machines are for.
Loading ...
Good point! There are a lot of sales people and consultants out there who will let you believe that you can have your cake and eat it too.
Online and on-premise are two different worlds in CRM.
Also, don't try and install the online version of the Data Migration Manager on a machine that has the outlook client installed…. if you want either to work that is. :)