Distribution Cleanup Job Fails

The distribution cleanup job that runs for our transactional replication on
sql server 2005 fails.
The job is:
EXEC dbo.sp_MSdistribution_cleanup @.min_distretention = 0,
@.max_distretention = 72
The Error is:
Msg 20015, Level 16, State 1, Procedure sp_MSreplremoveuncdir, Line 83
Could not remove directory
'\\sprs76\rysrepldata\unc\SPRS76_RYS_RYS_OPERATION ALTOREPLICAHIST\20060713140760\'.
Check the security context of xp_cmdshell and close other processes that may
be accessing the directory.
Replication-@.rowcount_only parameter must be the value 0,1, or 2. 0=7.0
compatible checksum. 1=only check rowcou: agent
RYSSprs76_distribution@.rowcount_only parameter must be the value 0,1, or 2.
0=7.0 compatible checksu scheduled for retry. Could not clean up the
distribution transaction tables.
If I remove this directory manually, would it cause the replication to
fail? I have tried this on a Test server and it seems that the replication
fails.
I tried to run this job in the Query window and it return this same error.
Our data file is growing and I cannot shrink it because of this issue.
What can i do to resolve this?
Thanks,
George Gopie
There's an MMC snapin to look at shared folders and their connections and
open files. This snapin could be used to drop the connections where needed.
If you have the folder open yourself locally, this snapin won't pick it up,
so you'd have to use the task manager to see what is likely to be accessing
it.
Another possibility is to drop the folder yourself then recreate it for the
distribution agent to later delete.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||No it would not cause replication to fail, only remove this portion
20060713140760
Make sure that xp_cmdshell is enabled and the SQL Serer agent account has
rights to list files and folders and delete files on the root of the
repldata directory and it subdirectories.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
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
"georgeg" <ggg@.hotamil.com> wrote in message
news:DFE68859-01CF-4236-AC2A-F9CA596B9482@.microsoft.com...
> The distribution cleanup job that runs for our transactional replication
> on
> sql server 2005 fails.
> The job is:
> EXEC dbo.sp_MSdistribution_cleanup @.min_distretention = 0,
> @.max_distretention = 72
> The Error is:
> Msg 20015, Level 16, State 1, Procedure sp_MSreplremoveuncdir, Line 83
> Could not remove directory
> '\\sprs76\rysrepldata\unc\SPRS76_RYS_RYS_OPERATION ALTOREPLICAHIST\20060713140760\'.
> Check the security context of xp_cmdshell and close other processes that
> may
> be accessing the directory.
> Replication-@.rowcount_only parameter must be the value 0,1, or 2. 0=7.0
> compatible checksum. 1=only check rowcou: agent
> RYSSprs76_distribution@.rowcount_only parameter must be the value 0,1, or
> 2.
> 0=7.0 compatible checksu scheduled for retry. Could not clean up the
> distribution transaction tables.
>
> If I remove this directory manually, would it cause the replication to
> fail? I have tried this on a Test server and it seems that the replication
> fails.
> I tried to run this job in the Query window and it return this same error.
> Our data file is growing and I cannot shrink it because of this issue.
> What can i do to resolve this?
> Thanks,
> --
> George Gopie
>

Distribution Agent History Clean Up Fails

Hi everyone.
i'm using sql database 7.0 setup for merge replication.suddenly i found out
that the "Agent History Cleanup:Distribution" had a red x mark.When i
examined,it shows that the agent did not run on its specied running
schedule.Even if i run it manually,still it won't work. When i check the
history of the agent why it fails to run it state their that:
could not find the index entry for RID '361526d0688a801749800300101801000'
in index page (1:1084), index ID 0, database 'distribution'. [SQLSTATE HY000]
(Error 644). The step failed.
Is this error will affect the replication process of my server?How can i fix
this one?
I will really appreciate any help you could give and thanksin advance.
I'd run dbcc checkdb on the distribution database.
Also consider dbcc dbreindex on each table in the distribution database.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||hi sir.first i want to thank you for your response.
I still have some query about my problem sir.
I already run a dbcc checkdb on my distribution database,but unfortunately
it still not solve my problem.
The dbcc checkdb returns a result that "checkdb found 0 allocation errors
and 0 consistency errors in my database".
Is there other way to resolve this problem sir?
Will this miscellaneous agent error affects my database replication?
Thank you and more power.
"Paul Ibison" wrote:

