resolver option and tracking level article options disabled

Hi, we are using SQL2005 merge replication, and have 2 publications that
reference the same article. We are trying to change the tracking level option
for this article, but it is greyed out and disabled, because it knows the
article is in another publication, and it disallows this change. We recreated
this on another server. The option, along with the resolver tab options, get
completely greyed when the 2nd publication is added. Any ideas how to change
the tracking level in this case? Should we use a stored procedure to set this
option? Thanks.
Some publication options are limited by other publications the article is
in. There is no way to change this without dropping all publications and
making these properties consistent in all publications.
Another example of one of these properties is automatic identity range
management.
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
"nkleinjan" <nkleinjan@.discussions.microsoft.com> wrote in message
news:325082EB-74C2-42E9-AFB7-843D23CB53B4@.microsoft.com...
> Hi, we are using SQL2005 merge replication, and have 2 publications that
> reference the same article. We are trying to change the tracking level
> option
> for this article, but it is greyed out and disabled, because it knows the
> article is in another publication, and it disallows this change. We
> recreated
> this on another server. The option, along with the resolver tab options,
> get
> completely greyed when the 2nd publication is added. Any ideas how to
> change
> the tracking level in this case? Should we use a stored procedure to set
> this
> option? Thanks.

resolve login problem after moving db

I'm moving databases from one server to another server.
Then I use the method in microsoft article 246133, to transfer logins.
1. If I use transfer logins dts task, it creates orphaned users. but default
database goes to the right one.
2. If I use the script that make use of the sp: sp_help_revlogin
It seems work OK, no orphaned users. But I found the default database all
goes to
master, instead of other databases as in the old server.
Then I need to reset the default database manually one by one.
Is that the way the scrip works? It seems it solves one problem but have
another?
Any solutions
Thanks
You need to run sp_help_revlogin AFTER you add the databases. Otherwise, it
defaults to what's available.
"Ann" <Ann@.discussions.microsoft.com> wrote in message
news:435B1BBE-E32B-4320-BAE7-9EF764044CC4@.microsoft.com...
> I'm moving databases from one server to another server.
> Then I use the method in microsoft article 246133, to transfer logins.
> 1. If I use transfer logins dts task, it creates orphaned users. but
default
> database goes to the right one.
> 2. If I use the script that make use of the sp: sp_help_revlogin
> It seems work OK, no orphaned users. But I found the default database all
> goes to
> master, instead of other databases as in the old server.
> Then I need to reset the default database manually one by one.
> Is that the way the scrip works? It seems it solves one problem but have
> another?
> Any solutions
> Thanks
|||Thank you. But that's exactly what I did. The databases were all there first.
Then I ran the output of sp_help_revlogin generated script.
I also take a look at the script, there is nothing indicating default
database.
It just create logins with the original sid and password.
Any further help?
Thanks
"Derrick Leggett" wrote:

> You need to run sp_help_revlogin AFTER you add the databases. Otherwise, it
> defaults to what's available.
>
> "Ann" <Ann@.discussions.microsoft.com> wrote in message
> news:435B1BBE-E32B-4320-BAE7-9EF764044CC4@.microsoft.com...
> default
>
>

resolve login problem after moving db

I'm moving databases from one server to another server.
Then I use the method in microsoft article 246133, to transfer logins.
1. If I use transfer logins dts task, it creates orphaned users. but default
database goes to the right one.
2. If I use the script that make use of the sp: sp_help_revlogin
It seems work OK, no orphaned users. But I found the default database all
goes to
master, instead of other databases as in the old server.
Then I need to reset the default database manually one by one.
Is that the way the scrip works? It seems it solves one problem but have
another?
Any solutions
ThanksYou need to run sp_help_revlogin AFTER you add the databases. Otherwise, it
defaults to what's available.
"Ann" <Ann@.discussions.microsoft.com> wrote in message
news:435B1BBE-E32B-4320-BAE7-9EF764044CC4@.microsoft.com...
> I'm moving databases from one server to another server.
> Then I use the method in microsoft article 246133, to transfer logins.
> 1. If I use transfer logins dts task, it creates orphaned users. but
default
> database goes to the right one.
> 2. If I use the script that make use of the sp: sp_help_revlogin
> It seems work OK, no orphaned users. But I found the default database all
> goes to
> master, instead of other databases as in the old server.
> Then I need to reset the default database manually one by one.
> Is that the way the scrip works? It seems it solves one problem but have
> another?
> Any solutions
> Thanks|||Thank you. But that's exactly what I did. The databases were all there first
.
Then I ran the output of sp_help_revlogin generated script.
I also take a look at the script, there is nothing indicating default
database.
It just create logins with the original sid and password.
Any further help?
Thanks
"Derrick Leggett" wrote:

> You need to run sp_help_revlogin AFTER you add the databases. Otherwise,
it
> defaults to what's available.
>
> "Ann" <Ann@.discussions.microsoft.com> wrote in message
> news:435B1BBE-E32B-4320-BAE7-9EF764044CC4@.microsoft.com...
> default
>
>sql

resolve login problem after moving db

I'm moving databases from one server to another server.
Then I use the method in microsoft article 246133, to transfer logins.
1. If I use transfer logins dts task, it creates orphaned users. but default
database goes to the right one.
2. If I use the script that make use of the sp: sp_help_revlogin
It seems work OK, no orphaned users. But I found the default database all
goes to
master, instead of other databases as in the old server.
Then I need to reset the default database manually one by one.
Is that the way the scrip works? It seems it solves one problem but have
another?
Any solutions
ThanksYou need to run sp_help_revlogin AFTER you add the databases. Otherwise, it
defaults to what's available.
"Ann" <Ann@.discussions.microsoft.com> wrote in message
news:435B1BBE-E32B-4320-BAE7-9EF764044CC4@.microsoft.com...
> I'm moving databases from one server to another server.
> Then I use the method in microsoft article 246133, to transfer logins.
> 1. If I use transfer logins dts task, it creates orphaned users. but
default
> database goes to the right one.
> 2. If I use the script that make use of the sp: sp_help_revlogin
> It seems work OK, no orphaned users. But I found the default database all
> goes to
> master, instead of other databases as in the old server.
> Then I need to reset the default database manually one by one.
> Is that the way the scrip works? It seems it solves one problem but have
> another?
> Any solutions
> Thanks|||Thank you. But that's exactly what I did. The databases were all there first.
Then I ran the output of sp_help_revlogin generated script.
I also take a look at the script, there is nothing indicating default
database.
It just create logins with the original sid and password.
Any further help?
Thanks
"Derrick Leggett" wrote:
> You need to run sp_help_revlogin AFTER you add the databases. Otherwise, it
> defaults to what's available.
>
> "Ann" <Ann@.discussions.microsoft.com> wrote in message
> news:435B1BBE-E32B-4320-BAE7-9EF764044CC4@.microsoft.com...
> > I'm moving databases from one server to another server.
> >
> > Then I use the method in microsoft article 246133, to transfer logins.
> > 1. If I use transfer logins dts task, it creates orphaned users. but
> default
> > database goes to the right one.
> > 2. If I use the script that make use of the sp: sp_help_revlogin
> > It seems work OK, no orphaned users. But I found the default database all
> > goes to
> > master, instead of other databases as in the old server.
> > Then I need to reset the default database manually one by one.
> > Is that the way the scrip works? It seems it solves one problem but have
> > another?
> >
> > Any solutions
> > Thanks
>
>

Reqplication queues up without any errors

