Daily Transaction Register hangs on "Processing Daily Transaction Register"

Cause

via  us-kb.sage.com/.../viewsolution.jsp

Thank you so much

Hi Karen Russell , if this suggested answer helped, please mark it as verified  (by clicking the "Verify Answer" button next to Reply, on the response) for the benefit of others in this forum . Thank you!

Is this only happening with the Daily Transaction Register?  or other registers also.

Is there any update on this? 

Does changing 32 bit to 64 bit work?  Do you need to upgrade to 2023?  

Thanks for any update,

Chris

Yes changing to 64 bit worked.  

Unfortunately, the issue may occur in Sage 100 2023 also.  (It happens in a variety of Sage 100 versions)

It is related to Windows version 22H2 and has been reported in both Windows 11 22H2 and Windows 10 22H2 from what I understand.

The current workaround is to run the 32_64_bit_switch_utility.exe from the Sage 100 installer used to install Sage 100 (it is in installation files) to convert from 32-bit Sage 100 to 64-bit Sage 100.  

Otherwise, it would be possible to kill the stuck DTR or other register and then re-launch that Register from the Sage 100 menu directly - the issue is with one Register process calling the next Register process automatically.

I talked with my reseller, Keith Fitzgerald at Back Bay Accounting Software Consultants, and he advised not switching to 64 bit as he has seen troubles with that.  We have some add-ons like IIG, GetX, and WebSite Pipeline. 

Instead, he showed me how to configure Windows 11 workstations so they work with 32 bit Sage.  My new Windows 11 workstation did all my sales updates last night just like my Windows 10 workstations have been doing.  I have to test with other updates today still, but I am pretty excited. 

Thank you,

Chris

Can you share what he had you change to help those that can't switch to 64 bit?

reg add "HKCU\Software\Microsoft\Print\UnifiedPrintDialog" /v "PreferLegacyPrintDialog" /d 1 /t REG_DWORD /f

I ran this for each user on the windows 11 computer.   I ran it last night for my admin account and all worked.  Today, I tried doing sales update with my regular user account without running this, and it hung during the update.  I ran this to add the registry entry and then retried and the sales update went right through.  This command was run in a CMD window as administrator at the C:\ prompt.  

Chris