Skip to main content
Announcements
A fresh, new look for the Data Integration & Quality forums and navigation! Read more about what's changed.
cancel
Showing results for 
Search instead for 
Did you mean: 
Jon_Donker
Creator

Upgraded Enterprise Manager failing to start

Hi,

We're currently running Qlik Enterprise Manager  May 2021 (2021.5.0.543) and wanting to update it to 2022.11.x.y to take advantage of newer API.  We are running QEM on a Windows 2019 server

When we do - the QEM service will cycle with error and restart with the following message in the error in the log file

[ERROR] Object reference not set to an instance of an object.

The same error happens when we go directly to 2022.11.x.y; or use 2022.05 as an intermediate upgrade.

We have a case opened with qlik; but checking if anyone has come across this problem before.

Labels (2)
1 Solution

Accepted Solutions
Jon_Donker
Creator
Author

I ran the upgrade today on production.  I rewrote the procedures above on my website so I can refine the steps later https://craftcookcode.com/?p=1108.

View solution in original post

6 Replies
OritA
Support

Hi, 

Please try to upgrade to the latest SP of QEM 2022.11  - SP2(see link below) as it includes several fixes that are relevant to the problem you are facing. If using this SP (SP2) you still face an issue,  please open a case to support so we can further troubleshoot  the cause of the problem. 
Link to installation files of QEM 2022.11 SP2: https://files.qlik.com/url/zni2gq5nfntjidwn

 

Thanks & regards,

Orit

Niteeshkv
Contributor

Were you able to resolve it, I ran into same issue.

Jon_Donker
Creator
Author

Niteeshkv - no luck yet.  2022.11 -SP2 returned the same error.  

narendersarva
Support

Hi @Jon_Donker 

Please check if the QEM user has sufficient permissions. To troubleshoot further we may need to review the logs for better understanding. I see you have already raised the case for this error.  Our support team will take care by reviewing the logs.

 

Thanks
Naren

Jon_Donker
Creator
Author

Hi @Niteeshkv - this is the work around process so far that we have got with Qlik.  Qlik is working on a permanent fix.  It is a bit lengthy of a process so I will leave it up to you whether to go forward with it; or wait for a patch.  

Please correct any steps that I might have gotten wrong 

I have it working in dev going from 2022.05 -> 2022.11 on a Windows server.

You will need:

  • Username/Password that AEM connects to the analytics database
  • Privilege user account for your Analytics database 
  • Password for the user that you use to connect your QR nodes to AEM
  • A SQLite database client 
  • Handy to have - an editor that can validate json format

 

  1. Log on to AEM and stop the monitoring of your QR nodes.  
  2. Remote desktop to your AEM box and stop the AEM server
  3. Backup the C:\Program Files\Attunity\Enterprise Manager\data
  4. Export the AEM repository with the command:
    aemctl repository export -f C:\temp\qem_repo_202205.json -w
    ​
  5. Connect to the Postgres server and run the following command to export the schema:
    cd C:\Program Files\PostgreSQL\10\bin
    pg_dump -U <username> -p <password> -s -c <analytic database> > C:\Temp\cdcanalyticsp.sql​
  6. Edit C:\Temp\cdcanalyticsp.sql and find/replace the analytics database name with a new temp database name (eg: cdcanalytics_2022_11_p)
    Save the file
  7. Run the following command to import the new database:
    psql -d postgres -U <username> -f C:\Temp\cdcanalyticsp.sql​

    This will create a new database that we can temporarily connect to and not lose existing database when re-initialising the repository

  8. PVT that the new database is there 
  9. Open up the file C:\temp\qem_repo_202205.json
  10. Find the json section with 
    "name": "Replication Analytics",
    "type": "AttunityLicense",

    And remove this whole section.  Save the json file as C:\temp\qem_repo_202205_Fix.json

  11. Go to Add/Remove and uninstall Enterprise manager
  12. Once remove - delete the the folder C:\Program Files\Attunity\Enterprise Manager
  13. Install AEM 2022.11 but don't install the postgres section.  Log into AEM and confirm that the installation worked.
  14. Stop the AEM service and run the following command:
    aemctl repository import -f C:\temp\qem_repo_202205_Fix.json -w​
  15. Restart AEM service; and go to AEM console
  16. Go to Settings -> Repository connections
    Enter in username password and database as the new database that was created (e.g cdcanalytics_2022_11_p)
    Intialize the repository and start the connector
  17. Stop the AEM service again:
    Open up Attunity\Enterprise Manager\data\Java\GlobalRepository.sqlite
    Browse the table AnalyticsConfiguration
    Look for name = "AnalyticsConfiguration" and modify the json value "cdcanalytics_2022_11" to the original PostgreSQL DB.
    Save sqlite database
    Restart AEM service
  18. Log onto Enterprise manager.
    For each server - edit the connection details and re-enter their passwords.
    One do - start monitoring them

 

Backout

  1. Uninstall AEM and delete the folder C:\Program Files\Attunity\Enterprise Manager\data
  2. Reinstall AEM 2022.5.
  3. Stop the AEM service
  4. Replace C:\Program Files\Attunity\Enterprise Manager\data with the backed up database folder.
  5. Restart the AEM service
  6. Re-enable the monitoring the the QR nodes.

 

 

Jon_Donker
Creator
Author

I ran the upgrade today on production.  I rewrote the procedures above on my website so I can refine the steps later https://craftcookcode.com/?p=1108.