OFX controller installation fails on source machine with error "ControllerInstallationNotCompleted".

  • 7008000
  • 25-Feb-2011
  • 01-Aug-2017

Environment

PlateSpin Portability Suite
PlateSpin Protect
PlateSpin Migrate
PlateSpin Forge

Situation

This article discusses information about a conversion job failing when installing controller on source machine with the error "Controller installation has not finished in a timely fashion. Possibly because the machine is slow"
 
This issue can also occur if controller installation is attempted as a seperate job via PortabilitySuiteBrowser/PlatespinBrowser. If manual installation of controller is attempted on source after a failed job, it installs the controller fine. Below error is seen in the diagnostics from the failed job:
 
Type                    RequiresUserIntervention
ReportCode        ControllerInstallationNotCompleted
KB Link              
http://support.platespin.com/kb2/login.aspx?errorCodes=ControllerInstallationNotCompleted
Reason               Possibly because the machine is slow.
Message            Controller installation has not finished in a timely fashion. Possibly because the machine is slow.
 

This error occurs due to remote execution of controller installation failing. The underlying reason is unknown but most likely cause is a security policy preventing remote execution. Controller installation files are copied and can be viewed on source machine in "%Windir%\Platespin" directory.

Resolution

Web.config file needs to be edited to disable remote execution service for controller installation. Follow the instructions below to make the change:
  1. Navigate to the ".\Program Files\PlateSpin PortabilitySuite(\Migrate\Protect) Server\Web" directory.
  2. Using a text editor, open the web.config file.
  3. In the web.config file, locate the following entry (located near the end):

    <add key="InstallControllerUsingService" value="true" />
  4. Change the value from "true" to "false". The entry will look as under:

    <add key="InstallControllerUsingService" value="false" />
  5. Save the changes to the web.config file.

This will change the controller installation mechanism from using remote execution service to using local WMI on the source machine.