Problem replication complex database

I have been have real trouble over the last few weeks trying to get an
application database to replicate. The database is relatively complex in
structure - but not ridiculously so.
It doesnt seem to matter what replication technique that is used we always
get the same problem.
Line516: Incorrect syntax near '-'.
(Source: SERVER2 (Data source); Error number: 50007)
xp_execresultset: unable to execute result set
{Source: SERVER2 (Data source); Error number: 50007)
The process could not deliver the snapshot to the Subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
However we found an article
http://support.microsoft.com/default...b;en-us;299439
We have followed this and tried moving the GUID columns to the end but now a
new error is seen...
The schema script '\\SERVER1\d$\sql
data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\2005110313 5903\spGetCriticalSectionToken_32.sch'
could not be propagated to the subscriber.
The schema script '\\SERVER1\d$\sql
data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\2005110313 5903\spGetCriticalSectionToken_32.sch'
could not be propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
------
Operand type clash: int is incompatible with uniqueidentifier
(Source: SERVER2(Data source); Error number: 206)
-----
Any ideas would be very welcome!
Could you please provide the SQL Server version of all servers involved --
select @.@.version.
Could you also please try to manually apply the schema script below to the
subscriber database via query analyzer. Hopefully, this will allow you to
determine where the failure is coming from in the script. Please post the
information back to this thread.
Thanks,
Tom
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mark Broadbent" <nospam@.nospam.co.uk> wrote in message
news:uCwDBuI4FHA.2364@.TK2MSFTNGP12.phx.gbl...
>I have been have real trouble over the last few weeks trying to get an
>application database to replicate. The database is relatively complex in
>structure - but not ridiculously so.
> It doesnt seem to matter what replication technique that is used we always
> get the same problem.
> Line516: Incorrect syntax near '-'.
> (Source: SERVER2 (Data source); Error number: 50007)
> xp_execresultset: unable to execute result set
> {Source: SERVER2 (Data source); Error number: 50007)
> The process could not deliver the snapshot to the Subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> However we found an article
> http://support.microsoft.com/default...b;en-us;299439
> We have followed this and tried moving the GUID columns to the end but now
> a new error is seen...
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\2005110313 5903\spGetCriticalSectionToken_32.sch'
> could not be propagated to the subscriber.
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\2005110313 5903\spGetCriticalSectionToken_32.sch'
> could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ------
> Operand type clash: int is incompatible with uniqueidentifier
> (Source: SERVER2(Data source); Error number: 206)
> -----
> Any ideas would be very welcome!
>
|||For what it is worth, we ran into similar '-' problems with our server names
in a recent re-engineering. I don't remember the error number(s), but we did
two things: 1- qualified the server names in source code with [server-name]
2- renamed several servers or changed dns entries to remove the
'-'
Just a thought.
Joseph R.P. Maloney, CSP,CCP,CDP
"Mark Broadbent" wrote:

> I have been have real trouble over the last few weeks trying to get an
> application database to replicate. The database is relatively complex in
> structure - but not ridiculously so.
> It doesnt seem to matter what replication technique that is used we always
> get the same problem.
> Line516: Incorrect syntax near '-'.
> (Source: SERVER2 (Data source); Error number: 50007)
> xp_execresultset: unable to execute result set
> {Source: SERVER2 (Data source); Error number: 50007)
> The process could not deliver the snapshot to the Subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> However we found an article
> http://support.microsoft.com/default...b;en-us;299439
> We have followed this and tried moving the GUID columns to the end but now a
> new error is seen...
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\2005110313 5903\spGetCriticalSectionToken_32.sch'
> could not be propagated to the subscriber.
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\2005110313 5903\spGetCriticalSectionToken_32.sch'
> could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ------
> Operand type clash: int is incompatible with uniqueidentifier
> (Source: SERVER2(Data source); Error number: 206)
> -----
> Any ideas would be very welcome!
>
>
|||Guys, thanks for your suggestions. It appears (I think) that the new problem
is down to a stored procedure inserting data into a table not using named
columns! Since the ordering of the tables has changed due to the GUID
columns being moved, this caused a problem. The developers have changed the
script.
br,
mark.
"Mark Broadbent" <nospam@.nospam.co.uk> wrote in message
news:uCwDBuI4FHA.2364@.TK2MSFTNGP12.phx.gbl...
>I have been have real trouble over the last few weeks trying to get an
>application database to replicate. The database is relatively complex in
>structure - but not ridiculously so.
> It doesnt seem to matter what replication technique that is used we always
> get the same problem.
> Line516: Incorrect syntax near '-'.
> (Source: SERVER2 (Data source); Error number: 50007)
> xp_execresultset: unable to execute result set
> {Source: SERVER2 (Data source); Error number: 50007)
> The process could not deliver the snapshot to the Subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> However we found an article
> http://support.microsoft.com/default...b;en-us;299439
> We have followed this and tried moving the GUID columns to the end but now
> a new error is seen...
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\2005110313 5903\spGetCriticalSectionToken_32.sch'
> could not be propagated to the subscriber.
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\2005110313 5903\spGetCriticalSectionToken_32.sch'
> could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ------
> Operand type clash: int is incompatible with uniqueidentifier
> (Source: SERVER2(Data source); Error number: 206)
> -----
> Any ideas would be very welcome!
>
sql