﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2012 / SQL 2012 - General  / Mirroring failed due to invalid connection string / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Fri, 24 May 2013 09:30:12 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Mirroring failed due to invalid connection string</title><link>http://www.sqlservercentral.com/Forums/Topic1425386-2799-1.aspx</link><description>In the database mirroring endpoints do not specify the instance name. Should be http://servername.fqdn:port.</description><pubDate>Tue, 05 Mar 2013 13:52:53 GMT</pubDate><dc:creator>Mohit K. Gupta</dc:creator></item><item><title>Mirroring failed due to invalid connection string</title><link>http://www.sqlservercentral.com/Forums/Topic1425386-2799-1.aspx</link><description>Hello,  I'm receiving the following error:ALTER DATABASE command failed due to an invalid server connection string.when I issue the command:ALTER DATABASE DBName SET PARTNER = 'TCP://DCDRSQLv01.datacoremarketing.com\SQLMICH01:5022';GOSituation - I'm attempting to mirror from a default instance to a named instance.  Each instance is running SQL 2012 SP1.  Each server is in a different domain and I have configured logins and certificates to make it work properly.  I've seen several posts indicating try the following:- check that both servers can be pinged, name resolves and telnet succeeds to the configured port 5022.- confirm that mirroring is started and logins are granted permission.- restore database and transaction log with NORECOVERY option.- Confirm the database and instance are correct.- Attempt connection without the instance name.- Start the Browser service on all nodes.None of these appear to be providing a different result except for the later which complains "network address cannot be reached" (note telnet to 5022 does work).Any assistance is most appreciated.  I'm out of ideas.</description><pubDate>Fri, 01 Mar 2013 01:07:24 GMT</pubDate><dc:creator>jerrycutshaw</dc:creator></item></channel></rss>