Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
CRM 2011 - Unable to open Deployment Manager - ActiveDirectoryObjectNotFoundException RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    1
    Sign in to vote

    I recently installed UR12 and UR17 on the CRM 2011 server. After this point I am unable to open deployment manager. Upon opening it display this exception:

    Type is not resolved for member 'Microsoft.Crm.CrmSecurityException,Microsoft.Crm.Core, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.

    I did a CRM trace and this is the underlying exception.

    at CrmException..ctor(String message, Exception innerException, Int32 errorCode, Boolean isFlowControlException)  ilOffset = 0x0
    at CrmException..ctor(String message, Exception innerException, Int32 errorCode)  ilOffset = 0x0
    at SecurityUtils.GetActiveDirectoryEntry(String searchItem, String searchFilter, String searchItemLogInfo, Boolean throwIfNotFound, String domainName)  ilOffset = 0x44
    at SystemUserService.GetCaseSafeName(String domain, String accountName)  ilOffset = 0x188
    at SystemUserService.GetCaseSafeName(String name)  ilOffset = 0x50
    at SystemUserService.GetIdsFromName(String userName)  ilOffset = 0xB
    at SecurityRoleService.TryVerifyUser(String userName, SecurityRole role)  ilOffset = 0xC
    at SystemUserController.TryVerifyUser()  ilOffset = 0xD
    at DMSnapInHelper.DisplayMessageBoxIfCurrentUserIsNotSystemUser(Console console)  ilOffset = 0x0
    at DMSnapIn.OnInitialize()  ilOffset = 0x27
    at SnapInBase.Initialized()  ilOffset = 0x41
    at SnapInClient.Microsoft.ManagementConsole.Internal.ISnapInClient.Initialize(ISnapInPlatform snapInPlatform)  ilOffset = 0x14
    at UnsafeNativeMethods.DispatchMessageW(MSG& msg)  ilOffset = 0xFFFFFFFF
    at ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)  ilOffset = 0x18E
    at ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)  ilOffset = 0x1F7
    at ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)  ilOffset = 0x13
    at SnapInMessagePumpProxy.Microsoft.ManagementConsole.Internal.ISnapInMessagePumpProxy.Run()  ilOffset = 0x34
    >Crm Exception: Message: Could not find AD entry for : 1234567 with SearchFilter: samAccountName, ErrorCode: -2147214038, InnerException: System.DirectoryServices.ActiveDirectory.ActiveDirectoryObjectNotFoundException: The specified domain does not exist or cannot be contacted.
    at System.DirectoryServices.ActiveDirectory.Domain.GetDomain(DirectoryContext context)
    at Microsoft.Crm.SecurityUtils.GetActiveDirectoryEntry(String searchItem, String searchFilter, String searchItemLogInfo, Boolean throwIfNotFound, String domainName)

    I have established the following things:

    1.) Account name is correct.
    2.) DC is contactable using FQDN and IP address

    I tried the following

    1.) Confirmed user can be queried in LDAP by writing a small console app and ran it in the crm server. The user is found. No exception.
    2.) Tried setting PreferredDc registry key in the crm server with a specific DC. Didn't make any difference.
    3.) LDAP tracing using tracelog. I could not pickup any useful information.

    This issue started happening only after installing UR12, UR17 and restarting the server. Have you guys seen this error before? If so, any suggestions as to what the fix is? My understanding is Deployment Manager runs under the context of the current user (checked this with process explorer). Does it under a different security context while querying LDAP and that could be a the reason for this issue?

    Wednesday, May 28, 2014 2:14 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    I tried to uninstall UR17 following Adam's advice and I encountered owner_import constraint violation on ImportBase table. I could only uninstall the rollup only after disabling this constraint. It seems the uninstall process tries to insert two rows into the ImportBase table with OwnerId 00000000-0000-0000-0000-000000000000, which is obviously not in the OwnerBase table. Once the constraint was disabled I was successfully able to uninstall UR17. I deleted these two rows from the ImportBase table after this and re-enabled the constraint. I am now able to open Deployment Manager after I downgraded to UR16. This whole issue has taken me 1 week to resolve and has been quite frustrating.
    • Proposed as answer by Andre.K.MMVP Sunday, June 1, 2014 10:41 AM
    • Marked as answer by NatrajYMVP Sunday, June 1, 2014 10:53 PM
    Friday, May 30, 2014 11:14 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I faced similar issue. In my scenario the server suddenly powered off and caused this issue. I rejoined the server to the AD and added the required prevgroup settings on AD. So, the issue completely resolved. Maybe this could help you.

    Persian Dynamics CRM Community | انجمن متخصصان فارسی زبان

    Wednesday, May 28, 2014 5:34 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Having the same issue after installing UR17. No resolution as yet.

    It appears to be a bug in UR 17.

    our domain is company_com or company.com

    the code resolves company_com to company.com and then chops of everything after the first '.'

    From the log

    The user that has been passed is NOT a local system user. Use the current domain to query AD. Full domain name: company.com. Short domain name: company

    • Edited by AdamMills Wednesday, May 28, 2014 3:52 PM New info
    Wednesday, May 28, 2014 3:22 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you for you replies guys. Adam - I saw the same line in the CRM trace logs too just before it queries the DC using the samAccountName. I didn't pay much attention, as my console app, which uses similar code was working. One thing that I noticed yesterday was that the network traffic differs between been console app and the Deployment Manager when I traced it using netmon. The FQDN for our machines is as such: machinename.part1.part2.part3. I can see from the netmon logs that a NbtNs message is being sent out to query the part1 DC after multiple LDAP messages. There is no such message from my console app. I am not sure whether uninstalling UR17 and installing UR16 is the fix. Did you have the same issue with UR16 Adam?

    Payman - Are you on UR17 as well?

    • Edited by NatrajYMVP Wednesday, May 28, 2014 10:44 PM Forgot to add question to Payman
    Wednesday, May 28, 2014 10:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Reverting to UR16 fixes the issue.
    Thursday, May 29, 2014 1:11 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    There is a workaround:

    Install the CRM Server Role "Deployment Administration Server" on another server, using CRM 2011 UR6 (5.0.9690.1992) and connect to the existent CRM deployment.

    Thursday, May 29, 2014 4:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I'm experiencing the exact same issue on two different CRM installations after installing UR17.  Has anyone successfully opened Deployment Manager after installing UR17?
    Friday, May 30, 2014 10:32 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I tried to uninstall UR17 following Adam's advice and I encountered owner_import constraint violation on ImportBase table. I could only uninstall the rollup only after disabling this constraint. It seems the uninstall process tries to insert two rows into the ImportBase table with OwnerId 00000000-0000-0000-0000-000000000000, which is obviously not in the OwnerBase table. Once the constraint was disabled I was successfully able to uninstall UR17. I deleted these two rows from the ImportBase table after this and re-enabled the constraint. I am now able to open Deployment Manager after I downgraded to UR16. This whole issue has taken me 1 week to resolve and has been quite frustrating.
    • Proposed as answer by Andre.K.MMVP Sunday, June 1, 2014 10:41 AM
    • Marked as answer by NatrajYMVP Sunday, June 1, 2014 10:53 PM
    Friday, May 30, 2014 11:14 AM
  • Question
    Sign in to vote
    3
    Sign in to vote

    Rolling back to UR16 isn't really an acceptable 'fix' for this issue, given that UR17 fixes other critical issues for us.  The fact that you have to mess around in the database disabling constraints in order to uninstall UR17 and go back to UR16 should really be logged as a separate bug with Microsoft.

    Please upvote the bug regarding being unable to open Deployment Manager on connect: https://connect.microsoft.com/dynamicssuggestions/feedback/details/883263/bug-ur17-deployment-manager-domain-resolution

    Monday, June 2, 2014 4:20 PM
  • Question
    Sign in to vote
    2
    Sign in to vote
    Thank you Adam for posting this connect. I wanted to do this today. Please vote up on connect (https://connect.microsoft.com/dynamicssuggestions/feedback/details/883263/bug-ur17-deployment-manager-domain-resolution) so this can be fixed ASAP. Thank you for the workaround Alexander.
    Wednesday, June 4, 2014 9:40 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Voted - I've never been on that site before but in case anyone else runs into the 'page not found' error, you need to first go to

    https://connect.microsoft.com/directory/?keywords=dynamics and click Join on the Dynamics CRM program

    Thursday, June 5, 2014 12:06 AM