Multi server administration broken in SQL Server 2005

Hello,
When I try to setup multiserver administration for SQL Server I
always get the error 'The enlist operation failed (reason:
SQLServerAgent Error: Unable to connect to MSX 'my master server name')
(Microsoft SQL Server, Error 22026). I have a fresh installation of the
two instances (the one who must become the master and the one who must
become target. The sql service and sql server agent accounts are a
domain accounts (both servers sit in the same domain) and have full
administrative rights. I have enabled the tcp and named pipes network
library on both sql servers and applied SP1 on both servers.
Frankly I have tried to get this working from the first CTP until now
and never succeed, either I'm doing something wrong our multiserver
administration does not work at all on Sql server 2005.
Has someone managed to get this working on SQL Server 2005 and if so
how did he get it to work.
To be honest this is the third time I ask this question on this
newsgroup but I have never had a reply with a solution, so I'm tempted
to thing that this is broken on SQL Server 2005. If so I have to start
telling my students that this is one thing which does not work (unless
at least someone reports that it is working for him.
Thx.
Marc Mertensconfiguration for tsx/msx is set (by default) to only allow certified
servers. Google search on "msx2005" and /or security. There is a registry
entry you need to change to allow servers w/o certificates in msx/tsx
configuration.
"Marc Mertens" wrote:

> Hello,
> When I try to setup multiserver administration for SQL Server I
> always get the error 'The enlist operation failed (reason:
> SQLServerAgent Error: Unable to connect to MSX 'my master server name')
> (Microsoft SQL Server, Error 22026). I have a fresh installation of the
> two instances (the one who must become the master and the one who must
> become target. The sql service and sql server agent accounts are a
> domain accounts (both servers sit in the same domain) and have full
> administrative rights. I have enabled the tcp and named pipes network
> library on both sql servers and applied SP1 on both servers.
> Frankly I have tried to get this working from the first CTP until now
> and never succeed, either I'm doing something wrong our multiserver
> administration does not work at all on Sql server 2005.
> Has someone managed to get this working on SQL Server 2005 and if so
> how did he get it to work.
> To be honest this is the third time I ask this question on this
> newsgroup but I have never had a reply with a solution, so I'm tempted
> to thing that this is broken on SQL Server 2005. If so I have to start
> telling my students that this is one thing which does not work (unless
> at least someone reports that it is working for him.
> Thx.
> Marc Mertens
>

MSX/TSX question between SQL 2000 and 2005

Hi,
I have a SQL Server 2005 as a master server, I want to make a SQL Server
2000 default instance a target server, but it failed and the error message i
s
'The master server version 9.00.2047 is not compatible with the target serve
r
version 8.00.818'. Can we have a SQL 2000 server as a target server when we
have a SQL 2005 as a master server? If so, how?
Thanks for your help.So far i have not seen any documentation on mingling 2k and 2k5 MSX and
TSX services. I believe you would have to have both instances running
on the MSX server and have 2 complete MSX db's running.
Hong Wang wrote:
> Hi,
> I have a SQL Server 2005 as a master server, I want to make a SQL Server
> 2000 default instance a target server, but it failed and the error message
is
> 'The master server version 9.00.2047 is not compatible with the target ser
ver
> version 8.00.818'. Can we have a SQL 2000 server as a target server when w
e
> have a SQL 2005 as a master server? If so, how?
> Thanks for your help.

MSX/TSX question between SQL 2000 and 2005

Hi,
I have a SQL Server 2005 as a master server, I want to make a SQL Server
2000 default instance a target server, but it failed and the error message is
'The master server version 9.00.2047 is not compatible with the target server
version 8.00.818'. Can we have a SQL 2000 server as a target server when we
have a SQL 2005 as a master server? If so, how?
Thanks for your help.So far i have not seen any documentation on mingling 2k and 2k5 MSX and
TSX services. I believe you would have to have both instances running
on the MSX server and have 2 complete MSX db's running.
Hong Wang wrote:
> Hi,
> I have a SQL Server 2005 as a master server, I want to make a SQL Server
> 2000 default instance a target server, but it failed and the error message is
> 'The master server version 9.00.2047 is not compatible with the target server
> version 8.00.818'. Can we have a SQL 2000 server as a target server when we
> have a SQL 2005 as a master server? If so, how?
> Thanks for your help.

MSSQLServerADHelper

MSSQLServerADHelper failed to start with error code
1073741724 on the initial error message box. When going
into event viewer the error code for the failed service
is 3221225572.
I have tried restarting the service and restarting the
server but it still fails, I have also tried starting the
service with the Admin account.
Any advice would be much appreciated.
ThanksHello,
Theres something it doesn't like about the account. See
http://support.microsoft.com/default.aspx?scid=kb;en-
us;273499.
Try deleing then recreating it.
>--Original Message--
>MSSQLServerADHelper failed to start with error code
>1073741724 on the initial error message box. When going
>into event viewer the error code for the failed service
>is 3221225572.
>I have tried restarting the service and restarting the
>server but it still fails, I have also tried starting the
>service with the Admin account.
>Any advice would be much appreciated.
>Thanks
>.
>

MSSQLSERVER 2005 service failed to start only on Windows startup

MSSQLServer service will not start when I startup Windows Server 2003
Std, but when I start the service manually, it works.
Here is the event (ID: 7000, Source: Service Control Manager) recorded:
The SQL Server (MSSQLSERVER) service failed to start due to the
following error:
%%6057960
I don't see anything in the SQL Server Logs for the initial attempt to
startup. Anyone have any ideas? I had set the service's Recovery for
First Failure to "Restart the Service" with "Reset Service after" set
to 5 minutes, but it hasn't worked.
Any ideas?Hi
I have not seen your error, it seems like the error message is not well
formed!
Has the server been starting ok previously?
Have you installed any patches/updates since it was last re-started?
If you change the service account does it start?
Are any other services failing to start?
John
"ccjjharmon@.gmail.com" wrote:
> MSSQLServer service will not start when I startup Windows Server 2003
> Std, but when I start the service manually, it works.
> Here is the event (ID: 7000, Source: Service Control Manager) recorded:
> The SQL Server (MSSQLSERVER) service failed to start due to the
> following error:
> %%6057960
>
> I don't see anything in the SQL Server Logs for the initial attempt to
> startup. Anyone have any ideas? I had set the service's Recovery for
> First Failure to "Restart the Service" with "Reset Service after" set
> to 5 minutes, but it hasn't worked.
> Any ideas?
>|||John,
I was wondering if the message was complete or not too...
It is a relatively new server (few months old) - but it has been
happening really since we installed yet... I am not sure if it ever
started up as a service on reboot.
No patches/updates since last restart (but Windows Update has them
downloaded - they just haven't been installed yet).
I haven't tried changing the service account... but didn't think to
because it starts when I manually start it - just not when all services
normally startup automatically.
SQLServerAgent also doesn't start - but all other services set to
Automatic startup go fine.|||I also checked to make sure the recent event mirrored the same text as
previous events and it does ... BUT the same error was only recorded
two other times (twice on 4/7). Before then, this event was instead
recorded (but I believe SQL Server still wasn't started as a service
automatically):
The SQL Server Integration Services service failed to start due to the
following error:
Waiting for a process to open the other end of the pipe.
Hope this info helps...
Chris|||Hi
Have you tried installing SP1? Otherwise you may have to log a call with PSS.
John
"ccjjharmon@.gmail.com" wrote:
> I also checked to make sure the recent event mirrored the same text as
> previous events and it does ... BUT the same error was only recorded
> two other times (twice on 4/7). Before then, this event was instead
> recorded (but I believe SQL Server still wasn't started as a service
> automatically):
> The SQL Server Integration Services service failed to start due to the
> following error:
> Waiting for a process to open the other end of the pipe.
> Hope this info helps...
> Chris
>

MSSQLSERVER 2005 service failed to start only on Windows startup

MSSQLServer service will not start when I startup Windows Server 2003
Std, but when I start the service manually, it works.
Here is the event (ID: 7000, Source: Service Control Manager) recorded:
The SQL Server (MSSQLSERVER) service failed to start due to the
following error:
%%6057960
I don't see anything in the SQL Server Logs for the initial attempt to
startup. Anyone have any ideas? I had set the service's Recovery for
First Failure to "Restart the Service" with "Reset Service after" set
to 5 minutes, but it hasn't worked.
Any ideas?Hi
I have not seen your error, it seems like the error message is not well
formed!
Has the server been starting ok previously?
Have you installed any patches/updates since it was last re-started?
If you change the service account does it start?
Are any other services failing to start?
John
"ccjjharmon@.gmail.com" wrote:

> MSSQLServer service will not start when I startup Windows Server 2003
> Std, but when I start the service manually, it works.
> Here is the event (ID: 7000, Source: Service Control Manager) recorded:
> The SQL Server (MSSQLSERVER) service failed to start due to the
> following error:
> %%6057960
>
> I don't see anything in the SQL Server Logs for the initial attempt to
> startup. Anyone have any ideas? I had set the service's Recovery for
> First Failure to "Restart the Service" with "Reset Service after" set
> to 5 minutes, but it hasn't worked.
> Any ideas?
>|||John,
I was wondering if the message was complete or not too...
It is a relatively new server (few months old) - but it has been
happening really since we installed yet... I am not sure if it ever
started up as a service on reboot.
No patches/updates since last restart (but Windows Update has them
downloaded - they just haven't been installed yet).
I haven't tried changing the service account... but didn't think to
because it starts when I manually start it - just not when all services
normally startup automatically.
SQLServerAgent also doesn't start - but all other services set to
Automatic startup go fine.|||I also checked to make sure the recent event mirrored the same text as
previous events and it does ... BUT the same error was only recorded
two other times (twice on 4/7). Before then, this event was instead
recorded (but I believe SQL Server still wasn't started as a service
automatically):
The SQL Server Integration Services service failed to start due to the
following error:
Waiting for a process to open the other end of the pipe.
Hope this info helps...
Chris