Unable to mirror a database in mode sync full


I'm trying to mirror a database which is hosted by a SQL Server 2008 R2 on another SQL Server 2008 R2 which is not in a domain. The database is set in full mode and I'm trying to mirror it on this new server but it returns an error at the end.

I've backup the database on the source server as well as the logs and imported them on the new server in NO RECOVERY mode.

The connection between the servers seems to be just fine, there isn't any firewall between them but I still got this error message after the wizard ends and I don't understand why :

*Alter Failed for Database 'Test'. An exception occured while executing a Transact-SQL statement or batch. The network address TCP://" 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"

Any ideas ?
Kind Regards,

PS : There is no witness server. Is it mandatory to have one?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Daniel_PLDB Expert/ArchitectCommented:
Did you enable tcp/ip protocol in sql server configuration manager on both servers? Are remote connections enabled?
While connecting outside domain you need to use sql authentication with sql account so mixed authentication need to be enabled.
David_PazosAuthor Commented:
Hi Daniel_PL and thanks for your message.

Everything was set as you mentioned. Only the Named/Pipes is not activated on one of the servers and the VIA on both of them. Could that be the reason of my problem?

Kind Regards,
David_PazosAuthor Commented:
Hello again, I've activated the named Pipes, restarted the services and still the same problem...

any ideas are welcome )
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

Daniel_PLDB Expert/ArchitectCommented:
No, don't use named pipes. TCP/IP is best protocol for this.
You can't use GUI because of no integrated security, you need t-sql. Try this approach:

About mirroring:
David_PazosAuthor Commented:
Daniel_PL, thanks for your message.

I was a bit worried to try your solution, so I tried to create another SQL server in same VLAN, same domain, same sa account, and guess what, the error is the same.... Did I missed something? Is it mandatory to do that T-SQL security each time we want to do a mirroring sync???

Kind Regards,
Daniel_PLDB Expert/ArchitectCommented:
I've just went thru setting up database mirroring using this procedure: http://msdn.microsoft.com/en-us/library/ms191140.aspx
I've used 2 machines without domain (WinXP SP3 x86 and Windows 7 Professional x86). I used SQL Server 2008 Developer edition SP1.
I suggest you to check following:
TCP/IP is enabled
No firewalls are on (or ports are unblocked)
When creating users and certificates using article do it in master database
Assure whether database is restored on mirror with no_recovery
Assure whether at least one tlog backup is restored on mirror with no_recovery
Assure all log backups taken after full backup are restored on mirror with no_recovery
Check whther instances are using Local System account instead of Network Service

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
David_PazosAuthor Commented:
Hi Daniel_PL and thanks for your support. I think our problem is really special. I guess that all the problem becomes from our log backup. It might be corrupted or wrong and it makes all that problems with the connection. So, I'll try to find a way to rebuild the logs.

At least, your procedure to do it is really clear and I give you the points for sure.

Thanks again for your help.

Kind Regards,
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2008

From novice to tech pro — start learning today.