Thanks for reply, its a standard SQL install with SP2. I have figured out how to add the detailed logging, And the output is below. When you look at the publication in Replication monitor the status says OK. The snapshots were generated successfully and I have copied them over to the machine acting as the subscriber. The replication is between non-trusted domains. I wonder if there are firewall issues. I have go through the exact same process with another site sucessfully.
2008-10-03 14:48:07.070 Connecting
to Subscriber 'CLSCOMLSQL02'
2008-10-03 14:48:07.101 Connecting
to OLE DB Subscriber at datasource: 'CLSCOMLSQL02', location: '', catalog:
'VRCore_CC_Rep', providerstring: '' using provider
'SQLNCLI'
2008-10-03 14:48:07.273 OLE DB
Subscriber: CLSCOMLSQL02
DBMS: Microsoft SQL Server
Version: 09.00.3159
catalog name: VRCore_CC_Rep
user name: dbo
API conformance: 0
SQL conformance: 0
transaction capable: 1
read only: F
identifier quote char: "
non_nullable_columns: 0
owner usage: 15
max table name len: 128
max column name len: 128
need long data len:
max columns in table: 1000
max columns in index: 16
max char literal len: 131072
max statement len: 131072
max row size: 131072
2008-10-03 14:48:07.320 OLE DB
Subscriber 'CLSCOMLSQL02': {call sp_MSgetversion }
2008-10-03 14:48:07.351 OLE DB
Subscriber 'CLSCOMLSQL02': set nocount on declare @dbname sysname select @dbname
= db_name() declare @collation nvarchar(255) select @collation =
convert(nvarchar(255), databasepropertyex(@dbname, N'COLLATION')) select
collationproperty(@collation, N'CODEPAGE') as 'CodePage',
collationproperty(@collation, N'LCID') as 'LCID', collationproperty(@collation,
N'COMPARISONSTYLE') as 'ComparisonStyle',cast(case when convert
(int,databasepropertyex (@dbname,'comparisonstyle')) & 0x1 = 0x1 then 0 else
1 end as bit) as DB_CaseSensitive,cast(case when convert (int,serverproperty
('comparisonstyle')) & 0x1 = 0x1 then 0 else 1 end as bit) as
Server_CaseSensitive set nocount off
2008-10-03 14:48:07.445 The
subscription to publication 'VRCore_CC' could not be verified. Ensure that all
Merge Agent command line parameters are specified correctly and that the
subscription is correctly configured. If the Publisher no longer has information
about this subscription, drop and recreate the subscription.
2008-10-03 14:48:07.507 Percent
Complete: 0
2008-10-03 14:48:07.539
Category:NULL
Source: Merge Replication
Provider
Number:
-2147201019
Message: The subscription to
publication 'VRCore_CC' could not be verified. Ensure that all Merge Agent
command line parameters are specified correctly and that the subscription is
correctly configured. If the Publisher no longer has information about this
subscription, drop and recreate the subscription.