Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
tfountain
Constraint Violating Yak Guru
491 Posts |
 Posted - 2008-04-18 : 13:43:55
|
| What considerations do I need to take into account if trying to enlist a server into a master server when (a) both instances are on different physical servers and the SQL Server and SQL Server Agent services run under different domain accounts?The reason I ask is when attempting to create a master server through the SSMS wizard, I receive these errors:[CODE]Enlist TSX Progress- Create MSXOperator (Success) * Checking for an existing MSXOperator. * Updating existing MSXOperator. * Successfully updated MSXOperator.- Make sure the Agent service for 'MYMSX\INSTANCE' is running (Error) Messages * An exception occurred in SMO while trying to manage a service. (Microsoft.SqlServer.Smo) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&LinkId=20476 ------------------------------ ADDITIONAL INFORMATION: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) (mscorlib) - Ensure the agent startup account for 'MYTSX\INSTANCE' has rights to login as a target server (Error) * Checking to see if the starup account for 'MYTSX\INSTANCE' already exists. Messages * An exception occurred in SMO while trying to manage a service. (Microsoft.SqlServer.Smo) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&LinkId=20476 ------------------------------ ADDITIONAL INFORMATION: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) (mscorlib)- Enlist 'MYTSX\INSTANCE' into 'MYMSX\INSTANCE' (Error) * Enlisting target server 'MYTSX\INSTANCE' with master server 'MYMSX\INSTANCE'. * Using new enlistment method. Messages * MSX enlist failed for JobServer 'MYTSX\INSTANCE'. (Microsoft.SqlServer.Smo) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&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 'MYMSX\INSTANCE'.) (Microsoft SQL Server, Error: 22026) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3042&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476[/CODE]Now, the first two errors are what are puzzling me. I'm certain I can address the third and last error by making the accounts the SQL Server Agent services run as the necessary SQL permissions on each instance.I've tried making NT Authority\SYSTEM accounts on both servers, no luck. Any suggestions? |
|
|
tfountain
Constraint Violating Yak Guru
491 Posts |
Posted - 2008-04-18 : 14:53:10
|
Ok, I used T-SQL to do the enlistment on the target server:EXEC msdb.dbo.sp_msx_enlist N'MYMSX\INSTANCE' Once I added the domain account the SQL Agent runs under (on the MYTSX\INSTANCE server) to the MYMSX\INSTANCE and made it a sysadmin, that system procedure worked just fine (but the first two steps still failed through the wizard... go figure). I have verified that the jobs are all running on the target as needed. |
 |
|
|
triach
Starting Member
2 Posts |
Posted - 2009-05-19 : 11:52:48
|
| So did you ever fix this issue as i just recently had it and can tell you how to fix it in about 2 minutes - let me know if you still need the info. |
|
|
|
mialvarez2k
Starting Member
1 Post |
Posted - 2009-06-05 : 03:54:28
|
| I have that problem... can you tell me how you fix it? |
|
|
|
|
|
|
Assistance setting up master job server