10 Replies Latest reply: May 22, 2012 12:56 PM by Karl Humma RSS

    Reload Engine:Failed to contact service

    Darwin Natividad

      I am trying to reload a supporting tasks (batch file).

       

      The error looks like this (Status.jpg)

      Status.JPG

       

      The tasks looks like this (Supporting tasks.jpg).

      Supporting tasks.JPG

       

      The batch file,that works when manually opened,has this code

      pushd "\\FILES-NA\QV_Production\QlikViewSource\DataSources\XMLFiles\Monitor"

      del "\\FILES-NA\QV_Production\QlikViewSource\DataSources\XMLFiles\Monitor\*.xml"

      exit

       

       

      Any ideas how to fix this one and make the batch file reload?

        • Reload Engine:Failed to contact service
          Karl Humma

          Do you have a publisher license key? You can not run supporting tasks without one, from the reference manual (p.39):

           

          7.8 Reload Engine

          In the absence of a Publisher license, the Reload Engine provides a subset of the Publisher distribution

          services. The Reload Engine only reloads user documents and the settings are defined directly in the user

          documents.

            • Re: Reload Engine:Failed to contact service
              Darwin Natividad

              Hi Karl,

               

              In fact, we do have publisher key.

               

              What we are trying to execute in the supporting task is a batch file to run a certain executable that would extract CAL allocation (not usage). Then it failed so the Reload engine shows that error.

                • Re: Reload Engine:Failed to contact service
                  Karl Humma

                  Great! In that case you should create this task under the qds@qvpubdca01 instead and it will run if the cmd line reference to "C:\LicenseAllocationTool\CalAllocation.bat" is actually on the machine where the qds is installed and the service account running the qds has access to the .bat file.  Also remove the cmd.exe /c you only need the "C:\LicenseAllocationTool\CalAllocation.bat" and it will run fine.

                   

                  /Karl

                   

                  P.S. That reload engine showing the red x is not a task error it is actually a "status" of the service itself error saying the service is disconnected it a bug, i've seen that before in version 10.  The reload engine should have gone away when you entered your publisher license key.  There is a bad reference in your qvpr which causes that reload engine reference to show up.

                    • Re: Reload Engine:Failed to contact service
                      Darwin Natividad

                      Hi Karl,

                       

                      That’s one thing. The task (that runs a bat file to open a certain executable) is failing.

                       

                      I have filed the concern to Qlikview Support and they mention something like this (which also fails. Need to try the executable)

                       

                       

                      Hello!

                       

                       

                       

                      There are sometimes problems running .bat or .vbs scripts directly from a supporting task as the supporting task will only run executable files and .bat and .vbs files do not always get picked up as executable.

                       

                       

                       

                      But it should be possible to run the bat script by adding a task that uses cscript (or wscript), like this:

                       

                       

                       

                      cscript "c:\LicenseAllocationTool\CalAllocationTool.bat"

                        • Re: Reload Engine:Failed to contact service
                          Karl Humma

                          Have you tried copying "c:\LicenseAllocationTool\CalAllocationTool.bat" to qds@qvpubdca01 >external programs and running from there? Bat files do work I have many of them on our internal deployment here at Qliktech.  They are sometimes tricky to setup but when you get it right they are very useful and helpful.  I usually place my .bat files on a shard drive since I have clustered qds servers run them. 

                           

                          /karl