Sage 100

Threatlocker is a silent failure, if installed... disable it to narrow down the cause.

Standard doesn't have any processes on the server, unless you have 3rd party services (WSP, SF, CRM...).  If they have a different server, perhaps try copying the MAS90 folder elsewhere and see if it runs without the resets.

Obviously, check the server for any changes to the server at the same time the crashes started... like a Windows update, and roll them back.

@Kevin Moyes Thanks for your advice. I just checked the SAGE 100 Activity Log for the last 14 days and no errors at all except for a few entries regarding "Auto-Logoff - Forced close of task "XXX" on workstation: DESKTOP-XXXXXX". When they had to reboot the server. But certainly not 3 -5 occurrences each day.  

Threatlocker is a silent failure, if installed... disable it to narrow down the cause.

Standard doesn't have any processes on the server, unless you have 3rd party services (WSP, SF, CRM...).  If they have a different server, perhaps try copying the MAS90 folder elsewhere and see if it runs without the resets.

Obviously, check the server for any changes to the server at the same time the crashes started... like a Windows update, and roll them back.

@Kevin Moyes Thanks for your advice. I just checked the SAGE 100 Activity Log for the last 14 days and no errors at all except for a few entries regarding "Auto-Logoff - Forced close of task "XXX" on workstation: DESKTOP-XXXXXX". When they had to reboot the server. But certainly not 3 -5 occurrences each day.  

Threatlocker is a silent failure, if installed... disable it to narrow down the cause.

Standard doesn't have any processes on the server, unless you have 3rd party services (WSP, SF, CRM...).  If they have a different server, perhaps try copying the MAS90 folder elsewhere and see if it runs without the resets.

Obviously, check the server for any changes to the server at the same time the crashes started... like a Windows update, and roll them back.

I meant changes back "last week", when the crashes started overall... not something happening with each instance.  It could easily be something like a bad print driver, or conflicting DLL... but I'd expect something in the Event Viewer in those cases.

Failing hardware is always a possibility too...

@Kevin Moyes Thanks for your advice. I just checked the SAGE 100 Activity Log for the last 14 days and no errors at all except for a few entries regarding "Auto-Logoff - Forced close of task "XXX" on workstation: DESKTOP-XXXXXX". When they had to reboot the server. But certainly not 3 -5 occurrences each day.  

Threatlocker is a silent failure, if installed... disable it to narrow down the cause.

Standard doesn't have any processes on the server, unless you have 3rd party services (WSP, SF, CRM...).  If they have a different server, perhaps try copying the MAS90 folder elsewhere and see if it runs without the resets.

Obviously, check the server for any changes to the server at the same time the crashes started... like a Windows update, and roll them back.

@Kevin Moyes and @Wayne Schulz  The SAGE PEP option is not activated on this v2025 install and SAGE Update Advisor has been removed on this server. It's going to be hard to suggest to the internal IT guy that "Failing hardware is always a possibility too...". Thank you for your ideas.

I meant changes back "last week", when the crashes started overall... not something happening with each instance.  It could easily be something like a bad print driver, or conflicting DLL... but I'd expect something in the Event Viewer in those cases.

Failing hardware is always a possibility too...

@Kevin Moyes Thanks for your advice. I just checked the SAGE 100 Activity Log for the last 14 days and no errors at all except for a few entries regarding "Auto-Logoff - Forced close of task "XXX" on workstation: DESKTOP-XXXXXX". When they had to reboot the server. But certainly not 3 -5 occurrences each day.  

Threatlocker is a silent failure, if installed... disable it to narrow down the cause.

Standard doesn't have any processes on the server, unless you have 3rd party services (WSP, SF, CRM...).  If they have a different server, perhaps try copying the MAS90 folder elsewhere and see if it runs without the resets.

Obviously, check the server for any changes to the server at the same time the crashes started... like a Windows update, and roll them back.

Not a solution, but an observation.  I try to move STD users to ADV (one or two users excluded) whenever I do upgrades now.  No cost from Sage, reports can run faster (CSODBC), etc.

You mention Auto Logoff - Is that setting on for everyone?  Maybe turn that off.

