Sage 100

Interesting observation @Carmen Cruz - Thank you for sharing!!

Happy New Year!

If this is on a user station, not the cloud, if you install the correct drivers that go to the actual printer you're trying to install instead of letting Windows choose the driver for you It WILL work in 32 bit. I have already tested this number of times. It does not like the new driver that windows has come up with. Get the real drivers for your printers and install them correctly and the DTR will do its job. Why the DTR cares..... no idea

	Carmen Cruz Sage Consultant carmen.cruz@compudata.com 215-969-1000 Ext. 279 www.compudata.com Work Smarter... Together
CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106

Reference link with more:

https://communityhub.sage.com/us/sage100/f/unique-business-challenges/204944/windows-11-compatibility/512956

If you're using Adobe Acrobat, have you tried changing Adobe settings: deselecting 'Enable Protected Mode at Startup' and selecting 'Enable Enhanced Security' in Adobe's Security (Enhanced) preferences? Also, in General Settings turn off 'Show messages when I launch Adobe Acrobat'. 

If you're using Adobe Acrobat, have you tried changing Adobe settings: deselecting 'Enable Protected Mode at Startup' and selecting 'Enable Enhanced Security' in Adobe's Security (Enhanced) preferences? Also, in General Settings turn off 'Show messages when I launch Adobe Acrobat'. 

I am blown away, actually flabbergasted.  Are you telling me Sage couldn't figure out that solution this entire time this has been an issue?!  Unbelievable!  No, instead they ridiculously say we need to go with 64-bit. For this issue to have impacted SO MANY clients over a long period of time, Sage completely mishandled this. I'm now thinking this was an intentional ploy by Sage to try and get folks to 64-bit. BS!!

If you're using Adobe Acrobat, have you tried changing Adobe settings: deselecting 'Enable Protected Mode at Startup' and selecting 'Enable Enhanced Security' in Adobe's Security (Enhanced) preferences? Also, in General Settings turn off 'Show messages when I launch Adobe Acrobat'. 

@Carmen Cruz for the win! Again. 

I am blown away, actually flabbergasted.  Are you telling me Sage couldn't figure out that solution this entire time this has been an issue?!  Unbelievable!  No, instead they ridiculously say we need to go with 64-bit. For this issue to have impacted SO MANY clients over a long period of time, Sage completely mishandled this. I'm now thinking this was an intentional ploy by Sage to try and get folks to 64-bit. BS!!

If you're using Adobe Acrobat, have you tried changing Adobe settings: deselecting 'Enable Protected Mode at Startup' and selecting 'Enable Enhanced Security' in Adobe's Security (Enhanced) preferences? Also, in General Settings turn off 'Show messages when I launch Adobe Acrobat'. 

I am pretty sure installing the OEM driver did not work for my one client with this issue. I will reinstall the printers on her machine and report back.

@Carmen Cruz for the win! Again. 

I am blown away, actually flabbergasted.  Are you telling me Sage couldn't figure out that solution this entire time this has been an issue?!  Unbelievable!  No, instead they ridiculously say we need to go with 64-bit. For this issue to have impacted SO MANY clients over a long period of time, Sage completely mishandled this. I'm now thinking this was an intentional ploy by Sage to try and get folks to 64-bit. BS!!

If you're using Adobe Acrobat, have you tried changing Adobe settings: deselecting 'Enable Protected Mode at Startup' and selecting 'Enable Enhanced Security' in Adobe's Security (Enhanced) preferences? Also, in General Settings turn off 'Show messages when I launch Adobe Acrobat'. 

Cough (bs) Cough (bs).  Right on @Brett Zimmerman.  I share your thought.  I do believe they are using it as a reason to move everyone up to 64 bit.  What better way to force the issue and place the monkey on someone else's back?  But it is not surprising.  I am sure it is a standard ploy for any software publisher.  

I am pretty sure installing the OEM driver did not work for my one client with this issue. I will reinstall the printers on her machine and report back.

@Carmen Cruz for the win! Again. 

I am blown away, actually flabbergasted.  Are you telling me Sage couldn't figure out that solution this entire time this has been an issue?!  Unbelievable!  No, instead they ridiculously say we need to go with 64-bit. For this issue to have impacted SO MANY clients over a long period of time, Sage completely mishandled this. I'm now thinking this was an intentional ploy by Sage to try and get folks to 64-bit. BS!!

