Network Connects to Wrong SQL Instance

I have a server running Windows Server 2003 with two instances of SQL Server
2000 - a default instance and a named instance I shall call "INSTANCE_A".
Locally, SQL Server works correctly. Query Analyzer connects to both
instances (SERVER and SERVER\INSTANCE_A) correctly. However, over the
network, when I connect to default instance SERVER it actually connects to
SERVER\INSTANCE_A. Over the network, access to SERVER\INSTANCE_A is unchange
d
and works correctly. Port numbers are set correctly to 1433 and 1226
respectively. The server has been rebooted several times - no change. All
network clients are behaving the same - they all see SERVER\INSTANCE_A when
pointed to SERVER. Any ideas on what's gone wrong?"Jonno" <Jonno@.discussions.microsoft.com> wrote in message
news:57B7981D-0750-43F9-8BB5-F39B4A581570@.microsoft.com...
>I have a server running Windows Server 2003 with two instances of SQL
>Server
> 2000 - a default instance and a named instance I shall call "INSTANCE_A".
> Locally, SQL Server works correctly. Query Analyzer connects to both
> instances (SERVER and SERVER\INSTANCE_A) correctly. However, over the
> network, when I connect to default instance SERVER it actually connects to
> SERVER\INSTANCE_A. Over the network, access to SERVER\INSTANCE_A is
> unchanged
> and works correctly. Port numbers are set correctly to 1433 and 1226
> respectively. The server has been rebooted several times - no change. All
> network clients are behaving the same - they all see SERVER\INSTANCE_A
> when
> pointed to SERVER. Any ideas on what's gone wrong?
Validate that the remote clients are connecting over TCP/IP.
Validate the ports the instances are using by looking into the log file for
each intance.
David|||Thanks David
Both instances have TCP/IP only.
Log files show that both instances are listening on TCP, with default
instance listening on port 1433, and INSTANCE_A listening on port 1226.
Is it possible the publishing of the default instance has become corrupted?
I've tried re-registering from the client side, but the problem persists.
"David Browne" wrote:

> "Jonno" <Jonno@.discussions.microsoft.com> wrote in message
> news:57B7981D-0750-43F9-8BB5-F39B4A581570@.microsoft.com...
>
> Validate that the remote clients are connecting over TCP/IP.
> Validate the ports the instances are using by looking into the log file fo
r
> each intance.
>
> David
>
>

Network Connects to Wrong SQL Instance

I have a server running Windows Server 2003 with two instances of SQL Server
2000 - a default instance and a named instance I shall call "INSTANCE_A".
Locally, SQL Server works correctly. Query Analyzer connects to both
instances (SERVER and SERVER\INSTANCE_A) correctly. However, over the
network, when I connect to default instance SERVER it actually connects to
SERVER\INSTANCE_A. Over the network, access to SERVER\INSTANCE_A is unchanged
and works correctly. Port numbers are set correctly to 1433 and 1226
respectively. The server has been rebooted several times - no change. All
network clients are behaving the same - they all see SERVER\INSTANCE_A when
pointed to SERVER. Any ideas on what's gone wrong?"Jonno" <Jonno@.discussions.microsoft.com> wrote in message
news:57B7981D-0750-43F9-8BB5-F39B4A581570@.microsoft.com...
>I have a server running Windows Server 2003 with two instances of SQL
>Server
> 2000 - a default instance and a named instance I shall call "INSTANCE_A".
> Locally, SQL Server works correctly. Query Analyzer connects to both
> instances (SERVER and SERVER\INSTANCE_A) correctly. However, over the
> network, when I connect to default instance SERVER it actually connects to
> SERVER\INSTANCE_A. Over the network, access to SERVER\INSTANCE_A is
> unchanged
> and works correctly. Port numbers are set correctly to 1433 and 1226
> respectively. The server has been rebooted several times - no change. All
> network clients are behaving the same - they all see SERVER\INSTANCE_A
> when
> pointed to SERVER. Any ideas on what's gone wrong?
Validate that the remote clients are connecting over TCP/IP.
Validate the ports the instances are using by looking into the log file for
each intance.
David|||Thanks David
Both instances have TCP/IP only.
Log files show that both instances are listening on TCP, with default
instance listening on port 1433, and INSTANCE_A listening on port 1226.
Is it possible the publishing of the default instance has become corrupted?
I've tried re-registering from the client side, but the problem persists.
"David Browne" wrote:
> "Jonno" <Jonno@.discussions.microsoft.com> wrote in message
> news:57B7981D-0750-43F9-8BB5-F39B4A581570@.microsoft.com...
> >I have a server running Windows Server 2003 with two instances of SQL
> >Server
> > 2000 - a default instance and a named instance I shall call "INSTANCE_A".
> > Locally, SQL Server works correctly. Query Analyzer connects to both
> > instances (SERVER and SERVER\INSTANCE_A) correctly. However, over the
> > network, when I connect to default instance SERVER it actually connects to
> > SERVER\INSTANCE_A. Over the network, access to SERVER\INSTANCE_A is
> > unchanged
> > and works correctly. Port numbers are set correctly to 1433 and 1226
> > respectively. The server has been rebooted several times - no change. All
> > network clients are behaving the same - they all see SERVER\INSTANCE_A
> > when
> > pointed to SERVER. Any ideas on what's gone wrong?
>
> Validate that the remote clients are connecting over TCP/IP.
> Validate the ports the instances are using by looking into the log file for
> each intance.
>
> David
>
>

network cards and instance names

Hi
I have a client that he needs to install three instance
names of SQL Server 2000 in a server.
Server is not in cluster but it has several network cards.
Client needs to install each instance using a network card
diferent
It is posible to select a network card during a setup of
SQL Server 2000?
There is any posibilite to setup this in SQL Server 2000
Thans for information about this problemTry using the SQL Server Network Utility. This is documented in Books
Online. It should allow you to pick the protocol and port that the server
instances listen on by default.
S. Ashwin
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm.
"ruth G" <caubd@.isa.com.co> wrote in message
news:086c01c361e9$a5a7fcf0$a101280a@.phx.gbl...
> Hi
> I have a client that he needs to install three instance
> names of SQL Server 2000 in a server.
> Server is not in cluster but it has several network cards.
> Client needs to install each instance using a network card
> diferent
> It is posible to select a network card during a setup of
> SQL Server 2000?
> There is any posibilite to setup this in SQL Server 2000
> Thans for information about this problem

nested cursors? @@FETCH_STATUS

Is there only one instance of @.@.FETCH_STATUS in T-SQL procs or triggers?
If I have two nested loops and I am using @.@.FETCH_STATUS to see when I am at
the end of the rowset....will the internal loop screw things up for the
external loop? Do I need to save @.@.FETCH_STATUS off to another variable and
use that to control the loop?
Will this work or fail:
DECLARE vcursor cursor local for
select i.id from inserted
Open vcursor
FETCH NEXT FROM vcursor into @.id
WHILE @.@.FETCH_STATUS=0
BEGIN
declare acursor cursor local for
select classcode FROM CLASSES WHERE ID=@.ID
Open acursor
FETCH NEXT FROM acursor into @.aclasscode
WHILE @.@.FETCH_STATUS=0
BEGIN
-- do processing
--
FETCH NEXT FROM acursor into @.aclasscode
END
CLOSE acursor
DEALLOCATE acursor
END
FETCH NEXT FROM vcursor into @.id
END
CLOSE vcursor
DEALLOCATE vcursor
eg will the internal loop reaching the last recods and setting
@.@.FETCH_STATUS=-1 cause the external loop to finish as well or do they each
have their own 'instance' of @.@.FETCH_STATUS
Al Blake, Canberra, AustraliaYour code will work fine. You are fetching the records in each of the loop
and @.@.FETCH_STATUS contains the latest value. So it won't make any problem
Babu M K
Comat Techonologies Pvt. Ltd.
"Al Blake" <al@._delete_this_.blakes.net> wrote in message
news:%231YQkILFFHA.3200@.TK2MSFTNGP10.phx.gbl...
> Is there only one instance of @.@.FETCH_STATUS in T-SQL procs or triggers?
> If I have two nested loops and I am using @.@.FETCH_STATUS to see when I am
at
> the end of the rowset....will the internal loop screw things up for the
> external loop? Do I need to save @.@.FETCH_STATUS off to another variable
and
> use that to control the loop?
> Will this work or fail:
> DECLARE vcursor cursor local for
> select i.id from inserted
> Open vcursor
> FETCH NEXT FROM vcursor into @.id
> WHILE @.@.FETCH_STATUS=0
> BEGIN
> declare acursor cursor local for
> select classcode FROM CLASSES WHERE ID=@.ID
> Open acursor
> FETCH NEXT FROM acursor into @.aclasscode
> WHILE @.@.FETCH_STATUS=0
> BEGIN
> -- do processing
> --
> FETCH NEXT FROM acursor into @.aclasscode
> END
> CLOSE acursor
> DEALLOCATE acursor
> END
> FETCH NEXT FROM vcursor into @.id
> END
> CLOSE vcursor
> DEALLOCATE vcursor
> eg will the internal loop reaching the last recods and setting
> @.@.FETCH_STATUS=-1 cause the external loop to finish as well or do they
each
> have their own 'instance' of @.@.FETCH_STATUS
> Al Blake, Canberra, Australia
>|||On Thu, 17 Feb 2005 16:32:56 +1100, Al Blake wrote:

>Is there only one instance of @.@.FETCH_STATUS in T-SQL procs or triggers?
>If I have two nested loops and I am using @.@.FETCH_STATUS to see when I am a
t
>the end of the rowset....will the internal loop screw things up for the
>external loop? Do I need to save @.@.FETCH_STATUS off to another variable and
>use that to control the loop?
>Will this work or fail:
Hi Al,
As Babu said: this will work. But it will probably be S-L-O-W.
From your code, I see absolutely no reason to use two nested cursors. You
can just do it in one cursor. Depending on what "-- do processing" really
is, you might even be able to do it without cursors at all.
Here's a version with just one cursor. If you need help to create a
completely set-based version, post some more information about what this
code actually does - and check out www.aspfaq.com/5006 for how to provide
the information.
DECLARE vcursor cursor local for
SELECT i.id, c.classcode
FROM inserted AS i
INNER JOIN classes AS c
ON c.ID = i.ID
Open vcursor
FETCH NEXT FROM vcursor into @.id, @.aclasscode
WHILE @.@.FETCH_STATUS=0
BEGIN
-- do processing
--
FETCH NEXT FROM vcursor into @.id
END
CLOSE vcursor
DEALLOCATE vcursor
Best, Hugo
--
(Remove _NO_ and _SPAM_ to get my e-mail address)

Neither the partner nor the witness server instance for data...

I am getting this error while trying to setup mirroring.
"Neither the partner nor the witness server instance for database "shop" is available. Reissue the command when at least one of the instances becomes available. (Microsoft SQL Server, Error: 1431)"

I am just using principal and mirror server, there is no witness server. I have tried fully qualified name and ip for the servers also. I can connect from the principal server to the mirror server using the management studio and it also creates endpoints on prinicipal and witness. But then gives me an error that it cannot find the instance of the mirror server and if I try again it gives the error above. I can also telnet to port 5022.

I have used -T1400 as the startup parameter.

I did the backup and recovery based on this link http://msdn2.microsoft.com/en-us/library/ms189053.aspx and the mirror server is in recovery mode now.

Can you list the steps you followed when setting up mirroring?

Thanks,

Matt

|||

This error message indicates that the partner thinks that its database should be the principal database, but cannot open the database up because the server needs quorum.

Quorum is required to serve the database if the safety is set to FULL and the witness server has been set. This prevents "split brain". Right now the server doesn't know if the partner and witness have gone ahead and failed over the database to serve it, and so this server leaves its database offline.

If you are getting the "cannot find that server or the instance isn't started" error, then there is a troubleshooting guide in BOL. Most likely it is a security problem.

Thanks,

Mark

|||Hi,

Thanks for the reply. I don't think I need quorum because I am not

using a witness server. The first error message I get after I click on

start mirroring on the wizard is this

"The server network address "TCP://NDIVERSBK: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 configure security without any problem and it creates the end

points on both the servers also but I get an error when I click on

start mirroring.

When I click OK and clcik on start mirroing again I get this error message "Neither

the partner nor the witness server instance for database "shop" is

available. Reissue the command when at least one of the instances

becomes available. (Microsoft SQL Server, Error: 1431)".

Both servers are using the same service account and have the same sa

and administrator passwords. They are on the same network and workgroup

but not on a a domain.

The steps I took to setup mirroring was:

1. Setup the SQL service to run on windows account with administrator

permissions and had the same account password on both the servers.

2. Added -T1400 as starup parameter on both servers and restarted them.

3. Backed up the database on the principal server and restored the it on the mirror server using no recovery mode.

4. Backed up a transaction log on primary server and restored it again on mirror in no-recovery mode.

5. Started mirroing wizard using on prinicipal server and cliked the configure secuirty button.

6. Selected only principal and mirror server and no witness server.

7. Set the principal and mirror server instance using the

same endpoint name and listener port and select encrypt data.

8. Left the service accounts principal and mirror blank

9. It created the end points on both servers and we checked

