Daily Transaction Register Hangs With Windows 11 Workstations

Sage City continues to take feedback from consultants who indicate:

Two clients with this issue - one on Sage 100 2021 and the other on Sage 100 2022. The symptom is that the progress bar keeps going during an update of the Daily Transaction Register.

Other comments:

We too are experiencing this on a Windows 11 machine, with Sage 2022, but it is in Purchase Order Receipt of Goods.

Replaced computers at 2022 client today. They got Windows 11 and are now having the issue. Didn't have it on their prior computers (win10) Opened up case with Sage.

Workaround: Go to the Daily Transaction Register on the main menu and run the process separately from there.

Read more on Sage City

How to exclude Sage 100 from anti-virus (antivirus) Real-time scans

Excluding your Sage 100 program from antivirus scanning can speed-up your system as well as reduce the possibility of errors from restricted access to key Sage 100 program or data files.

Sage periodically updates this list. For the latest instructions, please visit the Sage KB here.

These instructions are especially helpful during upgrades when you may be changing servers and therefore need to update your anti-virus exclusions to take the new server paths into consideration.

In your Antivirus product:

• Disable any aggressive or continuous (also known as on-access, constant, or real-time, or "network scanning") monitoring or scanning of Sage 100 (formerly Sage MAS 90 or 200) programs if they exist:

  • "..\MAS90\Home\Pvxwin32.exe"

  • "..\MAS90\Home\pvxiosvr.exe"

  • "..\MAS90\Launcher\Launch32.exe"

  • "..\MAS90\Launcher\Launcher.old.exe"

• Exclude the "..\MAS90" directory and sub-directories and contents on the server where Sage 100 is installed.

  
  

  • Note: Do the same for the workstations, if using Sage 100 Advanced or Premium editions (formerly Sage MAS 200 and Sage MAS 200 SQL editions) - default workstation install location is: C:\Sage\Sage 100 Workstation\.

  
  

• On Sage 100cloud workstations, including Standard, there are local folders created for Sage 100: exclude the Crystal Reports install (default: C:\Program Files (x86)\SAP BusinessObjects) and Common Components folder (Sage 100 2019 and earlier = C:\Program Files (x86)\Common Files\Sage. Sage 100 2020 & later = C:\ProgramData\Sage\Common Components).

  
  

• On Sage 100cloud workstations exclude the "Sage 100" folder under the Windows user's Documents folder.

  
  

• Exclude the following file extensions:

  • AUC, DCL, DD, DDE, DDF, EXP, LCK, LIB, KDF, M4D, M4L, M4P, M4T, M4X, PRM, PVC, PVX, RPT, SOA, XEQ

    
    

• Spa.NA.Com must be a trusted site

• Specifically for Sage Intellifgence running workstations, you may need to add .SDF file type and local folder to exclusions for workstation to avoid getting "Access to the path 'C:\Users\xxxx\AppData\Local\Alchemex (Pty) Ltd\TempFiles\alcworker_638112906898412190.sdf' is denied." when running Sage Intelligence on that workstation.

Via Sage KB

What Happens if You Change The Retained Earnings Number in General Ledger Setup?

File this under “you learn something new every day”

If you change the Retained Earnings Account within General Ledger, Sage 100 automatically moves all balances - EXCEPT any manual journal entries - to the new Retained Earnings Account.

More specifically as explained in Sage KB 33034 -

If you change the Retained Earnings Account in this field, the amount in the original Retained Earnings Account is moved to the updated Retained Earnings Account for each fiscal year. However, amounts posted by journal entry to a Retained Earnings Account are not moved to the updated account; the amounts remain in the Retained Earnings Account for which the journal entry was created.