Idea for Deferred Processing Automatic Start

Idea for Deferred Processing Automatic Start

Release Date: 03/08/2023
Version: 8.x & Up

Q - I noticed when the server is restarted, the Deferred Processing doesn't start. Therefore, if the server is restarted for any reason, including periodic Windows service pack updates, I have to login to the server, and manually restart the Deferred Processing.

Can I suggest an idea to add a time to start the Deferred Processing automatically? This is not 100% coverage, but if I know that the server is started every week at 10PM, I can schedule the start of the Deferred Processing accordingly. So on the Start in Ready mode, I would add a time.

A - This is an issue we are aware of. We currently don’t have good solution and no short-term fix either. Internally, we have discussed making Deferred Processing a service. However, that is a huge change. Especially since services do not have the ability to access mapped drives. To support running Elliott with services will require us to use a UNC path instead of a mapped drive. Therefore, it is unrealistic for us to make Deferred Processing a service at this time.

As for your idea about creating an auto start Deferred Processing, the issue still gets back to whether Elliott can run as a service or not.  If not, then someone must login as a user to host the Elliott session, which means it is not automated. If the Defer Processing is hosted on a client machine, then it seems that Deferred Processing needs the ability to reset the disconnected PSQL transaction engine session -- a capability that we don't have. Also, what if the client machine is rebooted (e.g., after a Windows services pack update)? So we still circle back to the same issue. The bottom line is if we want to solve this problem, then Deferred Processing needs to be a service. But for various reasons, that's not going to happen in the near future.


EMK

    • Related Articles

    • How to Start Deferred Processing Automatically When Logging Into Admin Account

      Release Date: 11/16/2018 Version: 8.0 & up To start Deferred Processing automatically when logging into an account, like Administrator, use the following procedure. This procedure was designed for Windows Server 2008 and Elliott 8.5. You may need to ...

    • Deferred Processing Icon Disappears from Task Tray and Multiple Deferred Sessions Are Running

      Release Date: 03/04/21 Modified Date: 02/08/24 Version: 7.5 & Up Q - Our Deferred Processing icon is disappearing from the task tray in the desktop bottom right corner. As a result, we thought Deferred Processing was not running and launched Deferred ...

    • Feature - Deferred Processing Multiple Times Per Day

      Release date: 03/31/2016 Some reports may need to be run multiple times each day. Prior to this release, a separate deferred process had to be created for each time during the day that the report needed to be run. This new feature allows for running ...

    • Deferred and PostOffice Processing in Elliott V8.6

      Version 8.6 Release Date: 4/28/23 Revised: 6/26/23 Overview Elliott V8.6 brings the following changes to Deferred Processing and PostOffice Processing: You no longer can specify Deferred Processing with any other output option. PDF PostOffice ...

    • Btrieve Error 80 In Deferred Processing

      Q - In Deferred Processing, we encounter the following error: Btrieve Error 080 on Order Header File This has been happening for the last 30 days off and on. What might cause this to happen? A - This is what Btrieve Error 80 means based on PSQL ...