Article ID: 129692, created on Oct 26, 2016, last review on Oct 26, 2016

  • Applies to:
  • Operations Automation 5.5


On new WPE node deployement, custom MS SQL instance name entered into extended paramemetrs of the wizard is ignored.


The wpe_SQL_deploy.ps1 script uses hard-coded instance name MSSQLSERVER. Such behaviour is considered to be a software issue #POA-96052.


The issue is planned to be fixed in one of the future product updates. Until the issue is fixed, only hard-coded instance name MSSQLSERVER is available for WPE database.

Search Words


cannot change instance name


cannot set custom instance name

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF