Hi,
I have a local and a remote sql server that connect to remote via dial-up
connection.
In local server, I'm member of sysadmin server role but in remote server
just member of dbowner database role.
I create my publication on the local but when I want to create pull
subscription
at the subscriber(remote server) I get this error:User does not have
permission to perform this action(error 15247).
When I try to create push subscription from local server, the error is
something like: Cannot initialize the
subscription.
Any help would be greatly appreciated.
Thanks in advance.
Amin
Amin,
please check that your remote server's agent in the PAL on the publisher.
Also, that the subscriber been added to the list of potential subscribers
(sp_addsubscriber).
HTH,
Paul Ibison
|||Paul,
My local server is both publisher and distributor. All agents are running
locally. sa login is in PAL of my publication. Would you please write me
more detail.
Thanks,
Amin
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:uTbm#x7VEHA.584@.TK2MSFTNGP09.phx.gbl...
> Amin,
> please check that your remote server's agent in the PAL on the publisher.
> Also, that the subscriber been added to the list of potential subscribers
> (sp_addsubscriber).
> HTH,
> Paul Ibison
>
|||Amin,
when replicating between non-trusted domains, several configuration changes
are necessary compared to the normal setup. Please have a look at this
article, which explains them: http://support.microsoft.com/?id=321822.
You'll need to set up an alias, consider pass-through security or SQL
security and the account used on subscriber must be in the PAL on the
publisher. Also you might need to edit the HOSTS file to resolve the IP
address. To test at various stages, try to use Query Analyser on the
subscriber to connect to the publisher using the subscriber agent's login.
HTH,
Paul Ibison
Showing posts with label subscription. Show all posts
Showing posts with label subscription. Show all posts
Thursday, March 22, 2012
Wednesday, March 21, 2012
error 15004: Name cannot be NULL'
Hi,
I am tring to create a pull subscription from a server and
receiving an error '15004: Name cannot be NULL'. Is any
one knows hot to resolve this issue? Please help me.
Thanks,
PingPlease see my reply in the Replication group.
Paul Ibison
I am tring to create a pull subscription from a server and
receiving an error '15004: Name cannot be NULL'. Is any
one knows hot to resolve this issue? Please help me.
Thanks,
PingPlease see my reply in the Replication group.
Paul Ibison
error 15004: Name cannot be NULL'
Hi,
I am tring to create a pull subscription from a server and
receiving an error '15004: Name cannot be NULL'. Is any
one knows hot to resolve this issue? Please help me.
Thanks,
PingPlease see my reply in the Replication group.
Paul Ibison
I am tring to create a pull subscription from a server and
receiving an error '15004: Name cannot be NULL'. Is any
one knows hot to resolve this issue? Please help me.
Thanks,
PingPlease see my reply in the Replication group.
Paul Ibison
error 15004: Name cannot be NULL'
Hi,
I am tring to create a pull subscription from a server and
receiving an error '15004: Name cannot be NULL'. Is any
one knows hot to resolve this issue? Please help me.
Thanks,
Ping
Please see my reply in the Replication group.
Paul Ibison
sql
I am tring to create a pull subscription from a server and
receiving an error '15004: Name cannot be NULL'. Is any
one knows hot to resolve this issue? Please help me.
Thanks,
Ping
Please see my reply in the Replication group.
Paul Ibison
sql
Error 14262: specified @job_id... does not exist
Got a client who is getting this error when trying "Start synchronizing" on
a subscription in Enterprise Manager. When the subscription is run using the
Administrator account which originally created it, it runs OK. But when a
different account is being used, this error is thrown. Do subscriptions have
to be synchronized by the account which created them?
--
Mark
Is this a push or pull subscription? How is the subscription run?
The account should be in the PAL and the job owner should be the sa account.
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
"Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
news:OKJGoHeFGHA.516@.TK2MSFTNGP15.phx.gbl...
> Got a client who is getting this error when trying "Start synchronizing"
> on a subscription in Enterprise Manager. When the subscription is run
> using the Administrator account which originally created it, it runs OK.
> But when a different account is being used, this error is thrown. Do
> subscriptions have to be synchronized by the account which created them?
> --
> --
> Mark
>
|||It's a pull subscription to a merge replication.
--
Mark
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ukMaDdeFGHA.3056@.TK2MSFTNGP09.phx.gbl...
> Is this a push or pull subscription? How is the subscription run?
> The account should be in the PAL and the job owner should be the sa
> account.
> --
> 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
> "Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
> news:OKJGoHeFGHA.516@.TK2MSFTNGP15.phx.gbl...
>
|||I've seen this error when the subscription has been running, was deleted,
and then recreated. EM has cached the old job's information. Can you try a
refresh before trying to run the job again?
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
"Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
news:%23mzaXIpFGHA.2012@.TK2MSFTNGP14.phx.gbl...
> It's a pull subscription to a merge replication.
> --
> --
> Mark
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ukMaDdeFGHA.3056@.TK2MSFTNGP09.phx.gbl...
>
a subscription in Enterprise Manager. When the subscription is run using the
Administrator account which originally created it, it runs OK. But when a
different account is being used, this error is thrown. Do subscriptions have
to be synchronized by the account which created them?
--
Mark
Is this a push or pull subscription? How is the subscription run?
The account should be in the PAL and the job owner should be the sa account.
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
"Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
news:OKJGoHeFGHA.516@.TK2MSFTNGP15.phx.gbl...
> Got a client who is getting this error when trying "Start synchronizing"
> on a subscription in Enterprise Manager. When the subscription is run
> using the Administrator account which originally created it, it runs OK.
> But when a different account is being used, this error is thrown. Do
> subscriptions have to be synchronized by the account which created them?
> --
> --
> Mark
>
|||It's a pull subscription to a merge replication.
--
Mark
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ukMaDdeFGHA.3056@.TK2MSFTNGP09.phx.gbl...
> Is this a push or pull subscription? How is the subscription run?
> The account should be in the PAL and the job owner should be the sa
> account.
> --
> 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
> "Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
> news:OKJGoHeFGHA.516@.TK2MSFTNGP15.phx.gbl...
>
|||I've seen this error when the subscription has been running, was deleted,
and then recreated. EM has cached the old job's information. Can you try a
refresh before trying to run the job again?
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
"Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
news:%23mzaXIpFGHA.2012@.TK2MSFTNGP14.phx.gbl...
> It's a pull subscription to a merge replication.
> --
> --
> Mark
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ukMaDdeFGHA.3056@.TK2MSFTNGP09.phx.gbl...
>
Monday, March 19, 2012
Error 14058: The subscription already exists
Hi,
I've got the error in the Subject when I tried to delete and recreate
manually a pull subscription to a publication.
How can I delete defenitely the subscription from that database?
Thank you.
get your publication name and issue the following command in your
subscription database:
sp_droppullsubscription @.publisher = 'publisher' , @.publisher_db =
'publisher_db' ,[ @.publication = 'publication'
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
"Siu" <Siu@.discussions.microsoft.com> wrote in message
news:7957B486-16ED-498A-BAFC-2755E49555E1@.microsoft.com...
> Hi,
> I've got the error in the Subject when I tried to delete and recreate
> manually a pull subscription to a publication.
> How can I delete defenitely the subscription from that database?
> Thank you.
|||Hi Hilary,
thanks for your answer, but your code still gives the message that the
subscription doesn't exist... I'm also sure that I've written correctly all
the parameter, namely the publisher name, publisher db and the publication
name.
Do you think that there is another problem?
"Hilary Cotter" wrote:
> get your publication name and issue the following command in your
> subscription database:
> sp_droppullsubscription @.publisher = 'publisher' , @.publisher_db =
> 'publisher_db' ,[ @.publication = 'publication'
>
> --
> 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
> "Siu" <Siu@.discussions.microsoft.com> wrote in message
> news:7957B486-16ED-498A-BAFC-2755E49555E1@.microsoft.com...
>
>
|||Hi Hilary,
now I solved the problem: I had to delete the pull subscription manually
from the Publisher database.
I have another question: when I started the syncronitation, I got the
following error:
"The process could not connect to Disctributor 'MYDISTRIBUTOR'. Login failed
for user'
How can I discover which USER NAME failed the login?
"Hilary Cotter" wrote:
> get your publication name and issue the following command in your
> subscription database:
> sp_droppullsubscription @.publisher = 'publisher' , @.publisher_db =
> 'publisher_db' ,[ @.publication = 'publication'
>
> --
> 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
> "Siu" <Siu@.discussions.microsoft.com> wrote in message
> news:7957B486-16ED-498A-BAFC-2755E49555E1@.microsoft.com...
>
>
I've got the error in the Subject when I tried to delete and recreate
manually a pull subscription to a publication.
How can I delete defenitely the subscription from that database?
Thank you.
get your publication name and issue the following command in your
subscription database:
sp_droppullsubscription @.publisher = 'publisher' , @.publisher_db =
'publisher_db' ,[ @.publication = 'publication'
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
"Siu" <Siu@.discussions.microsoft.com> wrote in message
news:7957B486-16ED-498A-BAFC-2755E49555E1@.microsoft.com...
> Hi,
> I've got the error in the Subject when I tried to delete and recreate
> manually a pull subscription to a publication.
> How can I delete defenitely the subscription from that database?
> Thank you.
|||Hi Hilary,
thanks for your answer, but your code still gives the message that the
subscription doesn't exist... I'm also sure that I've written correctly all
the parameter, namely the publisher name, publisher db and the publication
name.
Do you think that there is another problem?
"Hilary Cotter" wrote:
> get your publication name and issue the following command in your
> subscription database:
> sp_droppullsubscription @.publisher = 'publisher' , @.publisher_db =
> 'publisher_db' ,[ @.publication = 'publication'
>
> --
> 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
> "Siu" <Siu@.discussions.microsoft.com> wrote in message
> news:7957B486-16ED-498A-BAFC-2755E49555E1@.microsoft.com...
>
>
|||Hi Hilary,
now I solved the problem: I had to delete the pull subscription manually
from the Publisher database.
I have another question: when I started the syncronitation, I got the
following error:
"The process could not connect to Disctributor 'MYDISTRIBUTOR'. Login failed
for user'
How can I discover which USER NAME failed the login?
"Hilary Cotter" wrote:
> get your publication name and issue the following command in your
> subscription database:
> sp_droppullsubscription @.publisher = 'publisher' , @.publisher_db =
> 'publisher_db' ,[ @.publication = 'publication'
>
> --
> 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
> "Siu" <Siu@.discussions.microsoft.com> wrote in message
> news:7957B486-16ED-498A-BAFC-2755E49555E1@.microsoft.com...
>
>
Labels:
database,
defenitely,
delete,
error,
exists,
ive,
microsoft,
mysql,
oracle,
publication,
pull,
recreatemanually,
server,
sql,
subject,
subscription
error 14058: The subscription already exists
Hi,
I am using merge replication. The subscriber is using pull subscription.
The problem is this; a subscriber machine has crashed. The problem is how
do i delete any evidence of the subscriber on the publisher, so that i can
create this subscriber again, without getting this error: "error 14058: The
subscription already exists"
Any assistance would be greatly appreciated.
Kind Regards
Warren Patterson
use this script on the subscriber, and then recreate and redistribute the
snapshot.
http://groups-beta.google.com/group/...a?dmode=source
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Warren Patterson" <des@.newsgroups.nospam> wrote in message
news:%23hZS85$8EHA.2012@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I am using merge replication. The subscriber is using pull subscription.
> The problem is this; a subscriber machine has crashed. The problem is how
> do i delete any evidence of the subscriber on the publisher, so that i can
> create this subscriber again, without getting this error: "error 14058:
The
> subscription already exists"
> Any assistance would be greatly appreciated.
>
> Kind Regards
> Warren Patterson
>
|||Hi Hilary,
Many thanks for you reply.
From what you have said in the link, this will delete all publications, I
have 4 other publications and 4 other subscriptions on the server, so
following that route would not be a good idea, if its going to remove all
publications and subscriptions.
Is there another way?
Kind Regards
Warren Patterson
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OCfuaAA9EHA.3596@.TK2MSFTNGP12.phx.gbl...
> use this script on the subscriber, and then recreate and redistribute the
> snapshot.
>
http://groups-beta.google.com/group/...a?dmode=source[vbcol=seagreen]
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "Warren Patterson" <des@.newsgroups.nospam> wrote in message
> news:%23hZS85$8EHA.2012@.TK2MSFTNGP15.phx.gbl...
how[vbcol=seagreen]
can
> The
>
|||I'll rewrite it to address a specific article publication. Could you tell me
the problem table/publication name?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Warren Patterson" <des@.newsgroups.nospam> wrote in message
news:OXud%23AI9EHA.2452@.TK2MSFTNGP14.phx.gbl...[vbcol=seagreen]
> Hi Hilary,
> Many thanks for you reply.
> From what you have said in the link, this will delete all publications, I
> have 4 other publications and 4 other subscriptions on the server, so
> following that route would not be a good idea, if its going to remove all
> publications and subscriptions.
> Is there another way?
> Kind Regards
> Warren Patterson
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:OCfuaAA9EHA.3596@.TK2MSFTNGP12.phx.gbl...
the
>
http://groups-beta.google.com/group/...a?dmode=source[vbcol=seagreen]
subscription.[vbcol=seagreen]
> how
> can
14058:
>
|||Hi Hilary,
That wont be necessary, I have managed to get around this. I simply copied
everything from the subscriber from the mssql\data folder and overwrote the
new subscriber mssql\data folder. Seemed to setup everything okay. But now
another problem has occurred, I will post this under a new topic, but for
now, its this
"the process could not query row metadata at the subscriber"
I have seen previous posts by yourself, mentioning to increase queryTimeout,
but this has not helped me in anyway. Do you have any other suggestions?
Please see my new post title "the process could not query row metadata at
the subscriber"
Many thanks again for your help.
Kind Regards
Warren
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uF82xYL9EHA.2900@.TK2MSFTNGP09.phx.gbl...
> I'll rewrite it to address a specific article publication. Could you tell
me[vbcol=seagreen]
> the problem table/publication name?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "Warren Patterson" <des@.newsgroups.nospam> wrote in message
> news:OXud%23AI9EHA.2452@.TK2MSFTNGP14.phx.gbl...
I[vbcol=seagreen]
all
> the
>
http://groups-beta.google.com/group/...a?dmode=source[vbcol=seagreen]
> subscription.
is[vbcol=seagreen]
i
> 14058:
>
|||Sorry regarding my previous post, I meant to say
".... Seemed to setup everything okay. But now another problem has
occurred, I will post this under a new topic, "the process could not query
row metadata at the subscriber"......"
"Warren Patterson" <des@.newsgroups.nospam> wrote in message
news:u0mCjax9EHA.3368@.TK2MSFTNGP15.phx.gbl...
> Hi Hilary,
> That wont be necessary, I have managed to get around this. I simply
copied
> everything from the subscriber from the mssql\data folder and overwrote
the
> new subscriber mssql\data folder. Seemed to setup everything okay. But
now
> another problem has occurred, I will post this under a new topic, but for
> now, its this
> "the process could not query row metadata at the subscriber"
> I have seen previous posts by yourself, mentioning to increase
queryTimeout,[vbcol=seagreen]
> but this has not helped me in anyway. Do you have any other suggestions?
> Please see my new post title "the process could not query row metadata at
> the subscriber"
> Many thanks again for your help.
> Kind Regards
> Warren
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:uF82xYL9EHA.2900@.TK2MSFTNGP09.phx.gbl...
tell[vbcol=seagreen]
> me
publications,[vbcol=seagreen]
> I
> all
redistribute
>
http://groups-beta.google.com/group/...a?dmode=source[vbcol=seagreen]
problem[vbcol=seagreen]
> is
that
> i
>
|||can you enable logging and see exactly what the final error is?
Also, you might want to try to drop this subscription, and then do a nosync
subscription
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Warren Patterson" <des@.newsgroups.nospam> wrote in message
news:eJ5euox9EHA.1392@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Sorry regarding my previous post, I meant to say
> ".... Seemed to setup everything okay. But now another problem has
> occurred, I will post this under a new topic, "the process could not query
> row metadata at the subscriber"......"
>
>
>
>
> "Warren Patterson" <des@.newsgroups.nospam> wrote in message
> news:u0mCjax9EHA.3368@.TK2MSFTNGP15.phx.gbl...
> copied
> the
> now
for[vbcol=seagreen]
> queryTimeout,
suggestions?[vbcol=seagreen]
at[vbcol=seagreen]
> tell
> publications,
so[vbcol=seagreen]
remove
> redistribute
>
http://groups-beta.google.com/group/...a?dmode=source
> problem
> that
>
|||Hi,
I enabled logging and this is the ouput (see below):
Kind Regards
Warren Patterson
************************************************** ****************
************************************************** ****************
************************************************** ****************
Microsoft SQL Server Merge Agent 8.00.760
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent:
GENCENTRIC_SVR1-TGPS_LIVE-TGPS_LIVE_GN-GOKWENORTHSVR1-TGPS_LIVE_GN_SUBSCRIPT
I- 0
Percent Complete: 0
Connecting to Subscriber 'GOKWENORTHSVR1'
Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION'
Server: GOKWENORTHSVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:27 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call
sp_MSgetversion }
[1/10/2005 4:28:27 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {?=call
sp_helpsubscription_properties (N'GENCENTRIC_SVR1', N'TGPS_LIVE',
N'TGPS_LIVE_GN')}
Distributor security mode: 0, login name: sa, password: ********.
[1/10/2005 4:28:27 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {?=call
sp_helpsubscription_properties (N'GENCENTRIC_SVR1', N'TGPS_LIVE',
N'TGPS_LIVE_GN')}
Publisher security mode: 0, login name: sa, password: *********.
Percent Complete: 0
Connecting to Distributor 'GENCENTRIC_SVR1'
Connecting to Distributor 'GENCENTRIC_SVR1.'
Server: GENCENTRIC_SVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:27 PM]GENCENTRIC_SVR1.: {call sp_MSgetversion }
[1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.: {call sp_helpdistpublisher
(N'GENCENTRIC_SVR1') }
[1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.distribution: select datasource, srvid
from master..sysservers where upper(srvname) = upper(N'GENCENTRIC_SVR1')
[1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.distribution: {call
sp_MSadd_merge_anonymous_agent(N'0', N'TGPS_LIVE', N'TGPS_LIVE_GN',
N'TGPS_LIVE_GN_SUBSCRIPTION', N'GOKWENORTHSVR1',?, 5587)}
[1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.distribution: {call sp_MShelp_profile
(34, 4, N'')}
Percent Complete: 0
Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
Initializing
Percent Complete: 1
Connecting to Publisher 'GENCENTRIC_SVR1'
Server: GENCENTRIC_SVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:31 PM]GENCENTRIC_SVR1.TGPS_LIVE: set nocount on declare
@.dbname sysname select @.dbname = db_name() declare @.collation nvarchar(255)
select @.collation = convert(nvarchar(255), databasepropertyex(@.dbname,
N'COLLATION')) select collationproperty(@.collation, N'CODEPAGE') as
'CodePage', collationproperty(@.collation, N'LCID') as 'LCID',
collationproperty(@.collation, N'COMPARISONSTYLE') as 'ComparisonStyle'
Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
Server: GENCENTRIC_SVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:31 PM]GENCENTRIC_SVR1.TGPS_LIVE: {call sp_MSgetversion }
Percent Complete: 3
Retrieving publication information
Percent Complete: 4
Retrieving subscription information
Percent Complete: 4
The merge process is cleaning up meta data in database 'TGPS_LIVE'.
Percent Complete: 4
The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s) in
MSmerge_contents, and 0 row(s) in MSmerge_tombstone.
Percent Complete: 4
The merge process is cleaning up meta data in database
'TGPS_LIVE_GN_SUBSCRIPTION'.
Percent Complete: 4
The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s) in
MSmerge_contents, and 0 row(s) in MSmerge_tombstone.
Percent Complete: 4
Uploading data changes to the Publisher
Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION'
Server: GOKWENORTHSVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:42 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call
sp_MSgetversion }
Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
Server: GENCENTRIC_SVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:42 PM]GENCENTRIC_SVR1.TGPS_LIVE: {call sp_MSgetversion }
Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION'
Server: GOKWENORTHSVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:43 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call
sp_MSgetversion }
Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
Server: GENCENTRIC_SVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:43 PM]GENCENTRIC_SVR1.TGPS_LIVE: {call sp_MSgetversion }
Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION'
Server: GOKWENORTHSVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:43 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call
sp_MSgetversion }
Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
Server: GENCENTRIC_SVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:43 PM]GENCENTRIC_SVR1.TGPS_LIVE: {call sp_MSgetversion }
Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION'
Server: GOKWENORTHSVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:43 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call
sp_MSgetversion }
Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
Server: GENCENTRIC_SVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:43 PM]GENCENTRIC_SVR1.TGPS_LIVE: {call sp_MSgetversion }
Percent Complete: 5
Processing article 'tbl_audit'
Percent Complete: 5
Processing article 'tbl_zone'
Percent Complete: 5
Processing article 'tbl_wool_pack_condition'
Percent Complete: 5
Processing article 'tbl_webfiles_update_log'
Percent Complete: 5
Processing article 'tbl_webfiles'
Percent Complete: 5
Processing article 'tbl_user_type_functionality_ref'
Percent Complete: 5
Processing article 'tbl_user_type_functionality'
Percent Complete: 5
Processing article 'tbl_user'
Percent Complete: 5
Processing article 'tbl_system_config'
Percent Complete: 5
Processing article 'tbl_stock_level'
Percent Complete: 5
Processing article 'tbl_input_price'
Percent Complete: 5
Processing article 'tbl_grower_own_transport_rate'
Percent Complete: 5
Processing article 'tbl_grower_invoice_header'
Percent Complete: 5
Processing article 'tbl_grower_invoice_detail'
Percent Complete: 5
Processing article 'tbl_grower_account'
Percent Complete: 5
Processing article 'tbl_grower'
Percent Complete: 5
Processing article 'tbl_group'
Percent Complete: 5
Processing article 'tbl_field_officer_zone'
Percent Complete: 5
Processing article 'tbl_field_officer'
Percent Complete: 5
Processing article 'tbl_error_log'
Percent Complete: 5
Processing article 'tbl_dm_file_list'
Percent Complete: 5
Processing article 'tbl_dm_expense_issue_to_syspro'
Percent Complete: 5
Processing article 'tbl_dm_cash_and_cheques_to_syspro'
Percent Complete: 5
Processing article 'tbl_depot_system_lockdown'
Percent Complete: 5
Processing article 'tbl_cotton_buying_price'
Percent Complete: 5
Processing article 'tbl_audit'
Percent Complete: 5
Processing article 'tbl_assessment_initial_season_header'
Percent Complete: 5
Processing article 'tbl_area'
Percent Complete: 5
No data needed to be merged.
Percent Complete: 5
Downloading data changes to the Subscriber
Percent Complete: 60
Processing article 'tbl_zone'
Percent Complete: 60
Processing article 'tbl_wool_pack_condition'
Percent Complete: 60
Processing article 'tbl_webfiles_update_log'
Percent Complete: 60
Processing article 'tbl_user'
Percent Complete: 60
Processing article 'tbl_system_config'
Percent Complete: 60
Processing article 'tbl_stock_level'
Percent Complete: 60
Processing article 'tbl_input_price'
Percent Complete: 60
Processing article 'tbl_grower_invoice_header'
Percent Complete: 60
Processing article 'tbl_grower_invoice_detail'
Percent Complete: 60
Processing article 'tbl_grower_account'
Percent Complete: 60
Processing article 'tbl_grower'
The process could not query row metadata at the 'Subscriber'.
The process could not enumerate changes at the 'Publisher'.
The merge process encountered an unexpected network error. The connection to
Subscriber 'GOKWENORTHSVR1' is no longer available.
Percent Complete: 0
The process could not query row metadata at the 'Subscriber'.
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147200996
Message: The process could not query row metadata at the 'Subscriber'.
Percent Complete: 0
Category:COMMAND
Source: Failed Command
Number: 0
Message: {call sp_MSgetmetadatabatch(?,?,?)}
Percent Complete: 0
Category:SQLSERVER
Source: GOKWENORTHSVR1
Number: 0
Message: Communication link failure
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147199469
Message: The process was successfully stopped.
Disconnecting from Publisher 'GENCENTRIC_SVR1'
Disconnecting from Subscriber 'GOKWENORTHSVR1'
Disconnecting from Publisher 'GENCENTRIC_SVR1'
Disconnecting from Publisher 'GENCENTRIC_SVR1'
Disconnecting from Publisher 'GENCENTRIC_SVR1'
Disconnecting from Publisher 'GENCENTRIC_SVR1'
Disconnecting from Subscriber 'GOKWENORTHSVR1'
Disconnecting from Subscriber 'GOKWENORTHSVR1'
Disconnecting from Subscriber 'GOKWENORTHSVR1'
Disconnecting from Subscriber 'GOKWENORTHSVR1'
Disconnecting from Publisher 'GENCENTRIC_SVR1'
Disconnecting from Distributor 'GENCENTRIC_SVR1'
************************************************** ****************
************************************************** ****************
************************************************** ****************
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uacxxpz9EHA.1408@.TK2MSFTNGP10.phx.gbl...
> can you enable logging and see exactly what the final error is?
> Also, you might want to try to drop this subscription, and then do a
nosync[vbcol=seagreen]
> subscription
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "Warren Patterson" <des@.newsgroups.nospam> wrote in message
> news:eJ5euox9EHA.1392@.tk2msftngp13.phx.gbl...
query[vbcol=seagreen]
overwrote[vbcol=seagreen]
But
> for
> suggestions?
> at
> so
> remove
>
http://groups-beta.google.com/group/...a?dmode=source[vbcol=seagreen]
so[vbcol=seagreen]
"error
>
|||Not to worry, problem located, seems that the a table is corrupt and causing
the "communication link failure" The error was very obscure, pointing me in
teh wrong direction, I thought it was a network issue, it wasnt, it was a
corrupt table.
Now I have the "joy" of trying to recover data :-(
"Warren Patterson" <des@.newsgroups.nospam> wrote in message
news:OoscZ869EHA.1396@.tk2msftngp13.phx.gbl...
> Hi,
> I enabled logging and this is the ouput (see below):
> Kind Regards
> Warren Patterson
>
> ************************************************** ****************
> ************************************************** ****************
> ************************************************** ****************
> Microsoft SQL Server Merge Agent 8.00.760
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent:
>
GENCENTRIC_SVR1-TGPS_LIVE-TGPS_LIVE_GN-GOKWENORTHSVR1-TGPS_LIVE_GN_SUBSCRIPT
> I- 0
> Percent Complete: 0
> Connecting to Subscriber 'GOKWENORTHSVR1'
> Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION'
> Server: GOKWENORTHSVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:27 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call
> sp_MSgetversion }
> [1/10/2005 4:28:27 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {?=call
> sp_helpsubscription_properties (N'GENCENTRIC_SVR1', N'TGPS_LIVE',
> N'TGPS_LIVE_GN')}
> Distributor security mode: 0, login name: sa, password: ********.
> [1/10/2005 4:28:27 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {?=call
> sp_helpsubscription_properties (N'GENCENTRIC_SVR1', N'TGPS_LIVE',
> N'TGPS_LIVE_GN')}
> Publisher security mode: 0, login name: sa, password: *********.
> Percent Complete: 0
> Connecting to Distributor 'GENCENTRIC_SVR1'
> Connecting to Distributor 'GENCENTRIC_SVR1.'
> Server: GENCENTRIC_SVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:27 PM]GENCENTRIC_SVR1.: {call sp_MSgetversion }
> [1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.: {call sp_helpdistpublisher
> (N'GENCENTRIC_SVR1') }
> [1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.distribution: select datasource,
srvid
> from master..sysservers where upper(srvname) = upper(N'GENCENTRIC_SVR1')
> [1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.distribution: {call
> sp_MSadd_merge_anonymous_agent(N'0', N'TGPS_LIVE', N'TGPS_LIVE_GN',
> N'TGPS_LIVE_GN_SUBSCRIPTION', N'GOKWENORTHSVR1',?, 5587)}
> [1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.distribution: {call
sp_MShelp_profile
> (34, 4, N'')}
> Percent Complete: 0
> Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
> Initializing
> Percent Complete: 1
> Connecting to Publisher 'GENCENTRIC_SVR1'
> Server: GENCENTRIC_SVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:31 PM]GENCENTRIC_SVR1.TGPS_LIVE: set nocount on declare
> @.dbname sysname select @.dbname = db_name() declare @.collation
nvarchar(255)
> select @.collation = convert(nvarchar(255), databasepropertyex(@.dbname,
> N'COLLATION')) select collationproperty(@.collation, N'CODEPAGE') as
> 'CodePage', collationproperty(@.collation, N'LCID') as 'LCID',
> collationproperty(@.collation, N'COMPARISONSTYLE') as 'ComparisonStyle'
> Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
> Server: GENCENTRIC_SVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:31 PM]GENCENTRIC_SVR1.TGPS_LIVE: {call sp_MSgetversion }
> Percent Complete: 3
> Retrieving publication information
> Percent Complete: 4
> Retrieving subscription information
> Percent Complete: 4
> The merge process is cleaning up meta data in database 'TGPS_LIVE'.
> Percent Complete: 4
> The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s) in
> MSmerge_contents, and 0 row(s) in MSmerge_tombstone.
> Percent Complete: 4
> The merge process is cleaning up meta data in database
> 'TGPS_LIVE_GN_SUBSCRIPTION'.
> Percent Complete: 4
> The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s) in
> MSmerge_contents, and 0 row(s) in MSmerge_tombstone.
> Percent Complete: 4
> Uploading data changes to the Publisher
> Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION'
> Server: GOKWENORTHSVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:42 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call
> sp_MSgetversion }
> Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
> Server: GENCENTRIC_SVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:42 PM]GENCENTRIC_SVR1.TGPS_LIVE: {call sp_MSgetversion }
> Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION'
> Server: GOKWENORTHSVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:43 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call
> sp_MSgetversion }
> Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
> Server: GENCENTRIC_SVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:43 PM]GENCENTRIC_SVR1.TGPS_LIVE: {call sp_MSgetversion }
> Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION'
> Server: GOKWENORTHSVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:43 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call
> sp_MSgetversion }
> Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
> Server: GENCENTRIC_SVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:43 PM]GENCENTRIC_SVR1.TGPS_LIVE: {call sp_MSgetversion }
> Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION'
> Server: GOKWENORTHSVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:43 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call
> sp_MSgetversion }
> Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
> Server: GENCENTRIC_SVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:43 PM]GENCENTRIC_SVR1.TGPS_LIVE: {call sp_MSgetversion }
> Percent Complete: 5
> Processing article 'tbl_audit'
> Percent Complete: 5
> Processing article 'tbl_zone'
> Percent Complete: 5
> Processing article 'tbl_wool_pack_condition'
> Percent Complete: 5
> Processing article 'tbl_webfiles_update_log'
> Percent Complete: 5
> Processing article 'tbl_webfiles'
> Percent Complete: 5
> Processing article 'tbl_user_type_functionality_ref'
> Percent Complete: 5
> Processing article 'tbl_user_type_functionality'
> Percent Complete: 5
> Processing article 'tbl_user'
> Percent Complete: 5
> Processing article 'tbl_system_config'
> Percent Complete: 5
> Processing article 'tbl_stock_level'
> Percent Complete: 5
> Processing article 'tbl_input_price'
> Percent Complete: 5
> Processing article 'tbl_grower_own_transport_rate'
> Percent Complete: 5
> Processing article 'tbl_grower_invoice_header'
> Percent Complete: 5
> Processing article 'tbl_grower_invoice_detail'
> Percent Complete: 5
> Processing article 'tbl_grower_account'
> Percent Complete: 5
> Processing article 'tbl_grower'
> Percent Complete: 5
> Processing article 'tbl_group'
> Percent Complete: 5
> Processing article 'tbl_field_officer_zone'
> Percent Complete: 5
> Processing article 'tbl_field_officer'
> Percent Complete: 5
> Processing article 'tbl_error_log'
> Percent Complete: 5
> Processing article 'tbl_dm_file_list'
> Percent Complete: 5
> Processing article 'tbl_dm_expense_issue_to_syspro'
> Percent Complete: 5
> Processing article 'tbl_dm_cash_and_cheques_to_syspro'
> Percent Complete: 5
> Processing article 'tbl_depot_system_lockdown'
> Percent Complete: 5
> Processing article 'tbl_cotton_buying_price'
> Percent Complete: 5
> Processing article 'tbl_audit'
> Percent Complete: 5
> Processing article 'tbl_assessment_initial_season_header'
> Percent Complete: 5
> Processing article 'tbl_area'
> Percent Complete: 5
> No data needed to be merged.
> Percent Complete: 5
> Downloading data changes to the Subscriber
> Percent Complete: 60
> Processing article 'tbl_zone'
> Percent Complete: 60
> Processing article 'tbl_wool_pack_condition'
> Percent Complete: 60
> Processing article 'tbl_webfiles_update_log'
> Percent Complete: 60
> Processing article 'tbl_user'
> Percent Complete: 60
> Processing article 'tbl_system_config'
> Percent Complete: 60
> Processing article 'tbl_stock_level'
> Percent Complete: 60
> Processing article 'tbl_input_price'
> Percent Complete: 60
> Processing article 'tbl_grower_invoice_header'
> Percent Complete: 60
> Processing article 'tbl_grower_invoice_detail'
> Percent Complete: 60
> Processing article 'tbl_grower_account'
> Percent Complete: 60
> Processing article 'tbl_grower'
> The process could not query row metadata at the 'Subscriber'.
> The process could not enumerate changes at the 'Publisher'.
> The merge process encountered an unexpected network error. The connection
to[vbcol=seagreen]
> Subscriber 'GOKWENORTHSVR1' is no longer available.
> Percent Complete: 0
> The process could not query row metadata at the 'Subscriber'.
> Percent Complete: 0
> Category:NULL
> Source: Merge Replication Provider
> Number: -2147200996
> Message: The process could not query row metadata at the 'Subscriber'.
> Percent Complete: 0
> Category:COMMAND
> Source: Failed Command
> Number: 0
> Message: {call sp_MSgetmetadatabatch(?,?,?)}
> Percent Complete: 0
> Category:SQLSERVER
> Source: GOKWENORTHSVR1
> Number: 0
> Message: Communication link failure
> Percent Complete: 0
> Category:NULL
> Source: Merge Replication Provider
> Number: -2147199469
> Message: The process was successfully stopped.
> Disconnecting from Publisher 'GENCENTRIC_SVR1'
> Disconnecting from Subscriber 'GOKWENORTHSVR1'
> Disconnecting from Publisher 'GENCENTRIC_SVR1'
> Disconnecting from Publisher 'GENCENTRIC_SVR1'
> Disconnecting from Publisher 'GENCENTRIC_SVR1'
> Disconnecting from Publisher 'GENCENTRIC_SVR1'
> Disconnecting from Subscriber 'GOKWENORTHSVR1'
> Disconnecting from Subscriber 'GOKWENORTHSVR1'
> Disconnecting from Subscriber 'GOKWENORTHSVR1'
> Disconnecting from Subscriber 'GOKWENORTHSVR1'
> Disconnecting from Publisher 'GENCENTRIC_SVR1'
> Disconnecting from Distributor 'GENCENTRIC_SVR1'
>
> ************************************************** ****************
> ************************************************** ****************
> ************************************************** ****************
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:uacxxpz9EHA.1408@.TK2MSFTNGP10.phx.gbl...
> nosync
> query
simply[vbcol=seagreen]
> overwrote
> But
but[vbcol=seagreen]
metadata[vbcol=seagreen]
you[vbcol=seagreen]
server,
>
http://groups-beta.google.com/group/...a?dmode=source
> so
> "error
>
I am using merge replication. The subscriber is using pull subscription.
The problem is this; a subscriber machine has crashed. The problem is how
do i delete any evidence of the subscriber on the publisher, so that i can
create this subscriber again, without getting this error: "error 14058: The
subscription already exists"
Any assistance would be greatly appreciated.
Kind Regards
Warren Patterson
use this script on the subscriber, and then recreate and redistribute the
snapshot.
http://groups-beta.google.com/group/...a?dmode=source
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Warren Patterson" <des@.newsgroups.nospam> wrote in message
news:%23hZS85$8EHA.2012@.TK2MSFTNGP15.phx.gbl...
> Hi,
> I am using merge replication. The subscriber is using pull subscription.
> The problem is this; a subscriber machine has crashed. The problem is how
> do i delete any evidence of the subscriber on the publisher, so that i can
> create this subscriber again, without getting this error: "error 14058:
The
> subscription already exists"
> Any assistance would be greatly appreciated.
>
> Kind Regards
> Warren Patterson
>
|||Hi Hilary,
Many thanks for you reply.
From what you have said in the link, this will delete all publications, I
have 4 other publications and 4 other subscriptions on the server, so
following that route would not be a good idea, if its going to remove all
publications and subscriptions.
Is there another way?
Kind Regards
Warren Patterson
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OCfuaAA9EHA.3596@.TK2MSFTNGP12.phx.gbl...
> use this script on the subscriber, and then recreate and redistribute the
> snapshot.
>
http://groups-beta.google.com/group/...a?dmode=source[vbcol=seagreen]
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "Warren Patterson" <des@.newsgroups.nospam> wrote in message
> news:%23hZS85$8EHA.2012@.TK2MSFTNGP15.phx.gbl...
how[vbcol=seagreen]
can
> The
>
|||I'll rewrite it to address a specific article publication. Could you tell me
the problem table/publication name?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Warren Patterson" <des@.newsgroups.nospam> wrote in message
news:OXud%23AI9EHA.2452@.TK2MSFTNGP14.phx.gbl...[vbcol=seagreen]
> Hi Hilary,
> Many thanks for you reply.
> From what you have said in the link, this will delete all publications, I
> have 4 other publications and 4 other subscriptions on the server, so
> following that route would not be a good idea, if its going to remove all
> publications and subscriptions.
> Is there another way?
> Kind Regards
> Warren Patterson
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:OCfuaAA9EHA.3596@.TK2MSFTNGP12.phx.gbl...
the
>
http://groups-beta.google.com/group/...a?dmode=source[vbcol=seagreen]
subscription.[vbcol=seagreen]
> how
> can
14058:
>
|||Hi Hilary,
That wont be necessary, I have managed to get around this. I simply copied
everything from the subscriber from the mssql\data folder and overwrote the
new subscriber mssql\data folder. Seemed to setup everything okay. But now
another problem has occurred, I will post this under a new topic, but for
now, its this
"the process could not query row metadata at the subscriber"
I have seen previous posts by yourself, mentioning to increase queryTimeout,
but this has not helped me in anyway. Do you have any other suggestions?
Please see my new post title "the process could not query row metadata at
the subscriber"
Many thanks again for your help.
Kind Regards
Warren
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uF82xYL9EHA.2900@.TK2MSFTNGP09.phx.gbl...
> I'll rewrite it to address a specific article publication. Could you tell
me[vbcol=seagreen]
> the problem table/publication name?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "Warren Patterson" <des@.newsgroups.nospam> wrote in message
> news:OXud%23AI9EHA.2452@.TK2MSFTNGP14.phx.gbl...
I[vbcol=seagreen]
all
> the
>
http://groups-beta.google.com/group/...a?dmode=source[vbcol=seagreen]
> subscription.
is[vbcol=seagreen]
i
> 14058:
>
|||Sorry regarding my previous post, I meant to say
".... Seemed to setup everything okay. But now another problem has
occurred, I will post this under a new topic, "the process could not query
row metadata at the subscriber"......"
"Warren Patterson" <des@.newsgroups.nospam> wrote in message
news:u0mCjax9EHA.3368@.TK2MSFTNGP15.phx.gbl...
> Hi Hilary,
> That wont be necessary, I have managed to get around this. I simply
copied
> everything from the subscriber from the mssql\data folder and overwrote
the
> new subscriber mssql\data folder. Seemed to setup everything okay. But
now
> another problem has occurred, I will post this under a new topic, but for
> now, its this
> "the process could not query row metadata at the subscriber"
> I have seen previous posts by yourself, mentioning to increase
queryTimeout,[vbcol=seagreen]
> but this has not helped me in anyway. Do you have any other suggestions?
> Please see my new post title "the process could not query row metadata at
> the subscriber"
> Many thanks again for your help.
> Kind Regards
> Warren
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:uF82xYL9EHA.2900@.TK2MSFTNGP09.phx.gbl...
tell[vbcol=seagreen]
> me
publications,[vbcol=seagreen]
> I
> all
redistribute
>
http://groups-beta.google.com/group/...a?dmode=source[vbcol=seagreen]
problem[vbcol=seagreen]
> is
that
> i
>
|||can you enable logging and see exactly what the final error is?
Also, you might want to try to drop this subscription, and then do a nosync
subscription
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Warren Patterson" <des@.newsgroups.nospam> wrote in message
news:eJ5euox9EHA.1392@.tk2msftngp13.phx.gbl...[vbcol=seagreen]
> Sorry regarding my previous post, I meant to say
> ".... Seemed to setup everything okay. But now another problem has
> occurred, I will post this under a new topic, "the process could not query
> row metadata at the subscriber"......"
>
>
>
>
> "Warren Patterson" <des@.newsgroups.nospam> wrote in message
> news:u0mCjax9EHA.3368@.TK2MSFTNGP15.phx.gbl...
> copied
> the
> now
for[vbcol=seagreen]
> queryTimeout,
suggestions?[vbcol=seagreen]
at[vbcol=seagreen]
> tell
> publications,
so[vbcol=seagreen]
remove
> redistribute
>
http://groups-beta.google.com/group/...a?dmode=source
> problem
> that
>
|||Hi,
I enabled logging and this is the ouput (see below):
Kind Regards
Warren Patterson
************************************************** ****************
************************************************** ****************
************************************************** ****************
Microsoft SQL Server Merge Agent 8.00.760
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent:
GENCENTRIC_SVR1-TGPS_LIVE-TGPS_LIVE_GN-GOKWENORTHSVR1-TGPS_LIVE_GN_SUBSCRIPT
I- 0
Percent Complete: 0
Connecting to Subscriber 'GOKWENORTHSVR1'
Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION'
Server: GOKWENORTHSVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:27 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call
sp_MSgetversion }
[1/10/2005 4:28:27 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {?=call
sp_helpsubscription_properties (N'GENCENTRIC_SVR1', N'TGPS_LIVE',
N'TGPS_LIVE_GN')}
Distributor security mode: 0, login name: sa, password: ********.
[1/10/2005 4:28:27 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {?=call
sp_helpsubscription_properties (N'GENCENTRIC_SVR1', N'TGPS_LIVE',
N'TGPS_LIVE_GN')}
Publisher security mode: 0, login name: sa, password: *********.
Percent Complete: 0
Connecting to Distributor 'GENCENTRIC_SVR1'
Connecting to Distributor 'GENCENTRIC_SVR1.'
Server: GENCENTRIC_SVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:27 PM]GENCENTRIC_SVR1.: {call sp_MSgetversion }
[1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.: {call sp_helpdistpublisher
(N'GENCENTRIC_SVR1') }
[1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.distribution: select datasource, srvid
from master..sysservers where upper(srvname) = upper(N'GENCENTRIC_SVR1')
[1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.distribution: {call
sp_MSadd_merge_anonymous_agent(N'0', N'TGPS_LIVE', N'TGPS_LIVE_GN',
N'TGPS_LIVE_GN_SUBSCRIPTION', N'GOKWENORTHSVR1',?, 5587)}
[1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.distribution: {call sp_MShelp_profile
(34, 4, N'')}
Percent Complete: 0
Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
Initializing
Percent Complete: 1
Connecting to Publisher 'GENCENTRIC_SVR1'
Server: GENCENTRIC_SVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:31 PM]GENCENTRIC_SVR1.TGPS_LIVE: set nocount on declare
@.dbname sysname select @.dbname = db_name() declare @.collation nvarchar(255)
select @.collation = convert(nvarchar(255), databasepropertyex(@.dbname,
N'COLLATION')) select collationproperty(@.collation, N'CODEPAGE') as
'CodePage', collationproperty(@.collation, N'LCID') as 'LCID',
collationproperty(@.collation, N'COMPARISONSTYLE') as 'ComparisonStyle'
Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
Server: GENCENTRIC_SVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:31 PM]GENCENTRIC_SVR1.TGPS_LIVE: {call sp_MSgetversion }
Percent Complete: 3
Retrieving publication information
Percent Complete: 4
Retrieving subscription information
Percent Complete: 4
The merge process is cleaning up meta data in database 'TGPS_LIVE'.
Percent Complete: 4
The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s) in
MSmerge_contents, and 0 row(s) in MSmerge_tombstone.
Percent Complete: 4
The merge process is cleaning up meta data in database
'TGPS_LIVE_GN_SUBSCRIPTION'.
Percent Complete: 4
The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s) in
MSmerge_contents, and 0 row(s) in MSmerge_tombstone.
Percent Complete: 4
Uploading data changes to the Publisher
Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION'
Server: GOKWENORTHSVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:42 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call
sp_MSgetversion }
Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
Server: GENCENTRIC_SVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:42 PM]GENCENTRIC_SVR1.TGPS_LIVE: {call sp_MSgetversion }
Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION'
Server: GOKWENORTHSVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:43 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call
sp_MSgetversion }
Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
Server: GENCENTRIC_SVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:43 PM]GENCENTRIC_SVR1.TGPS_LIVE: {call sp_MSgetversion }
Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION'
Server: GOKWENORTHSVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:43 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call
sp_MSgetversion }
Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
Server: GENCENTRIC_SVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:43 PM]GENCENTRIC_SVR1.TGPS_LIVE: {call sp_MSgetversion }
Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION'
Server: GOKWENORTHSVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:43 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call
sp_MSgetversion }
Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
Server: GENCENTRIC_SVR1
DBMS: Microsoft SQL Server
Version: 08.00.0760
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
[1/10/2005 4:28:43 PM]GENCENTRIC_SVR1.TGPS_LIVE: {call sp_MSgetversion }
Percent Complete: 5
Processing article 'tbl_audit'
Percent Complete: 5
Processing article 'tbl_zone'
Percent Complete: 5
Processing article 'tbl_wool_pack_condition'
Percent Complete: 5
Processing article 'tbl_webfiles_update_log'
Percent Complete: 5
Processing article 'tbl_webfiles'
Percent Complete: 5
Processing article 'tbl_user_type_functionality_ref'
Percent Complete: 5
Processing article 'tbl_user_type_functionality'
Percent Complete: 5
Processing article 'tbl_user'
Percent Complete: 5
Processing article 'tbl_system_config'
Percent Complete: 5
Processing article 'tbl_stock_level'
Percent Complete: 5
Processing article 'tbl_input_price'
Percent Complete: 5
Processing article 'tbl_grower_own_transport_rate'
Percent Complete: 5
Processing article 'tbl_grower_invoice_header'
Percent Complete: 5
Processing article 'tbl_grower_invoice_detail'
Percent Complete: 5
Processing article 'tbl_grower_account'
Percent Complete: 5
Processing article 'tbl_grower'
Percent Complete: 5
Processing article 'tbl_group'
Percent Complete: 5
Processing article 'tbl_field_officer_zone'
Percent Complete: 5
Processing article 'tbl_field_officer'
Percent Complete: 5
Processing article 'tbl_error_log'
Percent Complete: 5
Processing article 'tbl_dm_file_list'
Percent Complete: 5
Processing article 'tbl_dm_expense_issue_to_syspro'
Percent Complete: 5
Processing article 'tbl_dm_cash_and_cheques_to_syspro'
Percent Complete: 5
Processing article 'tbl_depot_system_lockdown'
Percent Complete: 5
Processing article 'tbl_cotton_buying_price'
Percent Complete: 5
Processing article 'tbl_audit'
Percent Complete: 5
Processing article 'tbl_assessment_initial_season_header'
Percent Complete: 5
Processing article 'tbl_area'
Percent Complete: 5
No data needed to be merged.
Percent Complete: 5
Downloading data changes to the Subscriber
Percent Complete: 60
Processing article 'tbl_zone'
Percent Complete: 60
Processing article 'tbl_wool_pack_condition'
Percent Complete: 60
Processing article 'tbl_webfiles_update_log'
Percent Complete: 60
Processing article 'tbl_user'
Percent Complete: 60
Processing article 'tbl_system_config'
Percent Complete: 60
Processing article 'tbl_stock_level'
Percent Complete: 60
Processing article 'tbl_input_price'
Percent Complete: 60
Processing article 'tbl_grower_invoice_header'
Percent Complete: 60
Processing article 'tbl_grower_invoice_detail'
Percent Complete: 60
Processing article 'tbl_grower_account'
Percent Complete: 60
Processing article 'tbl_grower'
The process could not query row metadata at the 'Subscriber'.
The process could not enumerate changes at the 'Publisher'.
The merge process encountered an unexpected network error. The connection to
Subscriber 'GOKWENORTHSVR1' is no longer available.
Percent Complete: 0
The process could not query row metadata at the 'Subscriber'.
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147200996
Message: The process could not query row metadata at the 'Subscriber'.
Percent Complete: 0
Category:COMMAND
Source: Failed Command
Number: 0
Message: {call sp_MSgetmetadatabatch(?,?,?)}
Percent Complete: 0
Category:SQLSERVER
Source: GOKWENORTHSVR1
Number: 0
Message: Communication link failure
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147199469
Message: The process was successfully stopped.
Disconnecting from Publisher 'GENCENTRIC_SVR1'
Disconnecting from Subscriber 'GOKWENORTHSVR1'
Disconnecting from Publisher 'GENCENTRIC_SVR1'
Disconnecting from Publisher 'GENCENTRIC_SVR1'
Disconnecting from Publisher 'GENCENTRIC_SVR1'
Disconnecting from Publisher 'GENCENTRIC_SVR1'
Disconnecting from Subscriber 'GOKWENORTHSVR1'
Disconnecting from Subscriber 'GOKWENORTHSVR1'
Disconnecting from Subscriber 'GOKWENORTHSVR1'
Disconnecting from Subscriber 'GOKWENORTHSVR1'
Disconnecting from Publisher 'GENCENTRIC_SVR1'
Disconnecting from Distributor 'GENCENTRIC_SVR1'
************************************************** ****************
************************************************** ****************
************************************************** ****************
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uacxxpz9EHA.1408@.TK2MSFTNGP10.phx.gbl...
> can you enable logging and see exactly what the final error is?
> Also, you might want to try to drop this subscription, and then do a
nosync[vbcol=seagreen]
> subscription
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> "Warren Patterson" <des@.newsgroups.nospam> wrote in message
> news:eJ5euox9EHA.1392@.tk2msftngp13.phx.gbl...
query[vbcol=seagreen]
overwrote[vbcol=seagreen]
But
> for
> suggestions?
> at
> so
> remove
>
http://groups-beta.google.com/group/...a?dmode=source[vbcol=seagreen]
so[vbcol=seagreen]
"error
>
|||Not to worry, problem located, seems that the a table is corrupt and causing
the "communication link failure" The error was very obscure, pointing me in
teh wrong direction, I thought it was a network issue, it wasnt, it was a
corrupt table.
Now I have the "joy" of trying to recover data :-(
"Warren Patterson" <des@.newsgroups.nospam> wrote in message
news:OoscZ869EHA.1396@.tk2msftngp13.phx.gbl...
> Hi,
> I enabled logging and this is the ouput (see below):
> Kind Regards
> Warren Patterson
>
> ************************************************** ****************
> ************************************************** ****************
> ************************************************** ****************
> Microsoft SQL Server Merge Agent 8.00.760
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent:
>
GENCENTRIC_SVR1-TGPS_LIVE-TGPS_LIVE_GN-GOKWENORTHSVR1-TGPS_LIVE_GN_SUBSCRIPT
> I- 0
> Percent Complete: 0
> Connecting to Subscriber 'GOKWENORTHSVR1'
> Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION'
> Server: GOKWENORTHSVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:27 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call
> sp_MSgetversion }
> [1/10/2005 4:28:27 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {?=call
> sp_helpsubscription_properties (N'GENCENTRIC_SVR1', N'TGPS_LIVE',
> N'TGPS_LIVE_GN')}
> Distributor security mode: 0, login name: sa, password: ********.
> [1/10/2005 4:28:27 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {?=call
> sp_helpsubscription_properties (N'GENCENTRIC_SVR1', N'TGPS_LIVE',
> N'TGPS_LIVE_GN')}
> Publisher security mode: 0, login name: sa, password: *********.
> Percent Complete: 0
> Connecting to Distributor 'GENCENTRIC_SVR1'
> Connecting to Distributor 'GENCENTRIC_SVR1.'
> Server: GENCENTRIC_SVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:27 PM]GENCENTRIC_SVR1.: {call sp_MSgetversion }
> [1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.: {call sp_helpdistpublisher
> (N'GENCENTRIC_SVR1') }
> [1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.distribution: select datasource,
srvid
> from master..sysservers where upper(srvname) = upper(N'GENCENTRIC_SVR1')
> [1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.distribution: {call
> sp_MSadd_merge_anonymous_agent(N'0', N'TGPS_LIVE', N'TGPS_LIVE_GN',
> N'TGPS_LIVE_GN_SUBSCRIPTION', N'GOKWENORTHSVR1',?, 5587)}
> [1/10/2005 4:28:28 PM]GENCENTRIC_SVR1.distribution: {call
sp_MShelp_profile
> (34, 4, N'')}
> Percent Complete: 0
> Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
> Initializing
> Percent Complete: 1
> Connecting to Publisher 'GENCENTRIC_SVR1'
> Server: GENCENTRIC_SVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:31 PM]GENCENTRIC_SVR1.TGPS_LIVE: set nocount on declare
> @.dbname sysname select @.dbname = db_name() declare @.collation
nvarchar(255)
> select @.collation = convert(nvarchar(255), databasepropertyex(@.dbname,
> N'COLLATION')) select collationproperty(@.collation, N'CODEPAGE') as
> 'CodePage', collationproperty(@.collation, N'LCID') as 'LCID',
> collationproperty(@.collation, N'COMPARISONSTYLE') as 'ComparisonStyle'
> Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
> Server: GENCENTRIC_SVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:31 PM]GENCENTRIC_SVR1.TGPS_LIVE: {call sp_MSgetversion }
> Percent Complete: 3
> Retrieving publication information
> Percent Complete: 4
> Retrieving subscription information
> Percent Complete: 4
> The merge process is cleaning up meta data in database 'TGPS_LIVE'.
> Percent Complete: 4
> The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s) in
> MSmerge_contents, and 0 row(s) in MSmerge_tombstone.
> Percent Complete: 4
> The merge process is cleaning up meta data in database
> 'TGPS_LIVE_GN_SUBSCRIPTION'.
> Percent Complete: 4
> The merge process cleaned up 0 row(s) in MSmerge_genhistory, 0 row(s) in
> MSmerge_contents, and 0 row(s) in MSmerge_tombstone.
> Percent Complete: 4
> Uploading data changes to the Publisher
> Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION'
> Server: GOKWENORTHSVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:42 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call
> sp_MSgetversion }
> Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
> Server: GENCENTRIC_SVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:42 PM]GENCENTRIC_SVR1.TGPS_LIVE: {call sp_MSgetversion }
> Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION'
> Server: GOKWENORTHSVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:43 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call
> sp_MSgetversion }
> Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
> Server: GENCENTRIC_SVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:43 PM]GENCENTRIC_SVR1.TGPS_LIVE: {call sp_MSgetversion }
> Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION'
> Server: GOKWENORTHSVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:43 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call
> sp_MSgetversion }
> Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
> Server: GENCENTRIC_SVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:43 PM]GENCENTRIC_SVR1.TGPS_LIVE: {call sp_MSgetversion }
> Connecting to Subscriber 'GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION'
> Server: GOKWENORTHSVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:43 PM]GOKWENORTHSVR1.TGPS_LIVE_GN_SUBSCRIPTION: {call
> sp_MSgetversion }
> Connecting to Publisher 'GENCENTRIC_SVR1.TGPS_LIVE'
> Server: GENCENTRIC_SVR1
> DBMS: Microsoft SQL Server
> Version: 08.00.0760
> 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
> [1/10/2005 4:28:43 PM]GENCENTRIC_SVR1.TGPS_LIVE: {call sp_MSgetversion }
> Percent Complete: 5
> Processing article 'tbl_audit'
> Percent Complete: 5
> Processing article 'tbl_zone'
> Percent Complete: 5
> Processing article 'tbl_wool_pack_condition'
> Percent Complete: 5
> Processing article 'tbl_webfiles_update_log'
> Percent Complete: 5
> Processing article 'tbl_webfiles'
> Percent Complete: 5
> Processing article 'tbl_user_type_functionality_ref'
> Percent Complete: 5
> Processing article 'tbl_user_type_functionality'
> Percent Complete: 5
> Processing article 'tbl_user'
> Percent Complete: 5
> Processing article 'tbl_system_config'
> Percent Complete: 5
> Processing article 'tbl_stock_level'
> Percent Complete: 5
> Processing article 'tbl_input_price'
> Percent Complete: 5
> Processing article 'tbl_grower_own_transport_rate'
> Percent Complete: 5
> Processing article 'tbl_grower_invoice_header'
> Percent Complete: 5
> Processing article 'tbl_grower_invoice_detail'
> Percent Complete: 5
> Processing article 'tbl_grower_account'
> Percent Complete: 5
> Processing article 'tbl_grower'
> Percent Complete: 5
> Processing article 'tbl_group'
> Percent Complete: 5
> Processing article 'tbl_field_officer_zone'
> Percent Complete: 5
> Processing article 'tbl_field_officer'
> Percent Complete: 5
> Processing article 'tbl_error_log'
> Percent Complete: 5
> Processing article 'tbl_dm_file_list'
> Percent Complete: 5
> Processing article 'tbl_dm_expense_issue_to_syspro'
> Percent Complete: 5
> Processing article 'tbl_dm_cash_and_cheques_to_syspro'
> Percent Complete: 5
> Processing article 'tbl_depot_system_lockdown'
> Percent Complete: 5
> Processing article 'tbl_cotton_buying_price'
> Percent Complete: 5
> Processing article 'tbl_audit'
> Percent Complete: 5
> Processing article 'tbl_assessment_initial_season_header'
> Percent Complete: 5
> Processing article 'tbl_area'
> Percent Complete: 5
> No data needed to be merged.
> Percent Complete: 5
> Downloading data changes to the Subscriber
> Percent Complete: 60
> Processing article 'tbl_zone'
> Percent Complete: 60
> Processing article 'tbl_wool_pack_condition'
> Percent Complete: 60
> Processing article 'tbl_webfiles_update_log'
> Percent Complete: 60
> Processing article 'tbl_user'
> Percent Complete: 60
> Processing article 'tbl_system_config'
> Percent Complete: 60
> Processing article 'tbl_stock_level'
> Percent Complete: 60
> Processing article 'tbl_input_price'
> Percent Complete: 60
> Processing article 'tbl_grower_invoice_header'
> Percent Complete: 60
> Processing article 'tbl_grower_invoice_detail'
> Percent Complete: 60
> Processing article 'tbl_grower_account'
> Percent Complete: 60
> Processing article 'tbl_grower'
> The process could not query row metadata at the 'Subscriber'.
> The process could not enumerate changes at the 'Publisher'.
> The merge process encountered an unexpected network error. The connection
to[vbcol=seagreen]
> Subscriber 'GOKWENORTHSVR1' is no longer available.
> Percent Complete: 0
> The process could not query row metadata at the 'Subscriber'.
> Percent Complete: 0
> Category:NULL
> Source: Merge Replication Provider
> Number: -2147200996
> Message: The process could not query row metadata at the 'Subscriber'.
> Percent Complete: 0
> Category:COMMAND
> Source: Failed Command
> Number: 0
> Message: {call sp_MSgetmetadatabatch(?,?,?)}
> Percent Complete: 0
> Category:SQLSERVER
> Source: GOKWENORTHSVR1
> Number: 0
> Message: Communication link failure
> Percent Complete: 0
> Category:NULL
> Source: Merge Replication Provider
> Number: -2147199469
> Message: The process was successfully stopped.
> Disconnecting from Publisher 'GENCENTRIC_SVR1'
> Disconnecting from Subscriber 'GOKWENORTHSVR1'
> Disconnecting from Publisher 'GENCENTRIC_SVR1'
> Disconnecting from Publisher 'GENCENTRIC_SVR1'
> Disconnecting from Publisher 'GENCENTRIC_SVR1'
> Disconnecting from Publisher 'GENCENTRIC_SVR1'
> Disconnecting from Subscriber 'GOKWENORTHSVR1'
> Disconnecting from Subscriber 'GOKWENORTHSVR1'
> Disconnecting from Subscriber 'GOKWENORTHSVR1'
> Disconnecting from Subscriber 'GOKWENORTHSVR1'
> Disconnecting from Publisher 'GENCENTRIC_SVR1'
> Disconnecting from Distributor 'GENCENTRIC_SVR1'
>
> ************************************************** ****************
> ************************************************** ****************
> ************************************************** ****************
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:uacxxpz9EHA.1408@.TK2MSFTNGP10.phx.gbl...
> nosync
> query
simply[vbcol=seagreen]
> overwrote
> But
but[vbcol=seagreen]
metadata[vbcol=seagreen]
you[vbcol=seagreen]
server,
>
http://groups-beta.google.com/group/...a?dmode=source
> so
> "error
>
Labels:
crashed,
database,
error,
exists,
machine,
merge,
microsoft,
mysql,
oracle,
pull,
replication,
server,
sql,
subscriber,
subscription
Error 14046: Could not drop article.
Error 14046: Could not drop article. A subscription exists on it.
I get the above error when I try to drop a publication in SQL2k. I do not
show any subscriptions for this publication anywhere. How can I find the
subscription that is blocking me from dropping this publication?
Nevermind, I got it.
In distribution..MSsubscriptions, I found the "rogue" entry, causing this
error. I deleted it, and was then able to successfully delete the
publication.
"JAdams" wrote:
> Error 14046: Could not drop article. A subscription exists on it.
> I get the above error when I try to drop a publication in SQL2k. I do not
> show any subscriptions for this publication anywhere. How can I find the
> subscription that is blocking me from dropping this publication?
I get the above error when I try to drop a publication in SQL2k. I do not
show any subscriptions for this publication anywhere. How can I find the
subscription that is blocking me from dropping this publication?
Nevermind, I got it.
In distribution..MSsubscriptions, I found the "rogue" entry, causing this
error. I deleted it, and was then able to successfully delete the
publication.
"JAdams" wrote:
> Error 14046: Could not drop article. A subscription exists on it.
> I get the above error when I try to drop a publication in SQL2k. I do not
> show any subscriptions for this publication anywhere. How can I find the
> subscription that is blocking me from dropping this publication?
Sunday, February 19, 2012
ERROR - Subscription Failure (Please Help!)
The report subscription is returning the following error message.
How should I resolve this issue?
However, according to the Job executed, the process was successful but the
report manager is displaying the following.
ERROR:
Failure sending mail: The report server has encountered a configuration
error. See the report server log files for more information.
Also, the event viewer is displaying the following error message well.Also, the event viewer is displaying the following error message well.
User: NT AUTHORITY\SYSTEM
Computer: REPORTSERV
Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 529
Date: 11/30/2005
Time: 10:49:03 AM
User: NT AUTHORITY\SYSTEM
Computer: REPORTSERV
Description:
Logon Failure:
Reason: Unknown user name or bad password
User Name:
Domain:
Logon Type: 3
Logon Process: Authz
Authentication Package: Kerberos
Workstation Name: REPORTSERV
Caller User Name: NETWORK SERVICE
Caller Domain: NT AUTHORITY
Caller Logon ID: (0x0,0x3E4)
Caller Process ID: 5928
Transited Services: -
Source Network Address: -
Source Port: -
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
"Terry" wrote:
> The report subscription is returning the following error message.
> How should I resolve this issue?
> However, according to the Job executed, the process was successful but the
> report manager is displaying the following.
> ERROR:
> Failure sending mail: The report server has encountered a configuration
> error. See the report server log files for more information.
> Also, the event viewer is displaying the following error message well.
>
>
How should I resolve this issue?
However, according to the Job executed, the process was successful but the
report manager is displaying the following.
ERROR:
Failure sending mail: The report server has encountered a configuration
error. See the report server log files for more information.
Also, the event viewer is displaying the following error message well.Also, the event viewer is displaying the following error message well.
User: NT AUTHORITY\SYSTEM
Computer: REPORTSERV
Event Type: Failure Audit
Event Source: Security
Event Category: Logon/Logoff
Event ID: 529
Date: 11/30/2005
Time: 10:49:03 AM
User: NT AUTHORITY\SYSTEM
Computer: REPORTSERV
Description:
Logon Failure:
Reason: Unknown user name or bad password
User Name:
Domain:
Logon Type: 3
Logon Process: Authz
Authentication Package: Kerberos
Workstation Name: REPORTSERV
Caller User Name: NETWORK SERVICE
Caller Domain: NT AUTHORITY
Caller Logon ID: (0x0,0x3E4)
Caller Process ID: 5928
Transited Services: -
Source Network Address: -
Source Port: -
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
"Terry" wrote:
> The report subscription is returning the following error message.
> How should I resolve this issue?
> However, according to the Job executed, the process was successful but the
> report manager is displaying the following.
> ERROR:
> Failure sending mail: The report server has encountered a configuration
> error. See the report server log files for more information.
> Also, the event viewer is displaying the following error message well.
>
>
Wednesday, February 15, 2012
Erro 14040: The server "ServerB" is already a Subscriber
Hello.
I'm trying to create a Push subscription from ServerA to ServerB and am
getting the above message. I am using Enterprise Manager to do this.
ServerB already subscribes to a publication from ServerC.
I noticed that the error occurs on the first step of the "Completing the
Push Subscription Wizard", the one labelled "Enabling this server as a
subscriber" (for ServerB). Makes sense since ServerB would have already been
enabled because of the existing subscription to the publication on ServerC.
Is there a way to tell EM not to enable ServerB for subscriptions, or can
ServerB only subscribe to only one other server?
I'm running SQL 2000 SP3a.
Thanks in advance,
Mike
can you do this query and post the results back here?
select sub, srvname from sysservers where srvname='serverb'
Also check to see if ServerB is an enabled Subscriber. If so, uncheck/check
the check box and see if you get an error message.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Mike" <MichaelLopez@.inds.com> wrote in message
news:%233Tf5GbaEHA.2408@.tk2msftngp13.phx.gbl...
> Hello.
> I'm trying to create a Push subscription from ServerA to ServerB and am
> getting the above message. I am using Enterprise Manager to do this.
> ServerB already subscribes to a publication from ServerC.
> I noticed that the error occurs on the first step of the "Completing the
> Push Subscription Wizard", the one labelled "Enabling this server as a
> subscriber" (for ServerB). Makes sense since ServerB would have already
been
> enabled because of the existing subscription to the publication on
ServerC.
> Is there a way to tell EM not to enable ServerB for subscriptions, or can
> ServerB only subscribe to only one other server?
> I'm running SQL 2000 SP3a.
> Thanks in advance,
> Mike
>
I'm trying to create a Push subscription from ServerA to ServerB and am
getting the above message. I am using Enterprise Manager to do this.
ServerB already subscribes to a publication from ServerC.
I noticed that the error occurs on the first step of the "Completing the
Push Subscription Wizard", the one labelled "Enabling this server as a
subscriber" (for ServerB). Makes sense since ServerB would have already been
enabled because of the existing subscription to the publication on ServerC.
Is there a way to tell EM not to enable ServerB for subscriptions, or can
ServerB only subscribe to only one other server?
I'm running SQL 2000 SP3a.
Thanks in advance,
Mike
can you do this query and post the results back here?
select sub, srvname from sysservers where srvname='serverb'
Also check to see if ServerB is an enabled Subscriber. If so, uncheck/check
the check box and see if you get an error message.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Mike" <MichaelLopez@.inds.com> wrote in message
news:%233Tf5GbaEHA.2408@.tk2msftngp13.phx.gbl...
> Hello.
> I'm trying to create a Push subscription from ServerA to ServerB and am
> getting the above message. I am using Enterprise Manager to do this.
> ServerB already subscribes to a publication from ServerC.
> I noticed that the error occurs on the first step of the "Completing the
> Push Subscription Wizard", the one labelled "Enabling this server as a
> subscriber" (for ServerB). Makes sense since ServerB would have already
been
> enabled because of the existing subscription to the publication on
ServerC.
> Is there a way to tell EM not to enable ServerB for subscriptions, or can
> ServerB only subscribe to only one other server?
> I'm running SQL 2000 SP3a.
> Thanks in advance,
> Mike
>
Subscribe to:
Posts (Atom)