+ Reply to Thread
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 14

Thread: Job Not Printing

  1. #1
    Join Date
    Jul 2016
    Posts
    10

    Default Job Not Printing

    Hi,

    Using the node-js-samples and running 'node app' with the following: -

    loginSample,
    printJobSample,
    logoutSample,

    The script executes but job not sumbitted to CWS. The jobId is the ID column in CWS, for example 8605BAAE.579071C6.70553

    Running the script returns the following: -

    C:\Program Files\nodejs\src>node app

    Login
    {"authenticated":true,"fiery":true}

    Print a job


    Logout
    {"authenticated":false}


    In addition is it possible to submit the job based on Job Title?
    Thanks for any feedback.

  2. #2
    Yusuke_K is offline Senior Fiery Forum Contributor Yusuke_K is on a distinguished path
    Join Date
    Jul 2009
    Posts
    51

    Default

    Hi there

    Not sure which part is not working. I assume you are just trying to print a job in a held queue you see from CWS.

    If so you need to specify your job ID at line 26 in the app.js.

    var jobId = 'the_job_id';

    Enter the exact job ID you'd like to print.

    Thanks,
    Yusuke

  3. #3
    Join Date
    Jul 2016
    Posts
    10

    Default

    Thanks for the reply,

    Yes the job ID is in the jobId variable: -

    var jobId = '8605BAAE.579071C6.70553';

    the jobs is in the hold queue as per the attachment, it has already been printed.

    Appreciate your help,
    Kevin
    Attached Images  

  4. #4
    Yusuke_K is offline Senior Fiery Forum Contributor Yusuke_K is on a distinguished path
    Join Date
    Jul 2009
    Posts
    51

    Default

    Hi,

    I'm not sure what is going on.
    Did you manually print the job from CWS first? or you executed the script and it's printed?
    Please clarify what you did.

    I don't see any issue on our end. If the call is delivered, then you should see at CWS that the job gets processed and printed.

    Thanks,

  5. #5
    Join Date
    Jul 2016
    Posts
    10

    Default

    Hi,

    The job was previously printed via a hotfolder and is now sitting in the held queue. I'm trying to submit it again asa test using the API so I'm expecting it to process it and print again.

    I've enclosed the app code minus the api key, logon details etc.

    It looks like its running the 3 functions, loginSample, printJobSample and logoutSample from the output.

    Thanks.
    Attached Files

  6. #6
    Yusuke_K is offline Senior Fiery Forum Contributor Yusuke_K is on a distinguished path
    Join Date
    Jul 2009
    Posts
    51

    Default

    Hi there,

    I don't see any issue with your code. I just tried with our Fiery (except changing the job ID and Fiery IP address and etc.) and it works fine.

    I thought it's just a wrong job ID but it seems fine looking at your screenshot.

    You should get response like below if you successfully print it.

    ----

    Login
    {"authenticated":true,"accessrights":"true"}

    Printing job 00000000.578E060C.1977
    {"id":"00000000.578E060C.1977","method":true}

    Logout
    {"authenticated":false}
    ----


    Have you tried any other jobs in your held queue?

    By the way, printJobSample function only initiate the action (print) for the existing jobs in your Fiery. So you are technically not submitting the job. Submitting job part is postJobContentSample in this sample file.

    Thanks,
    Yusuke

  7. #7
    Join Date
    Jul 2016
    Posts
    10

    Default

    Hi and thanks again for your reply.

    Ive tried several job ID's all of which are in the held queue and the same result, no message returned in the printJobSample function.

    I've rebooted the server just in case but still the same.

    Thanks, yes understand the difference between postJobContentSample and printJobSample.

    I've tried some of the other functions as well but nothing so perhaps not a code problem but a system problem, is it to do with https as per the attachment or should it still run even if https isnt installed?

    Thanks again.
    Attached Images  

  8. #8
    Yusuke_K is offline Senior Fiery Forum Contributor Yusuke_K is on a distinguished path
    Join Date
    Jul 2009
    Posts
    51

    Default

    Hi there,

    Please let me investigate a little bit. Sorry about the hassle. I can see from your initial post that you have been able to successfully login and logout so I'm not sure.

    Thanks!
    Yusuke

  9. #9
    Yusuke_K is offline Senior Fiery Forum Contributor Yusuke_K is on a distinguished path
    Join Date
    Jul 2009
    Posts
    51

    Default

    Hi there,

    Three things we'd like to ask. We'd like to narrow down the issue.


    1. Please enable getSingleJobSample part to see if the job query comes back ok.
    2. Please check the res objet and tell us what it returns.
    3. If you are not using admin or operator username, make sure the username you are using in the code has print access.

    Thank you!
    Yusuke

  10. #10
    Join Date
    Jul 2016
    Posts
    10

    Default

    Hi, thanks again.

    Here is the output for the getSingleJobSample: -

    Login
    {"authenticated":true,"fiery":true}

    Get single job


    Logout
    {"authenticated":false}

    I tried changing the user and got this returned so I think the userame and password are OK? : -

    Login
    {"authenticated":false,"errors":"bad user name or password","fiery":true}

    Printing job 8605BAAE.57907D57.70677


    Logout
    {"authenticated":false}

    Thanks,

+ Reply to Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts