Apart from the obvious firewall and network communication issues that could occur between the two SQL Server instances that are configured in the mirroring and while also ensuring that domain service accounts are being used for the SQL Server instances, this error can also be caused by NOT restoring the database on the target/mirror SQL Server instance using the "NO RECOVERY" option and leaving that database in a restoring mode if you like.
Very confusing indeed, because the error refers to network communication failing and instead it just means that the SQL Server mirroring guidelines were not followed accordingly.
GET QUOTE
No comments:
Post a Comment