SQL2005镜像故障处理
2009-02-10 14:39
357 查看
SSB – Connection handshake failed
The following shows you some kinds of SSB exception when enabling Transport Security and Dialog Security in the cross-server Service Broker conversation.
1. Connection handshake failed. The certificate used by the peer is invalid due to the following reason: Certificate not found.
HINT: Usually this error is related to the EndPoint authentication, so the problem is from the certificates in MASTER DBs in two SQL SERVER instances. Please make sure that the right certificates are deployed and referenced. Look into master.sys.certificates in two respectively SQL SERVERS and validate the certificate cert_serial_number or thumbprint matches between two instances.
2. Connection handshake failed. The certificate used by the peer is invalid due to the following reason: The database principal has no mapping to a server principal..
HINT: You are using certificates for adjacent transport security. The certificate used by the peer belongs to a user in master DB who is not mapped to a login. This could happen for the following cases:
(1) You created a user in master without login.
(2) You created a user in master with login, but later dropped that login, thus orphaning that user.
The fix would be to create a SQL login, then create a user in master for this login and alter authorization of the peer’s certificate to be owned by this user. Next grant connection permission on the service broker endpoint to the newly created login.
You can refer to the following SQL SCRIPT for help.
-- Create a new login & user in the MASTER system database
Create Login Demo_Login
With password=’YOURPASSWORD’
GO
Create User Demo_User
For Login Demo_Login
GO
-- Give authorization permissions
Create Certificate YOURCERTIFICATENAME
Authorization Demo_User
From File=’THE PEERS CERTIFICATE FILE’
GO
-- Grant CONNECT permissions to the associated endpoint
Grant Connect on EndPoint::DB_ENDPOINT to Demo_Login
GO
The following shows you some kinds of SSB exception when enabling Transport Security and Dialog Security in the cross-server Service Broker conversation.
1. Connection handshake failed. The certificate used by the peer is invalid due to the following reason: Certificate not found.
HINT: Usually this error is related to the EndPoint authentication, so the problem is from the certificates in MASTER DBs in two SQL SERVER instances. Please make sure that the right certificates are deployed and referenced. Look into master.sys.certificates in two respectively SQL SERVERS and validate the certificate cert_serial_number or thumbprint matches between two instances.
2. Connection handshake failed. The certificate used by the peer is invalid due to the following reason: The database principal has no mapping to a server principal..
HINT: You are using certificates for adjacent transport security. The certificate used by the peer belongs to a user in master DB who is not mapped to a login. This could happen for the following cases:
(1) You created a user in master without login.
(2) You created a user in master with login, but later dropped that login, thus orphaning that user.
The fix would be to create a SQL login, then create a user in master for this login and alter authorization of the peer’s certificate to be owned by this user. Next grant connection permission on the service broker endpoint to the newly created login.
You can refer to the following SQL SCRIPT for help.
-- Create a new login & user in the MASTER system database
Create Login Demo_Login
With password=’YOURPASSWORD’
GO
Create User Demo_User
For Login Demo_Login
GO
-- Give authorization permissions
Create Certificate YOURCERTIFICATENAME
Authorization Demo_User
From File=’THE PEERS CERTIFICATE FILE’
GO
-- Grant CONNECT permissions to the associated endpoint
Grant Connect on EndPoint::DB_ENDPOINT to Demo_Login
GO
相关文章推荐
- SQL 2005 xml 处理的一些sample
- SQl 2008/2005 镜像
- sql 2005 数据库镜像
- SQL 2005 Report Server 请求因 HTTP 状态 400 失败: Bad Request 处理方法 的解决方法
- 无法在SQL 2005系统数据库中执行的T-SQL语句(XML处理)
- Microsoft SQL Server 2005 安装失败处理
- windows xp sp3 安装Sql 2005失败处理
- SQL 2005 数据库镜像
- 利用SQL 2005 CTE处理树型数据
- Microsoft SQL Server 2005 故障转移群集配置Troubleshooting篇(安装排错)
- 无法在SQL 2005系统数据库中执行的T-SQL语句(XML处理)
- webpart中访问SQL 2005 Express数据库问题的处理办法
- Sqlserver 2005 配置 数据库镜像:手工故障转移(即手工切换 镜像数据库 为 主数据库)
- 无法在SQL 2005系统数据库中执行的T-SQL语句(XML处理)
- SQL 2005 Errolog过大处理方法
- (笔记)《SQL 2005 技术内幕 T-SQL查询》第一章 逻辑查询处理
- 无法在SQL 2005系统数据库中执行的T-SQL语句(XML处理)
- MS SqlServer 2005 分页处理
- Inside Microsoft SQL Server 2005:T-SQL Querying (查询处理的数据流程|第二章)
- sql 2005 循环处理数据