Obscure snapshot failure

[pa...@halo.uk.com]

I know this problem has been encountered by a couple of others using SQL
replication in various configurations. My configuration is:

Merge replication, SQL2K SP3, two publications, each containing some common
articles (tables).
Both publications are using dynamic filters with the suser_sname() function.

I setup publication A, this sets up fine and the snapshot is created ok.
I setup publication B, this sets up fine but the snapshot fails with the
error Invalid column name 'X'. X being one of the names of the columns used
in the row-filter in B.

The bizarre thing is when i re-run the snapshot on publication A - it fails
with the same message "Invalid column name 'X'" and X isn't even used in a
row-filter in A.

This behaviour has only appeared after applying SQL2K SP3 - this all worked
fine under SP2.

If anyone can help with this one, i.e. has any idea of the snapshot
generation process work; any help would be greatly appreciated.

Kind Regards
Paul Heston

[TSVK [MSFT]]

I would appreciate if you turn on profiler on publisher and get me a trace
with following events
SQL: batchstarting
SQL batchcompleted
SQL stmtstarting
SP starting
SPcompleted
SP stmt starting
RPC starting
RPC completed
Errors and exceptions

<pa...@halo.uk.com> wrote in message
news:b7h8af$l6t$1...@sparta.btinternet.com...

[pa...@halo.uk.com]

The trace returns over 5Mb of trace info. is it okay to post a compressed
trace file to the group?

"TSVK [MSFT]" <sql...@microsoft.com> wrote in message
news:eKWCfr8A...@TK2MSFTNGP11.phx.gbl...