I have two publications (with only one article in each) based on the same
source table. Both of these publications have one pull subscription each.
Using sp_browsereplcmds and querying MSrepl_commands, I noticed that
replication queues up for these two articles. How can I check whether this
data has been replicated -- (I do not believe it has).
Also, I am not seeing any errors in replication but the queue keeps growing.
Why are no errors being thrown out?
select * from distribution.dbo.MSdistribution_status and check the number of
undelivered commands.
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
"Ziggy" <Ziggy@.discussions.microsoft.com> wrote in message
news:9B45D62C-616F-4D65-A02A-54FA74E24751@.microsoft.com...
>I have two publications (with only one article in each) based on the same
> source table. Both of these publications have one pull subscription each.
> Using sp_browsereplcmds and querying MSrepl_commands, I noticed that
> replication queues up for these two articles. How can I check whether
> this
> data has been replicated -- (I do not believe it has).
> Also, I am not seeing any errors in replication but the queue keeps
> growing.
> Why are no errors being thrown out?
>
|||The number of rows in MSrepl_commands and MSrepl_transactions will grow
without limitation. They are not removed when they have been applied to
each subscriber. Instead, a clean up process runs at a periodic interval.
This cleanup process removes anything older than the retention interval that
you specified. So, if you have a retention interval of 72 hours, the
cleanup process will remove anything from MSrepl_commands and
MSrepl_transactions that have been successfully applied to all subscribers
needing that transaction which are more than 72 hours old. Just because
data exists in these two tables doesn't mean that it has not been sent to
the subscriber.
MSdistribution_status will tell you how many rows have not been sent. You
can also spot check this using sp_browsereplcmds. It will give you the
exact data for the change sent. You can then simply run a select statement
against the subscriber to verify that the change made it.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"Ziggy" <Ziggy@.discussions.microsoft.com> wrote in message
news:9B45D62C-616F-4D65-A02A-54FA74E24751@.microsoft.com...
>I have two publications (with only one article in each) based on the same
> source table. Both of these publications have one pull subscription each.
> Using sp_browsereplcmds and querying MSrepl_commands, I noticed that
> replication queues up for these two articles. How can I check whether
> this
> data has been replicated -- (I do not believe it has).
> Also, I am not seeing any errors in replication but the queue keeps
> growing.
> Why are no errors being thrown out?
>
|||Thank you Mike and Hilary. Your answers were very helpful.
"Michael Hotek" wrote:

> The number of rows in MSrepl_commands and MSrepl_transactions will grow
> without limitation. They are not removed when they have been applied to
> each subscriber. Instead, a clean up process runs at a periodic interval.
> This cleanup process removes anything older than the retention interval that
> you specified. So, if you have a retention interval of 72 hours, the
> cleanup process will remove anything from MSrepl_commands and
> MSrepl_transactions that have been successfully applied to all subscribers
> needing that transaction which are more than 72 hours old. Just because
> data exists in these two tables doesn't mean that it has not been sent to
> the subscriber.
> MSdistribution_status will tell you how many rows have not been sent. You
> can also spot check this using sp_browsereplcmds. It will give you the
> exact data for the change sent. You can then simply run a select statement
> against the subscriber to verify that the change made it.
> --
> Mike
> Mentor
> Solid Quality Learning
> http://www.solidqualitylearning.com
>
> "Ziggy" <Ziggy@.discussions.microsoft.com> wrote in message
> news:9B45D62C-616F-4D65-A02A-54FA74E24751@.microsoft.com...
>
>
|||Actually, one more question. How do I check which replication commands /
transactions are not yet delivered? MSdistribution_Status ?
"Michael Hotek" wrote:

> The number of rows in MSrepl_commands and MSrepl_transactions will grow
> without limitation. They are not removed when they have been applied to
> each subscriber. Instead, a clean up process runs at a periodic interval.
> This cleanup process removes anything older than the retention interval that
> you specified. So, if you have a retention interval of 72 hours, the
> cleanup process will remove anything from MSrepl_commands and
> MSrepl_transactions that have been successfully applied to all subscribers
> needing that transaction which are more than 72 hours old. Just because
> data exists in these two tables doesn't mean that it has not been sent to
> the subscriber.
> MSdistribution_status will tell you how many rows have not been sent. You
> can also spot check this using sp_browsereplcmds. It will give you the
> exact data for the change sent. You can then simply run a select statement
> against the subscriber to verify that the change made it.
> --
> Mike
> Mentor
> Solid Quality Learning
> http://www.solidqualitylearning.com
>
> "Ziggy" <Ziggy@.discussions.microsoft.com> wrote in message
> news:9B45D62C-616F-4D65-A02A-54FA74E24751@.microsoft.com...
>
>
|||Check the subscriber and look at the value of transaction_timestamp for
your publication
select transaction_timestamp From MSreplication_subscriptions
Compare this with the xact_Seqno or xact_id in msrepl_transactions in your
publisher's distribution database. Get the xact_seqno - note that this
number will not be an exact match but rather in the range.
The number of rows remaining for that publication are the number of commands
which have to be applied there.
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
"Ziggy" <Ziggy@.discussions.microsoft.com> wrote in message
news:E478A229-D8A4-4511-807B-B977E8DA5E95@.microsoft.com...[vbcol=seagreen]
> Actually, one more question. How do I check which replication commands /
> transactions are not yet delivered? MSdistribution_Status ?
> "Michael Hotek" wrote:

