Sage 100

Customer running Sage 2017 Premium - During the Daily Sales Journal update, receives error below.  Enter "bye" to exit, restart update and works fine.  


------------------------------
Robert Ruff
ServiceWorld Business Solutions
------------------------------

Thanks Raymond...checking on the backup timing now.

------------------------------
Robert Ruff
ServiceWorld Business Solutions
------------------------------

Original Message:
Sent: 09-23-2020 11:32
From: Raymond Westcott
Subject: Sage 2017 Premium Error 0 during Daily Sales Order Sales Jnl update

Could the update process be running into a backup? A SQL backup should not interfere with the update, but if you are backing up the MAS90 folder there could be some log files that are getting locked. Do they have any customizations that would write data to a location other than SQL tables during the invoice update process?

 

Raymond Westcott

Business Software Consultant

 

(818) 338.7200 Main

(818) 338.7227 Direct Line

(818) 338.7210 Support

 

 

ERP Software Specialists

IT Strategy, MSSP Services

 

 

We had a Premium customer who posted massive monthly batches (hours to print the journal, then 6+ hours to update, left running overnight), which sometimes were interrupted.  To decrease the number of variables involved they had someone log into the Sage server to start the updates and that proved more reliable.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Thanks Kevin - we are looking into this possibility.

------------------------------
Robert Ruff
ServiceWorld Business Solutions
------------------------------

Original Message:
Sent: 09-23-2020 11:51
From: Kevin Moyes
Subject: Sage 2017 Premium Error 0 during Daily Sales Order Sales Jnl update

We had a Premium customer who posted massive monthly batches (hours to print the journal, then 6+ hours to update, left running overnight), which sometimes were interrupted.  To decrease the number of variables involved they had someone log into the Sage server to start the updates and that proved more reliable.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

We have a few scripts running during this process and really need to know what file/table it's failing on.  I remember in legacy, we could use the Providex prompt and locate the exact record causing a process to fail.

------------------------------
Robert Ruff
ServiceWorld Business Solutions
------------------------------

No error and debug options?

------------------------------
Lee Graham
Friendly Systems, Inc.
------------------------------

Original Message:
Sent: 09-23-2020 15:30
From: Robert Ruff
Subject: Sage 2017 Premium Error 0 during Daily Sales Order Sales Jnl update

We have a few scripts running during this process and really need to know what file/table it's failing on.  I remember in legacy, we could use the Providex prompt and locate the exact record causing a process to fail.

------------------------------
Robert Ruff
ServiceWorld Business Solutions
------------------------------