Blog

« “There is already an object named ‘AttributeTypes’ in the database” during CRM 4.0 Upgrade
Change the Identifier for IIS Websites »

“No Microsoft Dynamics CRM user exists with the specified domain name and user ID” Error after CRM 4.0 Upgrade

If you receive this error message upon accessing Microsoft CRM 4.0 for the first time after an upgrade, chances are you are simply using the wrong URL.  It is important to note that because of the new multi-tenancy feature in CRM 4.0 it is now necessary to reference the Organization name in the URL.  The correct format for the homepage for example is:

http://servername:5555/organizationname/

As always, if you are looking for professional Microsoft CRM Consulting for assistance with installation, migration, or upgrade, contact Kazmarek Technology Solutions directly.

This entry was posted on Tuesday, March 11th, 2008 at 6:57 am and is filed under CRM. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

4 Responses to ““No Microsoft Dynamics CRM user exists with the specified domain name and user ID” Error after CRM 4.0 Upgrade”

  1. Vidivec Says:
    March 24th, 2008 at 5:50 pm

    Hello!
    I found your hints very helpfull. In this case when I request http://servername:5555/organizationname/
    I get:
    Invalid column name ‘CustomizationLevel’.
    Exception Details: System.Data.SqlClient.SqlException: Invalid column name ‘CustomizationLevel’.

    The thing is in Deployment Manager in Organizations I can see status ‘Pending’ for my default Organization.

    Another thing is in License I have 0 Number of Licensed Users.

    The 3.0 version I have upgraded was a Microsoft partner’s test license, the license code for 4.0 is also partner’s test license.

    I have convienced my customer to upgrade 3.0 to 4.0 but I want to test the upgrade procedure. Now, I’ve been spent simply too much time on this. Any idea?

  2. tsales Says:
    March 26th, 2008 at 7:12 am

    Did you have any unsupported customizations or third-party add-ons such as C360 before upgrading?

  3. yi Says:
    March 30th, 2008 at 11:17 pm

    Hi,

    I received exactly the same exception after hitting the CRM site with the orginization name. My case was that during the upgrade process, it failed on creating the metabase. I tried running an repair and the repair was done without any errors. Both CRM databases were created afterwards. Not sure if this has something to do with the failure when running upgrade.

    Vidivec, did you ever resolve this issue?

  4. tsales Says:
    April 8th, 2008 at 11:53 pm

    Vidivec and I have been in communication on the back-end although I dont think he has resolved it yet. I offered to assist him remotely but his location in Central Europe makes it difficult. This is apparently becoming a common issue and is related to the ft_documentindex full text catalog being missing or corrupt (atleast it was in my case). I would recommend checking the existance of that catalog and make sure it is enabled for the keywords, title, and SearchText. Check the article: http://blog.kazmarek.com/2008/03/11/full-text-index-inconsistency-when-upgrading-to-crm-40/

Leave a Reply