• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 518
  • Last Modified:

SQL Mirroring erro SQL 2008 R2

I had mirroring working on 2 SQL servers, both on the same domain, running a domain account for their services. One of my colleagues had to break the mirror to clear up the transaction log for some reason, now we cannot enable mirroring again.

I have researched everywhere and tried setting up from scratch, I get the mirrored database enabled to see the principle, but when I run the script below on the principle:

ALTER DATABASE [Database]
    SET PARTNER =
    'TCP://FQDN of Mirror:5022';
GO

Msg 1418, Level 16, State 1, Line 1
The server network address "TCP://FQDN:5022" can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational.

I have no witness setup, and can telnet from each server to the other on 5022 successfully. this was working, so I am not sure. Principle server is on Full Recovery model, I did backup and restore to Mirror server WITH NORECOVERY option.
0
IT_Techno
Asked:
IT_Techno
  • 7
  • 4
  • 4
1 Solution
 
Mattijs33Commented:
Is the database in the mirrorserver in "Restoring" state.
Does the principe database also use port 5022?
Have you set the user permission to the mirrordatabase after the restore?
0
 
IT_TechnoAuthor Commented:
The mirrored database is in restoring state, the 2 servers are on server machines and both use port 5022 to communicate to each other. I tried setting user permissions but gave me some message about not being able to set permissins for sysadmin user, the domain account I am using is a sysadmin user.
0
 
IT_TechnoAuthor Commented:
sorry, I meant in my previous comment that both sql servers are on seperate servers.
0
Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

 
Ramesh Babu VavillaCommented:
check where  the port 5022 is blocked by <b> Firewall</b> or by anti virus software.

you can also use telnet to check the port is working or not.

allot grant connection for the port
0
 
Ramesh Babu VavillaCommented:
both the sql server services should be started eith the ame domain name,a
0
 
IT_TechnoAuthor Commented:
I did state earlier I did telnet test from each server to make sure it is not blocked. This was successful so nothing blocking it. The SQL services are using the same domain username.
0
 
Ramesh Babu VavillaCommented:
http://technet.microsoft.com/en-us/library/ms187811.aspx

check the endpoint permissions in the server
0
 
Ramesh Babu VavillaCommented:
0
 
Mattijs33Commented:
Are there other mirroring databases on one of the servers?
Have you tried to setup the database via the GUI?
0
 
IT_TechnoAuthor Commented:
Hi, I did try removing and re-creating the endpoints, with no luck. I also setup the initial mirror and tried first via the GUI, as it was working this way. I am trying in desperation with scripts to correct the problem, as I only get the error message originally posted with no direct resolution.
0
 
Mattijs33Commented:
Did you remove the original mirror database before you did a new restore?
0
 
IT_TechnoAuthor Commented:
Yes I removed the mirror first before I restored the mirror.
0
 
Mattijs33Commented:
Have you tried to connect via an IP address instead of the FQDN?

Does the mirrorserver allow remote connections via TCP/IP?

The shouldn't be any other databases on that server which are mirorring, is that the case?
0
 
IT_TechnoAuthor Commented:
Had to reinstall servers to resolve
0
 
IT_TechnoAuthor Commented:
No solution, reinstall resolved.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 7
  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now