Hi Greg,

If installing default driver does not work what kind of printer is this that you are working on?  Is this change being done directly on a user's computer?  Let me know.  Talk to you soon. ;)

	Carmen Cruz Sage Consultant carmen.cruz@compudata.com 215-969-1000 Ext. 279 www.compudata.com Work Smarter... Together
CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106

Cough (bs) Cough (bs).  Right on @Brett Zimmerman.  I share your thought.  I do believe they are using it as a reason to move everyone up to 64 bit.  What better way to force the issue and place the monkey on someone else's back?  But it is not surprising.  I am sure it is a standard ploy for any software publisher.  

I am pretty sure installing the OEM driver did not work for my one client with this issue. I will reinstall the printers on her machine and report back.

@Carmen Cruz for the win! Again. 

I am blown away, actually flabbergasted.  Are you telling me Sage couldn't figure out that solution this entire time this has been an issue?!  Unbelievable!  No, instead they ridiculously say we need to go with 64-bit. For this issue to have impacted SO MANY clients over a long period of time, Sage completely mishandled this. I'm now thinking this was an intentional ploy by Sage to try and get folks to 64-bit. BS!!

If you're using Adobe Acrobat, have you tried changing Adobe settings: deselecting 'Enable Protected Mode at Startup' and selecting 'Enable Enhanced Security' in Adobe's Security (Enhanced) preferences? Also, in General Settings turn off 'Show messages when I launch Adobe Acrobat'. 

@Carmen Cruz, the printer driver changes are on a user workstation. It is using the manufacturer's driver. The location field is blank. It is a Brother HL-2550 connected via USB.

I should add this is the default printer, BUT, there are other printers on the system, but they are not used by Sage.

Hi Greg,

If installing default driver does not work what kind of printer is this that you are working on?  Is this change being done directly on a user's computer?  Let me know.  Talk to you soon. ;)

	Carmen Cruz Sage Consultant carmen.cruz@compudata.com 215-969-1000 Ext. 279 www.compudata.com Work Smarter... Together
CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106

Cough (bs) Cough (bs).  Right on @Brett Zimmerman.  I share your thought.  I do believe they are using it as a reason to move everyone up to 64 bit.  What better way to force the issue and place the monkey on someone else's back?  But it is not surprising.  I am sure it is a standard ploy for any software publisher.  

I am pretty sure installing the OEM driver did not work for my one client with this issue. I will reinstall the printers on her machine and report back.

@Carmen Cruz for the win! Again. 

I am blown away, actually flabbergasted.  Are you telling me Sage couldn't figure out that solution this entire time this has been an issue?!  Unbelievable!  No, instead they ridiculously say we need to go with 64-bit. For this issue to have impacted SO MANY clients over a long period of time, Sage completely mishandled this. I'm now thinking this was an intentional ploy by Sage to try and get folks to 64-bit. BS!!

@Carmen Cruz for the win! Again. 

I am blown away, actually flabbergasted.  Are you telling me Sage couldn't figure out that solution this entire time this has been an issue?!  Unbelievable!  No, instead they ridiculously say we need to go with 64-bit. For this issue to have impacted SO MANY clients over a long period of time, Sage completely mishandled this. I'm now thinking this was an intentional ploy by Sage to try and get folks to 64-bit. BS!!

Thank you everyone.  Yeah, when Sage said you had to go 64-bit I was like BS.  Let me find the real issue and I tested with many own Windows 11 until things started working.      

@Greg 

I just thought of something.  Look at the settings of the printer.  Make sure the location field is blank on tab one of settings.  If it has some kind of url data cut and paste that to the comments field instead.  It confuses Sage when it is in the location field on the first tab and gives the DTR the printing issue. 

Happy New Years

Kind Regards,

	Carmen Cruz Sage Consultant carmen.cruz@compudata.com 215-969-1000 Ext. 279 www.compudata.com Work Smarter... Together
CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106

@Carmen Cruz for the win! Again. 

I am blown away, actually flabbergasted.  Are you telling me Sage couldn't figure out that solution this entire time this has been an issue?!  Unbelievable!  No, instead they ridiculously say we need to go with 64-bit. For this issue to have impacted SO MANY clients over a long period of time, Sage completely mishandled this. I'm now thinking this was an intentional ploy by Sage to try and get folks to 64-bit. BS!!

