Could Publisher Server Pull Subscriber Server

Hello,
I have two SQL SERVERs and I would like to establish a simple architecture
of one Publisher and one SUbscriber. the catch is that I would like to use
SQL 2005 EXPRESS as my source DB - Production Server (even though, as far as
I understand, it can only be a Subscriber) and SQL SERVER 2005 STANDARD will
be the replica DB (even though it will probebly have to be Publisher).
So, is it pusible that SQL SERVER STANDARD, which acts as a Publisher, be
able to make a Pull operation (and it will be replica DB) from SQL SERVER
EXPRESS, which acts as a Subscriber (and it will be the source DB)?
It is important to note that at the moment the SQL SERVER EXPRESS is used as
the only SERVER we have and it is operational.
I would like to add SQL SERVER 2005 STANDARD in order to let it pull every 5
minutes (or so) the SQL SERVER 2005 EXPRESS and copy all the changes made in
the existing SQL 2005 EXPRESS operational server.
I do not have the option to shutdown the SQL 2005 EXPRESS SERVER in order to
upgrade it to a STANDARD vertion.
Thanks in advanced
Yossi
You can use merge replication for this. However your SQL Server Standard
will have to be the publisher which can push to the Express version.
Why do you need a pull on the SQL Server standard machine?
RelevantNoise.com - dedicated to mining blogs for business intelligence.
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
"yoffir" <yoffir@.discussions.microsoft.com> wrote in message
news:5A0216BC-5D31-4AF2-B6BE-3A1B266C9A75@.microsoft.com...
> Hello,
> I have two SQL SERVERs and I would like to establish a simple architecture
> of one Publisher and one SUbscriber. the catch is that I would like to use
> SQL 2005 EXPRESS as my source DB - Production Server (even though, as far
> as
> I understand, it can only be a Subscriber) and SQL SERVER 2005 STANDARD
> will
> be the replica DB (even though it will probebly have to be Publisher).
> So, is it pusible that SQL SERVER STANDARD, which acts as a Publisher, be
> able to make a Pull operation (and it will be replica DB) from SQL SERVER
> EXPRESS, which acts as a Subscriber (and it will be the source DB)?
> It is important to note that at the moment the SQL SERVER EXPRESS is used
> as
> the only SERVER we have and it is operational.
> I would like to add SQL SERVER 2005 STANDARD in order to let it pull every
> 5
> minutes (or so) the SQL SERVER 2005 EXPRESS and copy all the changes made
> in
> the existing SQL 2005 EXPRESS operational server.
> I do not have the option to shutdown the SQL 2005 EXPRESS SERVER in order
> to
> upgrade it to a STANDARD vertion.
> Thanks in advanced
> Yossi
>
|||I want to save the huge fee fore having a license for the STANDARD version.
The database is used by many users and a license will give Bill Gats 7000$
extra to his bank account.
Currently we are using the EXPRESS version free of charge.
I would like to have a replica of that database in a remote site.
The thing is that it is pusible that our programmers will use the replica
database and make changes to it. So, the original EXPRESS database must not
be updated by the replica database.
This is why I thought to use a publisher STANDARD database as a replica and
pull the subscriber EXPRESS database every 5 minutes for changes.
If I will use a publisher STANDARD server I will have to pay only 800$ for a
single user license (sa).
Hope I didn't confuse you
"Hilary Cotter" wrote:

> You can use merge replication for this. However your SQL Server Standard
> will have to be the publisher which can push to the Express version.
> Why do you need a pull on the SQL Server standard machine?
> --
> RelevantNoise.com - dedicated to mining blogs for business intelligence.
> 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
> "yoffir" <yoffir@.discussions.microsoft.com> wrote in message
> news:5A0216BC-5D31-4AF2-B6BE-3A1B266C9A75@.microsoft.com...
>
>

Could not find the index entry for RID

