Sage 100 Advanced 2017 Client on Remote Desktop Server 2016

I'm preparing a new Remote Desktop server based on Windows Server 2016.  I have successfully installed the Sage 100 Advanced Client 2017 on the server in a remote session and it connects to the Sage server just fine.  I published the client app through the server manager interface and added the proper command line parameters.  It seems to start OK but never gets to the login prompt.  The remote session is active but it shows the client is disconnected.  I believe all settings and permissions are set correctly.  Has anyone seen this behavior before?  Other published apps work fine, including Office 365 Word and Excel.  I'm using the web interface to activate the remote app.  I've also tried IE and Chrome with the same results on both.

We are running an older version of Sage client on a Windows 2008 server with remote desktop for production.  It's never shown this behavior and works perfectly.

Parents
  • 0
    I can confirm this issue, as I am seeing the same symptoms today.
    -New 2016 remote app installation.
    -Sage 2017.
    -App runs fine when connected to the desktop.
    -Other apps are published and running without issue.
    -When you publish Sage 2017 with the Command-line parameters "../launcher/sota.ini *Client -ARG "cai100dcrds" "PORTID" "Sage 100""... the app tries to connect... and then nothing. User then shows logged in but disconnected from the RDS managment.

    Has there been any update from Sage on this issue?
  • 0 in reply to J001-1
    I just got this back from the vendor who is responsible for the Sage migration.

    "After talking with Sage, it has been confirmed that this is a defect.

    Sage 100 is fully compatible in just a normal terminal services mode on Server 2016 with no real problems, but publishing as an App on server 2016 is defective and not working at the moment. Engineering received the issue several weeks ago and are working on it but there is no time frame for completion yet.

    The workaround is to publish on Server 2012.
    "
Reply
  • 0 in reply to J001-1
    I just got this back from the vendor who is responsible for the Sage migration.

    "After talking with Sage, it has been confirmed that this is a defect.

    Sage 100 is fully compatible in just a normal terminal services mode on Server 2016 with no real problems, but publishing as an App on server 2016 is defective and not working at the moment. Engineering received the issue several weeks ago and are working on it but there is no time frame for completion yet.

    The workaround is to publish on Server 2012.
    "
Children