none
Exchange PST Capture 2010 - Can't browse mailboxes

    Question

  • I am unable to browse mailboxes from the tool in order to set a destination.
    Error from the PST capture service log...

    -------------------------------------------------

    13:46:13.108|Verbose|Active Directory    |7  |Creating Active Directory Service
    13:46:13.108|Verbose|Active Directory    |7  |Getting Active Directory Server Provider
    13:46:13.108|Verbose|Active Directory    |7  |Creating managed Exchanges and Domains state
    13:46:13.108|Verbose|AD                  |7  |GetDomainControllersForDomain: DC=domain,DC=com, code: NewCode, forceDC:
    13:46:13.122|Error  |CentralService      |7  |Error occured in get mailbox update check
    System.DirectoryServices.ActiveDirectory.ActiveDirectoryOperationException: Unable to obtain DNS hostname of Active Directory domain controller with ntdsa object name "CN=NTDS Settings,CN=DC,CN=Servers,CN=State,CN=Sites,CN=Configuration,DC=domain,DC=com".

    -------------------------------------------------

    We have 3 DCs in our enviroment: 2 @ HQ & 1 at a remote site.
    The weird part is that it ALWAYS goes for the remote DC.
    I tried running the tool from a machine @ the remote site to rule out our site to site firewall, and got the same error.
    Perhaps there is some tricky backdoor way to assign a preferred DC?

    I would REALLY like to use this tool rather than having to powerscript all the hundreds of PSTs manually, any suggestions?

    Monday, February 20, 2012 10:13 PM

Answers

  • I don't really have time to wait for a solution on this, so I've been importing mailboxes with New-MailboxImportRequest.
    Since all of my PST files are centrally stored on a file server, it's not that much more work to just do 2-3 at a time from the command line.
    There have also been a few employees who didn't want their PSTs merged together, so the -TargetRootFolder switch was required (didn't see an option for this in the capture tool).


    This tool would have been a time saver, but I guess we can technically close the ticket since I no longer require a solution.

    • Marked as answer by Frank.Wang Tuesday, February 28, 2012 1:59 AM
    Monday, February 27, 2012 5:37 PM

