How to Start Deferred Processing Automatically When Logging Into Admin Account

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 change this procedure based on your Windows OS and Elliott version accordingly.

Create Elliott Deferred Processing Icon (Shortcut) on Your Desktop
In this example, we log into the PSQL server as the Windows domain administrator.  On the desktop, we will create an Elliott Deferred Processing icon with the following properties:

For Run Local Option (Recommended)


For Run from Network Option


The above examples are for 8.5. For newer versions, like 8.6, replace 85 with 86.

The parameter /co:01 will bypass the company selection and launch Deferred Processing for company 01. Change this parameter according to your environment. 

For running in Local mode (preferred), it would be something like:
    Target: c:\users\administrator.NETCELLENT\appdata\local\netcellent\m\elliott7\bin85\el850dp.exe /co:01
    Start in: c:\users\ administrator.NETCELLENT\appdata\local\netcellent\m\elliott7\bin85
In this case, we assume you log in as "administrator" on the server. Notice the path is "administrator.NETCELLENT" because "administrator" is the local account profile path where "administrator.NETCELLENT" is for the domain account. You need to verify with your actual environment.

For running in Hybrid mode, it would be something like:
    Target: d:\netcellent\m\elliott7\bin85\el850dp.exe /co:01
    Start in: d:\netcellent\m\elliott7\bin85
Assuming the Elliott local folder is in d:\netcellent.

For running in Network mode, it would be something like:
    Target: m:\elliott7\bin85\el850dp.exe /co:01
    Start in: m:\elliott7\bin85

For 8.0-8.2, you can only run in Network mode.  The icon will be setup something like:
    Target: m:\elliott7\bin\el800dp.exe /co:01
    Start in: m:\elliott7\bin

Launch Deferred Processing in Ready Mode without Needing to Login 
There are still a few issues to resolve in order to launch Deferred Processing automatically.  First, you need to bypass the login screen.  Second, you need to start Deferred Processing in Ready mode.  To do so, start Elliott and click on the "Setup" icon in the top left corner of the Control Center screen.  Go to the "Print etc" tab.  In the Deferred Processing group area, do the following:
(1) Check the "Start in Ready Mode" checkbox
(2) Check the "Use Auto Login:" checkbox and fill in the Elliott user name and password.
See the sample screen below:

Save it and exit Elliott.

Now click on the Deferred Processing icon you created on the desktop and make sure that:
(1) You don't have to login.
(2) The Deferred Processing icon appears in the task tray.  The color should change from red to green.
If both are confirmed, then you are ready to proceed to the next step.

Copy and Paste Your Desktop Deferred Processing Icon to your Startup Folder
The program automatically creates a startup folder for Windows 2008 Server, which is typically:
    C:\Users\username\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
In our example we logged in as the Netcellent domain administrator, so the corresponding folder is
    C:\Users\administrator.NETCELLENT\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
Your startup folder would look like:

In this example, we start up Deferred Processing for both companies 01 and 03.

The final test is to log out of this PSQL server and log in again. Watch to see if Deferred Processing shows up in your task tray in green.  See the sample screen below:


You can mouse over the icon in the task tray and you will see a popup showing the company for the Deferred Processing task.  To manage Deferred Processing tasks, double right click on the icon and choose from the popup menu.

In order for Deferred Processing to continue to run, remain logged into the Windows server.  If you are logged into your server through Remote Desktop, simply click on the "x" in the Remote Desktop session to disconnect.

For the best performance, we suggest running Deferred Processing on your PSQL server directly to eliminate network traffic.


EMK



    • Related Articles

    • 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 ...

    • 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 ...

    • Error 114 with GUIUTL32.LBR\GUIUTIL.int in Deferred Processing

      Release Date: 04/09/2018 Q - We are receiving Error 114 in Defer Processing 2 - 3 times a week with the following messages: Executiion error : file 'GUIUTL32.LBR\GUIUTIL.int error code: 114, pc=EE, call=4, seg=4 (Signal 11) See sample screen below: ...

    • 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 ...

    • 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 ...