JMI_ITS_TEMP (Agent); Error number: 27160

Hi,

I have a problem with my replication.

01- First I add all my new column by script
I got this message that might have something to do with my problem

Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'JMI_articles' because schema replication is performed.
Cannot add rows to sysdepends for the current stored procedure because it
depends on the missing object 'sp_sel_B2BDB0B28197433107A0CE875AF642A2_pal'.
The stored procedure will still be created.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'JMI_articles' because schema replication is performed.
Cannot add rows to sysdepends for the current stored procedure because it
depends on the missing object 'sp_sel_2E113488D5C4402207A0CE875AF642A2_pal'.
The stored procedure will still be created.
Warning: The table 'temps' has been created but its maximum row size (12148)
exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row
in this table will fail if the resulting row length exceeds 8060 bytes.
Warning: The table 'temps' has been created but its maximum row size (12148)
exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row
in this table will fail if the resulting row length exceeds 8060 bytes.
Warning: The table 'conflict_JMI_articles_Temps' has been created but its
maximum row size (14135) exceeds the maximum number of bytes per row (8060).
INSERT or UPDATE of a row in this table will fail if the resulting row length
exceeds 8060 bytes.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'JMI_articles' because schema replication is performed.
Cannot add rows to sysdepends for the current stored procedure because it
depends on the missing object 'sp_sel_3F9EAC1D6D32403107A0CE875AF642A2_pal'.
The stored procedure will still be created.
Warning: The table 'temps' has been created but its maximum row size (12157)
exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row
in this table will fail if the resulting row length exceeds 8060 bytes.
Warning: The table 'temps' has been created but its maximum row size (12157)
exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row
in this table will fail if the resulting row length exceeds 8060 bytes.
Warning: The table 'conflict_JMI_articles_Temps' has been created but its
maximum row size (14143) exceeds the maximum number of bytes per row (8060).
INSERT or UPDATE of a row in this table will fail if the resulting row length
exceeds 8060 bytes.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'JMI_articles' because schema replication is performed.
Cannot add rows to sysdepends for the current stored procedure because it
depends on the missing object 'sp_sel_3F9EAC1D6D32403107A0CE875AF642A2_pal'.
The stored procedure will still be created.
Warning: The table 'temps' has been created but its maximum row size (12165)
exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row
in this table will fail if the resulting row length exceeds 8060 bytes.
Warning: The table 'temps' has been created but its maximum row size (12165)
exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row
in this table will fail if the resulting row length exceeds 8060 bytes.
Warning: The table 'conflict_JMI_articles_Temps' has been created but its
maximum row size (14151) exceeds the maximum number of bytes per row (8060).
INSERT or UPDATE of a row in this table will fail if the resulting row length
exceeds 8060 bytes.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'JMI_articles' because schema replication is performed.
Cannot add rows to sysdepends for the current stored procedure because it
depends on the missing object 'sp_sel_3F9EAC1D6D32403107A0CE875AF642A2_pal'.
The stored procedure will still be created.
Warning: only Subscribers running SQL Server 2000 can synchronize with
publication 'JMI_articles' because schema replication is performed.
Cannot add rows to sysdepends for the current stored procedure because it
depends on the missing object 'sp_sel_B2BDB0B28197433107A0CE875AF642A2_pal'.
The stored procedure will still be created.

(Here i made a sum of all the caracters by rows in this table and the
maximum caracters that i find is 2020 caracters so i am far from 8060)

By the way what is the sp_sel_,,,,_pal I dont understand that ?

02- After that I create and Add all my new tables
03- After I Add those tables to my snapshot and reinitialise the snapshot
so it can contains my new articles. The sanpshot succeed.

04- Then I launch my pull subscription from the subscriber and I got this
message
in the

The schema script 'exec sp_repladdcolumn '[dbo].[temps]','HeuresRNC',' float
NOT NULL DEFAULT 0 WITH VALUES ', 'JMI_articles', 1' could not be
propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
---------------------------------------------------------------------------------------------------------------
A column was added to or dropped from the replicated table.
(Source: JMI_ITS_TEMP (Agent); Error number: 27160)
---------------------------------------------------------------------------------------------------------------
Délai d'attente expiré
(Source: ODBC SQL Server Driver (ODBC); Error number: 0)
---------------------------------------------------------------------------------------------------------------

What I dont understand is that I one column was added to the table temps and
the second one could not be added on the subcriber
It is the same type of column the only different is the name of the column

Do you have an idea ?

Thasnks in advance.
.

Relevant Pages

  • Re: Couple more fixes to merge replication problems
    ... where "article replication procedures" are ... warning that referenced procedure is missing. ... after referencing procedure is created. ... > this case problem is in stored procedure sp_mergearticlecolumn. ...
    (microsoft.public.sqlserver.replication)
  • Re: varchar(8000) versus text field?
    ... declare @tstr2 varchar ... Warning: The table 'Table1' has been created but its maximum row size ... this table will fail if the resulting row length exceeds 8060 bytes. ... >> you'd better watch out for going over the max rowsize. ...
    (microsoft.public.sqlserver.fulltext)
  • Re: maximum row size exceeds
    ... >exceeds the maximum number of bytes per row. ... This is a warning message, ... insert testit (pk, vc1, vc2) ...
    (microsoft.public.sqlserver.clients)
  • RE: nested triggers
    ... Thank you for using the newsgroup and it is my pleasure to help you with ... One more things I have to say is, when I create the table3, ... Warning: The table 'tcsintraTB_UserPages' has been created but its maximum ... row size exceeds the maximum number of bytes per row. ...
    (microsoft.public.sqlserver.programming)
  • question on warnings recieved after running sp_repladdcolumn and sp_repldropcolumn
    ... Warning: The table 'GeneralInventory' has been created but its maximum row ... UPDATE of a row in this table will fail if the resulting row length exceeds ...
    (microsoft.public.sqlserver.replication)
Loading