1 Reply Latest reply: Apr 16, 2013 7:21 AM by John Lifter RSS

    Running Expressor Dataflows from normal command prompt

      Hi there,


      I am able to run my expressor dataflow from the expressor command prompt using eTask. The tutorials on this (http://community.qlik.com/docs/DOC-3238 and http://community.qlik.com/docs/DOC-3239) have proven very useful for this.


      Now what I need is to run this from a normal command line (and ultimately from the QlikView EDX task as external program task). I have tried the following commands (start folder does not seem to matter): 

      • "C:\Program Files (x86)\expressor\expressor3\Studio\Expressor.Launcher.exe" set "etask -x MyProject -p MyFlow -V 0 -D "C:\Project\ETL\Metadata\MyProject.0\dpp\dpp_MyFlow"
      • "C:\Program Files (x86)\expressor\expressor3\Studio\Expressor.Launcher.exe" set "etask -x MyFlow...0...MyProject [-D "C::\Project\ETL\Metadata\MyProject.0\dpp\dpp_MyFlow"]

      When I do this, an expressor windows pops up stating "Expressor.Launcher has stopped working".

      Am I doing the right thing here? What could cause the crash (what more information migth you need?) How can you call an expressor dataflow based on a normal command prompt? Or even better, from an EDX task? (maybe we do not need to be able to do this from a normal command line at all?)


      Eventually We want to trigger expressor dataflows from an external server (webservice and all are set up, calling of tasks works for QV applications, I just need to create something equal for expressor)

      Kind regards,


        • Re: Running Expressor Dataflows from normal command prompt

          When you install Expressor it does not alter the environment, which means that the Expressor directories are not put onto the path.  Consequently, a regular command window does not have the information needed to run a dataflow.  The Expressor.Launcher.exe utility sets the environment.


          See the knowledge base article on running Expressor from Windows scheduler.  This discusses how to use Expressor.Launcher.exe to run a dataflow from another process.



          Alternatively, examine the path in an Expressor command window and note all the Expressor directories.  Then modify the path entry on your computer to include these directories.  Once you do this, there is no need to set the environment using Expressor.Launcher.exe.