Yesterday I upgraded my CRM 1.2 installation to CRM 3.0
I started of with making sure the prerequisits were met.
This took most of the update time.
CRM 3.0 wants your system to be really up to date. Ofcourse I haven't touched my system anymore since the installation of 1.2 (somewhere in June) except for the occasional windows updates.
SQL SP4, reboot, .Net Framework 1.1 SP1, reboot, Exchange Server 2003 SP1, reboot, SharePoint Portal Services SP2, reboot, SBS 2003 SP1, etc... etc...
Took over 5 hours to just do that...
Then I started the CRM 3.0 installation.
The Installation Wizard is a great tool, but is not always very clear in its problem descriptions.
I received an error 'Unable to parse uri'.
I have several websites running on this server (webmail, www, intranet, crm, weblogs) all with their own host header.
CRM requires to be the website WITHOUT a host header.
After that was solved, I got a very vage error when it tried to insyall Reporting Services. Reporting Services wants SQL Server to be installed in C:\Program Files\Microsoft SQL Server, and ofcourse my installation was on D:\Microsoft SQL Server.
I managed to get around this by manually installing Reporting Services (don't forget to install the Service Pack afterwards, and another reboot).
The next error I got was that my database contained triggers which were not CRM 1.2 triggers. That was correct (and what a smart wizard) I added a triggers which changed the fullname of a lead into the companyname, so that I was able to search leads by company name instead of contact name.
After removing the trigger, the setup went pretty smooth.
At the end of the setup I got an error that the settings for the perfomance monitoring could not be written, but after ignoring that (and 1 more reboot) the installation was finished and CRM 3.0 was running.
I then installed CRM 3.o Desktop Outlook client on my desktop. No problems there.
1 more install on my laptop, the CRM 3.0 Laptop Outlook Client. And again no problems there.
Data was converted perfectly. I only found a small problem with 1 customized form that I still have to figure out, but that will probably happen tonight...
Talk to you later!