We’re going to be migrating from Sage 100 2015 Standard to Sage 100 2017 Standard, but we’re having some trouble getting a brand new installation of Sage 100 working on a brand new installation of Windows Server 2016; the server and workstation both install successfully, but when we try to open the workstation we get the error message “Unable to create a Session object. The workstation may have been corrupted. Re-install Workstation Setup.” This happens if we install the workstation on a separate computer or on the server itself. We’ve actually tried it on two workstations, both with brand new installations of Windows 10, but we get this error message on all of them. This is without even migrating any data from our existing Sage 100 2015 server, so nothing from our old server should be causing this.
I’ve tried re-installing the workstation as well as just re-downloading and re-installing the whole thing on the server, from a Sage knowledge base article on this issue I’ve verified SYSTEM has Full Control in the security permissions for the share and Everyone has Full Control in the share permissions for the share, tried running “C:\Program Files (x86)\Common Files\Sage\Common Components\Regcom.bat” (it just gives me a list of things that it was unable to register), tried renaming the SY_Workstation.m4t file in the ..\MAS90\MAS_System folder, and tried installing workstation via the IP address instead of the hostname, and then based on a forum post I verified Shadow Copy was turned off and I disabled UAC, opportunistic locking, anti-virus (i.e. Windows Defender), Windows Firewall, and power saving features for the network cards, but none of this made any difference.
This is a clean installation of Sage 100 2017 on a new server (actually a Hyper-V VM with a checkpoint from before I installed Sage 100 so I can keep reverting back to a pre-install state to try new things). It’s strange because last week we were running Sage 100 2018 Standard just fine in this exact same configuration, before the CFO decided he wanted us to go to 2017 instead.
