I have been getting this message in the past couple of hours. I
rebooted publisher and subscriber. Even if I restart the agent - it
doesn't help. I rebuilt transactional replication from scratch and I
still got this error message. I set for the agent to output to the
file and this is what I get
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
on 'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a
later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
on 'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a
later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
>>The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.<<
Try creating a new Profile for your log reader agent with a smaller number
for the -ReadBatchSize parameter, and/or a longer -LoginTimeout value
Could be you have a very large transaction stuck in the t-log of the
published database
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"tolcis" <nytollydba@.gmail.com> wrote in message
news:70357b88-b169-4b21-83b4-ddc5a00b6ad0@.q77g2000hsh.googlegroups.com...
>I have been getting this message in the past couple of hours. I
> rebooted publisher and subscriber. Even if I restart the agent - it
> doesn't help. I rebuilt transactional replication from scratch and I
> still got this error message. I set for the agent to output to the
> file and this is what I get
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
> on 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a
> later time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
> on 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a
> later time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
Showing posts with label sp_replcmds. Show all posts
Showing posts with label sp_replcmds. Show all posts
Wednesday, March 7, 2012
could not execute sp_replcmds on server - need help
I have been getting this message in the past couple of hours. I
rebooted publisher and subscriber. Even if I restart the agent - it
doesn't help. I rebuilt transactional replication from scratch and I
still got this error message. I set for the agent to output to the
file and this is what I get
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
on 'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a
later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
on 'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a
later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}>>The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.<<
Try creating a new Profile for your log reader agent with a smaller number
for the -ReadBatchSize parameter, and/or a longer -LoginTimeout value
Could be you have a very large transaction stuck in the t-log of the
published database
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"tolcis" <nytollydba@.gmail.com> wrote in message
news:70357b88-b169-4b21-83b4-ddc5a00b6ad0@.q77g2000hsh.googlegroups.com...
>I have been getting this message in the past couple of hours. I
> rebooted publisher and subscriber. Even if I restart the agent - it
> doesn't help. I rebuilt transactional replication from scratch and I
> still got this error message. I set for the agent to output to the
> file and this is what I get
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
> on 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a
> later time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
> on 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a
> later time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
rebooted publisher and subscriber. Even if I restart the agent - it
doesn't help. I rebuilt transactional replication from scratch and I
still got this error message. I set for the agent to output to the
file and this is what I get
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
on 'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a
later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
on 'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a
later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}>>The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.<<
Try creating a new Profile for your log reader agent with a smaller number
for the -ReadBatchSize parameter, and/or a longer -LoginTimeout value
Could be you have a very large transaction stuck in the t-log of the
published database
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"tolcis" <nytollydba@.gmail.com> wrote in message
news:70357b88-b169-4b21-83b4-ddc5a00b6ad0@.q77g2000hsh.googlegroups.com...
>I have been getting this message in the past couple of hours. I
> rebooted publisher and subscriber. Even if I restart the agent - it
> doesn't help. I rebuilt transactional replication from scratch and I
> still got this error message. I set for the agent to output to the
> file and this is what I get
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
> on 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a
> later time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
> on 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a
> later time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
could not execute sp_replcmds on server - need help
I have been getting this message in the past couple of hours. I
rebooted publisher and subscriber. Even if I restart the agent - it
doesn't help. I rebuilt transactional replication from scratch and I
still got this error message. I set for the agent to output to the
file and this is what I get
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
on 'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a
later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
on 'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a
later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}>>The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.<<
Try creating a new Profile for your log reader agent with a smaller number
for the -ReadBatchSize parameter, and/or a longer -LoginTimeout value
Could be you have a very large transaction stuck in the t-log of the
published database
--
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"tolcis" <nytollydba@.gmail.com> wrote in message
news:70357b88-b169-4b21-83b4-ddc5a00b6ad0@.q77g2000hsh.googlegroups.com...
>I have been getting this message in the past couple of hours. I
> rebooted publisher and subscriber. Even if I restart the agent - it
> doesn't help. I rebuilt transactional replication from scratch and I
> still got this error message. I set for the agent to output to the
> file and this is what I get
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
> on 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a
> later time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
> on 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a
> later time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
rebooted publisher and subscriber. Even if I restart the agent - it
doesn't help. I rebuilt transactional replication from scratch and I
still got this error message. I set for the agent to output to the
file and this is what I get
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
on 'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a
later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}
Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
on 'KOCL384017SQL'.'.
The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.
Disconnecting from Publisher 'KOCL384017SQL'
The agent failed with a 'Retry' status. Try to run the agent at a
later time.
Microsoft SQL Server Log Reader Agent 8.00.2039
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
Connecting to Publisher 'KOCL384017SQL.DL'
Server:
DBMS: Microsoft SQL Server
Version: 08.00.2040
user name: dbo
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
[12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
Status: 4096, code: 20024, text: 'Initializing'.
The agent is running. Use Replication Monitor to view the details of
this agent session.
Publisher: {call sp_repldone ( 0x000301d3000088650001,
0x000301d3000088650001, 0, 0)}
Publisher: {call sp_replcmds (500, 0)}>>The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
Status: 2, code: 0, text: 'Timeout expired'.<<
Try creating a new Profile for your log reader agent with a smaller number
for the -ReadBatchSize parameter, and/or a longer -LoginTimeout value
Could be you have a very large transaction stuck in the t-log of the
published database
--
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"tolcis" <nytollydba@.gmail.com> wrote in message
news:70357b88-b169-4b21-83b4-ddc5a00b6ad0@.q77g2000hsh.googlegroups.com...
>I have been getting this message in the past couple of hours. I
> rebooted publisher and subscriber. Even if I restart the agent - it
> doesn't help. I rebuilt transactional replication from scratch and I
> still got this error message. I set for the agent to output to the
> file and this is what I get
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:10:53 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
> on 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a
> later time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:16:54 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
> Status: 2, code: 0, text: 'The process could not execute 'sp_replcmds'
> on 'KOCL384017SQL'.'.
> The process could not execute 'sp_replcmds' on 'KOCL384017SQL'.
> Status: 2, code: 0, text: 'Timeout expired'.
> Disconnecting from Publisher 'KOCL384017SQL'
> The agent failed with a 'Retry' status. Try to run the agent at a
> later time.
> Microsoft SQL Server Log Reader Agent 8.00.2039
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent: KOCL384017SQL-DL-69
> Connecting to Publisher 'KOCL384017SQL.DL'
> Server:
> DBMS: Microsoft SQL Server
> Version: 08.00.2040
> user name: dbo
> API conformance: 2
> SQL conformance: 1
> transaction capable: 2
> read only: N
> identifier quote char: "
> non_nullable_columns: 1
> owner usage: 31
> max table name len: 128
> max column name len: 128
> need long data len: Y
> max columns in table: 1024
> max columns in index: 16
> max char literal len: 524288
> max statement len: 524288
> max row size: 524288
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: select @.@.SERVERNAME
> [12/21/2007 10:22:55 AM]KOCL384017SQL.DL: sp_MSgetversion
> Status: 4096, code: 20024, text: 'Initializing'.
> The agent is running. Use Replication Monitor to view the details of
> this agent session.
> Publisher: {call sp_repldone ( 0x000301d3000088650001,
> 0x000301d3000088650001, 0, 0)}
> Publisher: {call sp_replcmds (500, 0)}
could not execute sp_replcmds
I am working on SQL Server 2000 SP4
I am getting a very strange error on one of my instances;
The process could not execute 'sp_replcmds' on #SERVERNAME#
Replication failure. File 'T:\shiloh\sql\ntdbms\srvrepl\src\replicat.cpp',
line 1677.
(Source: #SERVERNAME# (Data source); Error number: 18759)
In microsoft http://support.microsoft.com/kb/308865 it tells you to apply
SQL SP4, which i have done and re did just incase it wasn't applied properly,
it made no difference to the situations. Ive restarted the intance and the
server and still to no avail.
Last month we did have a situation where our master database went suspect
and this is the first time anything has had to be replicated on that server
since then. The publisher and subscriber database are on the same server.
Thanks.
Was this post helpful to you?
Why should I rate a post?I have a recollection with replication that you have to enable replication before applying SP4 (or re-apply SP4 after enabling replication). You must do this on both the publisher and the distributor. If I recall the sequence correctly, you must do the distributor first and then then publisher.
I know that you said you re-applied SP4, did you do it in accordance with the steps outlined above?
Regards,
hmscott
I am getting a very strange error on one of my instances;
The process could not execute 'sp_replcmds' on #SERVERNAME#
Replication failure. File 'T:\shiloh\sql\ntdbms\srvrepl\src\replicat.cpp',
line 1677.
(Source: #SERVERNAME# (Data source); Error number: 18759)
In microsoft http://support.microsoft.com/kb/308865 it tells you to apply
SQL SP4, which i have done and re did just incase it wasn't applied properly,
it made no difference to the situations. Ive restarted the intance and the
server and still to no avail.
Last month we did have a situation where our master database went suspect
and this is the first time anything has had to be replicated on that server
since then. The publisher and subscriber database are on the same server.
Thanks.
Was this post helpful to you?
Why should I rate a post?I have a recollection with replication that you have to enable replication before applying SP4 (or re-apply SP4 after enabling replication). You must do this on both the publisher and the distributor. If I recall the sequence correctly, you must do the distributor first and then then publisher.
I know that you said you re-applied SP4, did you do it in accordance with the steps outlined above?
Regards,
hmscott
Subscribe to:
Posts (Atom)