> I'd run dbcc checkdb on the distribution database.
> Also consider dbcc dbreindex on each table in the distribution database.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>
|||OK - then please try running dbcc dbreinxdex on all tables in the
distribution database and we'll see if this fixes it.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Distribution agent fails with the following error message

The concurrent snapshot for publication<PubName> has not been activated by
the Log Reader Agent.
What did I do wrong ? I reinitinalized a subscription and the snapshot has
completed, but the distrib agent fails to start ..
has the snapshot agent started yet? Is the log reader agent started? Can you
bounce it?
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
"Jim" <jim@.hotmail.com> wrote in message
news:%23USywHPZFHA.3648@.TK2MSFTNGP14.phx.gbl...
> The concurrent snapshot for publication<PubName> has not been activated by
> the Log Reader Agent.
> What did I do wrong ? I reinitinalized a subscription and the snapshot has
> completed, but the distrib agent fails to start ..
>
|||I tried all of those..
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OTgqX%23PZFHA.892@.TK2MSFTNGP10.phx.gbl...
> has the snapshot agent started yet? Is the log reader agent started? Can
you[vbcol=seagreen]
> bounce it?
> --
> 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
> "Jim" <jim@.hotmail.com> wrote in message
> news:%23USywHPZFHA.3648@.TK2MSFTNGP14.phx.gbl...
by[vbcol=seagreen]
has
>
|||I'd drop the subscription and try again.
One more thing, if you deployed this publication from script make sure you
set @.status='active' in your sp_addpublication call,
ie
sp_addpublication 'test',@.status='active'
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
"Jim" <jim@.hotmail.com> wrote in message
news:uLuYLySZFHA.228@.TK2MSFTNGP12.phx.gbl...
>I tried all of those..
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:OTgqX%23PZFHA.892@.TK2MSFTNGP10.phx.gbl...
> you
> by
> has
>

Distribution Agent fails with Access Violation

I have a SQL Server 2000 installation on Windows 2000 Server, last night I
updated this server with SQL SP4. The install was successful but after the
installation one of my Publications failed with Data Transformation (DTS)
Failed.
In the Event log I have the following error.
Microsoft SQL Server Replication: The DISTRIB.EXE executable is terminating
abnormally because it hit an exception. Exception Code c0000005.
Check file ReplExceptDist.log for details
This log file does not exist on the Server.
I have traced the problem to a particular article in the publication. If I
Reinitilize this one application with a snapshot it is successful.
Any suggestions would be helpful at this point
Thanks
Janet
I think that this log should be in %windir%\system32
I have seen these events as well.Sometimes it is that the data is not in the
correct form and the distrib agent will fault, but on the next run will work
fine. Query your data to determine if this could account for the problem.
What happens if you restart your agent? Does the error clear?
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
"Janet" <Janet@.discussions.microsoft.com> wrote in message
news:BC4CCE66-3860-4558-B8BD-1AD6A6D99BD2@.microsoft.com...
> I have a SQL Server 2000 installation on Windows 2000 Server, last night I
> updated this server with SQL SP4. The install was successful but after
the
> installation one of my Publications failed with Data Transformation (DTS)
> Failed.
> In the Event log I have the following error.
> Microsoft SQL Server Replication: The DISTRIB.EXE executable is
terminating
> abnormally because it hit an exception. Exception Code c0000005.
> Check file ReplExceptDist.log for details
> This log file does not exist on the Server.
> I have traced the problem to a particular article in the publication. If I
> Reinitilize this one application with a snapshot it is successful.
> Any suggestions would be helpful at this point
> Thanks
> Janet
|||Log file is not in the system32 we have searched the entire machine for it.
I have checked the data and that looks fine, and the DTS should be ok too
because the Snapshot uses it and works. I have also restarted the SQL Agent
This article has been working now for a couple of months and started to fail
the moment SQL came back up after the SP4 install.
The other thing to note is that now whenever a distrubtion agent fails (for
other publications not just this one) the SPID doesn't seem to clear properly
and when the agent runs again it fails saying that the agent is already
running.
"Hilary Cotter" wrote:

