"Tony Toker" <xyzzy@identic.co.uk> wrote in message
news:crirfb$t5g$1$8300dec7@news.demon.co.uk...
> Under the conditions outlined in the kb article, we also get a failure in
> sp_replaaddcolumn:
>
> sp_repladdcolumn 'table_name','columnname','bit default 0','none'
> GO
>
> Server: Msg 207, Level 16, State 1, Procedure
> upd_7F7880ABD616444FAD031E1A0817242C, Line 72
> Invalid column name 'columnname'.
>
> sprepladdcolumn works fine on tables that are not filtered for merge
> replication.
>
> Can anyone on the consequences of adding the column without using
> sp_repladdcolumn? (The column won't be used for replication)
>
> Tony Toker
> Data Identic Ltd.
>
>

"Tony Toker" <xyzzy@identic.co.uk> wrote in message
news:crirfb$t5g$1$8300dec7@news.demon.co.uk...
> Under the conditions outlined in the kb article, we also get a failure in
> sp_replaaddcolumn:
>
> sp_repladdcolumn 'table_name','columnname','bit default 0','none'
> GO
>
> Server: Msg 207, Level 16, State 1, Procedure
> upd_7F7880ABD616444FAD031E1A0817242C, Line 72
> Invalid column name 'columnname'.
>
> sprepladdcolumn works fine on tables that are not filtered for merge
> replication.
>
> Can anyone on the consequences of adding the column without using
> sp_repladdcolumn? (The column won't be used for replication)
>
> Tony Toker
> Data Identic Ltd.
>
>

"Tony Toker" <xyzzy@identic.co.uk> wrote in message
news:crth55$k5i$1$8302bc10@news.demon.co.uk...
> Hilary / Kestutis
>
> Problem column is
>
> [AppearanceRef] [int] NOT NULL
>
> first column in the filtered table.
>
> SQL Version was 8.00.760, now 8.00.818
>
> After a conversation with MS support they advised that the fix for this
> problem (and a few others) is in the patch MS03-031
> http://support.microsoft.com/kb/821277 which takes the version to 8.00.818
>
> Applying this did not (for us) correct the problem for an existing
> publication, but it may do so for publications created in future, we'll be
> testing this week.
>
> Thanks for your interest,
>
> Tony Toker
>
>
>

"Kestutis Adomavicius" <kicker.lt@nospaamm_tut.by> wrote in message
news:uNFGouv9EHA.2192@TK2MSFTNGP14.phx.gbl...
> Could you check if stored procedure upd_7F7880ABD616444FAD031E1A0817242C
is
> a system object ? (in Enterprise
> manager see value in column Type beside this stored procedure).
>
> If it's not a SYSTEM object, then it might be a source of your mysterious
> problem, and I have a fix for that.
>
> --
> Regards,
> Kestutis Adomavicius
> Consultant
> UAB "Baltic Software Solutions"
>
>
> "Tony Toker" <xyzzy@identic.co.uk> wrote in message
> news:crth55$k5i$1$8302bc10@news.demon.co.uk...
> > Hilary / Kestutis
> >
> > Problem column is
> >
> > [AppearanceRef] [int] NOT NULL
> >
> > first column in the filtered table.
> >
> > SQL Version was 8.00.760, now 8.00.818
> >
> > After a conversation with MS support they advised that the fix for this
> > problem (and a few others) is in the patch MS03-031
> > http://support.microsoft.com/kb/821277 which takes the version to
8.00.818
> >
> > Applying this did not (for us) correct the problem for an existing
> > publication, but it may do so for publications created in future, we'll
be
> > testing this week.
> >
> > Thanks for your interest,
> >
> > Tony Toker
> >
> >
> >
>
>

"Kestutis Adomavicius" <kicker.lt@nospaamm_tut.by> wrote in message
news:uONMBdw9EHA.1524@TK2MSFTNGP09.phx.gbl...
> And also you could check if procedures with "_pal" at the end of their
names
> (for example upd_7F7880ABD616444FAD031E1A0817242C_pal) are system objects.
>
> --
> Regards,
> Kestutis Adomavicius
> Consultant
> UAB "Baltic Software Solutions"
>
>
> "Kestutis Adomavicius" <kicker.lt@nospaamm_tut.by> wrote in message
> news:uNFGouv9EHA.2192@TK2MSFTNGP14.phx.gbl...
> > Could you check if stored procedure upd_7F7880ABD616444FAD031E1A0817242C
> is
> > a system object ? (in Enterprise
> > manager see value in column Type beside this stored procedure).
> >
> > If it's not a SYSTEM object, then it might be a source of your
mysterious
> > problem, and I have a fix for that.
> >
> > --
> > Regards,
> > Kestutis Adomavicius
> > Consultant
> > UAB "Baltic Software Solutions"
> >
> >
> > "Tony Toker" <xyzzy@identic.co.uk> wrote in message
> > news:crth55$k5i$1$8302bc10@news.demon.co.uk...
> > > Hilary / Kestutis
> > >
> > > Problem column is
> > >
> > > [AppearanceRef] [int] NOT NULL
> > >
> > > first column in the filtered table.
> > >
> > > SQL Version was 8.00.760, now 8.00.818
> > >
> > > After a conversation with MS support they advised that the fix for
this
> > > problem (and a few others) is in the patch MS03-031
> > > http://support.microsoft.com/kb/821277 which takes the version to
> 8.00.818
> > >
> > > Applying this did not (for us) correct the problem for an existing
> > > publication, but it may do so for publications created in future,
we'll
> be
> > > testing this week.
> > >
> > > Thanks for your interest,
> > >
> > > Tony Toker
> > >
> > >
> > >
> >
> >
>
>

"Kestutis Adomavicius" <kicker.lt@nospaamm_tut.by> wrote in message
news:u$V7REy9EHA.3592@TK2MSFTNGP09.phx.gbl...
> Ok, I see... So looks like currently your system is impacted by the bug
> "introduced in version 8.00.818" :(
> These stored procedures with the "_pal" in the end of the name should be
> SYSTEM object.
>
> This problem is caused by a bug in stored procedure sp_MSsetartprocs. For
> more details and fixed stored procedure find my post in this newsgroup,
> named "Couple more fixes to merge replication problems" and posted on
> 2004.12.27
>
> After applying this fix, these stored procedures with "_pal" in the end of
> the name will be marked as SYSTEM objects. Of course it will happen only
for
> new publications.
> The way to fix your current publication (if you can not recreate it) is to
> mark all those procedures as SYSTEM objects (on publisher and subscriber).
> That can be done using exec dbo.sp_MS_marksystemobject. I have never tried
> to do that on runing replication, so I can not give you any hint if this
> will work... I detected this problem on test systems, so my approach was
to
> simply fix scripts included in MS patch MS03-031 (KB815495).
>
> --
> Regards,
> Kestutis Adomavicius
> Consultant
> UAB "Baltic Software Solutions"
>
>
> "Tony Toker" <xyzzy@identic.co.uk> wrote in message
> news:cru1v7$c2e$1$8302bc10@news.demon.co.uk...
> > upd_7F7880ABD616444FAD031E1A0817242C doesn't exist, closest is
> > upd_7F7880ABD616444F9CF278559C294C66 which is system
> >
> > however
> >
> > sel_26E366A06B2C4FB79CF278559C294C66_pal (and others with similar names)
> are
> > user
> >
> > Thanks
> >
> > Tony Toker
> >
> >
> >
> > "Kestutis Adomavicius" <kicker.lt@nospaamm_tut.by> wrote in message
> > news:uONMBdw9EHA.1524@TK2MSFTNGP09.phx.gbl...
> > > And also you could check if procedures with "_pal" at the end of their
> > names
> > > (for example upd_7F7880ABD616444FAD031E1A0817242C_pal) are system
> objects.
> > >
> > > --
> > > Regards,
> > > Kestutis Adomavicius
> > > Consultant
> > > UAB "Baltic Software Solutions"
> > >
> > >
> > > "Kestutis Adomavicius" <kicker.lt@nospaamm_tut.by> wrote in message
> > > news:uNFGouv9EHA.2192@TK2MSFTNGP14.phx.gbl...
> > > > Could you check if stored procedure
> upd_7F7880ABD616444FAD031E1A0817242C
> > > is
> > > > a system object ? (in Enterprise
> > > > manager see value in column Type beside this stored procedure).
> > > >
> > > > If it's not a SYSTEM object, then it might be a source of your
> > mysterious
> > > > problem, and I have a fix for that.
> > > >
> > > > --
> > > > Regards,
> > > > Kestutis Adomavicius
> > > > Consultant
> > > > UAB "Baltic Software Solutions"
> > > >
> > > >
> > > > "Tony Toker" <xyzzy@identic.co.uk> wrote in message
> > > > news:crth55$k5i$1$8302bc10@news.demon.co.uk...
> > > > > Hilary / Kestutis
> > > > >
> > > > > Problem column is
> > > > >
> > > > > [AppearanceRef] [int] NOT NULL
> > > > >
> > > > > first column in the filtered table.
> > > > >
> > > > > SQL Version was 8.00.760, now 8.00.818
> > > > >
> > > > > After a conversation with MS support they advised that the fix for
> > this
> > > > > problem (and a few others) is in the patch MS03-031
> > > > > http://support.microsoft.com/kb/821277 which takes the version to
> > > 8.00.818
> > > > >
> > > > > Applying this did not (for us) correct the problem for an existing
> > > > > publication, but it may do so for publications created in future,
> > we'll
> > > be
> > > > > testing this week.
> > > > >
> > > > > Thanks for your interest,
> > > > >
> > > > > Tony Toker
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

"Tony Toker" <xyzzy@identic.co.uk> wrote in message
news:cru1v7$c2e$1$8302bc10@news.demon.co.uk...
> upd_7F7880ABD616444FAD031E1A0817242C doesn't exist, closest is
> upd_7F7880ABD616444F9CF278559C294C66 which is system
>
> however
>
> sel_26E366A06B2C4FB79CF278559C294C66_pal (and others with similar names)
are
> user
>
> Thanks
>
> Tony Toker
>
>
>
> "Kestutis Adomavicius" <kicker.lt@nospaamm_tut.by> wrote in message
> news:uONMBdw9EHA.1524@TK2MSFTNGP09.phx.gbl...
> > And also you could check if procedures with "_pal" at the end of their
> names
> > (for example upd_7F7880ABD616444FAD031E1A0817242C_pal) are system
objects.
> >
> > --
> > Regards,
> > Kestutis Adomavicius
> > Consultant
> > UAB "Baltic Software Solutions"
> >
> >
> > "Kestutis Adomavicius" <kicker.lt@nospaamm_tut.by> wrote in message
> > news:uNFGouv9EHA.2192@TK2MSFTNGP14.phx.gbl...
> > > Could you check if stored procedure
upd_7F7880ABD616444FAD031E1A0817242C
> > is
> > > a system object ? (in Enterprise
> > > manager see value in column Type beside this stored procedure).
> > >
> > > If it's not a SYSTEM object, then it might be a source of your
> mysterious
> > > problem, and I have a fix for that.
> > >
> > > --
> > > Regards,
> > > Kestutis Adomavicius
> > > Consultant
> > > UAB "Baltic Software Solutions"
> > >
> > >
> > > "Tony Toker" <xyzzy@identic.co.uk> wrote in message
> > > news:crth55$k5i$1$8302bc10@news.demon.co.uk...
> > > > Hilary / Kestutis
> > > >
> > > > Problem column is
> > > >
> > > > [AppearanceRef] [int] NOT NULL
> > > >
> > > > first column in the filtered table.
> > > >
> > > > SQL Version was 8.00.760, now 8.00.818
> > > >
> > > > After a conversation with MS support they advised that the fix for
> this
> > > > problem (and a few others) is in the patch MS03-031
> > > > http://support.microsoft.com/kb/821277 which takes the version to
> > 8.00.818
> > > >
> > > > Applying this did not (for us) correct the problem for an existing
> > > > publication, but it may do so for publications created in future,
> we'll
> > be
> > > > testing this week.
> > > >
> > > > Thanks for your interest,
> > > >
> > > > Tony Toker
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>