If you're using Adobe Acrobat, have you tried changing Adobe settings: deselecting 'Enable Protected Mode at Startup' and selecting 'Enable Enhanced Security' in Adobe's Security (Enhanced) preferences? Also, in General Settings turn off 'Show messages when I launch Adobe Acrobat'. 

@Carmen Cruz I am seeing this user tomorrow and will get a report if the problem still exists and report back.

Thank you everyone.  Yeah, when Sage said you had to go 64-bit I was like BS.  Let me find the real issue and I tested with many own Windows 11 until things started working.      

@Greg 

I just thought of something.  Look at the settings of the printer.  Make sure the location field is blank on tab one of settings.  If it has some kind of url data cut and paste that to the comments field instead.  It confuses Sage when it is in the location field on the first tab and gives the DTR the printing issue. 

Happy New Years

Kind Regards,

	Carmen Cruz Sage Consultant carmen.cruz@compudata.com 215-969-1000 Ext. 279 www.compudata.com Work Smarter... Together
CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106

@Carmen Cruz for the win! Again. 

I am blown away, actually flabbergasted.  Are you telling me Sage couldn't figure out that solution this entire time this has been an issue?!  Unbelievable!  No, instead they ridiculously say we need to go with 64-bit. For this issue to have impacted SO MANY clients over a long period of time, Sage completely mishandled this. I'm now thinking this was an intentional ploy by Sage to try and get folks to 64-bit. BS!!

Sounds like a plan.  Cross my fingers for success. ��  Happy New Years!!!

	Carmen Cruz Sage Consultant carmen.cruz@compudata.com 215-969-1000 Ext. 279 www.compudata.com Work Smarter... Together
CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106

@Carmen Cruz I am seeing this user tomorrow and will get a report if the problem still exists and report back.

Thank you everyone.  Yeah, when Sage said you had to go 64-bit I was like BS.  Let me find the real issue and I tested with many own Windows 11 until things started working.      

@Greg 

I just thought of something.  Look at the settings of the printer.  Make sure the location field is blank on tab one of settings.  If it has some kind of url data cut and paste that to the comments field instead.  It confuses Sage when it is in the location field on the first tab and gives the DTR the printing issue. 

Happy New Years

Kind Regards,

	Carmen Cruz Sage Consultant carmen.cruz@compudata.com 215-969-1000 Ext. 279 www.compudata.com Work Smarter... Together
CompuData, Inc. • 325 Chestnut St, Ste 700 • Philadelphia • PA • 19106

@Carmen Cruz for the win! Again. 

I am blown away, actually flabbergasted.  Are you telling me Sage couldn't figure out that solution this entire time this has been an issue?!  Unbelievable!  No, instead they ridiculously say we need to go with 64-bit. For this issue to have impacted SO MANY clients over a long period of time, Sage completely mishandled this. I'm now thinking this was an intentional ploy by Sage to try and get folks to 64-bit. BS!!

If you're using Adobe Acrobat, have you tried changing Adobe settings: deselecting 'Enable Protected Mode at Startup' and selecting 'Enable Enhanced Security' in Adobe's Security (Enhanced) preferences? Also, in General Settings turn off 'Show messages when I launch Adobe Acrobat'. 

I just ran into this situation today with new Win 11 machines for a client. They had WIFI turned on but are not using WIFI to connect to anything.  Turned it off and the issue with the DTR hanging went away.  Tested by turning WIFI back on and tried updating again and the DTR hung.  It was definitely the WIFI setting.  May want to look at that.

I just noticed that someone in Sage Community ( formerly Sage City) posted the following update which they say involves a registry change that then resolved any conflict between 32-bit Sage 100 , Windows 100 and updating of DTR

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.  

@Wayne Schulz, I saw your post while onsite at a client's office that has this problem happening on both of their Sage computers and this did not work for them. 

I just noticed that someone in Sage Community ( formerly Sage City) posted the following update which they say involves a registry change that then resolved any conflict between 32-bit Sage 100 , Windows 100 and updating of DTR

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.  

I haven't been able to verify it. There seemed to be one or two additional people in Sage Community indicating that it worked for them. Perhaps there are other issues at hand and this one be a universal fix ?

@Wayne Schulz, I saw your post while onsite at a client's office that has this problem happening on both of their Sage computers and this did not work for them. 

I just noticed that someone in Sage Community ( formerly Sage City) posted the following update which they say involves a registry change that then resolved any conflict between 32-bit Sage 100 , Windows 100 and updating of DTR

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.  

Just tried the registry fix on my computer. 

Since the problem seems to be happening randomly, conclusions are pending.

I haven't been able to verify it. There seemed to be one or two additional people in Sage Community indicating that it worked for them. Perhaps there are other issues at hand and this one be a universal fix ?

@Wayne Schulz, I saw your post while onsite at a client's office that has this problem happening on both of their Sage computers and this did not work for them. 

I just noticed that someone in Sage Community ( formerly Sage City) posted the following update which they say involves a registry change that then resolved any conflict between 32-bit Sage 100 , Windows 100 and updating of DTR

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.  

Looks like registry patch did not work on my workstation.  I've got a hang this morning.

Maybe the registry patch needs to be at the server as well (Advanced)?

Just tried the registry fix on my computer. 

Since the problem seems to be happening randomly, conclusions are pending.

I haven't been able to verify it. There seemed to be one or two additional people in Sage Community indicating that it worked for them. Perhaps there are other issues at hand and this one be a universal fix ?

@Wayne Schulz, I saw your post while onsite at a client's office that has this problem happening on both of their Sage computers and this did not work for them. 

I just noticed that someone in Sage Community ( formerly Sage City) posted the following update which they say involves a registry change that then resolved any conflict between 32-bit Sage 100 , Windows 100 and updating of DTR

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.  

HI All,  So with this same client I have done the following:

• Set a default printer
• Made sure all printers had the "real" drivers installed
• Made sure all printers are valid
• The version of Acrobat they are running does not have the Security setting that has been mentioned as a possible fix.
• Did the registry update
• They are not on WiFi
• Note that the printer they are using is a Xerox & I have had bad experiences with them a number of times.

With all of this, they are still having the issue.   There is one accounting user that is the one getting the issue, there are two other users that very occasionally to DTR updates. They sometimes get the issue as well  but they generally just retry.   I suggested the scheduled update but they want to do it "on demand" (I have suggested an update every 15 minutes..)  

  What I am wondering in this is if there is a problem with the DTR report file.  Seems odd but this whole thing is odd.  Maybe rewriting the report from "scratch".??  I tend to think it is program related but with this still grasping at straws.  

Looks like registry patch did not work on my workstation.  I've got a hang this morning.

Maybe the registry patch needs to be at the server as well (Advanced)?

Just tried the registry fix on my computer. 

Since the problem seems to be happening randomly, conclusions are pending.

I haven't been able to verify it. There seemed to be one or two additional people in Sage Community indicating that it worked for them. Perhaps there are other issues at hand and this one be a universal fix ?

@Wayne Schulz, I saw your post while onsite at a client's office that has this problem happening on both of their Sage computers and this did not work for them. 

I just noticed that someone in Sage Community ( formerly Sage City) posted the following update which they say involves a registry change that then resolved any conflict between 32-bit Sage 100 , Windows 100 and updating of DTR

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.  

Did you see this post on Sage City today?

HI All,  So with this same client I have done the following:

• Set a default printer
• Made sure all printers had the "real" drivers installed
• Made sure all printers are valid
• The version of Acrobat they are running does not have the Security setting that has been mentioned as a possible fix.
• Did the registry update
• They are not on WiFi
• Note that the printer they are using is a Xerox & I have had bad experiences with them a number of times.

With all of this, they are still having the issue.   There is one accounting user that is the one getting the issue, there are two other users that very occasionally to DTR updates. They sometimes get the issue as well  but they generally just retry.   I suggested the scheduled update but they want to do it "on demand" (I have suggested an update every 15 minutes..)  

  What I am wondering in this is if there is a problem with the DTR report file.  Seems odd but this whole thing is odd.  Maybe rewriting the report from "scratch".??  I tend to think it is program related but with this still grasping at straws.  

Looks like registry patch did not work on my workstation.  I've got a hang this morning.

Maybe the registry patch needs to be at the server as well (Advanced)?

Just tried the registry fix on my computer. 

Since the problem seems to be happening randomly, conclusions are pending.

