Database mirroring errors typically occur at two main points: during setup and at runtime. This section covers each of these separately.
You may get the following error while setting up database mirroring:
2006-08-20 17:53:16.630 spid15s Database mirroring connection error 4'An error occurred while receiving data: '64(The specified network name is no longer available.)'.' for 'TCP://yourMirrorServer:5023'. 2006-08-20 17:55:13.710 spid15s Error: 1443, Severity: 16, State: 2.
It may be that the firewall on the mirror server or the principal server is blocking the connection on the specified port. Check whether the firewall is blocking that communication port.
Similarly, you may get the following error while setting up database mirroring on the principal server:
Msg 1412, Level 16, State 0, Line 1 The remote copy of database "AdventureWorks2008" has not been rolled forward to a point in time that is encompassed in the local copy of the database log.
This indicates that the database on the mirror server is not rolled forward enough to establish the mirroring session. You may have backed up some transaction logs while backing up and restoring the database, so you have to restore these transaction logs to the mirror server with the NORECOVERY option to synchronize the mirror with the principal. See the RestoreLogOnMirror.sql script for an example.
Make sure that the SQL Server service accounts on each server ...