Advertisement

04.23.2007 at 11:53AM PDT, ID: 22528669
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.8

SQL 2005 mirroring - Error 1418 setting partner instance

Asked by firstbankak in SQL Server 2005, Microsoft Windows Operating Systems

Tags: , , , ,

I am setting up asynchronous mirroring in SQL 2005. The Mirror database is able to set it's partner as the Principal database. It does not work the other way around.

When I issue the following TSQL command on the Principal database:

alter database <DB> set partner = 'TCP//<IP OF MIRROR>:5022';

I get the following error:

Msg 1418, Level 16, State 1, Line 1
The server network address ..... can not be reached or does not exist.

I scanned for open ports and both the mirror and principal servers are listening on port 5022. They can ping each other. I have Googled this without any luck.Start Free Trial
[+][-]04.23.2007 at 04:15PM PDT, ID: 18962369

View this solution now by starting your 7-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: SQL Server 2005, Microsoft Windows Operating Systems
Tags: 1418, sql, 2005, error, mirror
Sign Up Now!
Solution Provided By: dready
Participating Experts: 1
Solution Grade: A
 
 
[+][-]09.15.2008 at 04:35AM PDT, ID: 22477529

Experts Exchange has a courteous staff of administrators who help members get the most out of the website by means of administrative comments like this one.

Start your 7-day free trial to view this Administrative Comment or ask the Experts your question.

 
[+][-]09.19.2008 at 06:47PM PDT, ID: 22527557

Experts Exchange has a courteous staff of administrators who help members get the most out of the website by means of administrative comments like this one.

Start your 7-day free trial to view this Administrative Comment or ask the Experts your question.

 
 
Loading Advertisement...
20080716-EE-VQP-32