Solved

Database mirroring connection error 4

Posted on 2013-05-16
3
2,051 Views
Last Modified: 2013-05-22
I'm getting these error message every other week or so!  The mirror is configured on Windows Server 2008 R2 Enterprise edition with Active/Active Cluster setting!

Error Msg: Database mirroring connection error 4 'An error occurred while receiving data: '121(The semaphore timeout period has expired.)'.' for 'TCP://Servername:5022'.

Screenshot provided
0
Comment
Question by:angel7170
  • 2
3 Comments
 
LVL 16

Expert Comment

by:Surendra Nath
ID: 39172202
The SQL Server Installation Wizard provides a single feature tree for upgrade of SQL Server components.
You can also install SQL Server 2008 R2 side by side with an earlier version, or migrate existing databases and configuration settings from an earlier SQL Server version, and apply them to an instance of SQL Server 2008 R2.
0
 

Accepted Solution

by:
angel7170 earned 0 total points
ID: 39175455
Since principal server keep on sending logs to mirror server every 60 sec, for each interval if transaction doesn't get committed to mirror server completely then the witness starting sending error stating Mirror Session are not syncing.  Basically, it was network latency issue with the witness server.
0
 

Author Closing Comment

by:angel7170
ID: 39186877
When network bandwidth got better data start syncing again...and everything was back to normal!
0

Featured Post

Simplifying Server Workload Migrations

This use case outlines the migration challenges that organizations face and how the Acronis AnyData Engine supports physical-to-physical (P2P), physical-to-virtual (P2V), virtual to physical (V2P), and cross-virtual (V2V) migration scenarios to address these challenges.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

International Data Corporation (IDC) prognosticates that before the current the year gets over disbursing on IT framework products to be sent in cloud environs will be $37.1B.
Ever needed a SQL 2008 Database replicated/mirrored/log shipped on another server but you can't take the downtime inflicted by initial snapshot or disconnect while T-logs are restored or mirror applied? You can use SQL Server Initialize from Backup…
Via a live example, show how to backup a database, simulate a failure backup the tail of the database transaction log and perform the restore.
Via a live example, show how to set up a backup for SQL Server using a Maintenance Plan and how to schedule the job into SQL Server Agent.

756 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question