Scenario â?? MS CRM 1.2 installed and functional on DEV1 server. Related
databases on separate database server. Purchased a new surver to host CRM.
Need to install new instance of CRM on the new server that is attached to the
existing database so as not to lose any customer data.
Problem â?? Installation on new server failed. Message appeared saying
â??unable to register security serviceâ??, which is a vital part of the
application. CRM requires that all patches and hotfixes applied to the
original server must be applied to the new server for redeployment as well.
The event log message for the above mentioned error stated:
Error: Incorrect or incompatible database version. If you have applied any
patches or hotfixes for Microsoft CRM,
please apply them to this server as well.-2147467259 (0x80004005)
Description: Unspecified error
Comments: Database Version: 1.2.3297.106
Installed Version: 1.2.3297.0
QFE number to apply: 0
There was a hotfix that was applied to DEV1. However, the hotfix requires
that CRM Server be installed in order for it to be applied. So I installed
CRM again, opting to ignore the error messages, then successfully applied the
hotfix. I tried to uninstall/reinstall CRM again, but still received the
same error.
On the advice of some users on the MS CRM community boards, I added the
service accounts to the â??Pre windows 2000 Compatabilityâ?? group in Active
Directory. Did not help. Also made service account for main CRM service a
domain admin, still no help (service account is no longer domain admin, but
is still in pre win2k compato group.)
Solution â?? After further digging, I found the buildversion table in the
company_MSCRM database. It listed the build version and revision numbers in
one row of data. The revision number can be changed when hotfixes are
applied. That data apparently must match exactly that of the instance of CRM
you are trying to install (when attaching to an existing database, of course)
or the install will fail. The problem is that a fresh install of CRM has 0
for the revision number, so it will not match a previous install if there was
a hotfix applied. However, you can not apply the hotfix to the new server
until CRM is installed. This seems to be a catch 22. To get around this, I
manually changed the revision number in the table back to 0 then attempted
the install. It worked fine. I then reapplied the hotfix for good measure
(though it wouldnâ??t let me reinstall the hot fix until I changed the revision
number back to its original value, in this case 106). CRM then worked fine
and the problem was solved.
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/Businesssolutions/Community/NewsGroups/dgbrowser/en-us/default.mspx?mid=9af883bb-fbd6-4319-9c9a-c83dc1ba7d05&dg=microsoft.public.crm