Upgrading to June 2017 from QlikSense 3.0.0

[ansarikashif2017]

Hi All,

We want to upgrade our QliKSense 3.0.0 environment to QlikSense June 2017. As I understand, we need to upgrade to 3.1 SR2 before we upgrade July 2017.

I wanted to know which of the below path makes more sense or if people have encountered less issues on which path :-

Path 1 :    QlikSense 3.0.0 -> QlikSense 3.1.2 -> QlikSense June 2017

Path 2 :    QlikSense 3.0.0 -> QlikSense 3.2.4 -> QlikSense June 2017

Calling out the experts for their view : pwy‌ mto‌ korsikov‌ gwassenaar

Also, does the change to Shared Persistence model entails some action on our side or is it managed by QS internally?

Regards,

Kashif

[image242]

Hi Kashif,

I would actually recommend a combo of both paths (QlikSense 3.0.0 -> QlikSense 3.1.2 ->QlikSense 3.2.4 -> QlikSense June 2017). That worked well for us.

For Shared Persistence, you do need some initial setup:

• Create a shared folder (C:\QlikShare) and give your service account full red/write access)
• Then create 4 sub folders - Apps, ArchivedLogs, CustomData & StaticContent
• This link will show you what to copy into the folders: https://help.qlik.com/en-US/sense/June2017/Subsystems/PlanningQlikSenseDeployments/Content/Deploymen...

Reminder - Before you upgrade, back up everything including the repository, just in case you run into any issues.

Jason

[ansarikashif2017]

Thanks image242‌. Yes we have taken the backup of certificates, PostGreSQL DB and various folders.

[ansarikashif2017]

Hi image242‌,

An update. We tried the combo path. Everything went fine till 3.2.4 (synch persistence) but when we upgraded to June 2017 (shared persistence), the Hub and QMC never came backup. Though the installation showed successful completion without any errors.

Please refer to the details in the thread below :-

After upgrade to June 2017 QMC and Hub has stopped working