Skip to main content

Qlik Sense Enterprise on Windows Upgrade Failed due to MobilityRegistrarService or qlik_notifier_service

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Alan_Slaughter
Support
Support

Qlik Sense Enterprise on Windows Upgrade Failed due to MobilityRegistrarService or qlik_notifier_service

Last Update:

Mar 28, 2023 3:45:59 AM

Updated By:

Sonja_Bauernfeind

Created date:

Jun 21, 2022 3:43:31 PM

The Upgrade of Qlik Sense Enterprise for Windows fails on the Qlik Dispatcher Service with:

ERROR: schema "MobilityRegistrarService" already exists
ERROR:  schema "qlik_notifier_service" already exists

 

Environment

 

Resolution

The solution to this issue requires modifications to the database. Prior to applying the solution, take a backup. See Backup and Restore.

To resolve this, we will rename the 'qlik_mobility_registrar_service' (i.e. qlik_mobility_registrar_service_old) as well as the 'qlik_notifier_service' schema prior to performing the installation/upgrade.

This will allow for the creation of the schema. In multi-node environments, it is suggested to rename the schema prior to each rim node installation/upgrade.

To rename the schema, perform the following steps:

  1.  Log on to the server running the PostgreSQL server
  2. Use pgAdmin to access the database (Installing and Configuring PGAdmin 4 to access the PostgreSQL database used by Qlik Sense or NPrinti...)
  3. Expand the SenseServices database so that Schemas is displayed and then expand Schemas so that the qlik_mobility_registrar_service schema is displayed
  4. Right-click the qlik_mobility_registrar_service and choose Properties
  5. Rename the qlik_mobility_registrar_service and click Save (i.e.  qlik_mobility_registrar_service_old)
  6. Repeat 4 to 5 for qlik_notifier_service.
  7. Run the Qlik Sense server installer on the Rim node

 

Cause 

The upgrade from November 2019 to February 2020 failed on the dispatcher service with the following error on the installation log:

CAQuietExec:  MobilityRegistrarService configuration started.
CAQuietExec:  WARNING: Skiping the database initialization. No superuser or password 
CAQuietExec:  specified.
CAQuietExec:  Creating schema 'qlik_mobility_registrar_service'.
CAQuietExec:  True
CAQuietExec:  Error executing database command "CREATE SCHEMA 
CAQuietExec:  "qlik_mobility_registrar_service" AUTHORIZATION "qliksenserepository"": ERROR: 
CAQuietExec:   schema "qlik_mobility_registrar_service" already exists
CAQuietExec:  At C:\Program Files\Qlik\Sense\MobilityRegistrarService\install\install-utils\P 
CAQuietExec:  ostgres.ps1:113 char:11
CAQuietExec:  +           throw  "Error executing database command  ...
CAQuietExec:  +           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
CAQuietExec:      + CategoryInfo          : OperationStopped: (:) , Exception
CAQuietExec:      + FullyQualifiedErrorId : Error executing database command "CREATE SCHEMA  
CAQuietExec:     "qlik_mobility_registrar_service" AUTHORIZATION "qliksenserepository"": ER  
CAQuietExec:    ROR:  schema "qlik_mobility_registrar_service" already exists
CAQuietExec:   
CAQuietExec:  Error 0x80070001: Command line returned an error.
CAQuietExec:  Error 0x80070001: QuietExec Failed
CAQuietExec:  Error 0x80070001: Failed in ExecCommon method
CustomAction CA_SetupQMR returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

Labels (1)
Version history
Last update:
‎2023-03-28 03:45 AM
Updated by: