locked
Custom Aspx - User Access - Multi Tenant Error RRS feed

  • Question

  • I have a few custom aspx pages.  They were working fine for nearly everyone, except one person.  He was receiving an error, "User is disabled, or not a member of any business units", whenever he tried to access a custom aspx page.

    After many days of suffering I finally narrowed down the issue.  We have two CRM tenants on the same server, and the same user existed on both tenants.  On the first tenant, (the default tenant), the user was disabled.  On the second tenant the user was enabled. 

    So obviously there is a conflict there, when the same user exists on both tenants, and is disabled in one and enabled in the other.  I was able to temporarily fix the problem by enabling the user in both tenants.  This is not ideal as it takes up more licenses.

    Can someone help me with this error?  Perhaps I don't have things configured in IIS correctly for my custom apsx pages?

    Thanks for you help,
    Craig
    Sunday, January 11, 2009 7:36 PM

Answers

  • I expect the issue is that the organisation name is not being explicitly specified when connecting to the page. In this case, CRM will take each user's default organisation, and I expect that the default organisation for the user with connection problems is the organisation in which their user is disabled.

    One solution is to change the user's default organisation (note that this is different from the system-wide Default Organisation that you can set in Deployment Manager), but this can only be done with a direct SQL modification in the MSCRM_Config database, so a preferable approach would be to explicitly specify the organisation in the Url.

    THe details of this depend on how you launch the aspx page, but the main point is that you want a Url in the following format. You can use the prependOrgName client-side function to do this:

    /orgname/ISV/Folder/Page.aspx


    Microsoft CRM MVP - http://mscrmuk.blogspot.com  http://www.excitation.co.uk
    Tuesday, October 19, 2010 9:17 AM
    Moderator

All replies

  • I'm having a very similar problem. Strangely enough, on our development servers everything works fine, regardless if the user is disabled in one organization.

    The only difference is that we have a later roll-up installed on our dev servers. Could this be a solution to your problem?

    Tuesday, October 19, 2010 8:49 AM
  • I expect the issue is that the organisation name is not being explicitly specified when connecting to the page. In this case, CRM will take each user's default organisation, and I expect that the default organisation for the user with connection problems is the organisation in which their user is disabled.

    One solution is to change the user's default organisation (note that this is different from the system-wide Default Organisation that you can set in Deployment Manager), but this can only be done with a direct SQL modification in the MSCRM_Config database, so a preferable approach would be to explicitly specify the organisation in the Url.

    THe details of this depend on how you launch the aspx page, but the main point is that you want a Url in the following format. You can use the prependOrgName client-side function to do this:

    /orgname/ISV/Folder/Page.aspx


    Microsoft CRM MVP - http://mscrmuk.blogspot.com  http://www.excitation.co.uk
    Tuesday, October 19, 2010 9:17 AM
    Moderator