An error occurred in a SQL Server Service Broker/Database Mirroring transport connection endpoint (9642) – How to Resolve

Hi friends, in this article, we will be discussing about how to troubleshoot the following error message: “Event ID: 9642. An error occurred in a SQL Server Service Broker/Database Mirroring transport connection endpoint.“.

 

About the Service Broker/Database Mirroring transport connection endpoint error

We can see from the error message, that it refers to a Service Broker/Database Mirroring endpoint connection error. To this end, the first that comes in mind, is that this is something that might have to do with Service Broker or Database Mirroring (i.e. Always On Availability Groups replication) in SQL Server.

However, note that, the specific error message talks about an error in establishing a connection to a specific endpoint. This of course, does not necessarily mean that there’s something wrong with the configuration of Service Broker or Availability Groups replication on the SQL Server instance, but it might be something else.

 

How to Troubleshoot the Error

The first thing to do, towards troubleshooting the error, is to first make sure that indeed the configuration of Service Broker or Availability Groups deployments (if applicable) is OK without any issues.

If the above health check is successful, then a possible scenario for getting these error messages, is that a network/vulnerability scanner is attempting to connect to the ports that are defined in a Service Broker or Database Mirroring (i.e. Availability Groups) configuration on the SQL Server instance. Since these connection requests are not valid network traffic, this causes errors to be generated regarding these endpoints.

To this end, in such case, you should contact the Information Security Team, to confirm that the errors, are indeed generated due to a vulnerability scanning activity that tries to connect to the specific endpoints.

 

Extra Knowledge Tip – Finding Info about the Endpoints

In order to check if and which endpoints you have configured in your SQL Server instance, you can run the following T-SQL statements.

 

Retrieving Service Broker Endpoint Info

You can easily retrieve Service Broker Endpoint info with the below T-SQL statement:

SELECT * FROM sys.database_mirroring_endpoints;
GO

 

Retrieving Database Mirroring Endpoint Info

You can retrieve Database Mirroring Endpoint info with the below T-SQL statement:

SELECT * FROM sys.database_mirroring_endpoints;
GO

 

Retrieving TCP Endpoint Info

You can retrieve TCP Endpoint info with the below T-SQL statement:

SELECT * FROM sys.tcp_endpoints;
GO

 

 

 

---

Strengthen your SQL Server Administration Skills – Enroll to our Online Course!

Check our online course on Udemy titled “Essential SQL Server Administration Tips”
(special limited-time discount included in link).

Via the course, you will learn essential hands-on SQL Server Administration tips on SQL Server maintenance, security, performance, integration, error handling and more. Many live demonstrations and downloadable resources included!

Learn More

---

 

Featured Online Courses:

• AI Essentials: A Beginner’s Guide to Artificial Intelligence
• SQL Server 2022: What’s New – New and Enhanced Features 
• Introduction to Azure Database for MySQL
• Working with Python on Windows and SQL Server Databases
• Boost SQL Server Database Performance with In-Memory OLTP
• Introduction to Azure SQL Database for Beginners
• Essential SQL Server Administration Tips
• SQL Server Fundamentals – SQL Database for Beginners
• Essential SQL Server Development Tips for SQL Developers
• Introduction to Computer Programming for Beginners
• .NET Programming for Beginners – Windows Forms with C#
• SQL Server 2019: What’s New – New and Enhanced Features
• Entity Framework: Getting Started – Complete Beginners Guide
• A Guide on How to Start and Monetize a Successful Blog
• Data Management for Beginners – Main Principles

 

Read Also:

• How to Give Same Permission to Multiple Users in SQL Server using T-SQL
• Troubleshooting the File Activation Error in SQL Server
• Rule “Setup account privileges” failed – How to Resolve
• SQL Server error 18456: Login failed for user <username> – How to Resolve
• An object or column name is missing or empty
• Operating System Error 170 (Requested Resource is in use)
• There is no SQL Server Failover Cluster Available to Join
• Installing SQL Server 2016 on Windows Server 2012 R2: Rule KB2919355 failed
• Setup failed to start on the remote machine. Check the Task scheduler event log on the remote machine.
• A connection was successfully established with the server, but then an error occurred during the login process.
• SQL Server 2008 R2 Service Pack Installation Fails – Element not found. (Exception from HRESULT: 0x80070490)
• Could not load file or assembly ‘Microsoft.SqlServer.Smo, Version=10.0.0.0, …
• Fix: VS Shell Installation has Failed with Exit Code 1638
• Issue Adding Node to a SQL Server Failover Cluster – Greyed Out Service Account – How to Resolve
• initerrlog: could not open error log file. Operating system error=3 … – How to Resolve It
• Resolve SQL Server CTE Error – Incorrect syntax near ‘)’.
• There is insufficient system memory in resource pool ‘internal’ to run this query.
• How to Resolve: Bulk load data conversion error (type mismatch or invalid character for the specified codepage)…
• Resolving the Error Message: Rule “KB2919355 Installation” failed
• Error converting varchar to numeric in SQL Server
• Error converting data type varchar to float

 

Subscribe to our newsletter and stay up to date!

Subscribe to our YouTube channel (SQLNetHub TV)

Easily generate snippets with Snippets Generator!

Secure your databases using DBA Security Advisor!

Generate dynamic T-SQL scripts with Dynamic SQL Generator!

Check our latest software releases!

Check our eBooks!

 

Rate this article: (1 votes, average: 5.00 out of 5)

Loading...

Reference: SQLNetHub.com (https://www.sqlnethub.com)

© SQLNetHub