Reproducable bug, yay!

Hi Ian,
Here is a good article about changes in behavior for this function, between
versions 2000 and 2005.
Change in Behavior of RAND and NEWID in SQL Server 2005
http://www.sqlmag.com/Articles/ArticleID/97032/97032.html?Ad=1
Enjoy it,
AMB
"Ian Boyd" wrote:

> Steps to reproduce:
> --Create test table of one uniqueidentifier column
> CREATE TABLE [dbo].[UniverseCollapse] (
> [SomeID] [uniqueidentifier] NOT NULL
> )
> --Add clustered index
> CREATE CLUSTERED INDEX [IX_UniverseCollapse_1] ON
> [dbo].[UniverseCollapse]([SomeID])
> --Add test row
> INSERT INTO UniverseCollapse (SomeID) VALUES
> ('F9CB8628-571D-463B-9E82-0AC4D0A3C2EB')
> --Run the select over and over. Sometimes returns zero rows, sometimes
> returns one.
> SELECT SomeID
> FROM UniverseCollapse
> WHERE SomeID = 'F9CB8628-571D-463B-9E82-0AC4D0A3C2EB'
> AND '6c03c85d-8151-43ed-858f-7ec5d887689b' <> newID()
>
> Run the select over and over and sometimes you get zero rows, sometimes you
> get one.
> Without the clustered index, it never fails.
> Looking closer at the two WHERE clause conditions:
> 1) SomeID = '...'
> This is always the case, as it is the value that was inserted.
> 2) '6c03...' <> newid()
> This is a trueism, since guid's don't conflict very that often.
> If we run just:
> SELECT SomeID
> FROM UniverseCollapse
> WHERE SomeID = 'F9CB8628-571D-463B-9E82-0AC4D0A3C2EB'
> we always get one row. If we run:
> SELECT SomeID
> FROM UniverseCollapse
> WHERE '6c03c85d-8151-43ed-858f-7ec5d887689b' <> newID()
> we always get one row. Have both criteria together, and we sometimes get
> zero rows.
> Execution Plan:
> |--Filter(
> WHERE
> [UniverseCollapse].[SomeID]<newid()
> OR
> [UniverseCollapse].[SomeID]>newid() ))
> |--Clustered Index Seek(
> OBJECT
> [foo].[dbo].[UniverseCollapse].[IX_UniverseCollapse_1]),
> SEEK[UniverseCollapse].[SomeID]=F9CB8628-571D-463B-9E82-0AC4D0A3C2EB)
> ORDERED FORWARD)
> The "ID < newid OR ID > newid" is very interesting. If "newid()" is
> evaluated twice, once for each half of the WHERE clause, and it happens to
> get a GUID that has swung the other way, it could then eliminate the row
> when it shouldn't.
>
> If i only execute:
> SELECT SomeID
> FROM UniverseCollapse
> WHERE '6c03c85d-8151-43ed-858f-7ec5d887689b' <> newID()
> i get the plan:
> |--Filter(
> WHERE
> STARTUP
> R(6C03C85D-8151-43ED-858F-7EC5D887689B<>newid()) ))
> |--Clustered Index Scan(
> OBJECT[foo].[dbo].[UniverseCollapse].[IX_UniverseCollapse_1]))
> And it's only evaluating newid() once. So the question then becomes, "Why
> does it fail when a clustered index is there?" Looking at the execution
> plan if i remove the clustered index:
> |--Filter(
> WHERESTARTUP EXPR(6C03C85D-8151-43ED-858F-7EC5D887689B<>newid())))
> |--Table Scan(
> OBJECT[foo].[dbo].[UniverseCollapse]),
> WHERE[UniverseCollapse].[SomeID]=F9CB8628-571D-463B-9E82-0AC4D0A3C2EB))
> It doesn't do a "guid > newid or guid < newid", but instead does a "Startup
> Expression". Which means that the problem is in fact that newID is being
> evaluated twice for the "field <> newid()"
>
> Yay! i found a bug! So do i get a cheque or something?
>
>
> Here is a good article about changes in behavior for this function,
> between
> versions 2000 and 2005.
> Change in Behavior of RAND and NEWID in SQL Server 2005
> http://www.sqlmag.com/Articles/ArticleID/97032/97032.html?Ad=1
It should be mentioned that these changes to newid() are not intended for
this case. These changes ensure that Rand() and Newid() are only evaluated
once for each reference. Before if you aliased a column that was a Rand or a
NewID, it would generate a new value for each time the alias is used.
For example in:
SELECT
CASE
WHEN TheValue < 0.5 THEN 'LessThanPoint5'
ELSE 'GreaterThanPoint5'
END AS Test1,
CASE
WHEN TheValue < 0.5 THEN 'LessThanPoint5'
ELSE 'GreaterThanPoint5'
END AS Test2,
CASE
WHEN TheValue < 0.5 THEN 'LessThanPoint5'
ELSE 'GreaterThanPoint5'
END AS Test3
FROM (SELECT rand() as TheValue) ADerivedTable
it happens that for any given execution, Test1 Test2 and Test3 need not be
equal, even through you're selecting rand() only once. Because the rand
column is aliased, it generates a new value.
This is also a bug, but not quite the situation i have, since i am not
referencing the rand or newid column more than once. The optimizer is
internally turning my one reference into two references - and then exposing
the bug.

