AndreasSandgren
Wed Aug 03 04:36:13 CDT 2005
Yes. The db was on the crm server. I tried to unregister and register the
service and got the following error message:
Error: An error was encountered during security service registration.
-2147023564 (0x80070534) Description: No mapping between account names and
security IDs was done.
Do you have any idea what is wrong?
/Andreas
"Matt Parks" wrote:
> Was your original DB on the same machine as CRM itself? If so, then you
> probably registered the security service to be dependant on SQL. You could
> re-register the security service (I think it's the CRMSecurity.exe file). If
> you run that with a /? parm, it will give you a list of parms. There should be
> parms to unregister and then reregister it. You do not want to use the -S parm
> though as that will make it dependant on SQL.
>
> Matt Parks
> MVP - Microsoft CRM
>
> ----------------------------------------
> ----------------------------------------
> On Tue, 2 Aug 2005 02:23:01 -0700, "Andreas Sandgren"
> <AndreasSandgren@discussions.microsoft.com> wrote:
>
> Hi!
> I have just completed a change of sql server with the deployment manager. I
> changed from a local sql server on the crm server to a separate sql server in
> the same domain. I can access the crm after the change but I have this
> problem: The MSCRM Security Service is still dependant on the old (local) sql
> server. So when I stop this sql service I can't access the crm any more. How
> can I change the Security Service to use the new sql server? (Shouldn't this
> have been done by the deployment manager when I changed the sql server?. I
> also had to change the ODBC datasource for Crystal Reports, CE90, manually to
> use the new server.)
> Best regards
> Andreas Sandgren
>
> "Matt Parks" wrote:
>
> > This is not what I would recommend. The problem with this approach is that if
> > something goes wrong, you are now basically w/o a functioning app.
> >
> > Here are the steps I would recommend:
> >
> > 1) Restore the DB's to the new server.
> > 2) Use deployment manager to point CRM to the new DB - This is documented in the
> > IG in the Disaster Recovery section.
> > 3) Verify everything is working
> > 4) Then, remove the old DB's
> >
> > If you find problems in step 3, you can always point back tot he original DB.
> >
> > If you have SFO clients, you may need to reinstall them as the replication
> > settings may have issues connecting to the new DB.
> >
> > Matt Parks
> > MVP - Microsoft CRM
> >
> > ----------------------------------------
> > ----------------------------------------
> > On Fri, 8 Jul 2005 14:13:16 +0200, "Olivier Schmitt"
> > <oliviers@online.microsoft.com> wrote:
> >
> > Hi,
> >
> > I would uninstall CRM, move the databases (using backup/restore), reinstall
> > CRM connecting to existing database and reapply all patches that you
> > applied.
> >
> > You could also stop all CRM services, move the databases and change the
> > ConnectionString settings in HKLM\Software\Microsoft\MSCRM and start the
> > services again (I never test this though and I cannot guarantee that it will
> > actually work...)
> >
> >
>
>