@gis3780 Thanks for letting us know you have found the solution to your connection issue.
@MarkAtSafe Sorry to take your time thinking about this, but FME appears to be fine with the revised connection string format to include the port number: server\instance,port. It turns out there was yet another dba policy instituted unbeknownst to me whereby certain machines were being blocked from connecting to the new server, including the one on which I was attempting to establish the updated db connection in FME Desktop. When I moved Desktop to a more privileged machine, the connection worked fine. Thanks again for your response, and sorry to take your time, but thought you'd also be happy to know that all is fine with the FME part of this issue.
@MarkAtSafe In the working connection, I am not specifying an instance name or a port number, just the db server name. I have attached a screen shot to show what the db connection dialog looks like. Hopefully I didn't obscure too much to see what's going on. I was able to confirm with a dba that the default port 1433 has been the standard until a recent policy change was enacted such that all connections must be made through a non-default port number, hence the comma port number in the connection string. And then on top of that, when our db was just moved to a new server it was under a named instance as well. Thanks for your response. Let me know if I can clarify anything further.
@gis3780 Could you give me an example of the connection string you use for the original (working) connection? Does it include an instance name?
Attachments: