Error 1911 replication column does not exist

Source server MSSQL7.0
Destination server MSSQL2K

I'm setting up replication for reporting purposes to another SQL-server.
When I start the distribution agent I get the following error:
Column name '<here's the name of a column I didn't publish and don't need to replicate>' does not exist in the target table.
Error number: 1911

I assume this is because of some dependencies between the columns.

Is there any way I can replicate without those columns?

RegardsDependency doesn't get replicated unless you specified. If you think the error was caused by the column dependency, check the unique index and the foreign key constraint to see whether the 'for replication' is checked or not.|||Thanks, you gave me the hint I needed.
I was scripting the creation of the publication because I need to setup replication for over 20 db's.
In the script you have to change the sp_addarticle @.schema_option value.

Regards

error 18483 & 18482

Hi ,
At first i was trying to set up replication where i got the Error 18483:
could not connect to server 'SQL1; because 'distributor_admin' is not defined
as a remote login at the server.
as per some of the posting i used "Select @.@.Servername" (e.g SQL2)and found
that the name returned is not the same as the computer name(e.g SQL1)
so i executed sp_dropserver @.@.Servername (SQl2)
now when i tried to configure it as a publisher , it gives me "could not
configure SQL1 as the distributor for SQL1. error 18482 : could not connect
to SQL1 because 'SQL2' is not defined as a remote server
i have tried sp_addserver SQL1 but it does not work either
kindly advise
tks & rdgs
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ation/200512/1
Hi ,
After i stop & start SQL Server , i got error 14114 : null is not
configured as a distributor and null is returned for select @.@.Servername
kindly advise
tks & rdgs
maxzsim wrote:
>Hi ,
> At first i was trying to set up replication where i got the Error 18483:
>could not connect to server 'SQL1; because 'distributor_admin' is not defined
>as a remote login at the server.
>as per some of the posting i used "Select @.@.Servername" (e.g SQL2)and found
>that the name returned is not the same as the computer name(e.g SQL1)
>so i executed sp_dropserver @.@.Servername (SQl2)
>now when i tried to configure it as a publisher , it gives me "could not
>configure SQL1 as the distributor for SQL1. error 18482 : could not connect
>to SQL1 because 'SQL2' is not defined as a remote server
>i have tried sp_addserver SQL1 but it does not work either
>kindly advise
>tks & rdgs
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ation/200512/1
|||Hi,
The steps below from one of the posting works
sp_dropserver 'wrong server name'
sp_addserver 'correct server name'
stop & start sql services( i forgot to do this step earlier)
tks & rdgs
maxzsim wrote:[vbcol=seagreen]
>Hi ,
> After i stop & start SQL Server , i got error 14114 : null is not
>configured as a distributor and null is returned for select @.@.Servername
>kindly advise
>tks & rdgs
>[quoted text clipped - 16 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ation/200512/1
|||Had similar problem with starting the replication distributor.
Got login failed message for distributor_admin user.
Problem: Local SQL Server instance name incorrect
We changed the name of the server a while back but the @.@.Servername had the
old server name.
Solution:
sp_dropserver 'oldservername'
sp_addserver 'newservername', @.local = 'local'
The @.local ='local' is required because the replication server is the local
server not a remote server.
Also you need to stop and restart SQL Server Agent.
"maxzsim via droptable.com" wrote:

> Hi,
> The steps below from one of the posting works
> sp_dropserver 'wrong server name'
> sp_addserver 'correct server name'
> stop & start sql services( i forgot to do this step earlier)
> tks & rdgs
>
> maxzsim wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...ation/200512/1
>

Error 18456: Login failed for user 'Distributor_admin'

Hi,
When going through the replication wizard to setup transactional replication
the following error is returned when it starts to setup replication.
SQL Server Enterprise Manager could not configure '<four part servername>'
as the distributor for '<four part servername>'
Error 18456: Login failed for user 'Distributor_admin'
Can someone please help. Is it because of the four part server name?
Thanks
It could be. What happens when you create an alias using the client network
utility. After doing this de-register your server in EM, and then reregister
it with the new one part alias.
Is the distributor local?
"mm" <postto@.news.com> wrote in message
news:eIM2gdb$EHA.2196@.TK2MSFTNGP14.phx.gbl...
> Hi,
> When going through the replication wizard to setup transactional
> replication
> the following error is returned when it starts to setup replication.
> SQL Server Enterprise Manager could not configure '<four part servername>'
> as the distributor for '<four part servername>'
> Error 18456: Login failed for user 'Distributor_admin'
>
> Can someone please help. Is it because of the four part server name?
> Thanks
>
>
|||Hi Hilary,
There is no alisa defined in the the client network utility.
This happens when trying to setup a local distributor. However there is a
database on the SQL server that subscribes to a remote distributor.
Thanks
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eiLeJZi$EHA.3472@.TK2MSFTNGP14.phx.gbl...
> It could be. What happens when you create an alias using the client
network
> utility. After doing this de-register your server in EM, and then
reregister[vbcol=seagreen]
> it with the new one part alias.
> Is the distributor local?
>
> "mm" <postto@.news.com> wrote in message
> news:eIM2gdb$EHA.2196@.TK2MSFTNGP14.phx.gbl...
servername>'
>

Error 15401 windows NT user or group not found+sql 2000

hi all,
i'm doing replication now ...when i add a new login to sqlserver i got
the message if i click ok..."Error 15401 windows NT user or group not
found"...i don't understand......why the error happens.......any one
pls help me!!
--thank youSQL Server cannot resolve the name of the login you specified. The name may
be incorrect, or it may belong to a different domain to which your current
domain does not have access.
Thanks
Laurentiu
Laurentiu Cristofor [MSFT]
Software Development Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"nafi" <hnbnafisha@.gmail.com> wrote in message
news:1168574381.666181.290820@.a75g2000cwd.googlegroups.com...
> hi all,
> i'm doing replication now ...when i add a new login to sqlserver i got
> the message if i click ok..."Error 15401 windows NT user or group not
> found"...i don't understand......why the error happens.......any one
> pls help me!!
> --thank you
>|||hi Mr.Laurentiu Cristofor,
thank u very much....yeh.. correct...my computer doesn't have access
to that domain
Laurentiu Cristofor [MSFT] wrote:[vbcol=seagreen]
> SQL Server cannot resolve the name of the login you specified. The name ma
y
> be incorrect, or it may belong to a different domain to which your current
> domain does not have access.
> Thanks
> Laurentiu
> --
> Laurentiu Cristofor [MSFT]
> Software Development Engineer
> SQL Server Engine
> http://blogs.msdn.com/lcris/
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "nafi" <hnbnafisha@.gmail.com> wrote in message
> news:1168574381.666181.290820@.a75g2000cwd.googlegroups.com...

Error 15004 Name cannot be null

I made a publisher for marge replication via ISDN Dialup connected server and registered server x to y and y to x with TCP/IP.

I can see both data on each other.

I publish one database and try to configure pull subscription on 2nd one got following error.

SQL Server enterprise manager could not create a pull asubscription to publication pmst

Error 15004 Name cannot be null

Thanks to all of youYou've got a relatively unusual configuration for replication. I don't know of anywhere to look for specific details to help you, but I've got some ideas.

I'd start by synchronizing the clocks on both servers, preferably to a common time source or better yet synch one machine's clock to the other's clock. Open a copy of SQL Profiler on both machines and trace with no filtering (so you can see every command executed against the server). Try to re-subscribe again. The last command in each profile is suspect, the one with the later timestamp is likely to be the source of your problem.

You are probably looking for an empty string or NULL string parameter. Once you find it, you'll have to post what you find and maybe one of us can help you.

-PatP|||Do "SELECT @.@.SERVERNAME" on both servers.

Error 14294 in replication

Hi
I have a server with Windows 2000 Server SP4 and SQL 2000 with SP3.
This server has several published databases that they replicate data to
another server.
All the replications is of transactional type.
When creating to publish another database it leaves me the following error:
Error 14294
Supply either @.job_id or @.job_name to indentify the job.
That I can make to correct the problem?
Thank you
are you or have you deployed the other publications using a script?
If you, you must use unique publication names and ensure that you don't
specify a snapshot agent name, log reader agent name, or distribution agent
name.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Mario" <Mario@.discussions.microsoft.com> wrote in message
news:C083E5F7-8740-4ACC-B73E-51B6B35FCE62@.microsoft.com...
> Hi
> I have a server with Windows 2000 Server SP4 and SQL 2000 with SP3.
> This server has several published databases that they replicate data to
> another server.
> All the replications is of transactional type.
> When creating to publish another database it leaves me the following
error:
> Error 14294
> Supply either @.job_id or @.job_name to indentify the job.
> That I can make to correct the problem?
> Thank you
|||Hi Hilary
I don′t use a script, my publications was created by wizard.
"Hilary Cotter" wrote:

> are you or have you deployed the other publications using a script?
> If you, you must use unique publication names and ensure that you don't
> specify a snapshot agent name, log reader agent name, or distribution agent
> name.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Mario" <Mario@.discussions.microsoft.com> wrote in message
> news:C083E5F7-8740-4ACC-B73E-51B6B35FCE62@.microsoft.com...
> error:
>
>
|||Can you do a Select @.@.SERVERNAME on your publisher and see what server name
it returns? Did you rename this server recently.
There are some reports that this error can be cleared by disabling
replication on your publisher and then recreating it.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Mario" <Mario@.discussions.microsoft.com> wrote in message
news:C083E5F7-8740-4ACC-B73E-51B6B35FCE62@.microsoft.com...
> Hi
> I have a server with Windows 2000 Server SP4 and SQL 2000 with SP3.
> This server has several published databases that they replicate data to
> another server.
> All the replications is of transactional type.
> When creating to publish another database it leaves me the following
error:
> Error 14294
> Supply either @.job_id or @.job_name to indentify the job.
> That I can make to correct the problem?
> Thank you

error 14294

Hi -
I am an extremely novice user attempting to use transactional replication. I successfully ran the replication and then opted to remove the subscriptions, publications and so forth and start again. I did not remove the distributor. I may have removed
jobs associated with the distributor though. When i attempt to recreate the publication, I recieve error 14294 - indicating that a job name or id is desired. I am seeking suggestions as to how I can recover from the error.
Lily,
probably the best way is to start again. You can disable publishing which
removes the distribution database and any remaining jobs/alerts then enable
publishing and distribution which will add all the plumbing including any
alerts and jobs which have been deleted.
HTH,
Paul Ibison
|||Thanks you are the greatest!!
It worked and I am on my way again.
Thanks again!
sql

Error 14262

Merge replication - SQL 2000. I ran some scripts to add a column to a table
and to add a new table and view to articles. All went fine. Then I tried
to manually start the snapshot agent and it gave me this error "The
specified @.job_id('guid number...') does not exist."
What do I need to do? I looked at Paul's site and found the explanation but
I'm not sure if this applies and was not clear what to do. Please help,
thanks.
David
Hi David - the explanation on my site refers to a scripting error and
doesn't seem relevant to your case to be honest. Can you refresh the jobs
folder as I think that you might be attempting to start a job that has been
removed/replaced. Also check under replication monitor that the agent has a
job (right-click and select "Agent properties..." and see what the name is
there.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Paul,
I got this message from the Snapshot Agents folder, right-click of the
publication (which has a red X on it) and selecting "Start Agent". The
status column shows "Failed" due to "Timeout expired. ..." Apparently the
last attempt to create this had a problem. This server is not on our site,
so I'm not sure what happened. Also, this publication under the Publishers
folder also has a red X on it. Do I have to re-create the Publication
entirely?
Also, when I was there yesterday I created a new table and added it to the
articles via sp_addmergearticle. I also ran sp_repladdcolumn to add a
column to an existing publication. I have 2 publications, one for tables
and the other for views and stored procs. The one with the problems is the
tables publication and these problems (red X) existed before I ran these
additions.
David
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:egCdwmKMHHA.4000@.TK2MSFTNGP06.phx.gbl...
> Hi David - the explanation on my site refers to a scripting error and
> doesn't seem relevant to your case to be honest. Can you refresh the jobs
> folder as I think that you might be attempting to start a job that has
> been removed/replaced. Also check under replication monitor that the agent
> has a job (right-click and select "Agent properties..." and see what the
> name is there.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>

Error 14113 while trying to setup replication on SQL Server 2000 S

Hi,
I'm trying to run the wizard to setup replication on a SQL Server 2000 SP3.
Entering the parameters goes without a problem but when executing the script
I'm getting an error 14113:
SQL Server Enterprise MAnager could not configure 'XYZ' as the distributor
for 'XYZ'.
Error 14113: Could not execute c:\... \instdist.sql
I have all the necessary rights on the DB server and on Win 2003.
I also noticed that XP_CMDSHELL doesn't work on this server (probably needed
to execute the previous line) so I executed the instdist.sql manually in
query analyzer.
This clearly isn't enough to get replication working.
The problem with XP_CMDSHELL:
Msg 50001, Level 1, State 50001
xpsql.cpp: Error 1260 from CreateProcess on line 675
I already dropped XP_CMDSHELL:
exec sp_dropextendedproc 'xp_cmdshell'
then replaced the dll with one from another server (just in case) and
re-installed it:
exec sp_addextendedproc 'xp_cmdshell', 'xplog70.dll'
all with the same result.
IMHO both problems are related. Any suggestions?
Tanks in advance,
Gaston.
Can you try to run command shell from within query analyzer? Can you create
subfolders within your snapshot location?
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
"Gaston" <Gaston@.discussions.microsoft.com> wrote in message
news:ADC431B8-38B5-477D-BE35-AFBF9D6903EC@.microsoft.com...
> Hi,
> I'm trying to run the wizard to setup replication on a SQL Server 2000
> SP3.
> Entering the parameters goes without a problem but when executing the
> script
> I'm getting an error 14113:
> SQL Server Enterprise MAnager could not configure 'XYZ' as the distributor
> for 'XYZ'.
> Error 14113: Could not execute c:\... \instdist.sql
> I have all the necessary rights on the DB server and on Win 2003.
> I also noticed that XP_CMDSHELL doesn't work on this server (probably
> needed
> to execute the previous line) so I executed the instdist.sql manually in
> query analyzer.
> This clearly isn't enough to get replication working.
> The problem with XP_CMDSHELL:
> Msg 50001, Level 1, State 50001
> xpsql.cpp: Error 1260 from CreateProcess on line 675
> I already dropped XP_CMDSHELL:
> exec sp_dropextendedproc 'xp_cmdshell'
> then replaced the dll with one from another server (just in case) and
> re-installed it:
> exec sp_addextendedproc 'xp_cmdshell', 'xplog70.dll'
> all with the same result.
> IMHO both problems are related. Any suggestions?
> Tanks in advance,
> Gaston.
>
|||If you mean if I can run "xp_cmdshell" fromwithin query analyzer: No, this
doesn't work.
The problem with XP_CMDSHELL:
> Msg 50001, Level 1, State 50001
> xpsql.cpp: Error 1260 from CreateProcess on line 675
And it seems that the OSQL command wouldn't even be executed, so the
distribution server can't be setup.
I can create subfolders on the snapshot location, np.
Thanks already,
Gaston.
"Hilary Cotter" wrote:

> Can you try to run command shell from within query analyzer? Can you create
> subfolders within your snapshot location?
> --
> 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
> "Gaston" <Gaston@.discussions.microsoft.com> wrote in message
> news:ADC431B8-38B5-477D-BE35-AFBF9D6903EC@.microsoft.com...
>
>
|||I suspect this is your problem.
Can you reapply SP3, or better yet SP4 and try again?
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
"Gaston" <Gaston@.discussions.microsoft.com> wrote in message
news:667B866F-107F-47AB-9355-AC6C9CDF9CE5@.microsoft.com...[vbcol=seagreen]
> If you mean if I can run "xp_cmdshell" fromwithin query analyzer: No, this
> doesn't work.
> The problem with XP_CMDSHELL:
> And it seems that the OSQL command wouldn't even be executed, so the
> distribution server can't be setup.
> I can create subfolders on the snapshot location, np.
> Thanks already,
> Gaston.
>
> "Hilary Cotter" wrote:
|||Hi Hilary,
The xp_cmdshell works after we applied SP4. So now we're on to the
replication problem. I suppose that this will work now as well!
Thanks for your efforts so far!
/Gaston Verelst
"Hilary Cotter" wrote:

> I suspect this is your problem.
> Can you reapply SP3, or better yet SP4 and try again?
> --
> 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
> "Gaston" <Gaston@.discussions.microsoft.com> wrote in message
> news:667B866F-107F-47AB-9355-AC6C9CDF9CE5@.microsoft.com...
>
>
|||Hi Hilary,
The replication is up and running, thanks for your support!
Kind regards,
Gaston Verelst (Belgium)
"Hilary Cotter" wrote:

> I suspect this is your problem.
> Can you reapply SP3, or better yet SP4 and try again?
> --
> 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
> "Gaston" <Gaston@.discussions.microsoft.com> wrote in message
> news:667B866F-107F-47AB-9355-AC6C9CDF9CE5@.microsoft.com...
>
>

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
>

Error 14053: Cannot load the DLL replincrementlsn extended procedure...

I am setting up a transactional replication between two MSSBS2K servers, both running MSSQL2K. Both are on different domains, but are currently in the same network (until all data is replicated, then the subscribe will move to a remote site and pull changes periodically).

Everything is working on the publisher/distributor side, but when I attempt to subscribe to the distributor, I get the following message:

Error 14053: Cannot load the DLL replincrementlsn extended procedure, or one of the DLLs it references. Reason: 126(The specified module could not be found.).
The subscription could not be updated at this time.
The subscription could not be created.

Has anyone experienced this? I have scoured the Internet for this error, and have come up basically empty. All I found either suggest checking for the existence of the sp_replincrementlsn and sp_replincrementlsn_internal (both of which exist) or suggest an incomplete SP install. Neither of these is the case.

Personally, I tend to suspect a permissions issue when trying to launch the appropriate DLLs is generating this less-than-intuitive error message, but I cannot determine how to go about resolving this. I am using SQL authentication to connect, and both servers use local (to their domain) non-system accounts to log in. This works fine for launching queries across the servers. Could there be a deeper permissions issue at play here?

I'm at a dead end, and I need to get this issue resolved ASAP, as this server needs to be deployed yesterday. Any help you can provide will be most appreciated!Did you have any options on the install of SQL Server, or was it all a big black box install courtesy of Microsoft? On the surface, I would suspect that replication was not installed on the SQL Server. Do a search on your box for xprepl.dll. Let us know what comes back.|||Yes, xprepl.dll is installed in the C:\Program Files\Microsoft SQL Server\MSSQL\Binn folder.

This install is a Windows Small Business Server 2000 install that I performed personally. I installed MS SQL based on the standard defaults. Just to be sure, though, I just now re-ran the installer and verified that the "Replication" checkbox is checked by default.

Did you have any options on the install of SQL Server, or was it all a big black box install courtesy of Microsoft? On the surface, I would suspect that replication was not installed on the SQL Server. Do a search on your box for xprepl.dll. Let us know what comes back.|||Update: Never could get past that error. Went with merge replication instead of transactional replication and it works fine. Only caveat is that this did require I move the new server under the same domain as the publisher/distributor server (rather than as a separate domain in the same forest). Small price to pay for getting this replication up and going.

Error 14053 and Push Replication

SQL Server Enterprise Manager encountered errors creating push subscriptions
for the following Subscribers:
[Subscriber Server Name]: Error 14053: Cannot load the DLL replincrementlsn
extended procedure, or one of the DLLs it references. Reason: 126(error not
found).
The subscription could not be updated at this time.
The subscription could not be created.
The publisher and distributor are running SQL Server 2000 SP3a, the
subscriber is RTM (no SP applied expect for the criticial release update).
The subscriber has a new server just released into production, hence why no
SP yet.
The publisher and subscriber are on non trusting domains, but on the
internal network.
I have checked the SP log file (C:\Windows\) and have been advised that both
sp_replincrementlsn and sp_replincrementlsn_internal exist in the master
table on both servers. I also reattempted to install SP3a on the publisher
server to no avail.
All work has been carried out in Ent Mgr.
I thank anyone in advance for their assistance, as I am totally lost for
ideas.
Betty,
can you run this on the distributor, just to confirm that the stored
procedure was created correctly:
sp_helptext sp_replincrementlsn
Please check that xprepl.dll is in your sql bin directory (eg C:\Program
Files\Microsoft SQL Server\MSSQL\Binn).
Please check the sql server error log for any issues recorded there.
Have a look at sqlsp.log file from the c:\windows directory this might shed
some light on any failed actions during the sp installation
If any of this returns something interesting then please post it up,
otherwise I'd reinstall sp3a.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
I ran the steps you requested on our distribution server (which is also the
publication server)
- sp_helptext sp_replincrementlsn returned no issue, the sp does exist, but
only in the master table.
- xprepl.dll DOES exist in the BINN directory of the SQL Server
- The SQL Server reports no error, and even reports that it is using
xprepl.dll for replication
- SQLsp.log appears to contain no critical errors (the only error of sort is
the one that indicates that some data files could not be modified - the
reason being that those databases are in the offline state.
- I am still yet to reinstall SP3a, awaiting for authorisation from the
server controller, but previous attempts have not worked.
Anyother ideas?
Thanks,
Betty.
"Paul Ibison" wrote:

> Betty,
> can you run this on the distributor, just to confirm that the stored
> procedure was created correctly:
> sp_helptext sp_replincrementlsn
> Please check that xprepl.dll is in your sql bin directory (eg C:\Program
> Files\Microsoft SQL Server\MSSQL\Binn).
> Please check the sql server error log for any issues recorded there.
> Have a look at sqlsp.log file from the c:\windows directory this might shed
> some light on any failed actions during the sp installation
> If any of this returns something interesting then please post it up,
> otherwise I'd reinstall sp3a.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||With this type of installation error, I'd apply the
service pack, reinstall completely and ring PSS in this
order assuming the error is repeated at each step.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
one interesting thing is that the SP3Readme.htm states that this error can
be safely ignored.
Regards,
Betty.
"Paul Ibison" wrote:

> With this type of installation error, I'd apply the
> service pack, reinstall completely and ring PSS in this
> order assuming the error is repeated at each step.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Paul,
after applying SP3 it appears that the replication works, it states, that it
said the replication was created successfully.
I think what happens, is if you attempt to create your first publication,
distributor, or subscriber, after SP3 has been applied, you need to reapply
SP3 to update the replication system files.
Thank you for your assitance,
Betty.

Error 14027 When Trying to Configure P2P Topology

I'm beginning to wonder if replication is worth the trouble I've had to spend on it!

Trying to create a simple peer-to-peer replication topology. I can create the initial publication. I can change the property to allow P2P. I can backup the database and I can create a snapshot. When, however, I try to configure the peer-to-peer topology, I get a 14027 error message telling me that ONE table out of 250, or so, "does not exist in the current database." That's pretty troubling given that I can run a select query against that specific table. I would appreciate any information that would help me to understand what's going on or successfully set up replication.

Thanks!

Randy

Hi Randy,

To be honest, I am deeply puzzled by the error that you were getting as well. So let me ask you a few questions which will hopefully narrow down the problem somewhat:

1) Does the name of the table giving you problem contain any special characters ($%#@.\{} etc.) I am especially interested to know if there are any leading or trailing spaces in the table name.

2) Is the table owned by dbo or some other schema?

3) This is a long shot but is the table giving you problems really a table? Can it be an indexed view for example?

