My photo
Auckland, New Zealand
Smurf sized geeky person with a penchant for IT, gaming, music and books. Half of industrial duo 'the craze jones'. Loves data, learning new things, teaching new things and being enthusiastic.

Monday, 12 October 2009

Dynamics CRM - reinstalling a broken install

A week was spent doing battle with virtual machines, setting up servers, sorting out IIS, SQL Server, AD etc etc... and when everything was in place, Dynamics CRM was installed. More time was then spent making sure that the install would make it past the verification page and at long last we had a beautifully set up instance of Dynamics CRM running on a virtual server, attached to our domain and residing on my PC. Life was good. Then someone unintentionally broke it before I'd had a chance to take a copy of the virtual machine, except that because of what was broken it wouldn't have mattered if we'd had a copy as the AD links and machine name were toasted on the domain. Pants! So next came the mission to fix things.

Several options were tried and after much hair pulling eventually the domain was recognizing the server again. Once the server was back in play there was an attempt to connect to the Dynamics CRM site but lady luck was not with us that day and we received the error: “Business Management Error. The user id associated with the current record is not valid”. This was happening when we accessed using localhost:5555 and servername:5555. Bugger! Says I.

My Google mojo was in poor shape at the end of last week and only two websites offered any inkling of help. When all two options had been tried and there was still no joy, the next step was to contact a very nice man at Microsoft who spent quite a bit of time helping me with this issue. Alas still no joy.

So on to the next option. Uninstall and reinstall Dynamics CRM. Probably not an option you can do in a production situation but then again, in a production situation if someone decides to take a copy of your server and rename it whilst being attached to the domain you've probably got bigger problems to worry about.

Uninstalling is nice and easy but before you reinstall you need to drop the SQL databases that were created as part of the initial Dynamics CRM install. Renaming them won't work as Dynamics CRM still manages to maintain links to them and will fail with lots of groovy messages about missing log files. If you drop the tables then all goes swimmingly with the install. If you've got data you want to keep, take a backup or a copy of the databases first and then do a merge after you've got things up and running again.

Once you've dropped your tables, reinstall using most of the same options as you did previously but this time with one difference, don't use the default website, select the option to create a new website.

And that should be it. You'll be up and running again. Phew....

No comments: