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 read file 'snapshot.pre' due to OS error 5

Hi,
I am new to this replication thing and got bogged down on this issue.
My system consists of:
1. Publisher, SQL 2000 login xxxx password yyyy. Transactional
replication. Allow pull. On PAL, xxxx exists. Snapshot on default
folder
2. Subscriber, SQL 2005, existing on non-trusted domain, login xxxx
password yyyy. Pull replication. Read snapshot from default. Agent
process account = Subscriber\xxxx, Distributor connection = xxxx using
sql server authentication (I tried Impersonating but won't work).
Publisher can create a snapshot but Subscriber seem to have problem. I
cannot possibly add Subscriber\xxxx into PAL because it's not a
trusted domain(?). What am I doing wrong? Please help.
ben
error 5 is generic access denied. Is the snapshot folder shared? And does
the SQL Server Agent account or the account you are impersonating with have
read and list files and folders rights on the snapshot share and underlying
files and folders?
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
"benito" <lochinvar.geo@.gmail.com> wrote in message
news:f7d8b5fe-38d1-4073-b4d4-6f2d5023e272@.o6g2000hsd.googlegroups.com...
> Hi,
> I am new to this replication thing and got bogged down on this issue.
> My system consists of:
> 1. Publisher, SQL 2000 login xxxx password yyyy. Transactional
> replication. Allow pull. On PAL, xxxx exists. Snapshot on default
> folder
> 2. Subscriber, SQL 2005, existing on non-trusted domain, login xxxx
> password yyyy. Pull replication. Read snapshot from default. Agent
> process account = Subscriber\xxxx, Distributor connection = xxxx using
> sql server authentication (I tried Impersonating but won't work).
> Publisher can create a snapshot but Subscriber seem to have problem. I
> cannot possibly add Subscriber\xxxx into PAL because it's not a
> trusted domain(?). What am I doing wrong? Please help.
> ben
|||Thanks for your reply Hilary. I reviewed the folder rights, password,
logins to make sure they are correct and now it seems to work fine.
ben
On Dec 4, 9:23 am, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:
> error 5 is generic access denied. Is the snapshot folder shared? And does
> the SQL Server Agent account or the account you are impersonating with have
> read and list files and folders rights on the snapshot share and underlying
> files and folders?
> --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 FTShttp://www.indexserverfaq.com"benito" <lochinvar...@.gmail.com> wrote in message
> news:f7d8b5fe-38d1-4073-b4d4-6f2d5023e272@.o6g2000hsd.googlegroups.com...
>
>
>
>
> - Show quoted text -

Could not find stored procedure 'sp_MSin_<TableName>'

Hi,
Just completed the transactional replication and when tried to test the
changes made in the publisher data it (Distribution Agent) failed with the
following error:
Could not find stored procedure 'sp_MSupd_ACCOUNT'.
(Source: PARISDB2 (Data source); Error number: 2812)
Checked the sysobjects and all these procedures (sp_MSins, sp_MSupd etc) are
present in the database.
Current Configuration is: 1 Publisher, 1 Subscriber, Distributor database is
on the Publisher server, SQLServer 2000 (SP4), Windows 2003)
Please help me out....need to know the reason and the solution
Thanks & Regards
Sangra
Hi Sangra
This problem will happen when the snapshot schema is not applied on the
subscriber.
You can generate the scripts manually using the following procedure
exec sp_scriptinsproc 'articleid'
exec sp_scriptdelproc 'articleid'
exec sp_scriptmappedupdproc 'articleid'
Apply this script on the subscriber.
For getting the articleid check sysarticles table.
P. Srinivasan MCDBA
Consultant
C-13/1,GF,Tulip Garden, Ardee City,
Sector-52,
Gurgaon-122003
India
Mobile:+91-9810321551
"Sangra" <Sangra@.discussions.microsoft.com> wrote in message
news:1A700079-F991-4D00-82A6-756AF23CC16E@.microsoft.com...
> Hi,
> Just completed the transactional replication and when tried to test the
> changes made in the publisher data it (Distribution Agent) failed with the
> following error:
> Could not find stored procedure 'sp_MSupd_ACCOUNT'.
> (Source: PARISDB2 (Data source); Error number: 2812)
> Checked the sysobjects and all these procedures (sp_MSins, sp_MSupd etc)
> are
> present in the database.
> Current Configuration is: 1 Publisher, 1 Subscriber, Distributor database
> is
> on the Publisher server, SQLServer 2000 (SP4), Windows 2003)
> Please help me out....need to know the reason and the solution
> Thanks & Regards
> Sangra

Could not find stored procedure 'dbo.sp_MS_replication_installed'.

Dear all,
I want to add a new server as a publisher to an existing distributor,
but each time I try, I get this error:
Could not find stored procedure 'dbo.sp_MS_replication_installed'.
I also tried making this machine it's own distributor, but the same
error comes up.
Thanks in advance.
Aramid
Aramid,
Does the proc exist?
Try:
USE MASTER
GO
IF OBJECT_ID('SP_MS_REPLICATION_INSTALLED') IS NULL
PRINT 'PROC NOT INSTALLED'
ELSE
PRINT 'PROC INSTALLED'
Also, you may want to post this to:
http://www.microsoft.com/technet/com...replica tion
HTH
Jerry
"Aramid" <aramid@.hotmail.com> wrote in message
news:6t8sl19hf5c6mbgphm3nubjhim3b6ncg7b@.4ax.com...
> Dear all,
> I want to add a new server as a publisher to an existing distributor,
> but each time I try, I get this error:
> Could not find stored procedure 'dbo.sp_MS_replication_installed'.
> I also tried making this machine it's own distributor, but the same
> error comes up.
> Thanks in advance.
>
> Aramid