4) Is the table giving you trouble a partitioned table? A partitioned view?

For the sake of narrowing down the problem, it may be worthwhile to try setting up a separate (non-p2p) publication containing just the problematic table. It would also be great if you can post the row content corresponding to the problematic table when you execute sp_MShelp_replication_table in the publisher database.

Thanks for the feedback.

-Raymond

|||

Raymond,

Thank you for the response. In answer to your questions:

1. The only non alpha character is an underscore like this: claim_cat.

2. Table is owned by dbo

3. I dropped and recreated the table so it is definitely a table.

4. The table is a lookup with onlyl two columns, claim_cat and claim_cat_desc.

One thing I want to try this morning is setting up the entire replication before doing a full backup from the publisher, then initialize the replications from the backup. Originally, I had backed up the publisher database, restored it to the two subscribers, then created the replication. We'll see.

Thanks again.

Randy

|||

Hi Randy,

I find that your comment about using backups that were taken before the publication was created and the fact that you have dropped and recreated the problematic table to be rather interesting in the sense that it may point us to a potential explanation of your original problem. The current implementation of the p2p wizard makes very strong assumption that all nodes involved have identical schema, so is it possible that the p2p wizard hit the "table not found" error when it is setting up re-publishing from the nodes initialized with the slightly out-dated backup that happened to not contain the problematic table? In any case, it would be great if you can let us know if you have better luck setting up the topology with newer backups.