All replies

  • Hi PDX Tad,

    What permission you are assigned to run the console?

    If possible, please run the tool as Domain admin & Organization Management to test.


    Frank Wang

    TechNet Community Support

    Wednesday, February 22, 2012 6:53 AM
  • Hi,

    Did you manage to resolve this issue as I have the same problem....Unable to set a destination mailbox! :(Thanks

    thanks

    Adam


    Adam

    Monday, February 27, 2012 2:23 PM
  • The issue is still unresolved.

    I used our dommaster account and verified it was in the organizational management & Public folder management groups.
    I verified that the dommaster account has a mailbox.
    I assigned all the appropriate pre-requisits to a new service account and got the same error.
    I also got the tool working in our lab enviroment without any hitches.

    It still seems like an issue with it trying to authenticate with the remote DC.
    I tried fiddling with DNS and other stuff to try to make it use a local DC, but didn't get anywere.


    NOTE: I removed the server and domain names from the error logs above.
    • Edited by PDX Tad Monday, February 27, 2012 4:31 PM
    Monday, February 27, 2012 4:30 PM
  • Shame you didn't get it sorted.

    My error is a little different but I am trying to run the tool in a child domain, the tool does keep trying to access a DC in the forest root domain so I think that might be the problem although it should still work and be able to find the address book for a list of mailboxes.

    13:12:31.465|Error  |CentralService      |8  |Error occured in get mailbox update check
    System.InvalidCastException: Specified cast is not valid.
       at System.Data.SQLite.SQLiteDataReader.VerifyType(Int32 i, DbType typ)
       at System.Data.SQLite.SQLiteDataReader.GetString(Int32 i)
       at RedGate.PSTImporterForExchange.Engine.Repository.DbMailbox.GetMailboxes(Boolean is365)
       at RedGate.PSTImporterForExchange.Engine.Repository.RepositoryMailbox.GetMailboxes(Boolean is365)
       at RedGate.PSTImporterForExchange.CentralService.PstCentralService.DoADPoll(Object state)

    I have raised my own post here: http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/563bf3b6-89dc-4fdd-96f5-e4b3d563ff6b/

    Thanks


    Adam

    Monday, February 27, 2012 5:22 PM
  • I don't really have time to wait for a solution on this, so I've been importing mailboxes with New-MailboxImportRequest.
    Since all of my PST files are centrally stored on a file server, it's not that much more work to just do 2-3 at a time from the command line.
    There have also been a few employees who didn't want their PSTs merged together, so the -TargetRootFolder switch was required (didn't see an option for this in the capture tool).


    This tool would have been a time saver, but I guess we can technically close the ticket since I no longer require a solution.

    • Marked as answer by Frank.Wang Tuesday, February 28, 2012 1:59 AM
    Monday, February 27, 2012 5:37 PM
  • Did you ever find the fix? I'm running into the exact same issue - the tool worked great for 4+ months and recently it stopped working. The only change I could think of are security patches on the domain controllers. Uninstalled/re-installed the tool to no avail.. Would hate to use PS script as this tool was a real time saver especially for large quantity of PSTs.
    Thursday, July 19, 2012 8:13 PM
  • I ended up using powershell to import the mailboxes, and it only took a few days to do the whole enviroment.

    My specific problem was a domain authentication issue through a site to site link (firewall).
    I recently discovered that the firewall was blocking about half of the ports required for site to site replication and other active directory services (we never noticed it wasn't working properly).

    The fix in our case WOULD have been to resolve the site to site link between the DCs.
    An invaluable tool in discovering and verify that many ports required for DCs where being blocked was "portqryui".
    This tool can be run from a local and remote DC, and it's specifically used to test DC to DC communication.

    The PST import tool would have then been able to successfully authenticate to the remote DC and it probably would have worked.

    Thursday, July 19, 2012 8:33 PM
  • Thanks for the pointer on authentication.

    Unfortunately that can't be it as I've checked the account/password is still good with appropriate group membership (domain admin in fact).  Also with the same account / DC it was working previously for 4+ months.

    I'm leaning toward security patches, perhaps .net framework related, to be the culprit but don't know for sure at this point.

    Thursday, July 19, 2012 9:00 PM
  • I've come up with a workaround. It's not ideal but I think still beats resorting to PS scripts.

    Download this tool - "SQLite Database Browser" from SorceForge http://sourceforge.net/projects/sqlitedbrowser/

    Stop the central service (aka. Microsoft Exchange PST Capture Service) to prevent database from updating dynamically from agents.

    Then use SQLite browser to open c:\programdata\microsoft\exchange\pst capture\data . The table that you can modify to populate the target mailbox/SMTP address is "pst_import_files" .

    Save changes and then in PST Capture close and re-load the import list and the target mailbox is now populated! If you're in a large environment like ours this may actually be faster than the browse and select method (e.g. when it was working) as that takes time to come up - browse - select.

    Will

    Tuesday, July 31, 2012 9:26 PM
  • One more thing - the "import status" value should be changed from a 0 to 1
    Tuesday, July 31, 2012 9:37 PM
  • I'm finding that one user in the check is not getting NBName populated, perhaps this is the reason?

    Maybe the issue is in fact 1 bad AD object and the software just having awful error handling. I doubt we should expect an update from Microsoft unfortunately, but maybe we can figure it out ourselves - it's querying via LDAP as well.


    Phluxed

    Tuesday, August 07, 2012 1:12 PM
  • Ok so i had the same issues. Push the Set Mailbox and it wouldn't list anyone.

    Look in the Event Viewer > Applications and Services ... > Microsoft Exchange PSTCapture.

    I was seeing this every couple seconds.

    Event ID 32

    PST Capture Service:

    CentralService
    Error occured in get mailbox update check
    System.DirectoryServices.ActiveDirectory.ActiveDirectoryOperationException: A local error has occurred.
     ---> System.DirectoryServices.DirectoryServicesCOMException (0x8007203B): A local error has occurred.

    ------------------------------------------------------------------------------------------------------------------------------

    -

    We recently had some old domain controllers that were in AD but the servers were shutdown or not reachable. They were in AD Sites and Services so the Capture tool was trying to connect. In fact i think the PST Capture will connect to first alphabetical named DC. It was not reachable. So when this "Old" dc was removed from the domain properly and from AD Sites and Services properly the tool started working.

    I have attached some screen shots.

    What i noticed by restarting the service in Resource Monitor, the service was was initially connecting to all DC's in the local AD Site. So when those old servers were there but not reachable it would fail and log the event and no Set Mailbox would work. After the service does connect successfully, i noticed that PST Capture service would only really just connect to itself or another PC with the PST Capture Agent running on it.

    Key item is restart the PST Capture service and watch it connect to each DC and one connection to itself. They must ALL be reachable. Next issues are permissions/connectivity. I proved these by using the LDP.exe tool to simply create a connection and bind. All was good.


    * Blackberry Certified Support Specialist * Blackberry Certified Server Administrator * Blackberry Certified Server Support Specialist * Comptia A+ * Comptia Linux + * Comptia Network + * MCITP - Enterprise Support Technician * MCITP - Enterprise Desktop Administrator 7 * MCITP - Server Administrator * MCITP - Enterprise Messaging Administrator * MCTS - 70-620 - TS: Configuring Microsoft Windows Vista Client * MCTS - 70-622 - PRO: Supporting and Troubleshooting Applications on a Windows Vista Client for Enterprise Support Technicians * MCTS - 70-685 - Windows 7 Enterprise Desktop Support Technician * MCTS - 70-686 - Windows 7 Enterprise Desktop Administration * MCTS - 70-432 - Microsoft SQL Server 2008, Implementation and Maintenance * MCTS - 70-640 - Windows Server 2008 Active Directory Configuration * MCTS - 70-642 - Windows Server 2008 Network Infrastructure Configuration * MCTS - 70-643 - Windows Server 2008 Applications Infrastructure Configuration * MCTS - 70-646 - Windows Server 2008

    Friday, September 21, 2012 3:05 PM