Hitachi Vantara Pentaho Community Forums
Results 1 to 6 of 6

Thread: Starting kitchen with at, no repository found

  1. #1

    Default Starting kitchen with at, no repository found

    Hi all,
    i created a job within a repository (MySQL).
    I created a cmd file to start the job with kitchen:

    VIS.cmd:
    c:\pdi\data-integration\kitchen.bat /rep:01 /user:admin /pass:admin /job:"VIS V1" /leveletailed >> /PDI/LOG/VIS_V1.log

    When i start it from the windows-explorer or a cmd window, everything works fine.

    Then I added it to the Windows-Scheduler (AT) (at 12:00 vis.cmd)

    Then the vis.cmd starts, but the repositories.xml seems not to be found.

    INFO 28-07 16:51:01,015 - Using "C:\Windows\TEMP\vfs_cache" as temporary files store.
    INFO 28-07 16:51:01,408 - Kitchen - Kitchen
    INFO 28-07 16:51:01,410 - Kitchen - Kitchen
    INFO 28-07 16:51:01,410 - Kitchen - Kitchen
    ERROR: No repository provided, can't load job.
    ERROR: Kitchen can't continue because the job couldn't be loaded.

    Do I have to add some environment variables?

  2. #2
    Join Date
    Jun 2009
    Posts
    13

    Default

    I had the same problem, the ">>" reference to a log file appeared to be the issue for the Scheduled Task.

    I just removed the log file and allow the logging to happen on the screen, I am logging my Job and Transformation results to the database anyway...sorry, not really a solution, but a workaround that got me what I needed.

  3. #3

    Default

    I still have the same problem...

  4. #4
    Join Date
    Jun 2009
    Posts
    13

    Default

    Here is how mine is setup:

    FullLoadPrimary.bat:
    Code:
    Kitchen.bat /rep:"Repository Name" /job:"Job Name" /dir:"/Directory Path" /user:"admin" /pass:"password" /level:Detailed
    Then, I have a Windows Scheduled Task set up to run that .bat file, and I have the Start In: field pointed to my C:\pentaho\data-integration directory (or wherever the Kitchen.bat file exists)

    When I had the ">> logfilename.log" at the end of the code in the .bat file, it would bomb out with a similar error to yours, but once I took that off the end, it runs like a champ.

  5. #5
    Join Date
    Jul 2010
    Posts
    1

    Default

    We are having the exact same problem Lenzen.
    Removing the log file did not solve it.

    Have you had any other luck?

  6. #6
    Join Date
    Apr 2008
    Posts
    4,696

    Default

    What happens when you run VIS.cmd from c:\ ?

    I'm betting that you will get errors...

    I usually start my bat files with:
    set KETTLE_HOME=<<MY_KETTLE_DIR>>
    cd -d %KETTLE_HOME%
    <everything else>
    **THIS IS A SIGNATURE - IT GETS POSTED ON (ALMOST) EVERY POST**
    I'm no expert.
    Take my comments at your own risk.

    PDI user since PDI 3.1
    PDI on Windows 7 & Linux

    Please keep in mind (and this may not apply to this thread):
    No forum member is going to do your work for you. We will help you sort out how to do a specific part of the work, as best we can, in the timelines that our work will allow us.
    Signature Updated: 2014-06-30

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2019 Hitachi Vantara Corporation. All Rights Reserved.