Hope that helps.

-Raymond

Error "...could not enumerate changes.." Incorrect syntax ... 'a

Error in replication Merge:
{call sp_MSenumchanges(?,?,?,?,?,?,?,?)}
The process could not enumerate changes at the 'Subscriber'.
(Source: Merge Replication Provider (Agent); Error number: -2147200999)
Incorrect syntax near the keyword 'and'.
(Source: SERVIDOR (Data source); Error number: 156)
I already altered the store procedure sp_MSenumchanges/sp_MSenumchanges_Pal
and sp_MSenumchanges_Direct var @.genlist
and the mistake continues.
Please help me
Hamilton
SP, Brazil
Try installing the service pack 2 or above.
this usually happens when a column contains images.
"Hamilton" <Hamilton@.discussions.microsoft.com> wrote in message
news:CC77034E-D903-4552-8501-910B96E6D519@.microsoft.com...
> Error in replication Merge:
> {call sp_MSenumchanges(?,?,?,?,?,?,?,?)}
> The process could not enumerate changes at the 'Subscriber'.
> (Source: Merge Replication Provider (Agent); Error number: -2147200999)
> Incorrect syntax near the keyword 'and'.
> (Source: SERVIDOR (Data source); Error number: 156)
> I already altered the store procedure
> sp_MSenumchanges/sp_MSenumchanges_Pal
> and sp_MSenumchanges_Direct var @.genlist
> and the mistake continues.
> Please help me
> Hamilton
> SP, Brazil
|||Try using Profiler to capture which exactly SQL statement in which procedure
is failing. That should give a hint what could be wrong.

