We've been running Sage 100 Contractor for over 3 years. We have a simple environment with a single server running Windows Server 2008 R2 Standard x64. Since the server was installed, we have been running MS SQL Server for use with a different application and have had no issues. Now when attempting to upgrade Sage from 19.7 to latest 20.2, we get a error in the installer telling us we cannot install the database portion (SQL?) on our server, which is also the domain controller. Looking through the KB, Sage Support misleads the customer base by saying Microsoft "does not support" SQL on domain controller, when in fact Microsoft simply "recommends" that it be installed elsewhere. For customers like us, putting everything on the single stand-alone server is the appropriate method. Installing a 2nd server, whether virtual or not, or using a user's workstation to install SQL is not an ideal solution. This new "feature" in version 20.x is not justified when SQL Server can and does run fine on domain controller. Since we have been customers for over 3 years, it seems like a very poor design choice to just now incorporate this requirement for the SQL changes you are just now putting into the Sage 100 Contractor product

PLEASE REMOVE THIS ARTIFICIAL AND UNNECESSARY REQUIREMENT!!!!

Comments

  • We are a small company with the exact same issues. We only have one server that is the DC and are unable to install version 20 with SQL. The resources required on one of our local PCs would make the PC unusable. WE have it installed on the server for redundancy and backups. We don't have the resources to purchase a 2nd server just to run Master Builder.

    This is extremely inconvenient as this will stop us from being able to use the program once version 19 support expires next year.

    PLEASE RELEASE VERSION 20 ON THE EXISTING 19 PLATFORM.

  • Absolutely insane that we can't install Database Administrator on an Active Directory Controller. We are a small office with 8 workstations and a server that is more than able to handle SQL Server (which is already running fine on the server) and Active Directory. To require us to purchase a second server or use a workstation as the database server is just stupid. There should at least be an installation switch to bypass the check and let us proceed at our own risk.

  • SAGE SUPPORT - Please respond! We have the same problem here. SQL is supported and working on Windows Server, but your Version 20 will not install. We also don't want to purchase an additional/special server just to support your product. The original poster's entry has not been responded to.