Sign in
Microsoft.com
 
Resources for IT Professionals
 
 
 
Resources for IT Professionals > Dynamics Forums > CRM Deployment > Can not create/modify existing users on CRM
Ask a questionAsk a question
Search Forums:
 

AnswerCan not create/modify existing users on CRM

  • Saturday, October 24, 2009 10:03 PMYojan Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Hello all,

    We have a CRM application to which we restaure its data base - XXX_MSCRM to do a migration activity - custom logic.
    But all users that exist preivously are not working properly.

    So if they are changed to a new user - no existent previously - it is done perfectly - however if that is changed again to the older user ... it gives an error

    How can I know what the real error is ?

    any idea ?

    Thanks againg guys ...

    Yojan
     

Answers

  • Friday, October 30, 2009 10:14 PMCurt Spanburgh MVP ModeratorMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote

    I've seen this before in CRM 3.0 environments and there was a registry dword and setting to fix it.

    Basicly the problem is that the first DC in the forest could not be resolved so the registry tweek reduces the high awareness of CRM to the forest. 
    If you run netdiag from a CLR prompt you may get some information about how your application server is communicating with the AD forest.

    Here is the registry tweek.


    1. Click Start, click Run, type Regedit, and then click OK.
    2. Locate the following registry subkey:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM
    3. Right-click MSCRM, point to New, and then click DWORD Value to create a
    "New Value #1" value.
    4. Right-click New Value #1, and then click Rename.
    5. Rename the value VerifyDomainName.
    6. Double-click VerifyDomainName.
    7. In the Value data box, enter 0.
    8. Click OK.
    9. On the File menu, click Exit.
    10. Open CRM and add user again.

     

All Replies

  • Monday, October 26, 2009 2:36 PMYojan Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Guys,

    I have edited previous message cause in fact I do not yet where the error log goes.

    any idea ?  .. are we missing any configuration ?


    Regards
    Yojan
     
  • Wednesday, October 28, 2009 3:00 AMMatt ParksMVP, ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Can you provide a little more detail about what exactly is failing and what you have tried? 
    Matt, MVP - Dynamics CRM
     
  • Friday, October 30, 2009 10:14 PMCurt Spanburgh MVP ModeratorMVPUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote

    I've seen this before in CRM 3.0 environments and there was a registry dword and setting to fix it.

    Basicly the problem is that the first DC in the forest could not be resolved so the registry tweek reduces the high awareness of CRM to the forest. 
    If you run netdiag from a CLR prompt you may get some information about how your application server is communicating with the AD forest.

    Here is the registry tweek.


    1. Click Start, click Run, type Regedit, and then click OK.
    2. Locate the following registry subkey:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM
    3. Right-click MSCRM, point to New, and then click DWORD Value to create a
    "New Value #1" value.
    4. Right-click New Value #1, and then click Rename.
    5. Rename the value VerifyDomainName.
    6. Double-click VerifyDomainName.
    7. In the Value data box, enter 0.
    8. Click OK.
    9. On the File menu, click Exit.
    10. Open CRM and add user again.