Hello as an update.  We came in this morning and the error showing up after our changes is: Connection Timed out Waiting for your application to start.  So I shut down the service and am running the Sage Service as an application to see how things go.  Again this issue happens when more users are logged into the server.  Also, port 9998 is not a conflict either.

So this would all seem resource related but the VM it is running on is much higher end speced that the other one.  1 year Hyper-V host with 128GB RAM, SSD drives, etc.  Also I highly doubt this is a network related issue as well since it ran for years on another VM on the same host using the same NIC, etc.  

So we are kinda at a loss here.  Any input would be great...I will post back on our success running as an Application as opposed to a service.

Thanks for your consideration

Just wondering if you looked at this to see if anything helped? Error: "Connection failure to host: [TCP]<server>:<port number>:NODELAY;STREAM" (sage.com)

If Application works fine but Service gives errors, do Option 2:

https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=20344

Thanks...Yes...That was the article I linked to originally.  I went through all those steps to no avail.

That being said as an update if I run the application server as an "application" as opposed to a service things seem to be working ok.  But this was not the case on the older server.  That server was running with 1/3 the memory allocated under windows 2008 R2 as a service and never had an issue.  Perhaps there was some tweak we did many moons ago to allow it to run as a service.  But I am not seeing anything.

Is the workaround to run as an application as opposed to a service current advice?  I thought it was old advise.  And if it is current advice is there any tweaks that will allow us to run as a service?  There are about 20 users hitting this server.  It seems when the user count climbs that is why we have the issues when running as a service.

Thanks again for any potential info.

Thanks Kevin...We were posting at the same time.  OK...I will give this a shot.  I appreciate the feedback.  I did not know this was current advice.  

I appreciate it

It applies for as long as Microsoft manages Windows service memory the same way.

Thanks Kevin.!

This is likely what is happening and will fix the issue.  A suggestion to Sage in their documentation of the issue and the various workarounds would be to link to the post you provided near the end of their article where they discuss running under Application mode.  If we would have seen that we could have avoided all of this.  

But I truly appreciate the time you to respond.!!  Thanks