Existing Connection Was Forcibly Closed By Remote Host (3 replies)
Can you connect/Test to the database from the Admin Console?
When I test the database, I get the same error message. Okay, my boss' recommendation is that we simply move the Iman database to the Iman virtual, since everything else seems to be working okay (i.e. Sage 300 database connectivity). Since we're using v3 on a 2008 server with 2008 SQL, can we install SQL Express 2012 with v3?
Thanks! Sorry - all of their stuff is older than dirt. It would be some serious work and money to move it all - which they don't have. =)
Never mind! I found a "what's new" doc for v3 that says SQL 2014 is now supported. So I guess we're good. Okay, I'm closing this ticket for now. Thanks for the assistance!
I have a client who is still on v3 of Iman and everything has been running fine for quite a while. They really only have two jobs running - one posts orders to Accpac from xml download files from their webstore, the other creates IC Receipt batches in Sage based on a SQL database query.
One of their IT guys did some updates to the server environment this past weekend - running all windows updates (including KB4486563, KB4054530, KB4487078) and they moved a WSUS server to the hyper-v that our stuff is on. They set up some group policies for that new server.
Since then, I can't get logged into Iman, and though it's possible the jobs are still running successfully, we are getting a blank email every time they run. the only thing in the email body is the realisable logo.
I get the following error when I try to login to the Iman software: A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - An existing conneciton was forcibly closed by the remote host.)
In case any of this helps: we have an Iman virtual server, the sql database for Iman is on another server called Accpac-2012. My iman permissions use a windows login called ntc\iman and I have verified I can open Sage 300 on the iman virtual logged into windows as this windows iman user. So Sage 300 on the machine at least can see/read sql using this user. I also verified that my windows user has rights to the Accpac share.
We're not entirely sure even in which direction we should be looking, so if you have any brilliant ideas, they would be much appreciated. I've included a screenshot of the error.