2005 Agent - MSX enlist failed

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Cgal - 23 Dec 2005 15:18 GMT

I have a server that is running two SQL Server 2005 instances. The MSSQL
and AGENT services for both instances are both running with a local domain
account on the server. When setting up one instance as a master and the
target ("DBSVR2003\inst1") as the other instance on the server I get the
following message on the last step of the Master wizard:

MSX enlist failed for JobServer "DBSVR2003\inst1"

Additional Information:

An exception occurred wihile executing a Transact-SQL statement or
batch.
[Microsoft.SQLServer.ConnectionInfo]

The enlist operation failed9reason: SQLServerAgent Error: Una ble to
connect to MSX 'DBSVR2003'.0 (Microsoft SQL Server, Error: 22026)

"DBSVR2003" is the default instance on the server that I want to make the
master.

Any assistance that you can provide would be greatly appreciated.

Thanks!

Reply to this Message

Michael Cheng [MSFT] - 24 Dec 2005 07:07 GMT

Hi Cgal,

Have you created the Master Server before you create the Target Server?
Would you please let me know the detailed steps you are taking?

For more information about HOW-TO, check the list below

Creating a Multiserver Environment
http://msdn2.microsoft.com/library/ms191305.aspx

Please use T-SQL statement to create this multiserver environment directly,
we would trace to see which statement goes wrong.

Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!

Sincerely yours,

Michael Cheng
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================

Signature

This posting is provided "AS IS" with no warranties, and confers no rights.

Reply to this Message

Cgal - 26 Dec 2005 16:07 GMT

The instructions in the link you provided indicate that the the _msx_enlist
stored procedure should be used to add a master server with TSQL. The
master server that I wanted to add is on a machine named DBSVR2003 so I ran
the following command:

EXEC msdb.dbo.sp_msx_enlist N'DBSVR2003',
N'some location' ;

The result returns was:

Msg 14297, Level 16, State 1, Procedure sp_msx_enlist, Line 86
Cannot enlist into the local machine.

The other approach that I was using utilizes the master server wizard. When
I use the wizard the first three steps succeed but the last step fails. The
output from the report is as follows:

Enlist TSX Progress

- Create MSXOperator (Success)
Checking for an existing MSXOperator.
Updating existing MSXOperator.
Successfully updated MSXOperator.

- Make sure the Agent service for 'DBSVR2003' is running (Success)
The service 'SQLSERVERAGENT' is running.

- Ensure the agent startup account for 'DBSVR2003\inst1' has rights to login
as a target server (Success)
Checking to see if the starup account for 'DBSVR2003\inst1' already exists.
Login exists on server.
Checking to see if login has rights to msdb.
Login has rights to msdb.
Checking to see if user is a member of the TargetServersRole.
User is a member of the TargetServersRole.

- Enlist 'DBSVR2003\inst1' into 'DBSVR2003' (Error)
Enlisting target server 'DBSVR2003\inst1' with master server 'DBSVR2003'.
Using new enlistment method.

Messages
MSX enlist failed for JobServer 'DBSVR2003\inst1'.
(Microsoft.SqlServer.Smo)

For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.0
0&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationEx
ceptionText&EvtID=MSX+enlist+JobServer&LinkId=20476

------------------------------
ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)

------------------------------

The enlist operation failed (reason: SQLServerAgent Error: Unable to connect
to MSX 'DBSVR2003'.) (Microsoft SQL Server, Error: 22026)

For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&
EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476

> Hi Cgal,
>
[quoted text clipped - 24 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.

Reply to this Message

Michael Cheng [MSFT] - 28 Dec 2005 09:42 GMT

Hi Cgal,

Thanks for your patience.

In the SQL Server Configuration Manager, please make sure TCP/IP and Named
pipes are enabled for master instance. Also, please manually add "NT
Authority/SYSTEM" account to master instance and assign it to sysadmin role

Sincerely yours,

Michael Cheng
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================

Signature

This posting is provided "AS IS" with no warranties, and confers no rights.

Reply to this Message

Cgal - 28 Dec 2005 16:06 GMT

Hi Michael,

Thanks for staying with me on this one.

I checked the TCP/IP and Named Pipes settings on the master instance and
target instance and they were both enabled. I also checked "NT
Authority/System" and it was a valid login on the master instance and was a
member of the sysadmin role.

I tried to add the master server again with TSQL and the wizard and both of
these approaches fail. The same error messages are displayed for each
method that I sent before.

Please let me know what we can try next.

Thanks!

> Hi Cgal,
>
[quoted text clipped - 15 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.

Reply to this Message

Michael Cheng [MSFT] - 29 Dec 2005 05:47 GMT

Hi Cgal,

You are welcome.

For now, to find out the root cause of this issue I am afriad we may need
to analyze SQL Server internal, this work has to be done by contacting
Microsoft Customer Service and Support. Therefore, we probably will not be
able to resolve the issue through the newsgroups. I recommend that you open
a Support incident with Microsoft Customer Service and Support so that a
dedicated Support Professional can assist with this case. If you need any
help in this regard, please let me know.

For a complete list of Microsoft Customer Service and Support phone
numbers, please go to the following address on the World Wide Web:
http://support.microsoft.com/directory/overview.asp

Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!

Sincerely yours,

Michael Cheng
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================

Signature

This posting is provided "AS IS" with no warranties, and confers no rights.

Reply to this Message

Cgal - 30 Dec 2005 20:56 GMT

Thanks again for your help.

I will open up an incident. Do you know whether the incident will be
counted against my MSDN quota if this turns out to be a bug?

Thanks!

Chris

> Hi Cgal,
>
[quoted text clipped - 27 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.

Reply to this Message

Michael Cheng [MSFT] - 03 Jan 2006 01:49 GMT

Hi Cgal,

Thanks so much for your understanding.

Yes, if this turned out to be a problem in the product, you will be
refunded.

Sincerely yours,

Michael Cheng
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================

Signature

This posting is provided "AS IS" with no warranties, and confers no rights.

Reply to this Message