Video Screencast Help

Provisioning Task attempts to talk to all DCs

Created: 21 Apr 2008 • Updated: 15 Feb 2013 | 3 comments
This issue has been solved. See solution.
In our organization, we have dozens of different domains. Within the Vault, a site provisioning task wants to communicate with every domain controller it can, whether that domain is on the Vault or not. Is this something that is hard coded into the software or are there options to limit the task to only function within its domain?  Thanks!
It's causing the Provisioning Task to take far too long to do its job.
Here is one example of one of the domains it's trying to chat with.
Event Type: Warning
Event Source: Enterprise Vault
Event Category: Exchange Provisioning Task
Event ID: 41143
Date:  4/21/2008
Time:  12:05:52 AM
User:  N/A

The Exchange mailbox provisioning task could not connect to a domain controller for a domain in the forest. The task cannot process any Active Directory objects from this domain.
Task: Exchange Provisioning Task for ssv.wa.lcl
Domain: ssv.wa.lcl
Failed domain: SIB
Error code: DsGetDcName() [1355]
For more information, see Help and Support Center at
Discussion Filed Under:

Comments 3 CommentsJump to latest comment

MiaLid's picture

Did you ever get an answer on this?
Is there a registry hack so I don't have to see the warning anymore?

MichelZ's picture

Try setting an explicit GC.
Right click and select properties on your domain.
(VAC -> Targets -> Exchange -> <domain>)

imagebrowser image

Paul Grimshaw's picture

The only problem I see with that is if the DsGetDcName function cannot get the GC then will specifically assigning one work? It may do but without seeing like a DTRACE or maybe network sniff impossible to tell. What Michael has told you is correct to specify a GC but if that does not work then I would be using nltest etc to see what the problem is. Just do a google of dsgetdcname 1355 and you will get a plethera of information

EV Backline Technical Support Engineer APJ Region