Upgrade error

[Rueda]

Hello, I'm upgrading to version Nov-2021 from 6.5.581. After installation we got this error:

In version Nov-2020 it works fine (version currently running).  .PEM had been removed but the error still persist.

Did someone experience this error?

[john_wang]

Hello @Rueda ,

Because of Replicate 6.5 is out of support, the upgrade should be taken in 2 steps:

1- Upgrade from 6.5 to 2020.11 (v7.0)

2- Upgrade from 2020.11 to 2021.11 finally

The information can be found in Replicate 2021.11 Release Notes .

Please take note that backup the Replicate DATA folder before you performing every step so far you may roll back to previous version if you hit any error. A best practice is Upgrade Guide .

Regarding the error message, can you check the Windows Even Viewer to see if any helpful information there.

Hope this helps.

Regards,

John.

[Rueda]

Hi and thanks for your reply.
these are the steps we have followed, but it does not work. Actually we have the version 7 Nov-2020 running without problems, is when we try to upgrade to Nov-2021 the service cannot be started.
In below environments, we follow the same instructions and they work properly.

Please let me know if you need any other information that I can provide.

[shashi_holla]

Hi @Rueda 

Please reboot the windows server and then run the installable for 2021.11. It should internally stop the Replicate service for 7.0, upgrade the instance and bring up the services once the upgrade is done. Please check the services after you hit finish on the installation process and check if its active. If it still not running and get the same error when we try to start it manually then the best way to get help is to open a support case.

Thank you,

[Rueda]

Hello,

After test this solution it does not work. When the version 2021.11 is installed the service cannot start:

[shashi_holla]

Hi @Rueda 

My earlier response was not supposed to be marked a solution since we did not get confirmation from you. Please try this option:

1. stop Replicate windows service (both server and UI) if its running. Also if you have QEM make sure that all Replicate tasks are in stopped state.
2. Backup the current repctl.cfg file in installation directory bin folder. 
3. Add a new parameter "enable_passthrough_filter": true using an admin account. Or copy the file to desktop, add the parameter and copy it back to bin directory with admin privileges.
4. Restart the service.

Let me know if this works.

Thank you,

[Heinvandenheuvel]

When a Windows service fails to start it is unlikely to provide useful information in it's own log files, because it may not have run at all. The best place to start for this is the Windows Event Logger. On my own workstation i like to delete everything first, then retry the start and check all components for recent activity/messages. On a production server you'll have to be more careful checking the time for the test against many entries in the log. What did you find?

I assume the username was not changed during the upgrade, but that would be my first think to test. Go to the service tool; find the Attunity Replicate Server; right-click for Properties; check the 'Log On' tab. Is it running as 'Local System account'? If not , is the selected account still valid, with adequate privs? Does it still have access to mk.dat and the Replicate data directory (default: C:\Program Files\Qlik\Replicate\data)

User Guide: "Windows Permissions
By default, Qlik Replicate must be installed as an Administrator. After installing Qlik Replicate, you can opt to
run Replicate under a different account, as described in Running Replicate under a different account (page 33)"

Hope this helps,

Hein.