to make sure they are there.

10 Clicked on start mirroring and that’s when we got the

error that it cannot find mirror server first time.

When we clicked OK and clicked on start mirroring again we

got the second error and always shows up and is mentioned above.
We also tried using the sql queries and got the same

error.|||

Excellent repro steps!

OK, 1418 was one of the most mentioned errors that database mirroring had, and so I went and created a specific Books OnLine topic for it. If you search for "troubleshooting database mirroring" in BOL, then you should find the section.

If you have configured SQL to use the SA accounts (like you state you do), then my next guess is that the port is blocked by a firewall. Basically, the first error message (1418)means the principal cannot access the mirror. Then you connect to the mirror, but since it has never talked with the principal, the mirror does not know what state the session is in, and so it returns the 1431 error.

To verify that the endpoint is accessable, open up a command windows and type "telnet NDIVERSBK 5022". If the endpoint is working properly, then the screen should clear, and you should be able to make 16 keystrokes before the connection is terminated. If you can't do that, the port is probably blocked. If you can do that, we'll start looking in the errorlog files.

Thanks,

Mark

|||There is no firewall between the servers and I tried opening up a command windows and type "telnet NDIVERSBK 5022". The screen cleared, and I was able to make 16 keystrokes before the connection got terminated.

Thanks for your help.

|||

OK, the endpoints are waiting for connections...

Hmmmm...

If the endpoints are configured properly, and you can telnet into the endpoint from each server to the other server, then my guess is that the problem is security.

Could you send me the errorlogs from both servers that have the errors recorded in log?

Normally the errorlogs are in "Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\LOG\ERRORLOG" by default.

mwistrom@.microsoft.com

Thanks,

Mark

|||I have emailed the log file to the email address you provided. Thanks.|||Can this be a problem for mirroring:

The database owner is sa and I am logging in as sa in Management

Studio. But when I click on Database diagrams I get the following error

"Database diagram support objects cannot be installed because this

database does not have a valid owner. To continue, first use the Files

page of the Database Properties dialog box or the ALTER AUTHORIZATION

statement to set the database owner to a valid login, then add the

database diagram support objects."|||

I also already tried FQDN using this line

Alter database db set partner = 'NDIVERSBK.dds.com:5022' and this also does

not work and I still get the same error.

When I try to telnet to NDIVERSBK.dds.com at port 5022 the blank black

screen stay only for a second and then goes without any keystrokes.

|||

Don't forget that the syntax is 'tcp://ndiversbk.dds.com:5022'

If the telnet kicks you out after 1 second, then there is a problem with security and the endpoint. It should let you type 16 keystrokes and then kick you out.

Did you specify the 1400 trace flag?

|||

Just try

drop endpoint [mirroring]

in both server and restart the process

[];s

Marcelo Glauco

Neither the partner nor the witness server instance for data...

I am getting this error while trying to setup mirroring.
"Neither the partner nor the witness server instance for database "shop" is available. Reissue the command when at least one of the instances becomes available. (Microsoft SQL Server, Error: 1431)"

I am just using principal and mirror server, there is no witness server. I have tried fully qualified name and ip for the servers also. I can connect from the principal server to the mirror server using the management studio and it also creates endpoints on prinicipal and witness. But then gives me an error that it cannot find the instance of the mirror server and if I try again it gives the error above. I can also telnet to port 5022.

I have used -T1400 as the startup parameter.

I did the backup and recovery based on this link http://msdn2.microsoft.com/en-us/library/ms189053.aspx and the mirror server is in recovery mode now.

Can you list the steps you followed when setting up mirroring?

Thanks,

Matt

|||

This error message indicates that the partner thinks that its database should be the principal database, but cannot open the database up because the server needs quorum.

Quorum is required to serve the database if the safety is set to FULL and the witness server has been set. This prevents "split brain". Right now the server doesn't know if the partner and witness have gone ahead and failed over the database to serve it, and so this server leaves its database offline.

If you are getting the "cannot find that server or the instance isn't started" error, then there is a troubleshooting guide in BOL. Most likely it is a security problem.

Thanks,

Mark

|||Hi,

Thanks for the reply. I don't think I need quorum because I am not

using a witness server. The first error message I get after I click on

start mirroring on the wizard is this

"The server network address "TCP://NDIVERSBK: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 configure security without any problem and it creates the end

points on both the servers also but I get an error when I click on

start mirroring.

When I click OK and clcik on start mirroing again I get this error message "Neither

the partner nor the witness server instance for database "shop" is

available. Reissue the command when at least one of the instances

becomes available. (Microsoft SQL Server, Error: 1431)".

Both servers are using the same service account and have the same sa

and administrator passwords. They are on the same network and workgroup

but not on a a domain.

The steps I took to setup mirroring was:

1. Setup the SQL service to run on windows account with administrator

permissions and had the same account password on both the servers.

2. Added -T1400 as starup parameter on both servers and restarted them.

3. Backed up the database on the principal server and restored the it on the mirror server using no recovery mode.

4. Backed up a transaction log on primary server and restored it again on mirror in no-recovery mode.

5. Started mirroing wizard using on prinicipal server and cliked the configure secuirty button.

6. Selected only principal and mirror server and no witness server.

7. Set the principal and mirror server instance using the

same endpoint name and listener port and select encrypt data.

8. Left the service accounts principal and mirror blank

9. It created the end points on both servers and we checked

to make sure they are there.

10 Clicked on start mirroring and that’s when we got the

error that it cannot find mirror server first time.

When we clicked OK and clicked on start mirroring again we

got the second error and always shows up and is mentioned above.
We also tried using the sql queries and got the same

error.|||

Excellent repro steps!

OK, 1418 was one of the most mentioned errors that database mirroring had, and so I went and created a specific Books OnLine topic for it. If you search for "troubleshooting database mirroring" in BOL, then you should find the section.

If you have configured SQL to use the SA accounts (like you state you do), then my next guess is that the port is blocked by a firewall. Basically, the first error message (1418)means the principal cannot access the mirror. Then you connect to the mirror, but since it has never talked with the principal, the mirror does not know what state the session is in, and so it returns the 1431 error.

To verify that the endpoint is accessable, open up a command windows and type "telnet NDIVERSBK 5022". If the endpoint is working properly, then the screen should clear, and you should be able to make 16 keystrokes before the connection is terminated. If you can't do that, the port is probably blocked. If you can do that, we'll start looking in the errorlog files.

Thanks,

Mark

|||There is no firewall between the servers and I tried opening up a command windows and type "telnet NDIVERSBK 5022". The screen cleared, and I was able to make 16 keystrokes before the connection got terminated.

Thanks for your help.

|||

OK, the endpoints are waiting for connections...

Hmmmm...

If the endpoints are configured properly, and you can telnet into the endpoint from each server to the other server, then my guess is that the problem is security.

Could you send me the errorlogs from both servers that have the errors recorded in log?

Normally the errorlogs are in "Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\LOG\ERRORLOG" by default.

mwistrom@.microsoft.com

Thanks,

Mark

|||I have emailed the log file to the email address you provided. Thanks.|||Can this be a problem for mirroring:

The database owner is sa and I am logging in as sa in Management

Studio. But when I click on Database diagrams I get the following error

"Database diagram support objects cannot be installed because this

database does not have a valid owner. To continue, first use the Files

page of the Database Properties dialog box or the ALTER AUTHORIZATION

statement to set the database owner to a valid login, then add the

database diagram support objects."|||

I also already tried FQDN using this line

Alter database db set partner = 'NDIVERSBK.dds.com:5022' and this also does

not work and I still get the same error.

When I try to telnet to NDIVERSBK.dds.com at port 5022 the blank black

screen stay only for a second and then goes without any keystrokes.

|||

Don't forget that the syntax is 'tcp://ndiversbk.dds.com:5022'

If the telnet kicks you out after 1 second, then there is a problem with security and the endpoint. It should let you type 16 keystrokes and then kick you out.

Did you specify the 1400 trace flag?

|||

Just try

drop endpoint [mirroring]

in both server and restart the process

[];s

Marcelo Glauco

Neither the partner nor the witness server instance for data...

I am getting this error while trying to setup mirroring.
"Neither the partner nor the witness server instance for database "shop" is available. Reissue the command when at least one of the instances becomes available. (Microsoft SQL Server, Error: 1431)"

I am just using principal and mirror server, there is no witness server. I have tried fully qualified name and ip for the servers also. I can connect from the principal server to the mirror server using the management studio and it also creates endpoints on prinicipal and witness. But then gives me an error that it cannot find the instance of the mirror server and if I try again it gives the error above. I can also telnet to port 5022.

I have used -T1400 as the startup parameter.

I did the backup and recovery based on this link http://msdn2.microsoft.com/en-us/library/ms189053.aspx and the mirror server is in recovery mode now.

Can you list the steps you followed when setting up mirroring?

Thanks,

Matt

|||

