Posting Batches - Taking Forever

Good afternoon, our support staff is trying to close or "post" batches, however you phrase it, and are experiencing extreme delays. In most cases they are having to force quit and we are wondering if the batch is reflecting correctly throughout Sage. I wanted to know if this is a Sage issue and if anyone else is experiencing this, or do we have something going on internally.

Parents
  • 0

    What kind of batches, and at what stage of the process is being delayed?  At the "print" stage, terminating the process and restarting is fine.  At the "update" stage, terminating the process can cause data corruption.  If the issue is between the module update and the DTR, with Win 11 workstations, there is a known issue with that, being discussed in a different SC thread.

    SO invoices with credit cards being processed during the update, could be a problem communicating with the Paya / CC service.

    If on Premium and you have something like SQL mirroring set up (or SQL triggers), you're on your own. Disable those customizations and see if things improve.

    Also ensure you don't have anti-virus real-time scanning of the Sage 100 server folders (and / or scanning network files from workstations).  That can really cause delays and there is a Sage KB article on recommended exclusions.

    Updating really big batches can take hours.  We had one client system who had huge monthly invoicing batches that they had to leave running overnight.

Reply
  • 0

    What kind of batches, and at what stage of the process is being delayed?  At the "print" stage, terminating the process and restarting is fine.  At the "update" stage, terminating the process can cause data corruption.  If the issue is between the module update and the DTR, with Win 11 workstations, there is a known issue with that, being discussed in a different SC thread.

    SO invoices with credit cards being processed during the update, could be a problem communicating with the Paya / CC service.

    If on Premium and you have something like SQL mirroring set up (or SQL triggers), you're on your own. Disable those customizations and see if things improve.

    Also ensure you don't have anti-virus real-time scanning of the Sage 100 server folders (and / or scanning network files from workstations).  That can really cause delays and there is a Sage KB article on recommended exclusions.

    Updating really big batches can take hours.  We had one client system who had huge monthly invoicing batches that they had to leave running overnight.

Children