@Kevin Moyes and @Wayne Schulz  The SAGE PEP option is not activated on this v2025 install and SAGE Update Advisor has been removed on this server. It's going to be hard to suggest to the internal IT guy that "Failing hardware is always a possibility too...". Thank you for your ideas.

I meant changes back "last week", when the crashes started overall... not something happening with each instance.  It could easily be something like a bad print driver, or conflicting DLL... but I'd expect something in the Event Viewer in those cases.

Failing hardware is always a possibility too...

@Kevin Moyes Thanks for your advice. I just checked the SAGE 100 Activity Log for the last 14 days and no errors at all except for a few entries regarding "Auto-Logoff - Forced close of task "XXX" on workstation: DESKTOP-XXXXXX". When they had to reboot the server. But certainly not 3 -5 occurrences each day.  

Threatlocker is a silent failure, if installed... disable it to narrow down the cause.

Standard doesn't have any processes on the server, unless you have 3rd party services (WSP, SF, CRM...).  If they have a different server, perhaps try copying the MAS90 folder elsewhere and see if it runs without the resets.

Obviously, check the server for any changes to the server at the same time the crashes started... like a Windows update, and roll them back.

@Jeff Schwenk Thanks for your input. I believe the "Auto Logoff" entries in the SAGE Activity Log is not coming from User Maintenance > Preferences screen. I don't believe that preference is set up for anyone. But from the Master Console "Shutdown All" option when the internal IT guy tries to shut down all SAGE users after the server crashes.  

Not a solution, but an observation.  I try to move STD users to ADV (one or two users excluded) whenever I do upgrades now.  No cost from Sage, reports can run faster (CSODBC), etc.

You mention Auto Logoff - Is that setting on for everyone?  Maybe turn that off.

@Kevin Moyes and @Wayne Schulz  The SAGE PEP option is not activated on this v2025 install and SAGE Update Advisor has been removed on this server. It's going to be hard to suggest to the internal IT guy that "Failing hardware is always a possibility too...". Thank you for your ideas.

I meant changes back "last week", when the crashes started overall... not something happening with each instance.  It could easily be something like a bad print driver, or conflicting DLL... but I'd expect something in the Event Viewer in those cases.

Failing hardware is always a possibility too...

@Kevin Moyes Thanks for your advice. I just checked the SAGE 100 Activity Log for the last 14 days and no errors at all except for a few entries regarding "Auto-Logoff - Forced close of task "XXX" on workstation: DESKTOP-XXXXXX". When they had to reboot the server. But certainly not 3 -5 occurrences each day.  

Threatlocker is a silent failure, if installed... disable it to narrow down the cause.

Standard doesn't have any processes on the server, unless you have 3rd party services (WSP, SF, CRM...).  If they have a different server, perhaps try copying the MAS90 folder elsewhere and see if it runs without the resets.

Obviously, check the server for any changes to the server at the same time the crashes started... like a Windows update, and roll them back.

Remember, the Sage server cannot be affected on Standard by client activity, other than file access over the network.  (In Standard the Sage server is just serving the files through the share, and does not run any Sage 100 program / services unless you have 3rd party services / scheduled tasks...).

If you don't see any pvxwin##.exe processes on the machine that is locking up, the root problem is not related to Sage 100 programs.

@Jeff Schwenk Thanks for your input. I believe the "Auto Logoff" entries in the SAGE Activity Log is not coming from User Maintenance > Preferences screen. I don't believe that preference is set up for anyone. But from the Master Console "Shutdown All" option when the internal IT guy tries to shut down all SAGE users after the server crashes.  

Not a solution, but an observation.  I try to move STD users to ADV (one or two users excluded) whenever I do upgrades now.  No cost from Sage, reports can run faster (CSODBC), etc.

You mention Auto Logoff - Is that setting on for everyone?  Maybe turn that off.

@Kevin Moyes and @Wayne Schulz  The SAGE PEP option is not activated on this v2025 install and SAGE Update Advisor has been removed on this server. It's going to be hard to suggest to the internal IT guy that "Failing hardware is always a possibility too...". Thank you for your ideas.

I meant changes back "last week", when the crashes started overall... not something happening with each instance.  It could easily be something like a bad print driver, or conflicting DLL... but I'd expect something in the Event Viewer in those cases.

Failing hardware is always a possibility too...

