Sage 100

Problems w installing a working v2018 Adv. with the the Domain Administrator highest possible rights. I have a brand new clean virtual server win server 2016 Standard, 64-bit. There is no anti-virus running, UAC is lowest setting and DEP (Data Execution & Prevention) is set to ""Turn on DEP for essential Windows programs and services only"". The base install is taking about an hour before SU (suspect Canadian Postal Codes is cause). Installed SU1 (customer has JobOps and SU1 is compatible SU). Workstation would not launch gave ""Sage 100 is not setup properly. Please run Workstation setup to configure this workstation"", then ""WindX Client Connection, The Server Has Disconnected"" The service is running fine, has a service account with domain admin rights setup on the log on tab (its not the issue). Removal and reinstall of workstation do not fix it. Ran in ""MAS90"" mode and launches but the Installed Applications Report can't even run, says ""The database login failed. Failed to open the connection. SY_InstalledModuleListing blah blah blah. Totally removed everything Sage & rebooted, downloaded fresh media, installed base 2018.0 again and SU1 tested MAS90 mode again under base no SU and w SU1 and still cant generate the Installed Applications Report, the installation seems bad. Does anyone know what the the problem is or how to get around it?

Have you tried with Local Admin? It's possible a GPO is allowing the service to run but failing to allow ODBC to load to the right folder. Experienced this just recently with a client. The work around was to add the domain user group to the local admin group on the server.

Ouch! bunch of questions - did you install the client on the server, and does it run from there ? in service mode and/or application mode and/or mas90 mode all on the server ? if issue is reporting only, have you tried enabling odbc within role maintenance in setup, then make sure the roles have everything checked ?

Beware. UAC works differently on Server 2016. It actually NEEDS to be on for some things to work.

Resolved - had to use a console session, no RDP.

Thanks for the follow up. As a rule of thumb, I always insist on a GTA console session as the administrator when doing the initial install. When IT pushes back, I say Shxx happens. Please humor me for the installation. Once this is past, I will finish via a RDP session. I will bookmark this thread and send to IT for my next install.