> I already altered the store procedure
sp_MSenumchanges/sp_MSenumchanges_Pal
> and sp_MSenumchanges_Direct var @.genlist
> and the mistake continues.
What have you changed in those procedures ? For what reason ?
Regards,
Kestutis Adomavicius
Consultant
UAB "Baltic Software Solutions"
"Hamilton" <Hamilton@.discussions.microsoft.com> wrote in message
news:CC77034E-D903-4552-8501-910B96E6D519@.microsoft.com...
> Error in replication Merge:
> {call sp_MSenumchanges(?,?,?,?,?,?,?,?)}
> The process could not enumerate changes at the 'Subscriber'.
> (Source: Merge Replication Provider (Agent); Error number: -2147200999)
> Incorrect syntax near the keyword 'and'.
> (Source: SERVIDOR (Data source); Error number: 156)
> I already altered the store procedure
sp_MSenumchanges/sp_MSenumchanges_Pal
> and sp_MSenumchanges_Direct var @.genlist
> and the mistake continues.
> Please help me
> Hamilton
> SP, Brazil

Error - could not initialize the Publisher

Hi,
I was synchronizing two SQL Server 2k (SP3) using merge replication for the last 4 months. There was an error in one partiucular table at the publisher because of which synchronization had stopped for around 14-18 hours between these two servers. I fixed
this table using the DBCC checktable with the REPAIR_DATA_LOSS option. No data as such was lost though.
Now when I sychronize the servers I get the following error - "The merge process could not initialize the Publisher 'ECOSYSTEM:MLEcosystem'."
I am attaching the contents of the log file below -
__________________________________________________ _______________________________________
__________________________________________________ _______________________________________
I have tried changing the merge agent profile's Query Timeout, Login Timeout parameter and quite a few parameters to solve this problem as these two servers synchronize over the Internet.
The MSmerge_genhistory at the subscriber has 7000 rows and the one at the publisher has around 8000 rows.
Can someone please advise as to how to synchronize these servers?
Thank you in advance.
Regards,
Manish
which table did you repair? If it is one of the replication system tables
you will have probably have to drop your subscription and rebuild it.
I'd try a re-initialization first.
"Manish Buttan" <manish@.ccipl.com> wrote in message
news:962865EC-16EE-457C-9353-26E105834430@.microsoft.com...
> Hi,
> I was synchronizing two SQL Server 2k (SP3) using merge replication for
the last 4 months. There was an error in one partiucular table at the
publisher because of which synchronization had stopped for around 14-18
hours between these two servers. I fixed this table using the DBCC
checktable with the REPAIR_DATA_LOSS option. No data as such was lost
though.
> Now when I sychronize the servers I get the following error - "The merge
process could not initialize the Publisher 'ECOSYSTEM:MLEcosystem'."
> I am attaching the contents of the log file below -
>
__________________________________________________ __________________________
_____________
>
>
__________________________________________________ __________________________
_____________
>
> I have tried changing the merge agent profile's Query Timeout, Login
Timeout parameter and quite a few parameters to solve this problem as these
two servers synchronize over the Internet.
> The MSmerge_genhistory at the subscriber has 7000 rows and the one at the
publisher has around 8000 rows.
> Can someone please advise as to how to synchronize these servers?
> Thank you in advance.
> Regards,
> Manish
>
>
>
|||Hi Paul, Yuan & Hillary,
I just wanted to thank you all for helping me fix this problem.
It was more of a bandwidth problem I guess. Once all the employees in my company left for the day, I tried to sync the servers, it synchronized without any problem.
This problem occured as the synchronization didn't happen for nearly 18 hours and there was too much data to synchronize at once.
How do I make sure that this problem does not happen again?
Thank you all again!
Regards,
Manish Buttan
|||Manish,
To be honest based on the error message I'm still not sure that this is the problem, but if it is you could try limiting the number of concurrent merge processes or schedule synchronization of the merge agents so as not to overlap (I'm assuming you have m
ultiple subscribers).
HTH,
Paul Ibison
|||Hi Paul,
Thank you once again!
I have only one subscriber. So I dont think it can be because of multiple merge agents running at the same time.
Also, it would really help if you can point me to some URL or if you yourself can give me some tips to configure the merge agent for an unreliable/slow connection.
Thank you.
Regards,
Manish
|||Manish,
have a look at the properties of the merge agent profile. In particular the
QueryTimeout needs maximising. You can use the Slow Link Profile as a model
then increase this parameter.
Profile parameters:
http://msdn.microsoft.com/library/de...lmerg_4y2h.asp
http://msdn.microsoft.com/library/de...plmon_5vqd.asp
Regards,
Paul Ibison
|||Hi Manish,
I also include the followiing articles for your reference.
315521 INF: How to Troubleshoot SQL Server Merge Replication Problems
http://support.microsoft.com/?id=315521
315642 INF: Information that PSS needs to troubleshoot SQL Server
replication
http://support.microsoft.com/?id=315642
Please feel free to let me know if you need further assistance on this
issue.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
|||Hi Yuan/Paul,
Thank you for all the help you have provided.
Regards,
Manish