I haven't been able to verify it. There seemed to be one or two additional people in Sage Community indicating that it worked for them. Perhaps there are other issues at hand and this one be a universal fix ?

@Wayne Schulz, I saw your post while onsite at a client's office that has this problem happening on both of their Sage computers and this did not work for them. 

Did you see this post on Sage City today?

HI All,  So with this same client I have done the following:

• Set a default printer
• Made sure all printers had the "real" drivers installed
• Made sure all printers are valid
• The version of Acrobat they are running does not have the Security setting that has been mentioned as a possible fix.
• Did the registry update
• They are not on WiFi
• Note that the printer they are using is a Xerox & I have had bad experiences with them a number of times.

With all of this, they are still having the issue.   There is one accounting user that is the one getting the issue, there are two other users that very occasionally to DTR updates. They sometimes get the issue as well  but they generally just retry.   I suggested the scheduled update but they want to do it "on demand" (I have suggested an update every 15 minutes..)  

  What I am wondering in this is if there is a problem with the DTR report file.  Seems odd but this whole thing is odd.  Maybe rewriting the report from "scratch".??  I tend to think it is program related but with this still grasping at straws.  

Looks like registry patch did not work on my workstation.  I've got a hang this morning.

Maybe the registry patch needs to be at the server as well (Advanced)?

Just tried the registry fix on my computer. 

Since the problem seems to be happening randomly, conclusions are pending.

I haven't been able to verify it. There seemed to be one or two additional people in Sage Community indicating that it worked for them. Perhaps there are other issues at hand and this one be a universal fix ?

@Wayne Schulz, I saw your post while onsite at a client's office that has this problem happening on both of their Sage computers and this did not work for them. 

I just noticed that someone in Sage Community ( formerly Sage City) posted the following update which they say involves a registry change that then resolved any conflict between 32-bit Sage 100 , Windows 100 and updating of DTR

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.  

Announcement of sorts: At MOTM in the Top Support Issues sessions done primarily by @Beth Bowers and less so by me, I talked in my slides about all the known but not always successful workarounds for the Windows 11 DTR hanging issue. Also mentioned the same occurs after printing the P/R Data Entry Audit Report where it hangs on the chained report Employer Expense Summary. Also the problem occurs with Windows 10 in some cases too. In all cases, the underlying o/s issue revolves around the failure of the Windows WOW64 thunking mechanism for a 32-bit app (Sage) printing reports in a chain.

** John Nichols of Sage was in the audience and took an interest, especially when he heard how just everyone in the audience had clients / customers with the issue. I then spoke with him at length afterwards. The short of it is they are already in the process of trying to fix it in Sage by dropping all the object and printers connections after the journal/register prints before the DTR is chained into and then re-establishing those. He has also been paying close attention to the HKCU registry edit and other ideas discussed on that Sage City / Sage Community Hub post.

Once ready he will send the Sage fix to Beth and me for testing either later this week or next. At this point I don't know how it will play out but I will definitely keep everyone apprised here.

Did you see this post on Sage City today?

HI All,  So with this same client I have done the following:

• Set a default printer
• Made sure all printers had the "real" drivers installed
• Made sure all printers are valid
• The version of Acrobat they are running does not have the Security setting that has been mentioned as a possible fix.
• Did the registry update
• They are not on WiFi
• Note that the printer they are using is a Xerox & I have had bad experiences with them a number of times.

With all of this, they are still having the issue.   There is one accounting user that is the one getting the issue, there are two other users that very occasionally to DTR updates. They sometimes get the issue as well  but they generally just retry.   I suggested the scheduled update but they want to do it "on demand" (I have suggested an update every 15 minutes..)  

  What I am wondering in this is if there is a problem with the DTR report file.  Seems odd but this whole thing is odd.  Maybe rewriting the report from "scratch".??  I tend to think it is program related but with this still grasping at straws.  

Looks like registry patch did not work on my workstation.  I've got a hang this morning.

Maybe the registry patch needs to be at the server as well (Advanced)?

Just tried the registry fix on my computer. 

Since the problem seems to be happening randomly, conclusions are pending.

I haven't been able to verify it. There seemed to be one or two additional people in Sage Community indicating that it worked for them. Perhaps there are other issues at hand and this one be a universal fix ?