Could not find stored procedure 'dbo.sp_MS_replication_installed'.

Dear all,
I want to add a new server as a publisher to an existing distributor,
but each time I try, I get this error:
Could not find stored procedure 'dbo.sp_MS_replication_installed'.
I also tried making this machine it's own distributor, but the same
error comes up.
Thanks in advance.
Aramid
Reapply the latest sp. There seems to be a problem with the sp setup program
where it drops all the replication related procs, but somehow occasionally
forgets to reinstall them.
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
"Aramid" <aramid@.hotmail.com> wrote in message
news:cs5sl1lm2mh8bso89aujduaii1gjpovpn4@.4ax.com...
> Dear all,
> I want to add a new server as a publisher to an existing distributor,
> but each time I try, I get this error:
> Could not find stored procedure 'dbo.sp_MS_replication_installed'.
> I also tried making this machine it's own distributor, but the same
> error comes up.
> Thanks in advance.
>
> Aramid
|||Thanks so much Hillary, I will try this one.
Aramid
On Tue, 25 Oct 2005 11:05:45 -0400, "Hilary Cotter"
<hilary.cotter@.gmail.com> wrote:

>Reapply the latest sp. There seems to be a problem with the sp setup program
>where it drops all the replication related procs, but somehow occasionally
>forgets to reinstall them.

Could not find stored procedure 'dbo.sp_MS_replication_installed'.

Dear all,
I want to add a new server as a publisher to an existing distributor,
but each time I try, I get this error:
Could not find stored procedure 'dbo.sp_MS_replication_installed'.
I also tried making this machine it's own distributor, but the same
error comes up.
Thanks in advance.
AramidAramid,
Does the proc exist?
Try:
USE MASTER
GO
IF OBJECT_ID('SP_MS_REPLICATION_INSTALLED')
IS NULL
PRINT 'PROC NOT INSTALLED'
ELSE
PRINT 'PROC INSTALLED'
Also, you may want to post this to:
http://www.microsoft.com/technet/co...ver.replication
HTH
Jerry
"Aramid" <aramid@.hotmail.com> wrote in message
news:6t8sl19hf5c6mbgphm3nubjhim3b6ncg7b@.
4ax.com...
> Dear all,
> I want to add a new server as a publisher to an existing distributor,
> but each time I try, I get this error:
> Could not find stored procedure 'dbo.sp_MS_replication_installed'.
> I also tried making this machine it's own distributor, but the same
> error comes up.
> Thanks in advance.
>
> Aramid

Could not find stored procedure 'dbo.sp_MS_replication_installed'.

Dear all,
I want to add a new server as a publisher to an existing distributor,
but each time I try, I get this error:
Could not find stored procedure 'dbo.sp_MS_replication_installed'.
I also tried making this machine it's own distributor, but the same
error comes up. :(
Thanks in advance.
AramidAramid,
Does the proc exist?
Try:
USE MASTER
GO
IF OBJECT_ID('SP_MS_REPLICATION_INSTALLED') IS NULL
PRINT 'PROC NOT INSTALLED'
ELSE
PRINT 'PROC INSTALLED'
Also, you may want to post this to:
http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/default.mspx?dg=microsoft.public.sqlserver.replication
HTH
Jerry
"Aramid" <aramid@.hotmail.com> wrote in message
news:6t8sl19hf5c6mbgphm3nubjhim3b6ncg7b@.4ax.com...
> Dear all,
> I want to add a new server as a publisher to an existing distributor,
> but each time I try, I get this error:
> Could not find stored procedure 'dbo.sp_MS_replication_installed'.
> I also tried making this machine it's own distributor, but the same
> error comes up. :(
> Thanks in advance.
>
> Aramid

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 drop procedure.

I have made transaction replication and it's working fine and now I want to
drop one procedure from publisher database but its gave me an error that you
can't drop the procedure b/c it's beeing used in Replication .. what should
I do? can any tell me .
Thanks in advance.
Noor
I am using the following commands but still it gave me an error.
sp_droparticle 'LMS','CmsUpdateIndividualTest', 1,1
Server: Msg 14046, Level 16, State 1, Procedure sp_droparticle, Line 161
Could not drop article. A subscription exists on it.
Any idea about this ?
Thanks
Noor
"Noorali Issani" <naissani@.softhome.net> wrote in message
news:eg%23cZgVEEHA.1600@.tk2msftngp13.phx.gbl...
> I have made transaction replication and it's working fine and now I want
to
> drop one procedure from publisher database but its gave me an error that
you
> can't drop the procedure b/c it's beeing used in Replication .. what
should
> I do? can any tell me .
> Thanks in advance.
> Noor
>
|||First you have to remove the article from any subscriptions that subscribe
to it. You can drop the subscription for that article ONLY:
Use pubs
go
sp_dropsubscription @.publication = 'pubs' , @.article ='authors',
@.subscriber='ALL'
Then drop the article from the publication:
sp_droparticle @.publication = 'pubs', @.article = 'authors'
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

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