[DBNETLIB][ConnectionOpen (ParseConnectParams().]Invalid connection on server 2008 R2

_{Tuesday, March 24, 2015 10:01 PM}

I am getting the above error when trying to instal the WSUS role on a Windows Server 2008 R2. I put in the ServerName\Instance just like the wizard asks but I get the Invalid Connection error above. I can make an ODBC connection to the server just fine. The account I am using to install WSUS has an SQL login with sysadmin role and rights to the master db. This server is going to replace a WSUS running on server 2003 and I want to use the same SQL server that one is using. I can connect to port 1433 fine with telnet so I am really lost at this point.

Any idea's?

..AR

_{Thursday, March 26, 2015 11:29 AM ✅Answered | 5 votes}

I got this to work. In looking over this forum I noted one person did not use the instance name in the SQL dialog and it worked. Sure enough this worked for me. Thank you Microsoft for letting me wrangle with this for 2 days! In the pop-up if specifically says DbServerName\InstanceName . Guess I'm SUPPOSED to read between the lines.

At least it's done. Thanks for trying to help tho. :)

...AR

_{Wednesday, March 25, 2015 6:19 AM | 1 vote}

Hi AR,

Is the SQL server installed on the same computer?

If yes, please check if the named pipe has been enabled on the SQL server.

If no, please check the event log of the SQL server. We may find the reason why the connection was denied.

Best Regards.

Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

_{Wednesday, March 25, 2015 11:18 AM}

Steven,

Thanks. That's just the thing - I see no errors in the SQL log to even say it attempted to connect. Firewall is off on the SQL server (it's a remote SQL- I try to have everything use one SQL where possible). Firewall was on in the "new" WSUS, will disable it, reboot and try again. Grasping at straws now.

..AR

_{Friday, January 19, 2018 2:42 PM}

Confirmed.  Do not specify the instance name and it works.  Same issue when installing ADMT 3.2.