Joe
You can use a distribution output log for the distribtuion agent and then see which command is causing the failure
Add this to the distriburtion agent job command
-output c:\dist.log -outputverboselevel 3

Stop the distribution agent and restart it.

You can also use SQL Profiler to get the same info

Regards
Paul Ibiso

ps if this works, please let me know how to reproduce your error

I always successfully created a snapshot of Northwind database and Pubs
database and published it. And I always successfully created subscribers
database for these sample databases. Then I published my own created
dabatase and many times I cannot created subscribers. A typical example is
as follow with it's error details, what is the problem and how can I fix
it?? This is and example error message with error details, what is the
problem here?? Normally what factors can cause unsuccessful/stop subscribers
creation???

Error Message:

The schema script '\\MERCURY\C$\Program Files\Microsoft SQL
Server\MSSQL\ReplData\unc\MERCURY_HOTL1_HOTL1Mercury\20040131012604\spADM_Da
taAsInsCommand_13.sch' could not be propagated to the subscriber.

Error Details:

The schema script '\\MERCURY\C$\Program Files\Microsoft SQL
Server\MSSQL\ReplData\unc\MERCURY_HOTL1_HOTL1Mercury\20040131012604\spADM_Da
taAsInsCommand_13.sch' could not be propagated to the subscriber.

(Source: Merge Replication Provider (Agent); Error number: -2147201001)

----------------------------------------------------------------------------
-----------------------------------

Invalid column name 'SELECT 'INSERT INTO '.

(Source: MERCURY (Data source); Error number: 207)

----------------------------------------------------------------------------
-----------------------------------

Invalid column name ' (TABLECOLUMNS) VALUES (' + '.

(Source: MERCURY (Data source); Error number: 207)

----------------------------------------------------------------------------
-----------------------------------

Hello -
Check the file:
\\MERCURY\C$\Program Files\Microsoft
SQLServer\MSSQL\ReplData\unc\MERCURY_HOTL1_HOTL1Mercury\20040131012604\spADM
_DataAsInsCommand_13.sch

This file would be creating an object. Check whether this file is looking
ok. Alternatively you can execute the contents of this file from a query
analyzer in your test database - just to check whether the file is ok or
not.

Also add the following in your distribution agent command property: -output
c:\distribution.log -outputverboselevel 3.

Once done, start the distribution agent and wait till it fails. Once the
agent is run, you can check the c:\distribution.log file to get to know
more information about why the agent failed. This file will give you good
indications as to what the detailed error is.

Regards,
Chandra


--------------------
||From: "Joe Mine" <huytuanattpgdotcomdotau>
||Subject: Cannot create Subscriber for some published Databases.??
||Date: Thu, 5 Feb 2004 16:22:10 +1100
||Lines: 43
||X-Priority: 3
||X-MSMail-Priority: Normal
||X-Newsreader: Microsoft Outlook Express 6.00.2800.1106
||X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
||Message-ID: <egKLDg66DHA.1052@TK2MSFTNGP12.phx.gbl>
||Newsgroups: microsoft.public.sqlserver.replication
||NNTP-Posting-Host: 220-244-64-102.tpgi.com.au 220.244.64.102
||Path:
cpmsftngxa07.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.
phx.gbl
||Xref: cpmsftngxa07.phx.gbl microsoft.public.sqlserver.replication:47004
||X-Tomcat-NG: microsoft.public.sqlserver.replication
||
||I always successfully created a snapshot of Northwind database and Pubs
||database and published it. And I always successfully created subscribers
||database for these sample databases. Then I published my own created
||dabatase and many times I cannot created subscribers. A typical example is
||as follow with it's error details, what is the problem and how can I fix
||it?? This is and example error message with error details, what is the
||problem here?? Normally what factors can cause unsuccessful/stop
subscribers
||creation???
||
||Error Message:
||
||The schema script '\\MERCURY\C$\Program Files\Microsoft SQL
||Server\MSSQL\ReplData\unc\MERCURY_HOTL1_HOTL1Mercury\20040131012604\spADM_
Da
||taAsInsCommand_13.sch' could not be propagated to the subscriber.
||
||Error Details:
||
||The schema script '\\MERCURY\C$\Program Files\Microsoft SQL
||Server\MSSQL\ReplData\unc\MERCURY_HOTL1_HOTL1Mercury\20040131012604\spADM_
Da
||taAsInsCommand_13.sch' could not be propagated to the subscriber.
||
||(Source: Merge Replication Provider (Agent); Error number: -2147201001)
||
||--------------------------------------------------------------------------
--
||-----------------------------------
||
||Invalid column name 'SELECT 'INSERT INTO '.
||
||(Source: MERCURY (Data source); Error number: 207)
||
||--------------------------------------------------------------------------
--
||-----------------------------------
||
||Invalid column name ' (TABLECOLUMNS) VALUES (' + '.
||
||(Source: MERCURY (Data source); Error number: 207)
||
||--------------------------------------------------------------------------
--
||-----------------------------------
||
||
||
||
||