Problem with 1 Server in 3 Server Peer-To-Peer

Boss created a new table in a database in which most, but not all, of
the tables are part articles in a peer-to-peer publication. He claims,
and I have no reason to doubt, that he did not add his new table to the
list of articles in the publication. Nevertheless, the replication on
the one server that he worked on is now failing with the message:
"Invalid object name dbo.hisTable"
The other two servers in the topology show no errors. The boss's table
is not among the articles listed for the publication. And, I can't fix
it! I deleted the table (it did not exist on the other two replicas). I
included it in the list of articles, let replication run for a couple
of minutes (still getting the same error), then de-listed the table.
All to no effect.
I'd appreciate any help anybody can offer.
Can you enable logging and post the results back here?
http://support.microsoft.com/default...312292&sd=tech
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
"EoRaptor013" <rchrismon@.gmail.com> wrote in message
news:1159914788.967187.170290@.m7g2000cwm.googlegro ups.com...
> Boss created a new table in a database in which most, but not all, of
> the tables are part articles in a peer-to-peer publication. He claims,
> and I have no reason to doubt, that he did not add his new table to the
> list of articles in the publication. Nevertheless, the replication on
> the one server that he worked on is now failing with the message:
> "Invalid object name dbo.hisTable"
> The other two servers in the topology show no errors. The boss's table
> is not among the articles listed for the publication. And, I can't fix
> it! I deleted the table (it did not exist on the other two replicas). I
> included it in the list of articles, let replication run for a couple
> of minutes (still getting the same error), then de-listed the table.
> All to no effect.
> I'd appreciate any help anybody can offer.
>
|||Hilary Cotter wrote:
> Can you enable logging and post the results back here?
>
Oh boy, now my ignorance goes on display. I don't see replication
logging anywhere in the documentation. Are you talking about the SQL
log?
Thanks.
Randy
|||Hilary,
I found a link to the MSDN documentation on replication logging in a
reply you made to someone else recently. I'll follow up and let you
know.
Thanks so much for the help.
|||Well, this is interesting! There's a bug either the documentation or in
the output logging implementation for replication agents. The
documentation clearly states that -Output should be the path and file
name of the text file for logging output:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/repref9/html/7b4fd480-9eaf-40dd-9a07-77301e44e2ac.htm
However, trying to enter any text yields an error that the -Output
parameter (NOT the -OutputVerboseLevel) must be an integer! Needless to
say, an integer doesn't help specify a file path and name.
I did enable verbose history but it doesn't seem to add any more
information. Here's what I get.
Date10/04/2006 10:52:19
LogJob History (ESICH1DV1-Endurance-EnduranceDEV20060821-ESINY1DV1-3)
Step ID2
ServerESICH1DV1
Job NameESICH1DV1-Endurance-EnduranceDEV20060821-ESINY1DV1-3
Step NameRun agent.
Duration00:41:20
Sql Severity0
Sql Message ID0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted0
Message
2006-10-04 16:33:27.943 Startup Delay: 9508 (msecs)
2006-10-04 16:33:37.442 Connecting to Distributor 'ESICH1DV1'
2006-10-04 16:33:37.567 Initializing
2006-10-04 16:33:37.567 Parameter values obtained from agent profile:
-bcpbatchsize 2147473647
-commitbatchsize 100
-commitbatchthreshold 1000
-historyverboselevel 2
-keepalivemessageinterval 300
-logintimeout 15
-maxbcpthreads 1
-maxdeliveredtransactions 0
-pollinginterval 5000
-querytimeout 1800
-skiperrors
-transactionsperhistory 100
2006-10-04 16:33:37.567 Connecting to Subscriber 'ESINY1DV1'
2006-10-04 16:33:39.645 Agent message code 208. Invalid object name
'dbo.genius_ClaimsLossQualificationDate'.
2006-10-04 16:33:39.661 Category:COMMAND
Source: Failed Command
Number:
Message: if @.@.trancount > 0 rollback tran
2006-10-04 16:33:39.661 Category:NULL
Source: Microsoft SQL Native Client
Number: 208
Message: Invalid object name 'dbo.genius_ClaimsLossQualificationDate'.
Thanks.
sql