We have a server with the default instance and 2 additional named instances running SQL 2000 SP4. Recently I installed another instance for SQL Server 2005. We also use MSX/TSX approach to manage the servers so I tried to enlist the SQL 2005 instance with the master server using the
msdb..sp_msx_enlist @.msx_server_name = N'SQLMON', @.location = N'Datacentre. Margin Lending overnight copy'
and got this error,
Msg 22026, Level 16, State 1, Line 0
The enlist operation failed (reason: SQLServerAgent Error: Unable to connect to MSX 'SQLMON'.)
Looking at the text for this procedure it looks like it reads the wrong registry keys. The procedure it hardcoded to read,
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\SQLServerAgent
This key doesn't exist, but this one does,
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\SQLServerAgent
Is this causing the connection error? I know that the MSX server is available as I can connect and query it in Management Studio.
http://msdn2.microsoft.com/en-us/library/ms365379.aspx
Please take a look at the above link on what has changed in MSX/TSX on security lines.
Also, note that in a mixed(SQL 2K and 2005) multi-server environment MSX can be only SQL 2000. TSXs can be both SQL 2K and 2005
|||Thanks for your reply. I set the Encryption option to zero.and was able to make the SQL 2005 server a TSX.
When will the encryption option be selecteable in the TSX setup wizard?
|||Unfortunately no. We have a tracking bug for the next release to expose it at SMO and UI level
No comments:
Post a Comment