August 2, 2007 at 7:40 am
Hi all,
i have a problem with MS SQL Server 2005...
i want to do a database mirroring (replication)...
i have 3 computers:
principal - WinServer 2003 R2 EE SP2
mirror - WinServer 2003 R2 EE SP2
witness - WinXP Pro SP2
When i will start mirroring with witness, i get always the same error:
Microsoft SQL Server Management Studio>
Alter failed for Database '...'. (Microsoft.SqlServer.Smo)
Additional information:
-> An exception occured while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
-> The ALTER DATABASE command could not be sent to the remote server instance
'TCP://PCname+Domain:5022'. The database mirroring configuration was not changed.
Verify that the server is connected, and try again. (Microsoft SQL Server, Error:
1456)
i try to ping, telnet each computer, and it works, but mirroring... 🙁
Could someone help me please?
Regards,
Martin
August 3, 2007 at 3:33 am
please check the server network addressses of principal, mirror and witness servers and configure security settings in Mirroring.
August 3, 2007 at 5:28 am
I checked these informations a few times, and i didn't see my problem...
Now, i checked the configure security once again and i saw that the endpoint of my witness was different from the others, so i drop the endpoint on witness and create a new one, with the same name as the others... and it works!!!!!!!
Very good!!!
Thanks...
Simple problem... 🙂
June 3, 2009 at 1:39 am
i tried giving same name to all endpoints(principal,mirror and witness)..
bt still not working..:crying:
Any help!!!
June 15, 2009 at 10:29 am
-SQL Server 2008 SE. on Win XP SP3.-
I am getting the same error with configuring the witness for automatic failover.
i recently noticed that my SQL Server Agent is running on LOCAL SYSTEM instead of NETWORK SERVICE, but when i try to change the status the service give me this 'TIME OUT' error.
Does anyone knows how can i run the service and if i need it to solve the witness problem?
thanks.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply