Error in replication
-
hi
i have a problem in replication .
- my type replication is merge.
and i used filter in that.
after three month good work i got this message :
(failed to enumerate changes in the filtered articles)
and the details of error was this(incorrect syntax near '-')
and this was the command that the SQL himself had made it .
and he had made this (create table #belong_agent_-1500631453(tablenick int not null , rowguid iniq......))
-
Hi,
I had the same problem.
You can find more detils here
http://support.microsoft.com/default.aspx?scid=kb;en-us;814916
"Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4."
I hv installed SP4 and the problem is fixed.
Rafal
-
A quick fix until you can move to SP4 is to reboot the subscriber. This error is caused by a counter that overcounts in memory. SQLserver creates a random name from the counter and after it overcounts it creates a name with a - sign in it. I usually have the problem between 1 and 2 months of constant use of a subscriber. I get my users to reboot the subscriber servers once a month and the problem never happens.
Don Tanner
-
Hi,
Further more, I have same scenario, we have Merge replication 1 publication is running without any filtered (horizontal filtration) replication and works fine, but 7 publications has filtered replication for different remote location. It was setup since last 4 years and was working fine but since last few months we are facing same problem as mentioned, also we noticed that the CPU usage at Publisher+ Distributor Server goes to 100% till we stop all filtered replications or it stops automatically after retrying.
Anyone has faced this situation or not? Among 7 one is working fine with a normal CPU usage at the moment when I am posting this query- don’t know how, but when I start any other subscription node, its stops on Action 5 with following error.
Failed to enumerate changes in the filtered articles.
(Source: Merge Replication Provider (Agent); Error number: -2147200925)
---------------------------------------------------------------------------------------------------------------
The merge process timed out while executing a query. Reconfigure the QueryTimeout parameter and retry the operation.
(Source: PUBLISHERSERVER (Data source); Error number: 0)
---------------------------------------------------------------------------------------------------------------
The merge process encountered an unexpected network error. The connection to Subscriber 'SUBSCRIBERSERVER' is no longer available.
(Source: Merge Process (Agent); Error number: -2147199469)
---------------------------------------------------------------------------------------------------------------
Shamshad Ali
-
With continuation of my last post/query, My top priority is to let down the CPU usage at the Main Publisher Server, coz if the error is removed by applying SP4, will it make me sure the CPU usage will also get normal or will be in the same condition as 100% ?
Also I want to ask query about the SP4 deployment, do I need to apply SP4 on all machines participating Replication with Publisher (Publisher and all Subscriber Servers)? Do I need to drop replication and then apply SP4 and re-configure replication or just apply SP4 with removing replication nodes.
Please reply ASAP.
Shamshad Ali
-
failed to enumerate changes in the filtered articles
i have the same problem and i'm working with SP4 and the problem still exist, can any one help me?
please i need the solution
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply