Mario,
there is a fix available, but you'll need to contact PSS to get hold of it:
http://support.microsoft.com/default...EN-US;CNTACTMS
Regards,
Paul Ibison
Is it free ?
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23m5nFqbPEHA.2256@.TK2MSFTNGP10.phx.gbl...
> Mario,
> there is a fix available, but you'll need to contact PSS to get hold of
it:
> http://support.microsoft.com/default...EN-US;CNTACTMS
> Regards,
> Paul Ibison
>
|||I haven't requested any fixes, but my colleague regularly receives Win 2003
fixes for free and she's never once had to pay. If you ring up MS there's no
obligation so you might as well just give them a call. If you call them,
please could you post back to let us know for sure.
Regards,
Paul Ibison
|||I am not sure what fix we are referring ot but if it is a post sp3a fix it
might be included in build 818. MS03-031 Security Bulletin. If it is a
build prior to build 818 you can downlad the MS03-031 and get the fix there.
http://www.microsoft.com/downloads/d...e9d-bd44-40c5-
add3-b8c99618e68d&DisplayLang=en
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||It's a post 818.
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:tgkUwmnPEHA.3664@.cpmsftngxa10.phx.gbl...
> I am not sure what fix we are referring ot but if it is a post sp3a fix it
> might be included in build 818. MS03-031 Security Bulletin. If it is a
> build prior to build 818 you can downlad the MS03-031 and get the fix
there.
>
http://www.microsoft.com/downloads/d...e9d-bd44-40c5-
> add3-b8c99618e68d&DisplayLang=en
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>
Showing posts with label agent. Show all posts
Showing posts with label agent. Show all posts
Thursday, March 22, 2012
Sunday, March 11, 2012
2k Replication errs .... Error 2812
Hey,
Having some probs w replication between 2 2k srvs running sql2k.
The dist agent is experiencing errors........
"Could not find stored procedure 'sp_MSins_tester'
Error number: 2812
Initially it gave an error of 18452 on dist agent of Could not connect.
I updated the id/pw for the subscriber and that went away and generated the above.
Any thoughts on what I should try next?
--mattHi Matt ,
from what I have experienced (both errors) you will have to create a stored procedure for you dist agent , that you should solve the problem.you might want to check sql books online there is more info there.
Hope this helps in some way..
Regards
Burner|||What did you end up doing to get by this problem ?|||Which service pack do you have installed for sql server 2000 (on both sql servers) ?
Having some probs w replication between 2 2k srvs running sql2k.
The dist agent is experiencing errors........
"Could not find stored procedure 'sp_MSins_tester'
Error number: 2812
Initially it gave an error of 18452 on dist agent of Could not connect.
I updated the id/pw for the subscriber and that went away and generated the above.
Any thoughts on what I should try next?
--mattHi Matt ,
from what I have experienced (both errors) you will have to create a stored procedure for you dist agent , that you should solve the problem.you might want to check sql books online there is more info there.
Hope this helps in some way..
Regards
Burner|||What did you end up doing to get by this problem ?|||Which service pack do you have installed for sql server 2000 (on both sql servers) ?
Saturday, February 25, 2012
2005 SQL EXPRESS DATABASE BACKUP
I am using Veritas backup exec 10.d with sql agent. I am able to see the sql express studio 2005 database files but there is difference in file size between original database file and the one shows in sql agent backup selection. The backup performs 100% successful but the original database file size is different e.g( original file:350MB, backup file: 28MB)..
Any ideas...?
Thanks in advance..
Have you talked to the folks at Veritas/Symantec about this? They can probably give you better information about their software.
Regards,
Mike Wachal
SQL Express team
-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1
The SQL API that BE plugs into will only send extents that are currently allocated by the database, so if you have created a database with an initial size and not filled it, we'd expect this delta.
Beyond this, I'd check if compression is enabled.
Of course, the ultimate test of whether a backup is valid or not is to attempt to do a restore. This should be a periodic task for any backup setup.
Sunday, February 19, 2012
2005 Merge Agent Degradation
I have a merge agent running extremely slow - schedule fires every 1 minute,
however it takes 1 to 3 minutes to execute. Delivery Rate 5 rows/sec or less,
all 5 other merge agents execute in less than 20 seconds and Delivery Rate 80
rows/sec or greater.
Each time merge agent fires, subscr cpu spikes to 85% - normally 15 to 20%.
Ran profiler and discovered this stamement below hogging the cpu and having
the longest duration.
I am rebuilding the MSmerge_genhistory table nightly w/ the following: DBCC
DBREINDEX (MSmerge_genhistory, '', 80)
Any ideas? A re-init will resolve problem , have had to do this many times
in past - at least every 30 days... however, want to get to root cause. tia
Chris
select top (@.numgens) *
from
(
select generation, guidsrc, art_nick,
case when genstatus = 4 then 0 else genstatus end as
genstatus,
pubid, nicknames,
okaytoskip = case when
art_nick is not null and art_nick <> 0
and genstatus in (0,4)
-- Skip all rows that are for incomplete
generations for articles that have no joins.
and not exists (select 1 from
dbo.sysmergesubsetfilters where (join_nickname = art_nick or art_nickname =
art_nick) and (filter_type & 1) = 1)
then 1 else 0 end
, changecount
from
(select generation, guidsrc, art_nick, genstatus, pubid,
nicknames, changecount
from dbo.MSmerge_genhistory with (rowlock, repeatableread)
where generation >= @.genstart
and generation <= @.maxgen_to_enumerate
and generation > @.mingen_to_enumerate
and (art_nick = 0 or art_nick is NULL or
art_nick in (select nickname from dbo.sysmergearticles
where pubid = @.pubid))
) as generation_range
UNION ALL -- use UNION ALL instead of UNION for perf
reasons. Merge agent code will skip dupes. Will only have max 2 dupes.
select generation = @.next_possible_watermark, guidsrc =
@.next_possible_watermark_guidsrc,
art_nick = @.next_possible_watermark_art_nick, genstatus =
@.next_possible_watermark_genstatus,
pubid = @.next_possible_watermark_pubid, nicknames =
@.next_possible_watermark_nicknames,
okaytoskip = 0, changecount =
@.next_possible_watermark_changecount
where @.next_possible_watermark is not null
union all
select generation = @.min_open_gen, guidsrc= @.min_open_gen_guid,
art_nick=@.min_open_gen_art_nick, genstatus=0,
pubid=@.pubid, nicknames=NULL, okaytoskip = 0,
changecount=0
where @.min_open_gen is not null
) as genertions
order by generation ASC
Two things I can suggest here is:
1. Avoid metadata contention. Make sure merge agents do not run at the
same time so stagger their schedules.
2. Retention period can cause lots of data to be stored in the contets
and tombstone tables. Default i think is 14 days. So 14 days worth of
changes are stored. Consider reducing this if subscribers are not
offline for a long time.
Regards Jim
http://jims-spanakopita.blogspot.com/
|||What do your join filters look like? By placing indexes on all the filters
you will get better performance. Another option to try is to modify your
filters to make them as shallow as possible.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:4ED9E8B8-9CA1-4B10-A609-E67921202C68@.microsoft.com...
> I have a merge agent running extremely slow - schedule fires every 1
> minute,
> however it takes 1 to 3 minutes to execute. Delivery Rate 5 rows/sec or
> less,
> all 5 other merge agents execute in less than 20 seconds and Delivery Rate
> 80
> rows/sec or greater.
> Each time merge agent fires, subscr cpu spikes to 85% - normally 15 to
> 20%.
> Ran profiler and discovered this stamement below hogging the cpu and
> having
> the longest duration.
> I am rebuilding the MSmerge_genhistory table nightly w/ the following:
> DBCC
> DBREINDEX (MSmerge_genhistory, '', 80)
>
> Any ideas? A re-init will resolve problem , have had to do this many times
> in past - at least every 30 days... however, want to get to root cause.
> tia
> Chris
>
> select top (@.numgens) *
> from
> (
> select generation, guidsrc, art_nick,
> case when genstatus = 4 then 0 else genstatus end as
> genstatus,
> pubid, nicknames,
> okaytoskip = case when
> art_nick is not null and art_nick <> 0
> and genstatus in (0,4)
> -- Skip all rows that are for incomplete
> generations for articles that have no joins.
> and not exists (select 1 from
> dbo.sysmergesubsetfilters where (join_nickname = art_nick or art_nickname
> =
> art_nick) and (filter_type & 1) = 1)
> then 1 else 0 end
> , changecount
> from
> (select generation, guidsrc, art_nick, genstatus, pubid,
> nicknames, changecount
> from dbo.MSmerge_genhistory with (rowlock, repeatableread)
> where generation >= @.genstart
> and generation <= @.maxgen_to_enumerate
> and generation > @.mingen_to_enumerate
> and (art_nick = 0 or art_nick is NULL or
> art_nick in (select nickname from dbo.sysmergearticles
> where pubid = @.pubid))
> ) as generation_range
> UNION ALL -- use UNION ALL instead of UNION for perf
> reasons. Merge agent code will skip dupes. Will only have max 2 dupes.
> select generation = @.next_possible_watermark, guidsrc =
> @.next_possible_watermark_guidsrc,
> art_nick = @.next_possible_watermark_art_nick, genstatus =
> @.next_possible_watermark_genstatus,
> pubid = @.next_possible_watermark_pubid, nicknames =
> @.next_possible_watermark_nicknames,
> okaytoskip = 0, changecount =
> @.next_possible_watermark_changecount
> where @.next_possible_watermark is not null
> union all
> select generation = @.min_open_gen, guidsrc= @.min_open_gen_guid,
> art_nick=@.min_open_gen_art_nick, genstatus=0,
> pubid=@.pubid, nicknames=NULL, okaytoskip = 0,
> changecount=0
> where @.min_open_gen is not null
> ) as genertions
> order by generation ASC
>
however it takes 1 to 3 minutes to execute. Delivery Rate 5 rows/sec or less,
all 5 other merge agents execute in less than 20 seconds and Delivery Rate 80
rows/sec or greater.
Each time merge agent fires, subscr cpu spikes to 85% - normally 15 to 20%.
Ran profiler and discovered this stamement below hogging the cpu and having
the longest duration.
I am rebuilding the MSmerge_genhistory table nightly w/ the following: DBCC
DBREINDEX (MSmerge_genhistory, '', 80)
Any ideas? A re-init will resolve problem , have had to do this many times
in past - at least every 30 days... however, want to get to root cause. tia
Chris
select top (@.numgens) *
from
(
select generation, guidsrc, art_nick,
case when genstatus = 4 then 0 else genstatus end as
genstatus,
pubid, nicknames,
okaytoskip = case when
art_nick is not null and art_nick <> 0
and genstatus in (0,4)
-- Skip all rows that are for incomplete
generations for articles that have no joins.
and not exists (select 1 from
dbo.sysmergesubsetfilters where (join_nickname = art_nick or art_nickname =
art_nick) and (filter_type & 1) = 1)
then 1 else 0 end
, changecount
from
(select generation, guidsrc, art_nick, genstatus, pubid,
nicknames, changecount
from dbo.MSmerge_genhistory with (rowlock, repeatableread)
where generation >= @.genstart
and generation <= @.maxgen_to_enumerate
and generation > @.mingen_to_enumerate
and (art_nick = 0 or art_nick is NULL or
art_nick in (select nickname from dbo.sysmergearticles
where pubid = @.pubid))
) as generation_range
UNION ALL -- use UNION ALL instead of UNION for perf
reasons. Merge agent code will skip dupes. Will only have max 2 dupes.
select generation = @.next_possible_watermark, guidsrc =
@.next_possible_watermark_guidsrc,
art_nick = @.next_possible_watermark_art_nick, genstatus =
@.next_possible_watermark_genstatus,
pubid = @.next_possible_watermark_pubid, nicknames =
@.next_possible_watermark_nicknames,
okaytoskip = 0, changecount =
@.next_possible_watermark_changecount
where @.next_possible_watermark is not null
union all
select generation = @.min_open_gen, guidsrc= @.min_open_gen_guid,
art_nick=@.min_open_gen_art_nick, genstatus=0,
pubid=@.pubid, nicknames=NULL, okaytoskip = 0,
changecount=0
where @.min_open_gen is not null
) as genertions
order by generation ASC
Two things I can suggest here is:
1. Avoid metadata contention. Make sure merge agents do not run at the
same time so stagger their schedules.
2. Retention period can cause lots of data to be stored in the contets
and tombstone tables. Default i think is 14 days. So 14 days worth of
changes are stored. Consider reducing this if subscribers are not
offline for a long time.
Regards Jim
http://jims-spanakopita.blogspot.com/
|||What do your join filters look like? By placing indexes on all the filters
you will get better performance. Another option to try is to modify your
filters to make them as shallow as possible.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:4ED9E8B8-9CA1-4B10-A609-E67921202C68@.microsoft.com...
> I have a merge agent running extremely slow - schedule fires every 1
> minute,
> however it takes 1 to 3 minutes to execute. Delivery Rate 5 rows/sec or
> less,
> all 5 other merge agents execute in less than 20 seconds and Delivery Rate
> 80
> rows/sec or greater.
> Each time merge agent fires, subscr cpu spikes to 85% - normally 15 to
> 20%.
> Ran profiler and discovered this stamement below hogging the cpu and
> having
> the longest duration.
> I am rebuilding the MSmerge_genhistory table nightly w/ the following:
> DBCC
> DBREINDEX (MSmerge_genhistory, '', 80)
>
> Any ideas? A re-init will resolve problem , have had to do this many times
> in past - at least every 30 days... however, want to get to root cause.
> tia
> Chris
>
> select top (@.numgens) *
> from
> (
> select generation, guidsrc, art_nick,
> case when genstatus = 4 then 0 else genstatus end as
> genstatus,
> pubid, nicknames,
> okaytoskip = case when
> art_nick is not null and art_nick <> 0
> and genstatus in (0,4)
> -- Skip all rows that are for incomplete
> generations for articles that have no joins.
> and not exists (select 1 from
> dbo.sysmergesubsetfilters where (join_nickname = art_nick or art_nickname
> =
> art_nick) and (filter_type & 1) = 1)
> then 1 else 0 end
> , changecount
> from
> (select generation, guidsrc, art_nick, genstatus, pubid,
> nicknames, changecount
> from dbo.MSmerge_genhistory with (rowlock, repeatableread)
> where generation >= @.genstart
> and generation <= @.maxgen_to_enumerate
> and generation > @.mingen_to_enumerate
> and (art_nick = 0 or art_nick is NULL or
> art_nick in (select nickname from dbo.sysmergearticles
> where pubid = @.pubid))
> ) as generation_range
> UNION ALL -- use UNION ALL instead of UNION for perf
> reasons. Merge agent code will skip dupes. Will only have max 2 dupes.
> select generation = @.next_possible_watermark, guidsrc =
> @.next_possible_watermark_guidsrc,
> art_nick = @.next_possible_watermark_art_nick, genstatus =
> @.next_possible_watermark_genstatus,
> pubid = @.next_possible_watermark_pubid, nicknames =
> @.next_possible_watermark_nicknames,
> okaytoskip = 0, changecount =
> @.next_possible_watermark_changecount
> where @.next_possible_watermark is not null
> union all
> select generation = @.min_open_gen, guidsrc= @.min_open_gen_guid,
> art_nick=@.min_open_gen_art_nick, genstatus=0,
> pubid=@.pubid, nicknames=NULL, okaytoskip = 0,
> changecount=0
> where @.min_open_gen is not null
> ) as genertions
> order by generation ASC
>
Thursday, February 9, 2012
2005 Agent doesn't start automatically on reboot
We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
machine is rebooted, the SQL Server agent is not automatically started.
It is set to start automatically in the Windows Services dialog. I
see a safe shutdown prior to the reboot, but no messages like it's even
trying to start up. I can start it manually with no problems.
Any ideas what to check or where to go from here?Hi
Have you checked the sql server agent log file in Management studio? Also
check what SQL Server Configuration Manager has for the service and check
that error reporting is selected on the advanced tab.
John
"PSPDBA" wrote:
> We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> machine is rebooted, the SQL Server agent is not automatically started.
> It is set to start automatically in the Windows Services dialog. I
> see a safe shutdown prior to the reboot, but no messages like it's even
> trying to start up. I can start it manually with no problems.
> Any ideas what to check or where to go from here?
>|||Agent log shows:
Message
[241] Startup error: Unable to initialize error reporting system
(reason: The EventLog service has not been started)
However, The EventLog service is also set to automatic.
John Bell wrote:
> Hi
> Have you checked the sql server agent log file in Management studio? Also
> check what SQL Server Configuration Manager has for the service and check
> that error reporting is selected on the advanced tab.
> John
> "PSPDBA" wrote:
> > We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> > machine is rebooted, the SQL Server agent is not automatically started.
> > It is set to start automatically in the Windows Services dialog. I
> > see a safe shutdown prior to the reboot, but no messages like it's even
> > trying to start up. I can start it manually with no problems.
> >
> > Any ideas what to check or where to go from here?
> >
> >|||Hi
I assume that the EventLog has started correctly?
Making SQL Agent dependent on the EventLog service would ensure that it has
started before SQL Agent starts.
If the service is running as LOCALSYSTEM you could change it to an domain
account.
John
"PSPDBA" wrote:
> Agent log shows:
> Message
> [241] Startup error: Unable to initialize error reporting system
> (reason: The EventLog service has not been started)
> However, The EventLog service is also set to automatic.
> John Bell wrote:
> > Hi
> >
> > Have you checked the sql server agent log file in Management studio? Also
> > check what SQL Server Configuration Manager has for the service and check
> > that error reporting is selected on the advanced tab.
> >
> > John
> >
> > "PSPDBA" wrote:
> >
> > > We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> > > machine is rebooted, the SQL Server agent is not automatically started.
> > > It is set to start automatically in the Windows Services dialog. I
> > > see a safe shutdown prior to the reboot, but no messages like it's even
> > > trying to start up. I can start it manually with no problems.
> > >
> > > Any ideas what to check or where to go from here?
> > >
> > >
>|||Yep, it sure has. I was thinking of doing both of those things. I'll
give it a try.
John Bell wrote:
> Hi
> I assume that the EventLog has started correctly?
> Making SQL Agent dependent on the EventLog service would ensure that it has
> started before SQL Agent starts.
> If the service is running as LOCALSYSTEM you could change it to an domain
> account.
> John
> "PSPDBA" wrote:
> > Agent log shows:
> >
> > Message
> > [241] Startup error: Unable to initialize error reporting system
> > (reason: The EventLog service has not been started)
> >
> > However, The EventLog service is also set to automatic.
> >
> > John Bell wrote:
> > > Hi
> > >
> > > Have you checked the sql server agent log file in Management studio? Also
> > > check what SQL Server Configuration Manager has for the service and check
> > > that error reporting is selected on the advanced tab.
> > >
> > > John
> > >
> > > "PSPDBA" wrote:
> > >
> > > > We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> > > > machine is rebooted, the SQL Server agent is not automatically started.
> > > > It is set to start automatically in the Windows Services dialog. I
> > > > see a safe shutdown prior to the reboot, but no messages like it's even
> > > > trying to start up. I can start it manually with no problems.
> > > >
> > > > Any ideas what to check or where to go from here?
> > > >
> > > >
> >
> >|||Hi
You didn't say if the service was running under local system or not'
Looking at other posts http://tinyurl.com/rvql2 the service account seems to
be a prime reason for this failure. To change this manually check out
http://support.microsoft.com/?id=283811
John
"PSPDBA" wrote:
> Yep, it sure has. I was thinking of doing both of those things. I'll
> give it a try.
>
> John Bell wrote:
> > Hi
> >
> > I assume that the EventLog has started correctly?
> >
> > Making SQL Agent dependent on the EventLog service would ensure that it has
> > started before SQL Agent starts.
> >
> > If the service is running as LOCALSYSTEM you could change it to an domain
> > account.
> >
> > John
> >
> > "PSPDBA" wrote:
> >
> > > Agent log shows:
> > >
> > > Message
> > > [241] Startup error: Unable to initialize error reporting system
> > > (reason: The EventLog service has not been started)
> > >
> > > However, The EventLog service is also set to automatic.
> > >
> > > John Bell wrote:
> > > > Hi
> > > >
> > > > Have you checked the sql server agent log file in Management studio? Also
> > > > check what SQL Server Configuration Manager has for the service and check
> > > > that error reporting is selected on the advanced tab.
> > > >
> > > > John
> > > >
> > > > "PSPDBA" wrote:
> > > >
> > > > > We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> > > > > machine is rebooted, the SQL Server agent is not automatically started.
> > > > > It is set to start automatically in the Windows Services dialog. I
> > > > > see a safe shutdown prior to the reboot, but no messages like it's even
> > > > > trying to start up. I can start it manually with no problems.
> > > > >
> > > > > Any ideas what to check or where to go from here?
> > > > >
> > > > >
> > >
> > >
>
machine is rebooted, the SQL Server agent is not automatically started.
It is set to start automatically in the Windows Services dialog. I
see a safe shutdown prior to the reboot, but no messages like it's even
trying to start up. I can start it manually with no problems.
Any ideas what to check or where to go from here?Hi
Have you checked the sql server agent log file in Management studio? Also
check what SQL Server Configuration Manager has for the service and check
that error reporting is selected on the advanced tab.
John
"PSPDBA" wrote:
> We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> machine is rebooted, the SQL Server agent is not automatically started.
> It is set to start automatically in the Windows Services dialog. I
> see a safe shutdown prior to the reboot, but no messages like it's even
> trying to start up. I can start it manually with no problems.
> Any ideas what to check or where to go from here?
>|||Agent log shows:
Message
[241] Startup error: Unable to initialize error reporting system
(reason: The EventLog service has not been started)
However, The EventLog service is also set to automatic.
John Bell wrote:
> Hi
> Have you checked the sql server agent log file in Management studio? Also
> check what SQL Server Configuration Manager has for the service and check
> that error reporting is selected on the advanced tab.
> John
> "PSPDBA" wrote:
> > We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> > machine is rebooted, the SQL Server agent is not automatically started.
> > It is set to start automatically in the Windows Services dialog. I
> > see a safe shutdown prior to the reboot, but no messages like it's even
> > trying to start up. I can start it manually with no problems.
> >
> > Any ideas what to check or where to go from here?
> >
> >|||Hi
I assume that the EventLog has started correctly?
Making SQL Agent dependent on the EventLog service would ensure that it has
started before SQL Agent starts.
If the service is running as LOCALSYSTEM you could change it to an domain
account.
John
"PSPDBA" wrote:
> Agent log shows:
> Message
> [241] Startup error: Unable to initialize error reporting system
> (reason: The EventLog service has not been started)
> However, The EventLog service is also set to automatic.
> John Bell wrote:
> > Hi
> >
> > Have you checked the sql server agent log file in Management studio? Also
> > check what SQL Server Configuration Manager has for the service and check
> > that error reporting is selected on the advanced tab.
> >
> > John
> >
> > "PSPDBA" wrote:
> >
> > > We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> > > machine is rebooted, the SQL Server agent is not automatically started.
> > > It is set to start automatically in the Windows Services dialog. I
> > > see a safe shutdown prior to the reboot, but no messages like it's even
> > > trying to start up. I can start it manually with no problems.
> > >
> > > Any ideas what to check or where to go from here?
> > >
> > >
>|||Yep, it sure has. I was thinking of doing both of those things. I'll
give it a try.
John Bell wrote:
> Hi
> I assume that the EventLog has started correctly?
> Making SQL Agent dependent on the EventLog service would ensure that it has
> started before SQL Agent starts.
> If the service is running as LOCALSYSTEM you could change it to an domain
> account.
> John
> "PSPDBA" wrote:
> > Agent log shows:
> >
> > Message
> > [241] Startup error: Unable to initialize error reporting system
> > (reason: The EventLog service has not been started)
> >
> > However, The EventLog service is also set to automatic.
> >
> > John Bell wrote:
> > > Hi
> > >
> > > Have you checked the sql server agent log file in Management studio? Also
> > > check what SQL Server Configuration Manager has for the service and check
> > > that error reporting is selected on the advanced tab.
> > >
> > > John
> > >
> > > "PSPDBA" wrote:
> > >
> > > > We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> > > > machine is rebooted, the SQL Server agent is not automatically started.
> > > > It is set to start automatically in the Windows Services dialog. I
> > > > see a safe shutdown prior to the reboot, but no messages like it's even
> > > > trying to start up. I can start it manually with no problems.
> > > >
> > > > Any ideas what to check or where to go from here?
> > > >
> > > >
> >
> >|||Hi
You didn't say if the service was running under local system or not'
Looking at other posts http://tinyurl.com/rvql2 the service account seems to
be a prime reason for this failure. To change this manually check out
http://support.microsoft.com/?id=283811
John
"PSPDBA" wrote:
> Yep, it sure has. I was thinking of doing both of those things. I'll
> give it a try.
>
> John Bell wrote:
> > Hi
> >
> > I assume that the EventLog has started correctly?
> >
> > Making SQL Agent dependent on the EventLog service would ensure that it has
> > started before SQL Agent starts.
> >
> > If the service is running as LOCALSYSTEM you could change it to an domain
> > account.
> >
> > John
> >
> > "PSPDBA" wrote:
> >
> > > Agent log shows:
> > >
> > > Message
> > > [241] Startup error: Unable to initialize error reporting system
> > > (reason: The EventLog service has not been started)
> > >
> > > However, The EventLog service is also set to automatic.
> > >
> > > John Bell wrote:
> > > > Hi
> > > >
> > > > Have you checked the sql server agent log file in Management studio? Also
> > > > check what SQL Server Configuration Manager has for the service and check
> > > > that error reporting is selected on the advanced tab.
> > > >
> > > > John
> > > >
> > > > "PSPDBA" wrote:
> > > >
> > > > > We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> > > > > machine is rebooted, the SQL Server agent is not automatically started.
> > > > > It is set to start automatically in the Windows Services dialog. I
> > > > > see a safe shutdown prior to the reboot, but no messages like it's even
> > > > > trying to start up. I can start it manually with no problems.
> > > > >
> > > > > Any ideas what to check or where to go from here?
> > > > >
> > > > >
> > >
> > >
>
2005 Agent doesn't start automatically on reboot
We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
machine is rebooted, the SQL Server agent is not automatically started.
It is set to start automatically in the Windows Services dialog. I
see a safe shutdown prior to the reboot, but no messages like it's even
trying to start up. I can start it manually with no problems.
Any ideas what to check or where to go from here?Hi
Have you checked the sql server agent log file in Management studio? Also
check what SQL Server Configuration Manager has for the service and check
that error reporting is selected on the advanced tab.
John
"PSPDBA" wrote:
> We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> machine is rebooted, the SQL Server agent is not automatically started.
> It is set to start automatically in the Windows Services dialog. I
> see a safe shutdown prior to the reboot, but no messages like it's even
> trying to start up. I can start it manually with no problems.
> Any ideas what to check or where to go from here?
>|||Agent log shows:
Message
[241] Startup error: Unable to initialize error reporting system
(reason: The EventLog service has not been started)
However, The EventLog service is also set to automatic.
John Bell wrote:[vbcol=seagreen]
> Hi
> Have you checked the sql server agent log file in Management studio? Also
> check what SQL Server Configuration Manager has for the service and check
> that error reporting is selected on the advanced tab.
> John
> "PSPDBA" wrote:
>|||Hi
I assume that the EventLog has started correctly?
Making SQL Agent dependent on the EventLog service would ensure that it has
started before SQL Agent starts.
If the service is running as LOCALSYSTEM you could change it to an domain
account.
John
"PSPDBA" wrote:
> Agent log shows:
> Message
> [241] Startup error: Unable to initialize error reporting system
> (reason: The EventLog service has not been started)
> However, The EventLog service is also set to automatic.
> John Bell wrote:
>|||Yep, it sure has. I was thinking of doing both of those things. I'll
give it a try.
John Bell wrote:[vbcol=seagreen]
> Hi
> I assume that the EventLog has started correctly?
> Making SQL Agent dependent on the EventLog service would ensure that it ha
s
> started before SQL Agent starts.
> If the service is running as LOCALSYSTEM you could change it to an domain
> account.
> John
> "PSPDBA" wrote:
>|||Hi
You didn't say if the service was running under local system or not'
Looking at other posts http://tinyurl.com/rvql2 the service account seems to
be a prime reason for this failure. To change this manually check out
http://support.microsoft.com/?id=283811
John
"PSPDBA" wrote:
> Yep, it sure has. I was thinking of doing both of those things. I'll
> give it a try.
>
> John Bell wrote:
>
machine is rebooted, the SQL Server agent is not automatically started.
It is set to start automatically in the Windows Services dialog. I
see a safe shutdown prior to the reboot, but no messages like it's even
trying to start up. I can start it manually with no problems.
Any ideas what to check or where to go from here?Hi
Have you checked the sql server agent log file in Management studio? Also
check what SQL Server Configuration Manager has for the service and check
that error reporting is selected on the advanced tab.
John
"PSPDBA" wrote:
> We have a Windows Server 2003 SP1, SQL Server 2005 SP1. When the
> machine is rebooted, the SQL Server agent is not automatically started.
> It is set to start automatically in the Windows Services dialog. I
> see a safe shutdown prior to the reboot, but no messages like it's even
> trying to start up. I can start it manually with no problems.
> Any ideas what to check or where to go from here?
>|||Agent log shows:
Message
[241] Startup error: Unable to initialize error reporting system
(reason: The EventLog service has not been started)
However, The EventLog service is also set to automatic.
John Bell wrote:[vbcol=seagreen]
> Hi
> Have you checked the sql server agent log file in Management studio? Also
> check what SQL Server Configuration Manager has for the service and check
> that error reporting is selected on the advanced tab.
> John
> "PSPDBA" wrote:
>|||Hi
I assume that the EventLog has started correctly?
Making SQL Agent dependent on the EventLog service would ensure that it has
started before SQL Agent starts.
If the service is running as LOCALSYSTEM you could change it to an domain
account.
John
"PSPDBA" wrote:
> Agent log shows:
> Message
> [241] Startup error: Unable to initialize error reporting system
> (reason: The EventLog service has not been started)
> However, The EventLog service is also set to automatic.
> John Bell wrote:
>|||Yep, it sure has. I was thinking of doing both of those things. I'll
give it a try.
John Bell wrote:[vbcol=seagreen]
> Hi
> I assume that the EventLog has started correctly?
> Making SQL Agent dependent on the EventLog service would ensure that it ha
s
> started before SQL Agent starts.
> If the service is running as LOCALSYSTEM you could change it to an domain
> account.
> John
> "PSPDBA" wrote:
>|||Hi
You didn't say if the service was running under local system or not'
Looking at other posts http://tinyurl.com/rvql2 the service account seems to
be a prime reason for this failure. To change this manually check out
http://support.microsoft.com/?id=283811
John
"PSPDBA" wrote:
> Yep, it sure has. I was thinking of doing both of those things. I'll
> give it a try.
>
> John Bell wrote:
>
2005 Agent does not start on Reboot
I have a Windows 2003 server that is running SQL Server 2005 SP1. When the
server is rebooted, the SQL Server agent does not start. The service is set
to start automatically and is running with a domain account that has local
administrative privileges.
The Agent log has the following entries immediately after the reboot:
Date 6/3/2006 10:59:18 AM
Log SQL Agent (Archive #1 - 6/3/2006 10:59:00 AM)
Message
[098] SQLServerAgent terminated (normally)
---
Date 6/3/2006 10:58:36 AM
Log SQL Agent (Archive #1 - 6/3/2006 10:59:00 AM)
Message
[241] Startup error: Unable to initialize error reporting system (reason
:
The EventLog service has not been started)
I think I have done my homework researching this issue but have not found
anything that has fixed the problem.
Any help would be appreciated.
Thanks!
ChrisDid you check whether the Event Log service is disabled or is a manual
startup service in the services applet (administrative tools). If it is not
set to auto-start, make it auto start, reboot machine and see what happens.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:eOgvVhKiGHA.3296@.TK2MSFTNGP05.phx.gbl...
I have a Windows 2003 server that is running SQL Server 2005 SP1. When the
server is rebooted, the SQL Server agent does not start. The service is set
to start automatically and is running with a domain account that has local
administrative privileges.
The Agent log has the following entries immediately after the reboot:
Date 6/3/2006 10:59:18 AM
Log SQL Agent (Archive #1 - 6/3/2006 10:59:00 AM)
Message
[098] SQLServerAgent terminated (normally)
---
Date 6/3/2006 10:58:36 AM
Log SQL Agent (Archive #1 - 6/3/2006 10:59:00 AM)
Message
[241] Startup error: Unable to initialize error reporting system (reason
:
The EventLog service has not been started)
I think I have done my homework researching this issue but have not found
anything that has fixed the problem.
Any help would be appreciated.
Thanks!
Chris
server is rebooted, the SQL Server agent does not start. The service is set
to start automatically and is running with a domain account that has local
administrative privileges.
The Agent log has the following entries immediately after the reboot:
Date 6/3/2006 10:59:18 AM
Log SQL Agent (Archive #1 - 6/3/2006 10:59:00 AM)
Message
[098] SQLServerAgent terminated (normally)
---
Date 6/3/2006 10:58:36 AM
Log SQL Agent (Archive #1 - 6/3/2006 10:59:00 AM)
Message
[241] Startup error: Unable to initialize error reporting system (reason
:
The EventLog service has not been started)
I think I have done my homework researching this issue but have not found
anything that has fixed the problem.
Any help would be appreciated.
Thanks!
ChrisDid you check whether the Event Log service is disabled or is a manual
startup service in the services applet (administrative tools). If it is not
set to auto-start, make it auto start, reboot machine and see what happens.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:eOgvVhKiGHA.3296@.TK2MSFTNGP05.phx.gbl...
I have a Windows 2003 server that is running SQL Server 2005 SP1. When the
server is rebooted, the SQL Server agent does not start. The service is set
to start automatically and is running with a domain account that has local
administrative privileges.
The Agent log has the following entries immediately after the reboot:
Date 6/3/2006 10:59:18 AM
Log SQL Agent (Archive #1 - 6/3/2006 10:59:00 AM)
Message
[098] SQLServerAgent terminated (normally)
---
Date 6/3/2006 10:58:36 AM
Log SQL Agent (Archive #1 - 6/3/2006 10:59:00 AM)
Message
[241] Startup error: Unable to initialize error reporting system (reason
:
The EventLog service has not been started)
I think I have done my homework researching this issue but have not found
anything that has fixed the problem.
Any help would be appreciated.
Thanks!
Chris
2005 Agent does not start on Reboot
I have a Windows 2003 server that is running SQL Server 2005 SP1. When the
server is rebooted, the SQL Server agent does not start. The service is set
to start automatically and is running with a domain account that has local
administrative privileges.
The Agent log has the following entries immediately after the reboot:
Date 6/3/2006 10:59:18 AM
Log SQL Agent (Archive #1 - 6/3/2006 10:59:00 AM)
Message
[098] SQLServerAgent terminated (normally)
---
Date 6/3/2006 10:58:36 AM
Log SQL Agent (Archive #1 - 6/3/2006 10:59:00 AM)
Message
[241] Startup error: Unable to initialize error reporting system (reason:
The EventLog service has not been started)
I think I have done my homework researching this issue but have not found
anything that has fixed the problem.
Any help would be appreciated.
Thanks!
ChrisDid you check whether the Event Log service is disabled or is a manual
startup service in the services applet (administrative tools). If it is not
set to auto-start, make it auto start, reboot machine and see what happens.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:eOgvVhKiGHA.3296@.TK2MSFTNGP05.phx.gbl...
I have a Windows 2003 server that is running SQL Server 2005 SP1. When the
server is rebooted, the SQL Server agent does not start. The service is set
to start automatically and is running with a domain account that has local
administrative privileges.
The Agent log has the following entries immediately after the reboot:
Date 6/3/2006 10:59:18 AM
Log SQL Agent (Archive #1 - 6/3/2006 10:59:00 AM)
Message
[098] SQLServerAgent terminated (normally)
---
Date 6/3/2006 10:58:36 AM
Log SQL Agent (Archive #1 - 6/3/2006 10:59:00 AM)
Message
[241] Startup error: Unable to initialize error reporting system (reason:
The EventLog service has not been started)
I think I have done my homework researching this issue but have not found
anything that has fixed the problem.
Any help would be appreciated.
Thanks!
Chris
server is rebooted, the SQL Server agent does not start. The service is set
to start automatically and is running with a domain account that has local
administrative privileges.
The Agent log has the following entries immediately after the reboot:
Date 6/3/2006 10:59:18 AM
Log SQL Agent (Archive #1 - 6/3/2006 10:59:00 AM)
Message
[098] SQLServerAgent terminated (normally)
---
Date 6/3/2006 10:58:36 AM
Log SQL Agent (Archive #1 - 6/3/2006 10:59:00 AM)
Message
[241] Startup error: Unable to initialize error reporting system (reason:
The EventLog service has not been started)
I think I have done my homework researching this issue but have not found
anything that has fixed the problem.
Any help would be appreciated.
Thanks!
ChrisDid you check whether the Event Log service is disabled or is a manual
startup service in the services applet (administrative tools). If it is not
set to auto-start, make it auto start, reboot machine and see what happens.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Cgal" <cgallelli@.newsgroups.nospam> wrote in message
news:eOgvVhKiGHA.3296@.TK2MSFTNGP05.phx.gbl...
I have a Windows 2003 server that is running SQL Server 2005 SP1. When the
server is rebooted, the SQL Server agent does not start. The service is set
to start automatically and is running with a domain account that has local
administrative privileges.
The Agent log has the following entries immediately after the reboot:
Date 6/3/2006 10:59:18 AM
Log SQL Agent (Archive #1 - 6/3/2006 10:59:00 AM)
Message
[098] SQLServerAgent terminated (normally)
---
Date 6/3/2006 10:58:36 AM
Log SQL Agent (Archive #1 - 6/3/2006 10:59:00 AM)
Message
[241] Startup error: Unable to initialize error reporting system (reason:
The EventLog service has not been started)
I think I have done my homework researching this issue but have not found
anything that has fixed the problem.
Any help would be appreciated.
Thanks!
Chris
2005 Agent - MSX enlist failed
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!
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.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||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?ProdN...r&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?ProdN...6&LinkId=20476
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:SsdHCjFCGHA.832@.TK2MSFTNGXA02.phx.gbl...
> 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.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
|||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.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||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!
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:xXDRRM5CGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> 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.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
|||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.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||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
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:h5EHZtDDGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> 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.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
|||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.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
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!
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.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||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?ProdN...r&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?ProdN...6&LinkId=20476
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:SsdHCjFCGHA.832@.TK2MSFTNGXA02.phx.gbl...
> 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.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
|||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.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||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!
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:xXDRRM5CGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> 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.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
|||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.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||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
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:h5EHZtDDGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> 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.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
|||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.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
2005 Agent - MSX enlist failed
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!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.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||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.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 '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
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:SsdHCjFCGHA.832@.TK2MSFTNGXA02.phx.gbl...
> 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.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||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.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||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!
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:xXDRRM5CGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> 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.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||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.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||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
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:h5EHZtDDGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> 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.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||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.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
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!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.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||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.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 '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
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:SsdHCjFCGHA.832@.TK2MSFTNGXA02.phx.gbl...
> 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.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||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.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||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!
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:xXDRRM5CGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> 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.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||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.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||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
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:h5EHZtDDGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> 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.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||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.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.
2005 Agent - MSX enlist failed
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!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.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||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?Prod...er&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?Prod...26&LinkId=20476
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:SsdHCjFCGHA.832@.TK2MSFTNGXA02.phx.gbl...
> 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.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||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.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||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!
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:xXDRRM5CGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> 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.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||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.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||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
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:h5EHZtDDGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> 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.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||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.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
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!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.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||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?Prod...er&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?Prod...26&LinkId=20476
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:SsdHCjFCGHA.832@.TK2MSFTNGXA02.phx.gbl...
> 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.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||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.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||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!
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:xXDRRM5CGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> 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.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||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.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||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
"Michael Cheng [MSFT]" <v-mingqc@.online.microsoft.com> wrote in message
news:h5EHZtDDGHA.3764@.TK2MSFTNGXA02.phx.gbl...
> 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.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||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.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to:
Posts (Atom)