Repost: Strange language mix

... Hmmmm. Either my brandnew OE has some problems in showing all
news/threads or.....
This is a repost of an article I wrote here and sent today 21:17. I cannot
find it... This is not the first time this happens to me, so I doubt to
have a news client problem...
Nevermind. Here the initial posting again.
Did anybody of you also encounter this strange language mixing problem? I'm
facing this from time to time, mostly when one component of my webserver had
to be restarted (e.g. IIS). Then RS appears either in plain english ("report
is beeing generated") or in a mixed form (german and english). If IIS is
restarted again everything is fine ...
Additional question: What is responsible for the language in which
subscription page is displayed?
I have uploaded two screenshots from the subscription page. One - ok.jpg -
shows the correct language layout and runs locally on a XP machine. The
latter - not_ok.jpg - runs on my web server and is not correct. This is
independent from the. a.m. restart situation.
http://www.ipviasky.net/Roland/rs/ok.JPG
http://www.ipviasky.net/Roland/rs/not_ok.JPG
The red dots show the problem zones. Both machines have GERMAN as "native"
language.
rolandThe language displayed is based on the accept language specified by the
browser header. We have not seen the problems you described. The
subscription information is a control that is associated with the delivery
extension. I'll see if anyone here can figure out how this could happen.
--
Brian Welcker
Group Program Manager
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Roland" <nomail@.spamprotect.com> wrote in message
news:ei6OrYVXEHA.2940@.TK2MSFTNGP09.phx.gbl...
> ... Hmmmm. Either my brandnew OE has some problems in showing all
> news/threads or.....
> This is a repost of an article I wrote here and sent today 21:17. I cannot
> find it... This is not the first time this happens to me, so I doubt to
> have a news client problem...
> Nevermind. Here the initial posting again.
> Did anybody of you also encounter this strange language mixing problem?
> I'm
> facing this from time to time, mostly when one component of my webserver
> had
> to be restarted (e.g. IIS). Then RS appears either in plain english
> ("report
> is beeing generated") or in a mixed form (german and english). If IIS is
> restarted again everything is fine ...
> Additional question: What is responsible for the language in which
> subscription page is displayed?
> I have uploaded two screenshots from the subscription page. One - ok.jpg -
> shows the correct language layout and runs locally on a XP machine. The
> latter - not_ok.jpg - runs on my web server and is not correct. This is
> independent from the. a.m. restart situation.
> http://www.ipviasky.net/Roland/rs/ok.JPG
> http://www.ipviasky.net/Roland/rs/not_ok.JPG
> The red dots show the problem zones. Both machines have GERMAN as "native"
> language.
> roland
>|||Brian, thanks for your answer.
> We have not seen the problems you described.
But you have seen this in my shots, right? OK, I'll wait for your results.
roland

Repost: Merge Replication Error - Failed to enumerate changes in the filtered article

Hi,
I am using Merge Replication and the subscriber is a pull subscriber.
Some tables are filtered, in the publication properties, if I go to FILTER
ROWS, then FILTER CLAUSE column, some tables are filtered like so
depot_system_id = 'xxxxx-xxxxx-xxxxx-xxxxxx' where x makes up the guid.
The replication objects are owned by DBO.
Versions of SQL:
Publisher:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: )
Subscriber:
MSDE
Everything was working fine, then all of a sudden, I get this error. (See
below)
Does anyone know what would cause this and how I can overcome it?
Thanks in Advance
Warren
************************************************** *
******************ERROR DETAILS******************
************************************************** *
Last command: {call sp_MSsetupbelongs(?,?,?,?,?,1,?,?,1,?,?,?,?,?,?)}
Error Message: Failed to enumerate changes in the filtered articles.
Error Details:
Failed to enumerate changes in the filtered articles.
(Source: Merge Replication Provider (Agent); Error number: -2147200925)
Incorrect syntax near the keyword 'where'.
(Source: GENCENTRIC_SVR1 (Data source); Error number: 156)
Incorrect syntax near the keyword 'and'.
(Source: GENCENTRIC_SVR1 (Data source); Error number: 156)
************************************************** *
*******************END OF ERROR******************
************************************************** *
Someone reported a similar problem and solved it by reapplying sp3a.
http://groups-beta.google.com/group/... e3a5eb8c1ea7a
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
"Warren Patterson" <des@.newsgroups.nospam> wrote in message
news:eYSANebNFHA.2468@.tk2msftngp13.phx.gbl...
> Hi,
> I am using Merge Replication and the subscriber is a pull subscriber.
> Some tables are filtered, in the publication properties, if I go to FILTER
> ROWS, then FILTER CLAUSE column, some tables are filtered like so
> depot_system_id = 'xxxxx-xxxxx-xxxxx-xxxxxx' where x makes up the guid.
> The replication objects are owned by DBO.
> Versions of SQL:
> Publisher:
> --
> Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
> Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation
> Standard Edition on Windows NT 5.2 (Build 3790: )
> Subscriber:
> --
> MSDE
>
> Everything was working fine, then all of a sudden, I get this error. (See
> below)
> Does anyone know what would cause this and how I can overcome it?
> Thanks in Advance
> Warren
> ************************************************** *
> ******************ERROR DETAILS******************
> ************************************************** *
> Last command: {call sp_MSsetupbelongs(?,?,?,?,?,1,?,?,1,?,?,?,?,?,?)}
> Error Message: Failed to enumerate changes in the filtered articles.
> Error Details:
> Failed to enumerate changes in the filtered articles.
> (Source: Merge Replication Provider (Agent); Error number: -2147200925)
> ----
--
> --
> Incorrect syntax near the keyword 'where'.
> (Source: GENCENTRIC_SVR1 (Data source); Error number: 156)
> ----
--
> --
> Incorrect syntax near the keyword 'and'.
> (Source: GENCENTRIC_SVR1 (Data source); Error number: 156)
> ----
--
> --
> ************************************************** *
> *******************END OF ERROR******************
> ************************************************** *
>
>
|||Hi Hilary,
Installing SP3a doesnt make sense to me. I have 4 other publications on
that same machine, setup the exact same way, except the filters are on other
ID {"depot_system_id = 'xxxxx-xxxxx-xxxxx-xxxxxx' where x makes up the
guid."} and they are working perfectly.
I am running service pack 3 only. I cant remember, but something in the
deep recesses of my mind is telling me that there was a reason I didnt
install SP3a onto the publisher, but I cant remember why.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eYPCVpeNFHA.508@.TK2MSFTNGP12.phx.gbl...
> Someone reported a similar problem and solved it by reapplying sp3a.
>
http://groups-beta.google.com/group/... e3a5eb8c1ea7a[vbcol=seagreen]
> --
> 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
> "Warren Patterson" <des@.newsgroups.nospam> wrote in message
> news:eYSANebNFHA.2468@.tk2msftngp13.phx.gbl...
FILTER[vbcol=seagreen]
(See
> ----
> --
> ----
> --
> ----
> --
>