@Kevin Moyes Thanks for your advice. I just checked the SAGE 100 Activity Log for the last 14 days and no errors at all except for a few entries regarding "Auto-Logoff - Forced close of task "XXX" on workstation: DESKTOP-XXXXXX". When they had to reboot the server. But certainly not 3 -5 occurrences each day.  

Threatlocker is a silent failure, if installed... disable it to narrow down the cause.

Standard doesn't have any processes on the server, unless you have 3rd party services (WSP, SF, CRM...).  If they have a different server, perhaps try copying the MAS90 folder elsewhere and see if it runs without the resets.

Obviously, check the server for any changes to the server at the same time the crashes started... like a Windows update, and roll them back.

@Michael McDonald - Amy update?

Remember, the Sage server cannot be affected on Standard by client activity, other than file access over the network.  (In Standard the Sage server is just serving the files through the share, and does not run any Sage 100 program / services unless you have 3rd party services / scheduled tasks...).

If you don't see any pvxwin##.exe processes on the machine that is locking up, the root problem is not related to Sage 100 programs.

@Jeff Schwenk Thanks for your input. I believe the "Auto Logoff" entries in the SAGE Activity Log is not coming from User Maintenance > Preferences screen. I don't believe that preference is set up for anyone. But from the Master Console "Shutdown All" option when the internal IT guy tries to shut down all SAGE users after the server crashes.  

Not a solution, but an observation.  I try to move STD users to ADV (one or two users excluded) whenever I do upgrades now.  No cost from Sage, reports can run faster (CSODBC), etc.

You mention Auto Logoff - Is that setting on for everyone?  Maybe turn that off.

@Kevin Moyes and @Wayne Schulz  The SAGE PEP option is not activated on this v2025 install and SAGE Update Advisor has been removed on this server. It's going to be hard to suggest to the internal IT guy that "Failing hardware is always a possibility too...". Thank you for your ideas.

I meant changes back "last week", when the crashes started overall... not something happening with each instance.  It could easily be something like a bad print driver, or conflicting DLL... but I'd expect something in the Event Viewer in those cases.

Failing hardware is always a possibility too...

@Kevin Moyes Thanks for your advice. I just checked the SAGE 100 Activity Log for the last 14 days and no errors at all except for a few entries regarding "Auto-Logoff - Forced close of task "XXX" on workstation: DESKTOP-XXXXXX". When they had to reboot the server. But certainly not 3 -5 occurrences each day.  

Threatlocker is a silent failure, if installed... disable it to narrow down the cause.

Standard doesn't have any processes on the server, unless you have 3rd party services (WSP, SF, CRM...).  If they have a different server, perhaps try copying the MAS90 folder elsewhere and see if it runs without the resets.

Obviously, check the server for any changes to the server at the same time the crashes started... like a Windows update, and roll them back.

@Jeff Schwenk Thanks for asking. Yesterday, (Tuesday 12-9) morning I received a message "Thanks" from the internal It guy. I sent more of the above suggestions and asked if the SAGE server is performing double duty i.e. performing other tasks like Exchange e-mail or IIS server(s) per the SAGE Supported Matrix.

This morning, (Wednesday 12-10), I connected remotely and viewed the SAGE 100 System Activity Log. I did not see any Error Messages but did see where a "Forced Shutdown Close" was performed three times Monday afternoon and twice on Tuesday afternoon.  I will see if I can get the internal IT guy to give me a status update today. 

@Michael McDonald - Amy update?

Remember, the Sage server cannot be affected on Standard by client activity, other than file access over the network.  (In Standard the Sage server is just serving the files through the share, and does not run any Sage 100 program / services unless you have 3rd party services / scheduled tasks...).

If you don't see any pvxwin##.exe processes on the machine that is locking up, the root problem is not related to Sage 100 programs.

@Jeff Schwenk Thanks for your input. I believe the "Auto Logoff" entries in the SAGE Activity Log is not coming from User Maintenance > Preferences screen. I don't believe that preference is set up for anyone. But from the Master Console "Shutdown All" option when the internal IT guy tries to shut down all SAGE users after the server crashes.  

Not a solution, but an observation.  I try to move STD users to ADV (one or two users excluded) whenever I do upgrades now.  No cost from Sage, reports can run faster (CSODBC), etc.