> I think that this log should be in %windir%\system32
> I have seen these events as well.Sometimes it is that the data is not in the
> correct form and the distrib agent will fault, but on the next run will work
> fine. Query your data to determine if this could account for the problem.
> What happens if you restart your agent? Does the error clear?
> --
> 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
> "Janet" <Janet@.discussions.microsoft.com> wrote in message
> news:BC4CCE66-3860-4558-B8BD-1AD6A6D99BD2@.microsoft.com...
> the
> terminating
>
>
|||Hi Janet, i write from Italy, i have the same problem.
Have you resolved the problem.
I don' t know more what to make.
Thanks
"Janet" wrote:
[vbcol=seagreen]
> Log file is not in the system32 we have searched the entire machine for it.
> I have checked the data and that looks fine, and the DTS should be ok too
> because the Snapshot uses it and works. I have also restarted the SQL Agent
> This article has been working now for a couple of months and started to fail
> the moment SQL came back up after the SP4 install.
> The other thing to note is that now whenever a distrubtion agent fails (for
> other publications not just this one) the SPID doesn't seem to clear properly
> and when the agent runs again it fails saying that the agent is already
> running.
> "Hilary Cotter" wrote:
|||Same problem, but only on non DTS publications sharing distribution agent.
Sorry, Janet, no answer. Hope somebody find it soon.
Rafa

Distribution Agent Fails on Pull subscriptions

Environment:
SQLServer 2000 Enterprise w/SP3
Win 2000 Server w/SP3
In testing replication against a copy of our production database, when I run
the snapshot agent, it completes with success. When I then run the
distribution agent, I get the following error returned:
The name ' ' is not permitted in this context. Only constants, expressions,
or variables allowed here. Column names are not permitted.
(Source: STAGING2 (Data source); Error number: 128)
As near as I can tell, the script being processed when the error is
generated is:
================================================== ==
SET QUOTED_IDENTIFIER ON
GO
drop procedure [spBDCInsertAddressRecord]
GO
CREATE PROCEDURE [spBDCInsertAddressRecord] @.pAddress_id_out int OUT
AS
/************************************************** ************************************************** ******
INSERTS A BLANK ADDRESS RECORD AND RETURNS THE ADDRESS_ID VALUE
************************************************** ************************************************** *******/
INSERT INTO ADDRESS (LINE1) VALUES(" ")
SELECT @.pAddress_id_out = @.@.IDENTITY
RETURN 0
GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO
================================================== =
This is a Transactional replication and the subscription is a Pull
subscription. The address_id column is the primary key for the table and is
an automatically generated INT data type.
Any thoughts?
TIA,
Ken
Try using INSERT INTO ADDRESS (LINE1) VALUES(' ') -- ie single quotes
Rgds,
Paul Ibison
"kmkrause2" <kmkrause2@.discussions.microsoft.com> wrote in message
news:3C35C8AF-8CD0-44E7-898C-BBF2C0978F5E@.microsoft.com...
> Environment:
> SQLServer 2000 Enterprise w/SP3
> Win 2000 Server w/SP3
> In testing replication against a copy of our production database, when I
run
> the snapshot agent, it completes with success. When I then run the
> distribution agent, I get the following error returned:
> The name ' ' is not permitted in this context. Only constants,
expressions,
> or variables allowed here. Column names are not permitted.
> (Source: STAGING2 (Data source); Error number: 128)
> As near as I can tell, the script being processed when the error is
> generated is:
> ================================================== ==
> SET QUOTED_IDENTIFIER ON
> GO
> drop procedure [spBDCInsertAddressRecord]
> GO
> CREATE PROCEDURE [spBDCInsertAddressRecord] @.pAddress_id_out int OUT
> AS
>
/************************************************** *************************
*******************************
> INSERTS A BLANK ADDRESS RECORD AND RETURNS THE ADDRESS_ID VALUE
>
************************************************** **************************
*******************************/
> INSERT INTO ADDRESS (LINE1) VALUES(" ")
> SELECT @.pAddress_id_out = @.@.IDENTITY
> RETURN 0
> GO
> SET QUOTED_IDENTIFIER OFF
> GO
> SET ANSI_NULLS ON
> GO
> ================================================== =
> This is a Transactional replication and the subscription is a Pull
> subscription. The address_id column is the primary key for the table and
is
> an automatically generated INT data type.
> Any thoughts?
> TIA,
> Ken

