x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 5 replies
  • Subscribers 138 subscribers
  • Views 1922 views
  • Users 0 members are here
Browse Forums
Announcements
237
topics
29
replies
General Discussion
5k
topics
13k
replies
Sage Data & Analytics
56
topics
95
replies
Sage Enterprise Intelligence
210
topics
416
replies
Sage Intelligence Reporting
121
topics
322
replies
Max J

Recurring Task says Finished, but does not produce a result

Posted By

Hi all,

I am trying to create a Recurring Tasks that would print a Crystal Report to a networked printer.

Recurring Task runs at expected times and completes without error. I can verify that by looking at it in Usage -> Batch Server -> Query Management. Status column there says ‘Finished’.

However, the printer does not receive a print job and prints nothing.

 

I want to run the report programatically, so I’ve written this code:

$TEST_1

    #Variable for report parameters

    Local Char    TBPAR_BP(15)(1..50), TBVAL_BP(30)(1..50)

    #Run the report without the info message 'print executed'

    Call ETAT("Z4GL","TESTMJ","",0,"",TBPAR_BP,TBVAL_BP) From AIMP3

 

When I run the script in Script Editor, the printer prints the report successfully.

 

Crystal Report for the sake of this task is elementary: just one text field, and no parameters.

Here is how I set up a task:

 

So the problem is not with a script, a report, or a printer, or a task per se, because taken separately they all work .

I suspect that something prevents task of reaching the printer, but not sure where to look.  

Ideas appreciated.

Thanks

  • 0

    Not sure if this helps, but I had this same problem after I replaced my SQL server. It was the ODBC connection on the X3 application server still pointing to the old server. I needed to edit the ADX_X3V6 DSN but in the 32-bit version of the ODBC administrator, not the 64-bit.

    However, after a reboot of the server it would revert back.  Support helped me fix that with the following:

    Determined when the Print service was restarted, it re-writes the ODBC

    settings on the print server ( registry under HKLM\Software\W

    ow6432Node\ODBC\ODBC.INI\ADX_X3V6  )

     

    Found this is coming from the file:  adxeditionserversolutions.xml

     

    Location:  C:\SAGE\SAFEX3\EDTV2\EDT211\srvedit\Config

    We updated the file to include the new server name.

     

    Restarted the print server.

    It's keeping the correct setting now.

  • 0

    Hello, 


    What version and patch is this on? 

    Regards,

  • 0 in reply to Esfahani

    Hello, 

    it's version 7.1 patch 6. 

  • 0 in reply to AGrover

    Thank you for sharing the info on ODBC connection glitch. We are going to replace SQL Server soon, and your info may help us save some grey hair.

  • 0

    Hi,

    Sorry for the delayed response. It works now but not without peculiarities.

    Here is what happened (I am attaching a screenshot of Recurring Task):

    As soon as server time crossed Start Time [00:01] in Time Range block, the printer started printing the report as I expected it to!

     

    Frequency field was initially set to 20 minutes – and the printer printed every 20 minutes.

    Then I decided to change Frequency from 20 to 720 minutes. I made a change and saved the Recurring Task. However, printer continued to print every 20 minutes.

    That is, until server time crossed Start Time [00:01] again. After that the printer prints only every 720 minutes.

     

    It seems that the Recurring Task is able to actually print when server time crosses Start Time.

    Change in Task’s frequency is also picked up when server time crosses Start Time.

    I did not test specifically for that, trying different Start Times, but this what it does.

    Am I missing something in my setup of a Recurring Task?

    Thanks

*Community Hub is the new name for Sage City