Can't Start a Job Message


This help topic covers the reason for the "blocking action" which stop certain jobs being performed and what you should do before blithely carrying on.

Why the message?
There are a number of jobs which once started must not be interrupted.  A power failure or "crashing" the system by using the Task Manager (Ctl+Alt+Del) can leave a job partially complete.  In multi-user installations some jobs must also be run only when all other users are logged out of the Aspect Property Manager so they can't change records your job is using.

To avoid interference when that type of job is started, a "Batch" record is written which stops other programs which may affect the job being started.  When the job is finished the record is removed and other users can perform the jobs which were blocked.  When the batch record is not removed all users will be blocked from performing any of the tasks which could have upset the job that wrote the record.  A warning message displays information about the job which was interrupted.

What jobs create a Batch record?
Some jobs write the record, finish the job completely, then remove the record.  Other jobs may have several steps and allow starting and stopping as reports are checked, amendments made, other records added or deleted.  In these latter cases the Batch record will be written and removed each time the program is exited.  The jobs which write and remove the Batch record are covered below as is the actions we think you should take when the blocking message is displayed.

What to do
Remember the most common causes of the Batch record not being deleted are:-
  • a user crashing out of one of the jobs identified below because "it is taking too long"
      4 You will get an idea of how long some jobs take but take care that there is not a message requiring attention hiding behind another program's active window.
  • the Aspect Property Manager being left open and the computer is turned off
  • a computer on a network running the Aspect Property Manager and blocking access to some function while the user has "gone to lunch"
  • a power failure or power spike

    Read the last section "When all else fails"

    Import Receipts
    This job may be started and exited several times by using the Close button.  Each start writes the Batch record and each Close deletes the record as does pressing Create Receipts.

  • Check the Bank menu > Cashbook last page(s) against the bank statement / transaction list to locate missing receipt records.
  • If all the bank records appear on the Cashbook remove the Batch record and continue as normal.
  • If only some of the bank records appear on the Cashbook the missing receipts need to be entered.  Do one of the following based on the work involved:-
    1.  Remove the Batch record.
    Enter the missing receipts manually

    2.  Import the batch again to the Matching step
    Unmatch the receipts already in the system
    Complete any matching required
    Press [Create Receipts] to create receipts for the remainder of the batch
      4 Note You now have two "Import Batch" lists both of which are wrong to some degree.  The first will indicate all the receipts were created.  The second will show those created on the second run and the unmatched first run receipts will be listed in the "Unmatched Transactions" section of the report.
    3.  Remove the Batch record
    Delete the receipts entered in each Tenants > Transactions grid and import the batch again.  The "Import Batch" report will have a new number and the old report can be discarded.

    Enter Bank Statement Details
    This job may be started and exited several times by using the Close button.  Each start writes the Batch Record and each Close deletes the record as does pressing Complete.

  • Go to Bank menu > Bank Statement Details report
  • Open the last (default) report
  • Scroll to the report summary found at the end of the report
  • Remove the Batch record.
  • If there is no "Out of balance ...." error message run the job again.
  • If there is an "Out of balance ...." error message the reconciliation will need to be done again.
      4 Take note of the Statement ID number on the last Bank menu > Bank Statement Details report
      4 Go to Bank menu > Cancel Bank Reconciliation
      4 Check the Statement ID number is the same and cancel it.
    Note  It may be necessary to repeat this step until the number noted above has been cancelled.
      4 Repeat the reconciliation process.

    Create Banking List
    The banking list does not create, edit or delete receipt records, it only "flags" those records as belonging to a particular group of receipts lodged as a single amount in one banking.
  • Remove the Batch record.
  • Reprint and check the last banking list
  • Correct any error which may require cancelling the Banking List depending upon where the system crashed or the Banking List process failed.

    Generate Payments
    This job writes the Batch record and deletes the record when either [Cancel] is pressed or [OK to Continue] is pressed and the task is finished.

    Running the Generate Payments program creates a payment which effectively "empties" each account of the amount to be paid.  If the system crashed you can safely run the Generate Payments again with the same criteria without fear of creating duplicate payments.
    However, if you do have this warning message you should:-
  • Print the Bank menu > Cashbook and check last payment transaction to see where the process failed.
  • Go to the transactions of the "owner" of the last payment listed to see that payment is correct.
  • Next check the transactions for the next landlord, supplier or tenant who should have been paid for a payment record.
  • If one is present and it was definitely not on the Cash Book report delete the transaction.  It may be necessary to use Admin menu > Utilities > Transaction Delete to do so.
  • Run the Generate Payments again with the same settings as before.
  • Answer "Yes" to the "There is an existing unconfirmed batch...."message.
  • Proceed as normal

    In the event you can not determine where the failure is return to the backup (which of course you did as suggested) taken prior to running Generate Payments and start again.

    Generate Standing Charges
    If this job is run multiple times it is has the potential to create multiple standing charge records in the landlords account.  Only the highlighted lines have records created.  

    Use the Standing Charges report to "spot check" the landlord transactions to locate the last landlord charged.
    Remove the Batch record..
    Re-run the Generate Standing Charges job with the lines of those already charged deselected.

    End of Period
    Apart from a power failure or computer malfunction this means you have either had two people trying to run the End of Period job in a multi-user environment or have tried to run the job twice in a single user environment and I'm not sure how you managed that!

    There is really only one option here which is to Restore the backup done before the End of period was started and run the job again.
    Having said that, if you did not take a backup before running End of Period try the following:-
    First, severely berate yourself for not doing a backup before running End of Period
    Then, do a backup
    Next, run Admin menu > Reverse End of Period
    Now, carefully check any reports printed prior to running End of Period produce the same results.
    Finally, do a backup and run End of Period.
    See the BackUp and Restore the Aspect Property Manager topic for more information.

    Reverse End of Period
    Well, if you manage this one you really are in the deep doo-doos.  The same comment applies here as for the End of Period section above.

    Again the best option is to return to the last good backup, which hopefully was run immediately prior to running End of Period as suggested.

    Create Archive
    Again, apart from a power failure or computer malfunction this means you have either had two people trying to run the Create Archive job in a multi-user environment or have tried to run the job twice in a single user environment.

    There is only one action to take which is to re-run the job.  

    Remove the Batch record.
    Run the Create Archive job again.
    You will receive a warning when an archive of the same name exists and you may choose to overwrite it.

    Removing the Batch record
    Go to Admin menu > Utilities > Close a Batch

    You will see a similar message to the blocking message that got you here.
    Only click [OK] after you have carried out the checking for your problem and possible recovery actions discussed above.

    When all else fails
    One of the effects of any system failure is there may be incomplete transactions written in the database.  This means that checking the last records written is important.  If you have any doubts consider restoring the database from the last backup and continue from that point.

    Before you restore the database >>> backup the current system, see BackUp and Restore the Aspect Property Manager and BackUp and Restore

    XXXX   User use of the delete tools,  previous period transactions, what other things ???