Distribution agent failes with Invalid Column name 207 error

Hi,
We have setup one way transactional replication on SQL 2000 SP3a.
It was running fine for weeks and now the distribution agent fails with
"Invalid Column Name 'Name.' " message. I tried re-starting the agent,
even reintializing, but it doesn't work. I set the verboselevel to 3,
and captured the output to a log file.
I tried executing sp_MSupd_Item in QA and I get the same message, but
don't know what's causing it.
I would really appreciate if someone can help me with this.
Thanks
GG
The output log:
[5/11/2005 5:57:22 PM]MSNDMART-STG1.Item: {CALL sp_MSupd_Item
(NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL ,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL ,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,0,0, 0,NULL,NULL,NULL,0,NULL,NULL,NULL,NULL,NULL,NULL,0 ,0,NULL,NULL,NULL,?,NULL,NULL,NULL,NULL,NULL,NULL, NULL,
0,?,0x00000000008000)}
Last transaction timestamp: 0x000011a00000249a000100000000
Transaction seqno: 0x000011a0000024a50004
Command Id: 1
Partial: 0
Type: 68
Command: STLDMART-PRD1Item
Parameterized values for above command(s): {{2005-05-11 17:07:05.523,
'820HK14 '}}
Agent message code 20046. Invalid column name 'Name'.
Repl Agent Status: 6
[5/11/2005 5:57:22 PM]STLDBA-PRD1.Dist_Prod04: {call
sp_MSadd_distribution_history(3, 6, ?, ?, 0, 0, 0.00, 0x01, 1, ?, 5,
0x01, 0x01)}
Adding alert to msdb..sysreplicationalerts: ErrorId = 7,
Transaction Seqno = 000011a00000249a000100000000, Command ID = 5
Message: Replication-Replication Distribution Subsystem: agent
STLSQL-PROD04-Item-MSNDMART-STG1-3 failed. Invalid column name
'Name'.[5/11/2005 5:57:22 PM]STLDBA-PRD1.Dist_Prod04: {call
sp_MSadd_repl_alert(3, 3, 7, 14151, ?, 5, N'STLSQL-PROD04', N'Item',
N'MSNDMART-STG1', N'Item', ?)}
ErrorId = 7, SourceTypeId = 1
ErrorCode = ''
ErrorText = '{CALL sp_MSupd_Item
(NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL ,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL ,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,0,0, 0,NULL,NULL,NULL,0,NULL,NULL,NULL,NULL,NULL,NULL,0 ,0,NULL,NULL,NULL,2005-05-11
17:07:05.523,NULL,NULL,NULL,NULL,NULL,NULL,NULL,0, '820HK14
',0x00000000008000)} '
[5/11/2005 5:57:22 PM]STLDBA-PRD1.Dist_Prod04: {call
sp_MSadd_repl_error(7, 0, 1, ?, N'', ?)}
Category:COMMAND
Source: Failed Command
Number:
Message: {CALL sp_MSupd_Item
(NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL ,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL ,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,0,0, 0,NULL,NULL,NULL,0,NULL,NULL,NULL,NULL,NULL,NULL,0 ,0,NULL,NULL,NULL,2005-05-11
17:07:05.523,NULL,NULL,NULL,NULL,NULL,NULL,NULL,0, '820HK14
',0x00000000008000)}
Repl Agent Status: 3
ErrorId = 7, SourceTypeId = 5
ErrorCode = '207'
ErrorText = 'Invalid column name 'Name'.'
[5/11/2005 5:57:22 PM]STLDBA-PRD1.Dist_Prod04: {call
sp_MSadd_repl_error(7, 0, 5, ?, N'207', ?)}
Category:SQLSERVER
Source: MSNDMART-STG1
Number: 207
Message: Invalid column name 'Name'.
Repl Agent Status: 3
ErrorId = 7, SourceTypeId = 5
ErrorCode = '207'
ErrorText = 'Invalid column name 'Name'.'
[5/11/2005 5:57:22 PM]STLDBA-PRD1.Dist_Prod04: {call
sp_MSadd_repl_error(7, 0, 5, ?, N'207', ?)}
Category:SQLSERVER
Source: MSNDMART-STG1
Number: 207
Message: Invalid column name 'Name'.
Repl Agent Status: 3
ErrorId = 7, SourceTypeId = 5
ErrorCode = '207'
ErrorText = 'Invalid column name 'Name'.'
[5/11/2005 5:57:22 PM]STLDBA-PRD1.Dist_Prod04: {call
sp_MSadd_repl_error(7, 0, 5, ?, N'207', ?)}
Category:SQLSERVER
Source: MSNDMART-STG1
Number: 207
Message: Invalid column name 'Name'.
Repl Agent Status: 3
[5/11/2005 5:57:22 PM]MSNDMART-STG1.Item: exec
dbo.sp_MSupdatelastsyncinfo N'STLSQL-PROD04',N'Item', N'', 0, 6,
N'Invalid column name ''Name''.'
Disconnecting from Subscriber 'MSNDMART-STG1'
Disconnecting from Distributor 'STLDBA-PRD1'
Disconnecting from Distributor History 'STLDBA-PRD1'
Microsoft SQL Server Distribution Agent 8.00.760
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent:
STLSQL-PROD04-Item-MSNDMART-STG1-3
Startup Delay: 3427 (msecs)
Connecting to Distributor 'STLDBA-PRD1'
Repl Agent Status: 3
Connecting to Distributor 'STLDBA-PRD1.'
[5/11/2005 5:57:36 PM]STLDBA-PRD1.: exec sp_helpdistpublisher
N'STLSQL-PROD04'
[5/11/2005 5:57:36 PM]STLDBA-PRD1.Dist_Prod04: select @.@.SERVERNAME
can you edit the proc and put [] around a column called name?
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
"GG" <gdabbara@.gmail.com> wrote in message
news:1115855598.735328.54830@.g44g2000cwa.googlegro ups.com...
> Hi,
> We have setup one way transactional replication on SQL 2000 SP3a.
> It was running fine for weeks and now the distribution agent fails with
> "Invalid Column Name 'Name.' " message. I tried re-starting the agent,
> even reintializing, but it doesn't work. I set the verboselevel to 3,
> and captured the output to a log file.
> I tried executing sp_MSupd_Item in QA and I get the same message, but
> don't know what's causing it.
> I would really appreciate if someone can help me with this.
> Thanks
> GG
> The output log:
> [5/11/2005 5:57:22 PM]MSNDMART-STG1.Item: {CALL sp_MSupd_Item
>
(NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL ,NULL,NULL,NULL,NULL,NULL,
NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL, NULL,NULL,NULL,NULL,0,0,0,
NULL,NULL,NULL,0,NULL,NULL,NULL,NULL,NULL,NULL,0,0 ,NULL,NULL,NULL,?,NULL,NUL
L,NULL,NULL,NULL,NULL,NULL,0,?,0x00000000008000)}
> Last transaction timestamp: 0x000011a00000249a000100000000
> Transaction seqno: 0x000011a0000024a50004
> Command Id: 1
> Partial: 0
> Type: 68
> Command: STLDMART-PRD1Item
> Parameterized values for above command(s): {{2005-05-11 17:07:05.523,
> '820HK14 '}}
> Agent message code 20046. Invalid column name 'Name'.
> Repl Agent Status: 6
> [5/11/2005 5:57:22 PM]STLDBA-PRD1.Dist_Prod04: {call
> sp_MSadd_distribution_history(3, 6, ?, ?, 0, 0, 0.00, 0x01, 1, ?, 5,
> 0x01, 0x01)}
> Adding alert to msdb..sysreplicationalerts: ErrorId = 7,
> Transaction Seqno = 000011a00000249a000100000000, Command ID = 5
> Message: Replication-Replication Distribution Subsystem: agent
> STLSQL-PROD04-Item-MSNDMART-STG1-3 failed. Invalid column name
> 'Name'.[5/11/2005 5:57:22 PM]STLDBA-PRD1.Dist_Prod04: {call
> sp_MSadd_repl_alert(3, 3, 7, 14151, ?, 5, N'STLSQL-PROD04', N'Item',
> N'MSNDMART-STG1', N'Item', ?)}
> ErrorId = 7, SourceTypeId = 1
> ErrorCode = ''
> ErrorText = '{CALL sp_MSupd_Item
>
(NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL ,NULL,NULL,NULL,NULL,NULL,
NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL, NULL,NULL,NULL,NULL,0,0,0,
NULL,NULL,NULL,0,NULL,NULL,NULL,NULL,NULL,NULL,0,0 ,NULL,NULL,NULL,2005-05-11
> 17:07:05.523,NULL,NULL,NULL,NULL,NULL,NULL,NULL,0, '820HK14
> ',0x00000000008000)} '
> [5/11/2005 5:57:22 PM]STLDBA-PRD1.Dist_Prod04: {call
> sp_MSadd_repl_error(7, 0, 1, ?, N'', ?)}
> Category:COMMAND
> Source: Failed Command
> Number:
> Message: {CALL sp_MSupd_Item
>
(NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL ,NULL,NULL,NULL,NULL,NULL,
NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL, NULL,NULL,NULL,NULL,0,0,0,
NULL,NULL,NULL,0,NULL,NULL,NULL,NULL,NULL,NULL,0,0 ,NULL,NULL,NULL,2005-05-11
> 17:07:05.523,NULL,NULL,NULL,NULL,NULL,NULL,NULL,0, '820HK14
> ',0x00000000008000)}
> Repl Agent Status: 3
> ErrorId = 7, SourceTypeId = 5
> ErrorCode = '207'
> ErrorText = 'Invalid column name 'Name'.'
> [5/11/2005 5:57:22 PM]STLDBA-PRD1.Dist_Prod04: {call
> sp_MSadd_repl_error(7, 0, 5, ?, N'207', ?)}
> Category:SQLSERVER
> Source: MSNDMART-STG1
> Number: 207
> Message: Invalid column name 'Name'.
> Repl Agent Status: 3
> ErrorId = 7, SourceTypeId = 5
> ErrorCode = '207'
> ErrorText = 'Invalid column name 'Name'.'
> [5/11/2005 5:57:22 PM]STLDBA-PRD1.Dist_Prod04: {call
> sp_MSadd_repl_error(7, 0, 5, ?, N'207', ?)}
> Category:SQLSERVER
> Source: MSNDMART-STG1
> Number: 207
> Message: Invalid column name 'Name'.
> Repl Agent Status: 3
> ErrorId = 7, SourceTypeId = 5
> ErrorCode = '207'
> ErrorText = 'Invalid column name 'Name'.'
> [5/11/2005 5:57:22 PM]STLDBA-PRD1.Dist_Prod04: {call
> sp_MSadd_repl_error(7, 0, 5, ?, N'207', ?)}
> Category:SQLSERVER
> Source: MSNDMART-STG1
> Number: 207
> Message: Invalid column name 'Name'.
> Repl Agent Status: 3
> [5/11/2005 5:57:22 PM]MSNDMART-STG1.Item: exec
> dbo.sp_MSupdatelastsyncinfo N'STLSQL-PROD04',N'Item', N'', 0, 6,
> N'Invalid column name ''Name''.'
> Disconnecting from Subscriber 'MSNDMART-STG1'
> Disconnecting from Distributor 'STLDBA-PRD1'
> Disconnecting from Distributor History 'STLDBA-PRD1'
> Microsoft SQL Server Distribution Agent 8.00.760
> Copyright (c) 2000 Microsoft Corporation
> Microsoft SQL Server Replication Agent:
> STLSQL-PROD04-Item-MSNDMART-STG1-3
> Startup Delay: 3427 (msecs)
> Connecting to Distributor 'STLDBA-PRD1'
> Repl Agent Status: 3
> Connecting to Distributor 'STLDBA-PRD1.'
> [5/11/2005 5:57:36 PM]STLDBA-PRD1.: exec sp_helpdistpublisher
> N'STLSQL-PROD04'
> [5/11/2005 5:57:36 PM]STLDBA-PRD1.Dist_Prod04: select @.@.SERVERNAME
>
|||We don't have a column called name in any of our tables, being
replicated.
Thanks
GG