Error "Setup has detected Opalis 6.3 installed on this computer" when installing System Center 2012 Orchestrator
Published Feb 15 2019 05:13 PM 248 Views
First published on TECHNET on Nov 09, 2011

Just a quick heads up on a new KB article we just published this morning on an error you may receive when attempting to install System Center 2012 Orchestrator on a system that had been running Opalis 6.3:

=====

Symptoms

When installing all components of System Center 2012 Orchestrator or one of the individual components (Runbook Designer, Runbook Server or Orchestration Console and Web Service), the following error is received:

Setup has detected Opalis 6.3 installed on this computer. To continue installing System Center 2012 Orchestrator, uninstall Opalis 6.3, and then run Setup again.

Cause

One or more Opalis Integration Server 6.3 components is being identified as installed by Windows Installer.

Resolution

Remove the following programs using Windows Programs and Features (Control Panel->Programs->Programs and Features):

  • Opalis Integration Server - Action Server
  • Opalis Integration Server - Foundation Objects
  • Opalis Integration Server v6.3 - Client
  • Opalis Integration Server v6.3 - Management Service


If all of the above programs have been removed and no longer appear in Programs and Features then an artifact of one of the programs must still exist and is visible to Windows Installer. If this is the case, you can search the registry for each of the following identifiers and remove any that are found:

  • {FE12BDDD-2CE7-4241-8B93-AF97BF361463} - (Opalis Integration Server v6.3 - Management Service)
  • {2F8661D7-FE34-451F-800B-EEE98D8097E9} - (Opalis Integration Server - Action Server)
  • {BAAC2B61-F3B5-4F13-AD13-784F59636F47} - (Opalis Integration Server v6.3 - Client)
  • {EC6D5121-8B27-439F-A00D-AB69E273F346} - (Opalis Integration Server - Foundation Objects)
More Information

Depending on what artifact is causing Windows Installer to recognize the program as at least partially installed, you may be able to utilize MsiZap.exe to forcibly remove the remaining artifacts as an alternative to manually modifying the registry.

Msizap.exe (Windows) : http://msdn.microsoft.com/en-us/library/aa370523(v=VS.85).aspx

=====

For the most current version of this article please see the following:

2634522: Error "Setup has detected Opalis 6.3 installed on this computer" when installing Syste...

J.C. Hornbeck | System Center Knowledge Engineer

App-V Team blog: http://blogs.technet.com/appv/
AVIcode Team blog: http://blogs.technet.com/b/avicode
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
OOB Support Team blog: http://blogs.technet.com/oob/
Opalis Team blog: http://blogs.technet.com/opalis
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
SCMDM Support Team blog: http://blogs.technet.com/mdm/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

Version history
Last update:
‎Mar 11 2019 08:55 AM
Updated by: