December 13, 2006 at 3:18 pm
Just as a follow-up to that last reply: that wasn't really it I don't think... there is no DNS server betwixt these 3 in their dedicated mirroring LAN, and why would there be up-looking of names if names aren't being used... setting database mirroring up by IP address and using certificates per the MSFT instructions was supposed to be an alternative to also setting up or having a Domain environment...
When one has it working (after using the HOSTS file in my case, though some other way may have surfaced), you still get:
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\xxxx>nslookup PARTNER02
Server: xxx.xxx.net
Address: xxx.xxx.xxx.xxx
*** xxx.xxx.net can't find PARTNER02: Non-existent domain
C:\Documents and Settings\xxxx>
August 26, 2008 at 8:53 am
has anyone had any success setting up a mirroring environment on a standalone machine running vista and SQL Developer editions. I am able to set up the principal and the mirror. But I am encountering an error when I attempt to set up the witness.
The ALTER DATABASE command could not be sent to the remote server instance
The instances are running under the same local account and this machine is not part of a domain.
Joe
August 26, 2008 at 10:35 am
I've tested DB-mirroring using 2 dev-editions (primary / mirror) and an express edition for witness.
Just make sure the service accounts can connect to one another !
What I did was using the same domain service account.
Since one instance will be backup for the other, that did make sence to me.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
August 27, 2008 at 6:48 am
I have seen these errors before.
Are you running the same Patch level of SQL Server Express Edition as the Principal and Mirror servers?
I was running my Standard SQL servers (Principal and Mirror) at SP2 and was only able to get an Express Edition Witness server installed and working after downloading an SP2 integrated copy of SQLEXPR32.exe from Microsoft.com.
Whilst the Witness server does not have to be of the same edition of SQL Server 2005 it probably needs the same patch level.
I'd recommend upgrading to SP2 anyway.
There are huge changes to supportability and functionality of Mirroring between RTM and SP2!
September 15, 2008 at 1:43 pm
I am running 3 instances of the developer ediditon on the same machine. All are running under the same service account and are patched to version 9.00.3073. It is a stand alone machine not part of any domain. The mirroring is working fine, but I cannot get the witness to join the mirror. Since It is not part of a domain, I am attempting to connect using IP addresses and ports. For the mirroring, it works fine, but when I attempt to to connect the witness to the principal, I get the error below.
Msg 1456, Level 16, State 3, Line 2
The ALTER DATABASE command could not be sent to the remote server instance 'TCP://xx.0.0.xx:xxxx'. The database mirroring configuration was not changed. Verify that the server is connected, and try again.
September 15, 2008 at 11:53 pm
- Can you connect from the witness to the principal or mirror using management studio and just execute some queries ?
- can you do the same using the witnesses service account ?
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
September 18, 2008 at 6:59 am
I am connected to all three instances using SMS and logged in with the same account. There are no issues there. My problem is connecting the witness server to the principal. All three instances are running on same standalone machine.
This was a proof of concept to see how mirroring works, so all three instances are running on the same box. I could get mirroing to work but not the witness. I found some info on the net on using alerts and I have for now implemented this approach. I would still like to implement the witness server.
September 18, 2008 at 7:04 am
are you using the same service account for all the instances ?
if not, you need to grant loging for all service accounts to all the instances
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
August 20, 2009 at 2:02 pm
Oh man...Why didn't anyone say that before?!?!
That was my exact problem. I can't believe I wasted so much time on that and didn't even think of service accounts.
Thank you SO much. I have mine up and working fine now.
August 24, 2009 at 12:56 am
Indeed ... some times we overlook the obvious. :hehe: ( been there .. done that 😀 )
Happy mirroring 😉
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
November 24, 2014 at 3:42 pm
I am having the same issue, only I am trying to use 1 witness server for 2 mirrored databases that reside on different servers. For example, I have db1 on server(A) being mirrored to server(B) using witness server(1), and db2 on server(C) mirrored to server(D) but I cannot get it High Safety using witness server (1) on the same port 5022.
I get error message: The ALTER DATABASE command could not be sent to the remote server instance 'TCP://witness server(1)'. The database mirroring configuration was not changed. Verify that the server is connected, and try again.
Mirroring is already up and working on the first db1 using witness1, and mirroring also works on the second set, however the second db on server(2) is unable to connect to the witness. The witness shows this error: Message
Database Mirroring login attempt failed with error: 'Connection handshake failed. The certificate used by the peer is invalid due to the following reason: Certificate not found. State 89.' Client x.x.x.x
I copied the original witness server cert over to both db2 primary/secondary servers. All 3 certs are on each server.
Not sure why this is happening. I am using SQL authentication. I can telnet to every port too. Microsoft Documentation of the witness server appears to suggest that you can use a single witness for multi pair mirroring, but doesn't tell you anything about how to do it.
Any help would be fantastic! (Using SQL Server 2014 Std on Windows 2012R2 x64 machines in AWS)
Viewing 11 posts - 16 through 25 (of 25 total)
You must be logged in to reply to this topic. Login to reply