SQL 2005 Mirroring Problems, HELP



I try to Mirror a Database, i get the following Exception:

The server network address "TCP://xxx.xxxx.xxx: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. (.Net SqlClient
Data Provider)

I can reach all Servers via Telnet.

All three Servers are in one Domain,with no windows firewall.


Principal: MSSQL 2005 x64 Enterprise Editon with SP1
Mirror: MSSQL 2005 x64 Enterprise Editon with SP1
Witness: MSSQL 2005 Standard Editon with SP1

-------------------------------------------------------------------------------
Principal
USE AdventureWorks
CREATE ENDPOINT Mirroring
STATE=STARTED
AS TCP (LISTENER_PORT=5022 )
FOR DATABASE_MIRRORING (ROLE=PARTNER)
GO
CREATE LOGIN [mydomain\dbmirroring] FROM WINDOWS ;
GO
GRANT CONNECT ON ENDPOINT::Mirroring TO [mydomain\dbmirroring];
GO

-------------------------------------------------------------------------------
Mirror
CREATE ENDPOINT Mirroring
STATE=STARTED
AS TCP (LISTENER_PORT=5022 )
FOR DATABASE_MIRRORING (ROLE=ALL)
GO

CREATE LOGIN [mydomain\dbmirroring] FROM WINDOWS ;
GO
GRANT CONNECT ON ENDPOINT::Mirroring TO [mydomain\dbmirroring];
GO

-------------------------------------------------------------------------------
Witness
CREATE ENDPOINT Mirroring
STATE=STARTED
AS TCP (LISTENER_PORT=5022 )
FOR DATABASE_MIRRORING (ROLE=WITNESS)
GO

CREATE LOGIN [mydomain\dbmirroring] FROM WINDOWS ;
GO
GRANT CONNECT ON ENDPOINT::Mirroring TO [mydomain\dbmirroring];
GO

-------------------------------------------------------------------------------
:CONNECT Principal
ALTER DATABASE [AdventureWorks] SET RECOVERY FULL WITH NO_WAIT
GO
BACKUP DATABASE [AdventureWorks]
TO DISK = 'C:\Backup\AdventureWorks_dump.bak'
WITH INIT
GO

-------------------------------------------------------------------------------
:CONNECT Mirror
RESTORE DATABASE [AdventureWorks]
FROM DISK = 'C:\Backup\AdventureWorks_dump.bak'
WITH
MOVE 'AdventureWorks_Data' TO
'C:\Program Files\Microsoft SQL Server\MSSQL.4' +
'\MSSQL\Data\AdventureWorks_Data.mdf',
MOVE 'AdventureWorks_Log' TO
'C:\Program Files\Microsoft SQL Server\MSSQL.4' +
'\MSSQL\Data\AdventureWorks_Log.ldf',
NORECOVERY, REPLACE

-------------------------------------------------------------------------------
:CONNECT Principal
BACKUP LOG [AdventureWorks]
TO DISK = 'C:\Backup\AdventureWorksLog_Dump.bak'
WITH INIT
GO

-------------------------------------------------------------------------------
:CONNECT Mirror
RESTORE LOG [AdventureWorks]
FROM DISK = 'C:\Backup\AdventureWorksLog_Dump.bak'
WITH NORECOVERY
GO

-------------------------------------------------------------------------------
:CONNECT Mirror
ALTER DATABASE AdventureWorks
SET PARTNER = 'TCP://Principal:5022'
GO

-------------------------------------------------------------------------------
:CONNECT Principal
ALTER DATABASE AdventureWorks
SET PARTNER = 'TCP://Mirror:5022'
GO

ALTER DATABASE AdventureWorks
SET WITNESS = 'TCP://Witness:5022'
GO





if i try this with different Port on tree local SQL Server instances it
works, but NOT on three diffrent SQL Server.

If i try the Mirroring Wizard i get the same Exception :o(

Thanx for help


Stefan

.



Relevant Pages

  • Re: SQL 2005 Mirroring Problems, HELP
    ... Mirror: MSSQL 2005 x64 Enterprise Editon with SP1 ... CREATE ENDPOINT Mirroring ... ALTER DATABASE [AdventureWorks] SET RECOVERY FULL WITH NO_WAIT ... but NOT on three diffrent SQL Server. ...
    (microsoft.public.sqlserver)
  • Re: Licensing for DB mirroring
    ... As long as you don't use it for anything other than a pure mirror it does not require a license similar to the way clustering works. ... Actually you do not need a license for the database server running the ... SQL Server Pricing and Licensing ...
    (microsoft.public.sqlserver.setup)
  • Re: Licensing for DB mirroring
    ... than a pure mirror it does not require a license similar to the way clustering works. ... Actually you do not need a license for the database server running the ... SQL Server Pricing and Licensing ...
    (microsoft.public.sqlserver.setup)
  • Re: Cant start mirroring
    ... Not setting mirror database' s recovery state as norecovery is one of the reasons of this problem. ... Are your Logins identical on your Principal and Mirror SQL Server Instances? ...
    (microsoft.public.sqlserver.setup)
  • Re: SQL Server 2005, Database Mirroring and SQL Server Agent
    ... Are you saying that you are mirroring the msdb database? ... think you even could mirror msdb... ... > The SQL I put in my original post will check that it is the principle ... >> Tibor Karaszi, SQL Server MVP ...
    (microsoft.public.sqlserver.server)