|
Home > Archive > MS SQL Server > February 2006 > SQL Server 2005 mirroring problems
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
SQL Server 2005 mirroring problems
|
|
|
| Hello,
I am facing with two problems with SQL Server 2005 mirroring:
When first trying to make a mirror there is a need to add trace flag –t1400
as there is messages that currently mirroring is only for evaluation.
Is that meaning that I have no license for mirroring or SQL Server 2005 is
not ready yet for mirroring?
* I have two licensed copies of SQL Server 2005 standard!
I have two servers' names:
SERVER
SERVER2
After running the "Configure Security…" without a "witness" server and press
the "Start Mirroring" button I am receiving the message"
"The server network address "TCP://server:5022" can not be reached or does
not exist. Check the network address name and reissue the command. (Microsoft
SQL Server, Error: 1418)"
I can "Ping" and "Telnet" to both SERVER & SERVER2 with port 5022.
Thanks in advanced for any help,
Asaf
| |
| Dan Guzman 2005-12-03, 9:23 am |
| Below is an excerpt from the Books Online. Last I heard, the mirroring
feature was planned to be made available for general use H1 2006.
<Excerpt
href="ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/25a44245-e28d-41b5-ad65-7778d50c42ea.htm">
Important:
Microsoft support policies do not apply to the database mirroring feature in
SQL Server 2005. Database mirroring is currently disabled by default, but
may be enabled for evaluation purposes only by using trace flag 1400 as a
startup parameter. (For more information about trace flags, see Trace Flags
(Transact-SQL).) Database mirroring should not be used in production
environments, and Microsoft support services will not support databases or
applications that use database mirroring. Database mirroring documentation
is included in SQL Server 2005 for evaluation purposes only, and the
Documentation Policy for SQL Server 2005 Support and Upgrade does not apply
to the database mirroring documentation.
</Excerpt>
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Asaf" <AG70@newsgroups.nospam> wrote in message
news:DD568096-0BAF-4302-AF9B- 31C8D8DA667B@microso
ft.com...
> Hello,
>
> I am facing with two problems with SQL Server 2005 mirroring:
>
> When first trying to make a mirror there is a need to add trace
> flag -t1400
> as there is messages that currently mirroring is only for evaluation.
> Is that meaning that I have no license for mirroring or SQL Server 2005 is
> not ready yet for mirroring?
> * I have two licensed copies of SQL Server 2005 standard!
>
> I have two servers' names:
> SERVER
> SERVER2
>
> After running the "Configure Security." without a "witness" server and
> press
> the "Start Mirroring" button I am receiving the message"
> "The server network address "TCP://server:5022" can not be reached or does
> not exist. Check the network address name and reissue the command.
> (Microsoft
> SQL Server, Error: 1418)"
>
> I can "Ping" and "Telnet" to both SERVER & SERVER2 with port 5022.
>
> Thanks in advanced for any help,
> Asaf
>
| |
|
| Hello ,
I met the same problem, did you resovle this one ?
Thanks
"Dan Guzman" a écrit :
> Below is an excerpt from the Books Online. Last I heard, the mirroring
> feature was planned to be made available for general use H1 2006.
>
> <Excerpt
> href="ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/25a44245-e28d-41b5-ad65-7778d50c42ea.htm">
> Important:
>
> Microsoft support policies do not apply to the database mirroring feature in
> SQL Server 2005. Database mirroring is currently disabled by default, but
> may be enabled for evaluation purposes only by using trace flag 1400 as a
> startup parameter. (For more information about trace flags, see Trace Flags
> (Transact-SQL).) Database mirroring should not be used in production
> environments, and Microsoft support services will not support databases or
> applications that use database mirroring. Database mirroring documentation
> is included in SQL Server 2005 for evaluation purposes only, and the
> Documentation Policy for SQL Server 2005 Support and Upgrade does not apply
> to the database mirroring documentation.
> </Excerpt>
>
> --
> Hope this helps.
>
> Dan Guzman
> SQL Server MVP
>
> "Asaf" <AG70@newsgroups.nospam> wrote in message
> news:DD568096-0BAF-4302-AF9B- 31C8D8DA667B@microso
ft.com...
>
>
>
| |
| Michael Hotek 2006-02-02, 11:23 am |
| There is no resolution to this. You have to turn on trace flag 1400.
Database Mirroring is still not officially supported. It exists in both
Standard and Enterprise Edition. There is no special licensing required.
You can use it wherever you want to use it. However, if you encounter an
issue, there isn't any support for that feature yet. I have implemented it
in production and haven't run into any issues in the last couple of months.
--
Mike
http://www. solidqualitylearning
.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"nono" <nono@discussions.microsoft.com> wrote in message
news:1E8F4C17-29AE-46BA-A80D- 66E3FD5AB6BC@microso
ft.com...[color=darkred]
> Hello ,
> I met the same problem, did you resovle this one ?
> Thanks
>
> "Dan Guzman" a écrit :
>
| |
| stephanie 2006-02-09, 3:23 am |
| I have turned on the trace flag 1400 and configuring database mirroring.
Once I press 'Start Mirroring', it shows the exact same error!
and I checked the tracestatus
TraceFlag Status Gloabl Session
1400 1 1 0
Anyone encounter the same problem or any idea on it? Thanks in advance
"Michael Hotek" wrote:
> There is no resolution to this. You have to turn on trace flag 1400.
> Database Mirroring is still not officially supported. It exists in both
> Standard and Enterprise Edition. There is no special licensing required.
> You can use it wherever you want to use it. However, if you encounter an
> issue, there isn't any support for that feature yet. I have implemented it
> in production and haven't run into any issues in the last couple of months.
>
> --
> Mike
> http://www. solidqualitylearning
.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
>
> "nono" <nono@discussions.microsoft.com> wrote in message
> news:1E8F4C17-29AE-46BA-A80D- 66E3FD5AB6BC@microso
ft.com...
>
>
>
| |
| Michael Hotek 2006-02-09, 11:23 am |
| Well....the solution as posted on this thread was due to network
connectivity issues.
--
Mike
http://www. solidqualitylearning
.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"stephanie" < stephanie@discussion
s.microsoft.com> wrote in message
news:CF88E3CE-A2A2-47C9-A20E- 08F4CC25A062@microso
ft.com...[color=darkred]
>I have turned on the trace flag 1400 and configuring database mirroring.
> Once I press 'Start Mirroring', it shows the exact same error!
>
> and I checked the tracestatus
> TraceFlag Status Gloabl Session
> 1400 1 1 0
> Anyone encounter the same problem or any idea on it? Thanks in advance
>
>
> "Michael Hotek" wrote:
>
| |
| stephanie 2006-02-10, 3:23 am |
| I can telnet to the servername with port# of mirror instance
any advise on it? Thanks in advance.
"Michael Hotek" wrote:
> Well....the solution as posted on this thread was due to network
> connectivity issues.
>
> --
> Mike
> http://www. solidqualitylearning
.com
> Disclaimer: This communication is an original work and represents my sole
> views on the subject. It does not represent the views of any other person
> or entity either by inference or direct reference.
>
>
> "stephanie" < stephanie@discussion
s.microsoft.com> wrote in message
> news:CF88E3CE-A2A2-47C9-A20E- 08F4CC25A062@microso
ft.com...
>
>
>
| |
| Michael Hotek 2006-02-10, 1:23 pm |
| It doesn't matter if you can telnet to the port. The principal instance can
not connect to the TCP endpoint of the mirror. That is different from being
able to telnet to it. You have to figure out what is causing the connection
issue: endpoint not created properly, endpoint not started, no permissions
on the endpoint, firewall restriction between principal and mirror, dozens
of other things. This is a pure connectivity issue and not a problem with
mirroring. You error message is simply saying "I can't connect".
--
Mike
http://www. solidqualitylearning
.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"stephanie" < stephanie@discussion
s.microsoft.com> wrote in message
news:E1416F70-3BDB-44E8-A735- EADF25F1C76C@microso
ft.com...[color=darkred]
>I can telnet to the servername with port# of mirror instance
> any advise on it? Thanks in advance.
>
>
> "Michael Hotek" wrote:
>
|
|
|
|
|