This error message indicates that the partner thinks that its database should be the principal database, but cannot open the database up because the server needs quorum.

Quorum is required to serve the database if the safety is set to FULL and the witness server has been set. This prevents "split brain". Right now the server doesn't know if the partner and witness have gone ahead and failed over the database to serve it, and so this server leaves its database offline.

If you are getting the "cannot find that server or the instance isn't started" error, then there is a troubleshooting guide in BOL. Most likely it is a security problem.

Thanks,

Mark

|||Hi,
Thanks for the reply. I don't think I need quorum because I am not using a witness server. The first error message I get after I click on start mirroring on the wizard is this
"The server network address "TCP://NDIVERSBK: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 configure security without any problem and it creates the end points on both the servers also but I get an error when I click on start mirroring.
When I click OK and clcik on start mirroing again I get this error message "Neither the partner nor the witness server instance for database "shop" is available. Reissue the command when at least one of the instances becomes available. (Microsoft SQL Server, Error: 1431)".
Both servers are using the same service account and have the same sa and administrator passwords. They are on the same network and workgroup but not on a a domain.
The steps I took to setup mirroring was:
1. Setup the SQL service to run on windows account with administrator permissions and had the same account password on both the servers.
2. Added -T1400 as starup parameter on both servers and restarted them.
3. Backed up the database on the principal server and restored the it on the mirror server using no recovery mode.
4. Backed up a transaction log on primary server and restored it again on mirror in no-recovery mode.
5. Started mirroing wizard using on prinicipal server and cliked the configure secuirty button.
6. Selected only principal and mirror server and no witness server.
7. Set the principal and mirror server instance using the same endpoint name and listener port and select encrypt data.
8. Left the service accounts principal and mirror blank
9. It created the end points on both servers and we checked to make sure they are there.
10 Clicked on start mirroring and that’s when we got the error that it cannot find mirror server first time.
When we clicked OK and clicked on start mirroring again we got the second error and always shows up and is mentioned above.
We also tried using the sql queries and got the same error.
|||

Excellent repro steps!

OK, 1418 was one of the most mentioned errors that database mirroring had, and so I went and created a specific Books OnLine topic for it. If you search for "troubleshooting database mirroring" in BOL, then you should find the section.

If you have configured SQL to use the SA accounts (like you state you do), then my next guess is that the port is blocked by a firewall. Basically, the first error message (1418)means the principal cannot access the mirror. Then you connect to the mirror, but since it has never talked with the principal, the mirror does not know what state the session is in, and so it returns the 1431 error.

To verify that the endpoint is accessable, open up a command windows and type "telnet NDIVERSBK 5022". If the endpoint is working properly, then the screen should clear, and you should be able to make 16 keystrokes before the connection is terminated. If you can't do that, the port is probably blocked. If you can do that, we'll start looking in the errorlog files.

Thanks,

Mark

|||There is no firewall between the servers and I tried opening up a command windows and type "telnet NDIVERSBK 5022". The screen cleared, and I was able to make 16 keystrokes before the connection got terminated.
Thanks for your help.
|||

OK, the endpoints are waiting for connections...

Hmmmm...

If the endpoints are configured properly, and you can telnet into the endpoint from each server to the other server, then my guess is that the problem is security.

Could you send me the errorlogs from both servers that have the errors recorded in log?

Normally the errorlogs are in "Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\LOG\ERRORLOG" by default.

mwistrom@.microsoft.com

Thanks,

Mark

|||I have emailed the log file to the email address you provided. Thanks.
|||Can this be a problem for mirroring:
The database owner is sa and I am logging in as sa in Management Studio. But when I click on Database diagrams I get the following error
"Database diagram support objects cannot be installed because this database does not have a valid owner. To continue, first use the Files page of the Database Properties dialog box or the ALTER AUTHORIZATION statement to set the database owner to a valid login, then add the database diagram support objects."
|||

I also already tried FQDN using this line

Alter database db set partner = 'NDIVERSBK.dds.com:5022' and this also does not work and I still get the same error.

When I try to telnet to NDIVERSBK.dds.com at port 5022 the blank black screen stay only for a second and then goes without any keystrokes.

|||

Don't forget that the syntax is 'tcp://ndiversbk.dds.com:5022'

If the telnet kicks you out after 1 second, then there is a problem with security and the endpoint. It should let you type 16 keystrokes and then kick you out.

Did you specify the 1400 trace flag?

|||

Just try

drop endpoint [mirroring]

in both server and restart the process

[];s

Marcelo Glauco