Sage 100

Is this 32-bit Sage 100 using Windows 11 workstations?

Try posting from the server directly, to eliminate potential network issues?

This is a good idea. I am concerned that because they say it's sporadic that this might be a tough suggestion.

Try posting from the server directly, to eliminate potential network issues?

This is a good idea. I am concerned that because they say it's sporadic that this might be a tough suggestion.

Try posting from the server directly, to eliminate potential network issues?

Also suggest they take a log of the times that interruptions happen.  If timings coincide with something like a backup, scheduled report, AV scan... that might give you a clue.

This is a good idea. I am concerned that because they say it's sporadic that this might be a tough suggestion.

Try posting from the server directly, to eliminate potential network issues?

What @Kevin Moyes said. I'll add this. In my experience, a big reason for these exact symptoms particularly with journals and registers, in older versions of Sage (haven't heard it reported so much in newer versions) was caused by DEP (Data Execution Prevention) settings of the Sage server and the RDS / Terminal Server too if present. Below is the Sage KB ID you can paste in to the search find the article which tells you or IT to either change the DEP level to "Turn on DEP for essential Windows programs and services only" OR add DEP exceptions for Sage EXEs. If the latter is required, I always add exceptions for pvxwin32.exe, pvxinw64.exe, and all variations of LaunchXX.exe. Once done, it absolutely requires a reboot of the server to take effect. 

I totally think it's worth a shot and Wayne you can just send the KB article to your customer's IT.

Solution ID: 223924250030732

Also suggest they take a log of the times that interruptions happen.  If timings coincide with something like a backup, scheduled report, AV scan... that might give you a clue.

This is a good idea. I am concerned that because they say it's sporadic that this might be a tough suggestion.

Try posting from the server directly, to eliminate potential network issues?

@Alnoor Cassim can you please tell me if the DEP suggestion applies if on Premium?  One of my clients has this problem and it is so frustrating and random and it doesn't happen with every user.  Also, they are on the 32-bit version.

What @Kevin Moyes said. I'll add this. In my experience, a big reason for these exact symptoms particularly with journals and registers, in older versions of Sage (haven't heard it reported so much in newer versions) was caused by DEP (Data Execution Prevention) settings of the Sage server and the RDS / Terminal Server too if present. Below is the Sage KB ID you can paste in to the search find the article which tells you or IT to either change the DEP level to "Turn on DEP for essential Windows programs and services only" OR add DEP exceptions for Sage EXEs. If the latter is required, I always add exceptions for pvxwin32.exe, pvxinw64.exe, and all variations of LaunchXX.exe. Once done, it absolutely requires a reboot of the server to take effect. 

I totally think it's worth a shot and Wayne you can just send the KB article to your customer's IT.

Solution ID: 223924250030732

Also suggest they take a log of the times that interruptions happen.  If timings coincide with something like a backup, scheduled report, AV scan... that might give you a clue.

This is a good idea. I am concerned that because they say it's sporadic that this might be a tough suggestion.

Try posting from the server directly, to eliminate potential network issues?

I don't think that this is the cause. I'm posting just in case someone runs across this thread and might have a similar issue.

A different customer just called complaining that they were not getting any prompt to update at the end of invoice printing. Turns out the issue was that the customer had checked off the "Keep Windows Open After" which has the result of NOT prompting you to print the register until/unless you click "Print Add'l Documents".

I don't think that this is the cause. I'm posting just in case someone runs across this thread and might have a similar issue.

A different customer just called complaining that they were not getting any prompt to update at the end of invoice printing. Turns out the issue was that the customer had checked off the "Keep Windows Open After" which has the result of NOT prompting you to print the register until/unless you click "Print Add'l Documents".

I don't think that this is the cause. I'm posting just in case someone runs across this thread and might have a similar issue.

A different customer just called complaining that they were not getting any prompt to update at the end of invoice printing. Turns out the issue was that the customer had checked off the "Keep Windows Open After" which has the result of NOT prompting you to print the register until/unless you click "Print Add'l Documents".

Latest update from this customer " haven't had any hang ups all day after disabling Symantec"

PS - with "weird" environmentally caused issues I find I have usually provided the solution to the customer or their IT department and they swipe it away as in "no it can't be that" or claim they tried the fix but frequently haven't.

Then it's not at all unusual for me to spend 15 days trying another dozen things only to go back to the first thing that was suggested and have that actually be the cause/fix.