Hi all, got this error and well want some advice really. Cheers
The process could not enumerate changes at the 'Subscriber'.
(Source: Merge Replication Provider (Agent); Error number: -2147200999)
------
Could not find the index entry for RID
'16f8db910fd437730d2cca409ba472f23ca363ef200' in index page (1:353425),
index ID 0, database 'VMR'.
(Source: BBSERVER-SAT1 (Data source); Error number: 644)
------
The merge process encountered an unexpected network error. The connection to
Subscriber 'BBSERVER-SAT1' is no longer available.
(Source: Merge Process (Agent); Error number: -2147199469)
------
Put the database in single user mode and run a dbcc dbreindex, this normally
solves this problem.
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
"andrew bourne" <andrewbourne@.vardells.com> wrote in message
news:OoLVGQN9FHA.4076@.tk2msftngp13.phx.gbl...
> Hi all, got this error and well want some advice really. Cheers
> The process could not enumerate changes at the 'Subscriber'.
> (Source: Merge Replication Provider (Agent); Error number: -2147200999)
> ------
> Could not find the index entry for RID
> '16f8db910fd437730d2cca409ba472f23ca363ef200' in index page (1:353425),
> index ID 0, database 'VMR'.
> (Source: BBSERVER-SAT1 (Data source); Error number: 644)
> ------
> The merge process encountered an unexpected network error. The connection
> to Subscriber 'BBSERVER-SAT1' is no longer available.
> (Source: Merge Process (Agent); Error number: -2147199469)
> ------
>

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)}

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)}

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)}

Could not deliver update

I have started merge replication. It was working. Now I get messege that 'The
process could not deliver update(s) at the Subscriber'.
If I start it manually, I see message come it has down loaded some records.
100 update, 1 insert etc. I can see my CPU usage is 100%. Then after few min
later it gives that message.
Do not see anythng in the conflict viewer.
Please help
can you enable logging so we can see the exact failure message? Please refer
to this link for more info.
http://support.microsoft.com/default...b;en-us;312292
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
"Aziz" <Aziz @.discussions.microsoft.com> wrote in message
news:59C17F3D-2C9D-4285-A476-E83BAC9E1025@.microsoft.com...
> I have started merge replication. It was working. Now I get messege that
'The
> process could not deliver update(s) at the Subscriber'.
> If I start it manually, I see message come it has down loaded some
records.
> 100 update, 1 insert etc. I can see my CPU usage is 100%. Then after few
min
> later it gives that message.
> Do not see anythng in the conflict viewer.
> Please help

could not deliver the snapshot to the subscriber

We have a customer w/ merge replication setup and has been functioning.
Their server's were hacked. We have spent 3 days on the phone w/ MS and
everything is working except for 1 client. When it is trying to deliver
the snapshot it is getting an error:
The process could not bulk copy into table {table name}
Violation of PRIMARY KEY constraint. Cannot insert duplicate key.
I understand what that means, so on that table (it is not a necessary
table, just a log), I deleted all records from that table and the
delivery got past that table to the next table in the list and displayed
the same message.
What can I do on the client to get this to work? I can't delete the info
in the second table because it is much more required and I don't want to
have it delete the same data on the main server. I know it is trying to
insert a new record that has the same primary key, but is it trying to
do that because the server record has one guid and the client has a
different guid (I don't really know how the guid's work in replication -
if the record has the same guid on all servers).
Darin
*** Sent via Developersdex http://www.codecomments.com ***
I would use a tool like RedGate's datacompare to reconcile the data to the
Publisher. You'll need to modify the scripts somewhat if you have PK issues
and then I'd reinitialize.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||I know they are duplicate keys. The client has a record w/ the key as 2
(identity column), so does the distributor. The snapshot is trying to
send that record down - why, and how can I make so the snapshot doesn't
try to send it down?
Darin
*** Sent via Developersdex http://www.codecomments.com ***
|||Hi.
In the publisher, mark that identity column which is acting as primary key
to NOT FOR REPLICATION in the design mode of that table.
in this case, the identity will be inserted independently at the subscriber
avoiding primary key errors.
"Darin" wrote:

> I know they are duplicate keys. The client has a record w/ the key as 2
> (identity column), so does the distributor. The snapshot is trying to
> send that record down - why, and how can I make so the snapshot doesn't
> try to send it down?
> Darin
> *** Sent via Developersdex http://www.codecomments.com ***
>
|||The table on both the subscriber and the distrubtor are setup that way.
Darin
*** Sent via Developersdex http://www.codecomments.com ***
|||Can you outline your situation a little more. Usually a snapshot of the
publisher's data is sent from the publisher to the subscriber. Initially
there is a drop table executed on the subscriber. There are variations - one
of which is a nosync initialization, where all the required info already
exists on the subscriber and the publisher just sends the metadata and
system stored procedures/triggers required to run replication. There are
other possibilities where the table and its data remain and the new data is
appended. Of these, which is your requirement, or is your requirement
something quite different?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

Could not connect to Subscriber

