To this day i still can't understand why Sage can't build an installer file to know where you installed your MAS90 on your server. Every time I install an update I have to browse out to where we have installed the application. Is there not a reason why they can't add a registry entry that tells each installer file this information. It would also be nice if Sage could build into their update files for EES customers, scripts to automatically stop and start the Integration service instead of prompting us to stop it manually.
by: Kevin T. | over a year ago | General Enhancements
Comments
Since there are often multiple MAS installs on servers the system will never be able to really know which one to install to.
Perhaps the system could use the opening dialogue box the install uses though and give the user a list of choices if multiple installs exist.
We just upgraded to Sage 100 Advanced and the update installers can't even stop/start the sage service with the install. You have to manually stop and start. I don't know of any other software that uses services, that can't perform this simple step during updating if required.