@Wayne Schulz, I saw your post while onsite at a client's office that has this problem happening on both of their Sage computers and this did not work for them. 

I just noticed that someone in Sage Community ( formerly Sage City) posted the following update which they say involves a registry change that then resolved any conflict between 32-bit Sage 100 , Windows 100 and updating of DTR

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.  

Announcement of sorts: At MOTM in the Top Support Issues sessions done primarily by @Beth Bowers and less so by me, I talked in my slides about all the known but not always successful workarounds for the Windows 11 DTR hanging issue. Also mentioned the same occurs after printing the P/R Data Entry Audit Report where it hangs on the chained report Employer Expense Summary. Also the problem occurs with Windows 10 in some cases too. In all cases, the underlying o/s issue revolves around the failure of the Windows WOW64 thunking mechanism for a 32-bit app (Sage) printing reports in a chain.

** John Nichols of Sage was in the audience and took an interest, especially when he heard how just everyone in the audience had clients / customers with the issue. I then spoke with him at length afterwards. The short of it is they are already in the process of trying to fix it in Sage by dropping all the object and printers connections after the journal/register prints before the DTR is chained into and then re-establishing those. He has also been paying close attention to the HKCU registry edit and other ideas discussed on that Sage City / Sage Community Hub post.

Once ready he will send the Sage fix to Beth and me for testing either later this week or next. At this point I don't know how it will play out but I will definitely keep everyone apprised here.

Did you see this post on Sage City today?

HI All,  So with this same client I have done the following:

• Set a default printer
• Made sure all printers had the "real" drivers installed
• Made sure all printers are valid
• The version of Acrobat they are running does not have the Security setting that has been mentioned as a possible fix.
• Did the registry update
• They are not on WiFi
• Note that the printer they are using is a Xerox & I have had bad experiences with them a number of times.

With all of this, they are still having the issue.   There is one accounting user that is the one getting the issue, there are two other users that very occasionally to DTR updates. They sometimes get the issue as well  but they generally just retry.   I suggested the scheduled update but they want to do it "on demand" (I have suggested an update every 15 minutes..)  

  What I am wondering in this is if there is a problem with the DTR report file.  Seems odd but this whole thing is odd.  Maybe rewriting the report from "scratch".??  I tend to think it is program related but with this still grasping at straws.  

Looks like registry patch did not work on my workstation.  I've got a hang this morning.

Maybe the registry patch needs to be at the server as well (Advanced)?

Just tried the registry fix on my computer. 

Since the problem seems to be happening randomly, conclusions are pending.

I haven't been able to verify it. There seemed to be one or two additional people in Sage Community indicating that it worked for them. Perhaps there are other issues at hand and this one be a universal fix ?

@Wayne Schulz, I saw your post while onsite at a client's office that has this problem happening on both of their Sage computers and this did not work for them. 

I just noticed that someone in Sage Community ( formerly Sage City) posted the following update which they say involves a registry change that then resolved any conflict between 32-bit Sage 100 , Windows 100 and updating of DTR

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.  

Thanks for the update @Alnoor Cassim

That was a great session & happy to hear he is looking into it further. I would agree on the chained report issue; PR is one of the first places we saw it with Windows11 as well. To add to the fun, one of our clients had it resolved until the workstation was rebooted. 

Announcement of sorts: At MOTM in the Top Support Issues sessions done primarily by @Beth Bowers and less so by me, I talked in my slides about all the known but not always successful workarounds for the Windows 11 DTR hanging issue. Also mentioned the same occurs after printing the P/R Data Entry Audit Report where it hangs on the chained report Employer Expense Summary. Also the problem occurs with Windows 10 in some cases too. In all cases, the underlying o/s issue revolves around the failure of the Windows WOW64 thunking mechanism for a 32-bit app (Sage) printing reports in a chain.

** John Nichols of Sage was in the audience and took an interest, especially when he heard how just everyone in the audience had clients / customers with the issue. I then spoke with him at length afterwards. The short of it is they are already in the process of trying to fix it in Sage by dropping all the object and printers connections after the journal/register prints before the DTR is chained into and then re-establishing those. He has also been paying close attention to the HKCU registry edit and other ideas discussed on that Sage City / Sage Community Hub post.

Once ready he will send the Sage fix to Beth and me for testing either later this week or next. At this point I don't know how it will play out but I will definitely keep everyone apprised here.

