Sage 100

@David Overholt this did happen to me last week at a client on v2023 Advanced.  I logged into the server with the same credentials used to Install Sage 100; and even before I had a chance to log into Sage 100, the server was rebooting.  30+ users were logged in at the time this happened.  Luckily it was not during any user "updates".  I thought it was a fluke.  I did see in the System Activity Log a "Sage Product Enhancement Program with a Force Close message.  We do not have PEP turned on for this client (for any client actually.)  I also see in Control Panel that the Sage Advisor Update was listed as "installed' on that date.  

I have not opened a case on this, but will.  This could create devastating problems if a client were updating a large batch and just logging into the server instituted that reboot.

------------------------------
Madeline Stefanou
RKL eSolutions, LLC
------------------------------

Now that I think about this, I did have an IT person contact me about two weeks ago wanting to have me stand by while they answered yes to a bunch of pop-ups that were on their server. They were all UAC-type prompts and when we cleared one of them (answered Yes), I thought it was odd because it did reboot the server. I could swear in the background I saw something about .net component or some type of Microsoft component was updating. This was while working directly on a Sage 100 2024 Advanced server doing nothing except answering yes to what appeared to be routine UAC prompts.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Connecticut
------------------------------

I had this happen one day last week.  Windows 2019 server.  Nothing in the Activity Log.  I believe I was the only one logged in, as no one reached out to me, and no one logged in within the 5-10 minutes I was on (thankfully).  No CC processing.  A GL/AR/AP 2-user system.  Sage Advisor uninstalled when I upgraded them a couple weeks ago to 2025.1.  No Windows updates that week.

------------------------------
Barbara Goldstein
Sr. Consultant
DSD Business Systems
------------------------------


Original Message:
Sent: 10-27-2025 12:39
From: Wayne Schulz
Subject: Sage 100 and server reboot

Now that I think about this, I did have an IT person contact me about two weeks ago wanting to have me stand by while they answered yes to a bunch of pop-ups that were on their server. They were all UAC-type prompts and when we cleared one of them (answered Yes), I thought it was odd because it did reboot the server. I could swear in the background I saw something about .net component or some type of Microsoft component was updating. This was while working directly on a Sage 100 2024 Advanced server doing nothing except answering yes to what appeared to be routine UAC prompts.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Connecticut

I know that 

@Madeline Stefanou said she was going to open a case with Sage. 

 I just got off the phone after opening a case with Sage support.

Sage's first answer was "Sage 100 is not able to reboot the server" I was talking to entry-level tech and she was messaging a higher-level tech. I told her to take down the exact message that IT found tied to the reboot. "The windows installer initiated a system restart to complete or continue the configuration of 'Sage Advisor Update'." 

She did that and sent it to the him/her, but after that, she told me that they were escalating it and someone would call me back.

I had this happen one day last week.  Windows 2019 server.  Nothing in the Activity Log.  I believe I was the only one logged in, as no one reached out to me, and no one logged in within the 5-10 minutes I was on (thankfully).  No CC processing.  A GL/AR/AP 2-user system.  Sage Advisor uninstalled when I upgraded them a couple weeks ago to 2025.1.  No Windows updates that week.

------------------------------
Barbara Goldstein
Sr. Consultant
DSD Business Systems


Original Message:
Sent: 10-27-2025 12:39
From: Wayne Schulz
Subject: Sage 100 and server reboot

Now that I think about this, I did have an IT person contact me about two weeks ago wanting to have me stand by while they answered yes to a bunch of pop-ups that were on their server. They were all UAC-type prompts and when we cleared one of them (answered Yes), I thought it was odd because it did reboot the server. I could swear in the background I saw something about .net component or some type of Microsoft component was updating. This was while working directly on a Sage 100 2024 Advanced server doing nothing except answering yes to what appeared to be routine UAC prompts.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Connecticut

Seems like it might be .NET-related, primarily because of the times the computer/server sometimes auto-reboots after Sage 100 prerequisites are installed, in particular .NET (although haven't really seen that happen in a while).  So maybe there was some sort of .NET update, and upon launching Sage 100 that triggered a similar thing?  

I know that 

@Madeline Stefanou said she was going to open a case with Sage. 

 I just got off the phone after opening a case with Sage support.

Sage's first answer was "Sage 100 is not able to reboot the server" I was talking to entry-level tech and she was messaging a higher-level tech. I told her to take down the exact message that IT found tied to the reboot. "The windows installer initiated a system restart to complete or continue the configuration of 'Sage Advisor Update'." 

She did that and sent it to the him/her, but after that, she told me that they were escalating it and someone would call me back.

I had this happen one day last week.  Windows 2019 server.  Nothing in the Activity Log.  I believe I was the only one logged in, as no one reached out to me, and no one logged in within the 5-10 minutes I was on (thankfully).  No CC processing.  A GL/AR/AP 2-user system.  Sage Advisor uninstalled when I upgraded them a couple weeks ago to 2025.1.  No Windows updates that week.

------------------------------
Barbara Goldstein
Sr. Consultant
DSD Business Systems


Original Message:
Sent: 10-27-2025 12:39
From: Wayne Schulz
Subject: Sage 100 and server reboot

Now that I think about this, I did have an IT person contact me about two weeks ago wanting to have me stand by while they answered yes to a bunch of pop-ups that were on their server. They were all UAC-type prompts and when we cleared one of them (answered Yes), I thought it was odd because it did reboot the server. I could swear in the background I saw something about .net component or some type of Microsoft component was updating. This was while working directly on a Sage 100 2024 Advanced server doing nothing except answering yes to what appeared to be routine UAC prompts.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Connecticut

If you open Sage Advisor Update on the server and click the History button is there recent history listed?

I checked and there is nothing showing in history since 2019 for this client. 

If you open Sage Advisor Update on the server and click the History button is there recent history listed?

Let me give an update to my client issue I saw on 10/20/25.  My Case (8010640294) was picked up by Nathan Shaw.  We spoke and he really felt it could have been anything, and did not believe it was Sage 100 that caused the reboot.  I mentioned that on 90Minds, it was not just my client experiencing this.  Today he reached out to request from me the Windows Event System Log.  He was able to segregate exactly what happened.  Earlier that morning, (a few hours before I logged in as the User that Installed Sage 100 on the Application Server); an event that triggered the reboot as soon as I logged in.  

He has passed this additional information on to his Development Team.  
  The process msiexec.exe has initiated the restart of computer XXXXX on behalf of user NT AUTHORITY\SYSTEM for the following reason:  No title for this reason could be found.
  Reason Code:  0x800300002
  Shutdown Type:  restart
  Comment:  The Windows Installer initiated a system restart to complete or continue the configuration of "Sage Advisor Update".  

Received closing notes from Nate in Support.  it was posted on Community Hub also.  

Hi Madeline,

The Global Development team responsible for the Sage Advisor Update application confirmed that a reboot may be triggered if Windows Installer detects that the SAU service or one of its associated files is still in use during the update process. In such cases, Windows Installer schedules a reboot to finalize the update. This behavior has been part of the default upgrade process in earlier versions as well.

Our Sage 100 DEV team recommends disabling the Sage Advisor Update Service and manually download updates from the Download Portal.

Please let us know if any of your other Sage customers encounter this issue.

Community Hub: Unexpected Reboot on Server