I am using Sql server replication wizard and it create
publisher, subscriber and Distributor successfully and
also apply initial snapshot and transfer data. but when i
try to synchronize manually it returns error "The process
could not connect to subscriber "MySubscriber". i am using
windows authentication.
Hi
I think u are not on the same domain. Try to implementing by SQL
authentication. I have done every thing successfully. It must be the error
of SQL Agent. i am also working on relication these days so i m also seeking
any thing/error/problem related to replication. I think u are missing some
thing during wizard.
Regards,
-Imran Iqbal
"Saima" <ucoxk@.yahoo.com> wrote in message
news:40b001c47308$9ff6c9e0$a301280a@.phx.gbl...
> I am using Sql server replication wizard and it create
> publisher, subscriber and Distributor successfully and
> also apply initial snapshot and transfer data. but when i
> try to synchronize manually it returns error "The process
> could not connect to subscriber "MySubscriber". i am using
> windows authentication.
|||I want to know what is that missing and what it can be.
while i try it on the same pc it is well. can u give me
help in detail
>--Original Message--
>Hi
>I think u are not on the same domain. Try to
implementing by SQL
>authentication. I have done every thing successfully. It
must be the error
>of SQL Agent. i am also working on relication these days
so i m also seeking
>any thing/error/problem related to replication. I think
u are missing some[vbcol=seagreen]
>thing during wizard.
>Regards,
>-Imran Iqbal
>"Saima" <ucoxk@.yahoo.com> wrote in message
>news:40b001c47308$9ff6c9e0$a301280a@.phx.gbl...
when i[vbcol=seagreen]
process[vbcol=seagreen]
using
>
>.
>
|||Hi,
During working i faced some strange errors and I reinslled MSDE and SQL
Server but i couldn't succed. After that i worked on freshly installed
windows 2000 Server PC and then i succeded. So you can try these things.
-Imran
"Saima" <ucoxk@.yahoo.com> wrote in message
news:40b001c47308$9ff6c9e0$a301280a@.phx.gbl...
> I am using Sql server replication wizard and it create
> publisher, subscriber and Distributor successfully and
> also apply initial snapshot and transfer data. but when i
> try to synchronize manually it returns error "The process
> could not connect to subscriber "MySubscriber". i am using
> windows authentication.

Could not automatically reinitialize

I have a series of publisher/ distributors that replicat to one subscriber.
The replication was off-line across the weekend and now most of the
subscriptions are marked inactive / needs reinitialization.
When I try to reinitialize I get a message box saying "SQL Server Enterprise
Manager could not automatically reinitialize this subscription. To
reinitialize this subscription, you must drop and recreate it."
Any suggestions as to places to start looking for a solution will be greatly
appreciated.
You likely have no-sync subscribers - these always need to be dropped and
recreated, or converted to sync subscribers.
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
"Ron Sellers" <RonSellers@.discussions.microsoft.com> wrote in message
news:2DB36478-12BA-431A-A5D7-10952637A116@.microsoft.com...
> I have a series of publisher/ distributors that replicat to one
subscriber.
> The replication was off-line across the weekend and now most of the
> subscriptions are marked inactive / needs reinitialization.
> When I try to reinitialize I get a message box saying "SQL Server
Enterprise
> Manager could not automatically reinitialize this subscription. To
> reinitialize this subscription, you must drop and recreate it."
> Any suggestions as to places to start looking for a solution will be
greatly
> appreciated.
>

Could not allocate space for object 'MSrepl_commands' in database

We have transaction replication set up in SQL 2K environment . It's simple
SQL 2k publisher to SQL 2K subscriber (both Enterprise). It works fine but
some times(once a week or so) we get error message "Could not allocate space
for object 'MSrepl_commands' in database 'zzzz_distribution' " and log reader
agent gets stopped. I don't see any issues with space and both data and log
files are set for auto grow. When I go back and see DB size is very minimal.
Can you throw some ideas.
Thanks,
Prabhu
This looks like a problem with the distribution database being unable to
grow, can you confirm that the distribution database has space to grow, and
the growth increment is not a percent but a fixed amount like 100 Mgs.
http://www.zetainteractive.com - Shift Happens!
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
"Prabhu" <Prabhu@.discussions.microsoft.com> wrote in message
news:7BD73EC1-0AF2-494B-AD3C-6AE6F3D2D605@.microsoft.com...
> We have transaction replication set up in SQL 2K environment . It's simple
> SQL 2k publisher to SQL 2K subscriber (both Enterprise). It works fine but
> some times(once a week or so) we get error message "Could not allocate
> space
> for object 'MSrepl_commands' in database 'zzzz_distribution' " and log
> reader
> agent gets stopped. I don't see any issues with space and both data and
> log
> files are set for auto grow. When I go back and see DB size is very
> minimal.
> Can you throw some ideas.
> Thanks,
> Prabhu