Did you see this post on Sage City today?

HI All,  So with this same client I have done the following:

• Set a default printer
• Made sure all printers had the "real" drivers installed
• Made sure all printers are valid
• The version of Acrobat they are running does not have the Security setting that has been mentioned as a possible fix.
• Did the registry update
• They are not on WiFi
• Note that the printer they are using is a Xerox & I have had bad experiences with them a number of times.

With all of this, they are still having the issue.   There is one accounting user that is the one getting the issue, there are two other users that very occasionally to DTR updates. They sometimes get the issue as well  but they generally just retry.   I suggested the scheduled update but they want to do it "on demand" (I have suggested an update every 15 minutes..)  

  What I am wondering in this is if there is a problem with the DTR report file.  Seems odd but this whole thing is odd.  Maybe rewriting the report from "scratch".??  I tend to think it is program related but with this still grasping at straws.  

Looks like registry patch did not work on my workstation.  I've got a hang this morning.

Maybe the registry patch needs to be at the server as well (Advanced)?

Just tried the registry fix on my computer. 

Since the problem seems to be happening randomly, conclusions are pending.

I haven't been able to verify it. There seemed to be one or two additional people in Sage Community indicating that it worked for them. Perhaps there are other issues at hand and this one be a universal fix ?

@Wayne Schulz, I saw your post while onsite at a client's office that has this problem happening on both of their Sage computers and this did not work for them. 

I just noticed that someone in Sage Community ( formerly Sage City) posted the following update which they say involves a registry change that then resolved any conflict between 32-bit Sage 100 , Windows 100 and updating of DTR

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.  

Announcement of sorts: At MOTM in the Top Support Issues sessions done primarily by @Beth Bowers and less so by me, I talked in my slides about all the known but not always successful workarounds for the Windows 11 DTR hanging issue. Also mentioned the same occurs after printing the P/R Data Entry Audit Report where it hangs on the chained report Employer Expense Summary. Also the problem occurs with Windows 10 in some cases too. In all cases, the underlying o/s issue revolves around the failure of the Windows WOW64 thunking mechanism for a 32-bit app (Sage) printing reports in a chain.

** John Nichols of Sage was in the audience and took an interest, especially when he heard how just everyone in the audience had clients / customers with the issue. I then spoke with him at length afterwards. The short of it is they are already in the process of trying to fix it in Sage by dropping all the object and printers connections after the journal/register prints before the DTR is chained into and then re-establishing those. He has also been paying close attention to the HKCU registry edit and other ideas discussed on that Sage City / Sage Community Hub post.

Once ready he will send the Sage fix to Beth and me for testing either later this week or next. At this point I don't know how it will play out but I will definitely keep everyone apprised here.

Did you see this post on Sage City today?

HI All,  So with this same client I have done the following:

• Set a default printer
• Made sure all printers had the "real" drivers installed
• Made sure all printers are valid
• The version of Acrobat they are running does not have the Security setting that has been mentioned as a possible fix.
• Did the registry update
• They are not on WiFi
• Note that the printer they are using is a Xerox & I have had bad experiences with them a number of times.

With all of this, they are still having the issue.   There is one accounting user that is the one getting the issue, there are two other users that very occasionally to DTR updates. They sometimes get the issue as well  but they generally just retry.   I suggested the scheduled update but they want to do it "on demand" (I have suggested an update every 15 minutes..)  

  What I am wondering in this is if there is a problem with the DTR report file.  Seems odd but this whole thing is odd.  Maybe rewriting the report from "scratch".??  I tend to think it is program related but with this still grasping at straws.  

Looks like registry patch did not work on my workstation.  I've got a hang this morning.

Maybe the registry patch needs to be at the server as well (Advanced)?

Just tried the registry fix on my computer. 

Since the problem seems to be happening randomly, conclusions are pending.

I haven't been able to verify it. There seemed to be one or two additional people in Sage Community indicating that it worked for them. Perhaps there are other issues at hand and this one be a universal fix ?

@Wayne Schulz, I saw your post while onsite at a client's office that has this problem happening on both of their Sage computers and this did not work for them. 

I just noticed that someone in Sage Community ( formerly Sage City) posted the following update which they say involves a registry change that then resolved any conflict between 32-bit Sage 100 , Windows 100 and updating of DTR

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.