Error - Building Replication

Hi,I am building the Transactional Replication.It thro's Error Like below.
The process could not bulk copy out of table
'[dbo].[syncobj_0x3435344541393145]'.
I/O error while writing BCP data-file
Category : ODBC
Source : ODBC SQL Server Driver
But I have Checked the Space in Both OLTP and Replication Server it has
enough space.
Is prob in ODBC Driver? pls guide me to rectify this Prob.
Regards
Sivaraman Latchapathi
Do a select * from syncobj_0x3435344541393145 to see if there aren't
physical problems with this table. Also do a sp_helptext
syncobj_0x3435344541393145 to see if this view can't benefit from indexes on
the base tables.
Now check the event log to see if you can't see disk error problems.
These errors tend to be transitory.
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
"Shiv" <Shiv@.discussions.microsoft.com> wrote in message
news:5483C669-8B80-4A67-927A-EDDFDFCFC790@.microsoft.com...
> Hi,I am building the Transactional Replication.It thro's Error Like below.
> The process could not bulk copy out of table
> '[dbo].[syncobj_0x3435344541393145]'.
> I/O error while writing BCP data-file
> Category : ODBC
> Source : ODBC SQL Server Driver
> But I have Checked the Space in Both OLTP and Replication Server it has
> enough space.
> Is prob in ODBC Driver? pls guide me to rectify this Prob.
> Regards
> Sivaraman Latchapathi
>
|||Hi, As u said syncobj_0x3435344541393145 is View ... i can able to see the
record
in that view also i can able to query physical table which is related to
that view.
"Hilary Cotter" wrote:

> Do a select * from syncobj_0x3435344541393145 to see if there aren't
> physical problems with this table. Also do a sp_helptext
> syncobj_0x3435344541393145 to see if this view can't benefit from indexes on
> the base tables.
> Now check the event log to see if you can't see disk error problems.
> These errors tend to be transitory.
> --
> 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
> "Shiv" <Shiv@.discussions.microsoft.com> wrote in message
> news:5483C669-8B80-4A67-927A-EDDFDFCFC790@.microsoft.com...
>
>
|||ok, now try to bcp out of this view into the file system to see if you can
do this successfully.
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
"Shiv" <Shiv@.discussions.microsoft.com> wrote in message
news:FF248563-F4E8-4AD5-89FE-DD42EF330917@.microsoft.com...[vbcol=seagreen]
> Hi, As u said syncobj_0x3435344541393145 is View ... i can able to see the
> record
> in that view also i can able to query physical table which is related to
> that view.
> "Hilary Cotter" wrote: