Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Subscribers are no longer getting all update applied at the Publisher

0 views
Skip to first unread message

jheaphy

unread,
Aug 12, 2008, 8:01:36 PM8/12/08
to
Some of the database updates on the Publisher are not being downloaded
to the Subscriber. However, all the changes at the subscribers are
being uploaded successfully to the Publisher. But, when I do a
complete download to a new local database I get all the data from the
Publisher. We've been running live for about one month. This was
working fine and we have made no configuration changes. I'm wondering
if we have the Publication configured correctly. And if we are might
some scheduled jobs.

Hilary Cotter

unread,
Aug 16, 2008, 11:21:33 AM8/16/08
to
Is it possible that these errors are showing up in the conflict table?

I also recently opened up a bug which involved timestamp columns which are
not at the end of a table.

Is this possibly your case too?

"jheaphy" <jjhe...@gmail.com> wrote in message
news:aa17b0ce-022e-4163...@a2g2000prm.googlegroups.com...

jheaphy

unread,
Aug 16, 2008, 3:50:59 PM8/16/08
to
On Aug 16, 8:21 am, "Hilary Cotter" <hilary.cot...@gmail.com> wrote:
> Is it possible that these errors are showing up in the conflict table?
>
> I also recently opened up a bug which involved timestamp columns which are
> not at the end of a table.
>
> Is this possibly your case too?
>
> "jheaphy" <jjhea...@gmail.com> wrote in message

>
> news:aa17b0ce-022e-4163...@a2g2000prm.googlegroups.com...
>
> > Some of the database updates on the Publisher are not being downloaded
> > to the Subscriber. However, all the changes at the subscribers are
> > being uploaded successfully to the Publisher. But, when I do a
> > complete download to a new local database I get all the data from the
> > Publisher. We've been running live for about one month. This was
> > working fine and we have made no configuration changes. I'm wondering
> > if we have the Publication configured correctly. And if we are might
> > some scheduled jobs.

Nope, no conflicts. I wish! I've opened a support ticket with
Microsoft and will post the results.

jheaphy

unread,
Aug 27, 2008, 12:10:06 PM8/27/08
to

The problem was on the IIS server. We had to apply SQL2005 SP2 to
upgrade the Sql Client Tools on the IIS server. Then we had to apply
the latest hot-fix bundle to the IIS server:
Yukon_SP2_CU6/09.00.3228.00

0 new messages