Solved

PST Capture Took

Posted on 2013-05-14
13
1,086 Views
Last Modified: 2013-05-24
Hi

I am running the PST Capture Tool 2.0 on 2008R2 - Exchange 2010

The tool finds the PSTs, but when I select "Set Mailbox" - it gives an error saying failed to retrieve mailboxes.

The error log shows this:

22:33:47.239|Verbose|Server Provider     |9  |Get server took 1.6536s - AD performance may not be optimal
22:33:47.239|Error  |CentralService      |9  |Error occured in get mailbox update check
System.DirectoryServices.ActiveDirectory.ActiveDirectoryOperationException: The directory service is busy.

I'm pulling my hair out with this, I've tried:

- re-installing the capture tool
- re-installing on a new 2012 server
- re-installing on the 2003R2 DC

What else can I try?
0
Comment
Question by:cakelayers
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 2
  • 2
  • +1
13 Comments
 
LVL 30

Expert Comment

by:Scott C
ID: 39164580
Contact the makers of the tool?
0
 

Author Comment

by:cakelayers
ID: 39164621
That's meant to be an Expert Comment?

What's the point of Experts Exchange if idiots come along and say "Why not contact Microsoft?"
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39164633
The first poster is obviously unaware of the tool in question and that is a Microsoft product.

Is Exchange installed on a domain controller?
Is the global catalog close to Exchange?

Are you running the tool on Exchange, or on a member server? What permissions does the account have that you are running the tool under?

Simon.
0
Instantly Create Instructional Tutorials

Contextual Guidance at the moment of need helps your employees adopt to new software or processes instantly. Boost knowledge retention and employee engagement step-by-step with one easy solution.

 
LVL 30

Expert Comment

by:Scott C
ID: 39164641
Nice...

Sometimes that is the suggestion.  

You have tried almost all of the troubleshooting steps.  At this point I'd contact the makers as there might be a bug with their program.

You might also want to watch the name calling.  That type of behavior is frowned on here.
0
 

Author Comment

by:cakelayers
ID: 39164676
Simon, thanks for the response.

- Exchange is not running on a DC
- tried on 2008R2 (Exchange Server) and 2012 Standard Member Server
- I'm running under the main domain administrator

Apologies for the name-calling, frustrated at the end of a thankless evening getting nowhere.
0
 

Author Comment

by:cakelayers
ID: 39164687
oh, and when you said 'close' to a GC server, it's on the same LAN, if that's what you mean?
0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 39164693
The files listed above are:
    PSTCapture.msi - Contains the console and administrative toolset
    PSTCaptureAgent.msi - Contains the agent for workstations

Pre reqs
Microsoft .NET Framework 4.5 or later
PowerShell 3.0 or later
Microsoft Outlook 2010 x64 (only required on the host computer where you install the Central Service and Console)

64-bit version of Microsoft Outlook 2010 (required only on the host computer where you install the PST Capture Console)

Try it on some Client thats 64 bit within the environment

- Rancy
0
 

Author Comment

by:cakelayers
ID: 39164859
tried 64 bit clients, still the exact same error on whichever client runs the console.

Looks like an AD problem??
0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 39164880
Do you have some different account that maybe you can try ..... if AD problem maybe you can check with Repadmin or some commands to ensure its healthy

- Rancy
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39165935
Create a specific account for the task that has the relevant permissions in EXCHANGE. Make it a domain only admin. From memory it will need Exchange View Only permissions as well to enumerate the mailboxes.

Same LAN is fine - the point I was making there for the GC was some people try to run it over a WAN and things start to time out because of the load on AD.

Simon.
0
 

Accepted Solution

by:
cakelayers earned 0 total points
ID: 39167642
I figured out today that it was because of an old tomb-stoned domain controller in sites and services.

Removed and cleaned up AD, it started working straight away.

Thanks for all your help in any event, can I mark this comment as the answer for others facing the same problem?
0
 

Author Closing Comment

by:cakelayers
ID: 39193721
Figured the answer out on our own, and none of the suggested solutions were accurate.
0

Featured Post

Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
This article shows theĀ method of using the Resultant Set of Policy Tool to locate Group Policy that applies a particular setting.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlleā€¦
This video discusses moving either the default database or any database to a new volume.

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question