Sage 100

Installed 2015 PU3 Advanced on new 2012 server. I am not able to get client to launch on the server itself, haven't yet ran wksetup on workstations. Getting Windx Client Connection: Server has disconnected error. I tried all the resolutions (changed port, checked permissions, ran wksetup with IP vs server name, turned off PEP. I am able to access Sage in MAS90 mode. App was set up as service, so stopped it and tried as application. This gave me a different error about CmdAsUser.exe (attached) and then I get a different Windx Client error (attached) referencing OSMSG. I just realized the operating system is 2012 R2 DataCenter. Can this OS be causing my problems?

Did you check windows Firewall settings and add an exception to allow on that port?

If David's suggestion doesn't work, try changing the workstation properties to run Sage 100 in one of the compatibility modes.

I did check the firewall and added both an inbound and outbound rule. I'll try the compatibility mode. Thanks

Try turning off the firewall altogether for testing, but in addition to the inbound and outbound port rule, I usually add the MAS90\Home\pvxwin32.exe and MAS90\Launcher\Launch32.exe to the firewall. These are more likely the culprits for WindX errors, as they communicate on higher -- random -- ports.

you may need to change permission to the C:\Sage folder (where the workstation files are) allow your user full control

Had to go to Sage for this one...Not sure how this happened but in the Application Server Config/Server tab, the 'use CmdUser' check box got checked. Once she unchecked it, everything worked. Evidently there is a KB article but I didn't look for that one as I think I felt it was a windows error. Moving forward now!