Knowledge Partner
Knowledge Partner
1429 views

Re: Exchange 2010 - ERROR: No provisioning handler is installed

On 29.06.2012 16:26, gdellatorre wrote:
>
> Further informations are:
> - Remote loader installed on Windows 2008 R2 standard with Exchange
> Management console 2010 sp1 RU6


When you installed the Exchange Service, did you use the Framework or
Framework64 path?

C:\WINDOWS\Microsoft.Net\Framework64

not

C:\WINDOWS\Microsoft.Net\Framework

---

It might be worth trying to uninstall/unregister the service and then
re-install it with the C:\WINDOWS\Microsoft.Net\Framework64 path (as per
the documentation.

https://www.netiq.com/documentation/idm402drivers/ad/data/bnutll4.html#bsdl6dc

Also is the Exchange Management console 2010 install on the remote
loader server patched to the same level as your actual Exchange mail
servers?
Alex McHugh - Knowledge Partner - Stavanger, Norway
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
Labels (1)
0 Likes
2 Replies
Knowledge Partner
Knowledge Partner

Re: Exchange 2010 - ERROR: No provisioning handler is installed

On 30.06.2012 16:06, gdellatorre wrote:
>
> Hi Alex,
> thank you for your suggestionn, yes, i'm sure it was installed using
> framework64 and not framework, but in case I anyway tried unregistering
> and re-registering the service, the I configured it to run with the
> right AD user permissions (as before) and I tested it (of course keeping
> my fingers crossed).
> Something changes, the provisiong continued a bit, but no mailbox is
> effectively provisioned and looking at the RL logs I see the problem is
> still there:


I'm pretty much out of ideas, at this point it doesn't sound like this
is an IDM issue, more likely it is an Exchange issue.

Can you provide more details regarding your config?

The AD remote loader box, is that the domain controller specified in the
trace "dc2k8x1a.group.local"?


Are there multiple Exchange mail servers in your environment? Could it
be possible that the command runs against a different mail server when
you run the Enable-Mailbox command via IDM vs running it via the
Exchange Shell? I know both commands are initiated from the remote
loader box, but the actual processing happens on an Exchange 2010 server.
Alex McHugh - Knowledge Partner - Stavanger, Norway
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Exchange 2010 - ERROR: No provisioning handler is installed

On 02.07.2012 09:16, gdellatorre wrote:
>
> Hi Alex,
> yes, dc2k8x1a is one of the 4 existing domain controllers, but the
> RL is not installed on it.
> RL is installed on Windows 2008 R2 standard SP1 with Exchange
> Management console, which is member of the group.local domain.


That configuration adds a lot of additional complexity to your
deployment (which makes it harder to troubleshoot)

> The Exchange server and the Exchange management console are at the same
> version and patch level (2010 sp1 RU6).
> I'll double check this morning how many exchange server there are, but
> it should be 3.
> I don't know if is possible that the command issued to one exchange
> server don't work on another server: from a logical point of view the
> exchange servers are exactly the same, and it looks to me that the same
> command should work on each server.


I strongly suspect it is a permission issue related to the remote
(exchange) server. This is based on the error code returned in your
trace 0x58, when you look up this error number it translates to a
network issue "A write fault occurred on the network."

> I don't understand one thing: if the problem is on exchange side, why
> the trace reports "-No provisioning handler is installed-"?


This is an Exchange error. It can mean several things. The error code
referenced in the same line gives a more specific clue (in this case
can't write to the network device)
-

One other thing.. in my experience, the AD Driver shim will append a
parameter that is missing from your trace -Alias 'mailnickname' to the
powershell command. This isn't strictly required as Exchange will just
use the value from sAMAccountName if the Alias parameter is omitted.

I don't think this is related to your problem, however as you haven't
provided the remote loader trace prior to the generation of the
powershell command I can't see if this is actually an error or not.
Alex McHugh - Knowledge Partner - Stavanger, Norway
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.