9 Replies Latest reply: Nov 20, 2015 6:42 AM by Thomas Karner RSS

    Qlik Sense 2.0 App Migration Failed

    Mark Hohlov

      I'm trying to migrate my apps to Qlik Sense 2.0 Server. I go to the QMC and navigate to Apps menu item. Then I see the list of my apps with migration status "Migration Failed". When I try to migrate an app once again, I get the following UNABLE_TO_VERIFY_LEAF_SIGNATURE error in log file:

       

      Logger Severity           Date    MicroSeconds Message

      7ed21caa-d299-4d8d-b66c-b87b819103a4   INFO   2015-06-29T08:20:33.500Z    4265010216.309         Initial state set to 'Migration pending'

      7ed21caa-d299-4d8d-b66c-b87b819103a4   INFO   2015-06-29T08:20:33.500Z    4265013715.287            Transitioned state from 'Migration pending' to 'Migration in progress'

      7ed21caa-d299-4d8d-b66c-b87b819103a4   WARN 2015-06-29T08:20:33.656Z    4265165803.891         Migration failed: UNABLE_TO_VERIFY_LEAF_SIGNATURE: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE\n    at SecurePair.<anonymous> (tls.js:1380:32)\n    at SecurePair.emit (events.js:92:17)\n    at SecurePair.maybeInitFinished (tls.js:979:10)\n    at CleartextStream.read [as _read] (tls.js:471:13)\n    at CleartextStream.Readable.read (_stream_readable.js:340:10)\n    at EncryptedStream.write [as _write] (tls.js:368:25)\n    at doWrite (_stream_writable.js:225:10)\n    at writeOrBuffer (_stream_writable.js:215:5)\n    at EncryptedStream.Writable.write (_stream_writable.js:182:11)\n    at write (_stream_readable.js:601:24)\n    at flow (_stream_readable.js:610:7)\n    at Socket.pipeOnReadable (_stream_readable.js:642:5)\nFrom previous event:\n    at Function.Promise$Defer (C:\\Program Files\\Qlik\\Sense\\ServiceDispatcher\\Node\\migration-service\\src\\node_modules\\bluebird\\js\\main\\promise.js:267:13)\n    at new e (C:\\Program Files\\Qlik\\Sense\\ServiceDispatcher\\Node\\migration-service\\src\\migrate\\mocks\\deferred.js:1:127)\n    at Object.o.rpc (C:\\Program Files\\Qlik\\Sense\\ServiceDispatcher\\Node\\migration-service\\web\\assets\\core\\models\\rpc-session.js:1:2575)\n    at o.rpc (C:\\Program Files\\Qlik\\Sense\\ServiceDispatcher\\Node\\migration-service\\web\\assets\\core\\models\\engine.js:1:2297)\n    at o [as openDoc] (C:\\Program Files\\Qlik\\Sense\\ServiceDispatcher\\Node\\migration-service\\web\\assets\\core\\models\\engine.js:1:1452)\n    at Object._.openApp (C:\\Program Files\\Qlik\\Sense\\ServiceDispatcher\\Node\\migration-service\\web\\assets\\core\\models\\engine.js:1:2706)\n    at C:\\Program Files\\Qlik\\Sense\\ServiceDispatcher\\Node\\migration-service\\src\\migrate\\migrate.js:1:959\nFrom previous event:

      7ed21caa-d299-4d8d-b66c-b87b819103a4   INFO   2015-06-29T08:20:33.656Z    4265166266.659            Transitioned state from 'Migration in progress' to 'Migration failed'

      7ed21caa-d299-4d8d-b66c-b87b819103a4   INFO   2015-06-29T08:20:33.656Z    4265166419.193         Notifying callback URI

      7ed21caa-d299-4d8d-b66c-b87b819103a4   WARN 2015-06-29T08:20:33.671Z    4265181299.296         Failed to notify callback URI 'https://biserver.com:4242/qrs/app/7ed21caa-d299-4d8d-b66c-b87b819103a4/migrationcompleted': UNABLE_TO_VERIFY_LEAF_SIGNATURE

      7ed21caa-d299-4d8d-b66c-b87b819103a4   INFO   2015-06-29T08:20:33.671Z    4265181483.887         Log closed, migration completed

       

      The error appeared only after migrating Qlik Sense Server to version 2.0. Can you please help how to solve the following problem and migrate apps to 2.0?

        • Re: Qlik Sense 2.0 App Migration Failed
          Pascal Theurot

          +1

           

          Migration failed: UNABLE_TO_VERIFY_LEAF_SIGNATURE: Error: UNABLE_TO_VERIFY_LEAF_SIGNATURE\n    at SecurePair.<anonymous> (tls.js:1380:32)\n    at SecurePair.emit (events.js:92:17)\n    at SecurePair.maybeInitFinished (tls.js:979:10)\n    at CleartextStream.read [as _read] (tls.js:471:13)\n    at CleartextStream.Readable.read (_stream_readable.js:340:10)\n    at EncryptedStream.write [as _write] (tls.js:368:25)\n    at doWrite (_stream_writable.js:225:10)\n    at writeOrBuffer (_stream_writable.js:215:5)\n    at EncryptedStream.Writable.write (_stream_writable.js:182:11)\n    at write (_stream_readable.js:601:24)\n    at flow (_stream_readable.js:610:7)\n    at Socket.pipeOnReadable (_stream_readable.js:642:5)\nFrom previous event:\n    at Function.Promise$Defer (C:\\Program Files\\Qlik\\Sense\\ServiceDispatcher\\Node\\migration-service\\src\\node_modules\\bluebird\\js\\main\\promise.js:267:13)\n    at new e (C:\\Program Files\\Qlik\\Sense\\ServiceDispatcher\\Node\\migration-service\\src\\migrate\\mocks\\deferred.js:1:127)\n    at Object.o.rpc (C:\\Program Files\\Qlik\\Sense\\ServiceDispatcher\\Node\\migration-service\\web\\assets\\core\\models\\rpc-session.js:1:2575)\n    at o.rpc (C:\\Program Files\\Qlik\\Sense\\ServiceDispatcher\\Node\\migration-service\\web\\assets\\core\\models\\engine.js:1:2297)\n    at o [as openDoc] (C:\\Program Files\\Qlik\\Sense\\ServiceDispatcher\\Node\\migration-service\\web\\assets\\core\\models\\engine.js:1:1452)\n    at Object._.openApp (C:\\Program Files\\Qlik\\Sense\\ServiceDispatcher\\Node\\migration-service\\web\\assets\\core\\models\\engine.js:1:2706)\n    at C:\\Program Files\\Qlik\\Sense\\ServiceDispatcher\\Node\\migration-service\\src\\migrate\\migrate.js:1:959\nFrom previous event:

          • Re: Qlik Sense 2.0 App Migration Failed
            Hardik Patel

            I was facing the same issue. Tried to repair by using repair option by reinstalling the same and it resolved.

            • Re: Qlik Sense 2.0 App Migration Failed
              Levi Turner

              Another option:

               

              1. Stop Repository Service (this includes Proxy, Scheduler, Engine) and Service Dispatcher service

              2. Remove “C:\ProgramData\Qlik\Sense\Repository\Exported Certificates\.Local Certificates” folder

              3. Windows Start menu -> Run -> Write: mmc -> Press Ok

              4. File -> Add/Remove Snap-in

              5. Select Certificates -> Add 6. Select ”My User account” -> Finish

              7. Press OK to close the Add/Remove Snap-In window

              8. Expand the tree: Current User/Trusted Root Certification Authorities/Certificates

              9. Remove Certificate that contain following properties: Issued To:-CA Issued By: -CA Friendly Name: -CA (The Hostname value can be different depending on what you entered as hostname when you installed Qlik Sense)

              10. Start Repository, Proxy, Engine and Scheduler service

              11. Wait until you can see files created inside “C:\ProgramData\Qlik\Sense\Repository\Exported Certificates\.Local Certificates” folder

              12. Start Service Dispatcher service

              13. Open up QMC -> Apps

              14. Select one App and press the Migrate button (Note: You can multi-select and press Migrate. But do not migrate too many at once)

              15. When Migration is succeeded verify that it is visible in Hub and can be opened

                • Re: Qlik Sense 2.0 App Migration Failed
                  Steve Crosby

                  Thanks Levi

                  This worked for me, I tried the export option flagged as the correct answer, but I got failure messages when trying to export my apps from within the QMC.

                   

                  Cheers

                  Steve

                  • Re: Qlik Sense 2.0 App Migration Failed
                    Pascal Theurot

                    Thanks Levi

                    it worked too for me

                     

                    Pascal

                    • Re: Qlik Sense 2.0 App Migration Failed
                      Per Christian Nødtvedt

                      Thanks Levi,

                       

                      These steps also worked when I got the following log error:

                      6747264a-9bc2-4734-89a8-6bb72267e014WARN2015-09-21T07:57:05.671Z1893624545.482Migration failed: ECONNRESET: Error: socket hang up\n    at SecurePair.error (tls.js:1010:23)\n    at EncryptedStream.CryptoStream._done (tls.js:702:22)\n    at CleartextStream.read [as _read] (tls.js:498:24)\n    at CleartextStream.Readable.read (_stream_readable.js:340:10)\n    at EncryptedStream.onCryptoStreamFinish (tls.js:303:47)\n    at EncryptedStream.g (events.js:180:16)\n    at EncryptedStream.emit (events.js:117:20)\n    at finishMaybe (_stream_writable.js:359:12)\n    at endWritable (_stream_writable.js:366:3)\n    at EncryptedStream.Writable.end (_stream_writable.js:344:5)\nFrom previous event:\n    at Function.Promise$Defer (C:\\Program Files\\Qlik\\Sense\\ServiceDispatcher\\Node\\migration-service\\src\\node_modules\\bluebird\\js\\main\\promise.js:267:13)\n    at new e (C:\\Program Files\\Qlik\\Sense\\ServiceDispatcher\\Node\\migration-service\\src\\migrate\\mocks\\deferred.js:1:140)\n    at Object.o.rpc (C:\\Program Files\\Qlik\\Sense\\ServiceDispatcher\\Node\\migration-service\\web\\assets\\core\\models\\rpc-session.js:1:2575)\n    at o.rpc (C:\\Program Files\\Qlik\\Sense\\ServiceDispatcher\\Node\\migration-service\\web\\assets\\core\\models\\engine.js:1:2297)\n    at o [as openDoc] (C:\\Program Files\\Qlik\\Sense\\ServiceDispatcher\\Node\\migration-service\\web\\assets\\core\\models\\engine.js:1:1452)\n    at Object._.openApp (C:\\Program Files\\Qlik\\Sense\\ServiceDispatcher\\Node\\migration-service\\web\\assets\\core\\models\\engine.js:1:2706)\n    at C:\\Program Files\\Qlik\\Sense\\ServiceDispatcher\\Node\\migration-service\\src\\migrate\\migrate.js:1:972\nFrom previous event:\nFrom previous event:\n    at new Promise (C:\\Program Files\\Qlik\\Sense\\ServiceDispatcher\\Node\\migration-service\\src\\node_modules\\bluebird\\js\\main\\promise.js:84:37)

                       

                      Your step-by-step guide is very appreciated.

                       

                      Per Christian

                      • Re: Qlik Sense 2.0 App Migration Failed
                        Thomas Karner

                        In my case I renamed the Qlik Sense server and import of apps failed.

                        The above step-by-step instructions solved the problem also for me.

                        Thanks Levi!