You mention Auto Logoff - Is that setting on for everyone?  Maybe turn that off.

@Kevin Moyes and @Wayne Schulz  The SAGE PEP option is not activated on this v2025 install and SAGE Update Advisor has been removed on this server. It's going to be hard to suggest to the internal IT guy that "Failing hardware is always a possibility too...". Thank you for your ideas.

I meant changes back "last week", when the crashes started overall... not something happening with each instance.  It could easily be something like a bad print driver, or conflicting DLL... but I'd expect something in the Event Viewer in those cases.

Failing hardware is always a possibility too...

@Kevin Moyes Thanks for your advice. I just checked the SAGE 100 Activity Log for the last 14 days and no errors at all except for a few entries regarding "Auto-Logoff - Forced close of task "XXX" on workstation: DESKTOP-XXXXXX". When they had to reboot the server. But certainly not 3 -5 occurrences each day.  

Threatlocker is a silent failure, if installed... disable it to narrow down the cause.

Standard doesn't have any processes on the server, unless you have 3rd party services (WSP, SF, CRM...).  If they have a different server, perhaps try copying the MAS90 folder elsewhere and see if it runs without the resets.

Obviously, check the server for any changes to the server at the same time the crashes started... like a Windows update, and roll them back.

Just looked up the client's registered SAGE 100 STD User License count = 6. Could the server crash be caused by exceeding the user count and someone ignoring a SAGE 100 message like "xx user limit exceeded - no valid activation found" or "Connection rejected. User Limit Exceeded"? 

@Jeff Schwenk Thanks for asking. Yesterday, (Tuesday 12-9) morning I received a message "Thanks" from the internal It guy. I sent more of the above suggestions and asked if the SAGE server is performing double duty i.e. performing other tasks like Exchange e-mail or IIS server(s) per the SAGE Supported Matrix.

This morning, (Wednesday 12-10), I connected remotely and viewed the SAGE 100 System Activity Log. I did not see any Error Messages but did see where a "Forced Shutdown Close" was performed three times Monday afternoon and twice on Tuesday afternoon.  I will see if I can get the internal IT guy to give me a status update today. 

@Michael McDonald - Amy update?

Remember, the Sage server cannot be affected on Standard by client activity, other than file access over the network.  (In Standard the Sage server is just serving the files through the share, and does not run any Sage 100 program / services unless you have 3rd party services / scheduled tasks...).

If you don't see any pvxwin##.exe processes on the machine that is locking up, the root problem is not related to Sage 100 programs.

@Jeff Schwenk Thanks for your input. I believe the "Auto Logoff" entries in the SAGE Activity Log is not coming from User Maintenance > Preferences screen. I don't believe that preference is set up for anyone. But from the Master Console "Shutdown All" option when the internal IT guy tries to shut down all SAGE users after the server crashes.  

Not a solution, but an observation.  I try to move STD users to ADV (one or two users excluded) whenever I do upgrades now.  No cost from Sage, reports can run faster (CSODBC), etc.

You mention Auto Logoff - Is that setting on for everyone?  Maybe turn that off.

@Kevin Moyes and @Wayne Schulz  The SAGE PEP option is not activated on this v2025 install and SAGE Update Advisor has been removed on this server. It's going to be hard to suggest to the internal IT guy that "Failing hardware is always a possibility too...". Thank you for your ideas.

I meant changes back "last week", when the crashes started overall... not something happening with each instance.  It could easily be something like a bad print driver, or conflicting DLL... but I'd expect something in the Event Viewer in those cases.

Failing hardware is always a possibility too...

@Kevin Moyes Thanks for your advice. I just checked the SAGE 100 Activity Log for the last 14 days and no errors at all except for a few entries regarding "Auto-Logoff - Forced close of task "XXX" on workstation: DESKTOP-XXXXXX". When they had to reboot the server. But certainly not 3 -5 occurrences each day.  

Threatlocker is a silent failure, if installed... disable it to narrow down the cause.

Standard doesn't have any processes on the server, unless you have 3rd party services (WSP, SF, CRM...).  If they have a different server, perhaps try copying the MAS90 folder elsewhere and see if it runs without the resets.

Obviously, check the server for any changes to the server at the same time the crashes started... like a Windows update, and roll them back.