Article ID: 111565, created on Jun 30, 2011, last review on Aug 23, 2015

  • Applies to:
  • Operations Automation

Automatic import from KB #111565

Symptoms

A Provider wants to deploy a new Windows Active Directory domain in POA to provision services through the Parallels Windows Provisioning Engine (WPE).

The Provider deploys two Domain Controllers, registers them in POA (installs POA Agent on the hosts), and tries to install the PPM package ADDomainController on them.

The package installation fails with an error like below:

Installation of package ADDomainController 1.9 (id=3037) to host ad01.host.local (id=300) was failed. Reason: Provisioning request failed. Invalid pointer []

Cause

The Provider did not deploy the WPE server in the new Windows domain; only domain controllers were deployed. POA could not find the provisioning engine to process the package installation request, so it throws the error message.

Resolution

The Provider has to deploy the WPE server prior to trying to install any packages on hosts in a newly deployed Windows domain. The same can be said about deploying a domain with the MPS provisioning engine.

In general, before trying to perform any provisioning task (and package installation is one of them), the needed provisioning engine (WPE or MPS) must be deployed in the Windows domain. Otherwise, POA will not be able to process the task.

Search Words

Reason: Provisioning request failed. Invalid pointer

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF