Problem Replication With DTS

I have transactional replication with DTS in SQL 2000.
In the initial snapshop i got de next error (trasnlate fron de spanish) " The process found invalid column date in the bcp file -path-".
I review the bcp file but i didn't found spacial characters. In order to discard DTS problems, the DTS had only the defult transformations that the SQL creates for it.
The problem does not appear when i don't use DTS with the same data and conditions.
Somebody has anay idea about this error?
Thank you.
what was the error number?
I am afraid your English is too poor for me to understand (and my Spanish is
too bad as well) what you are trying to do and what the problem is. Can you
post this in Spanish for me, and I'll have it translated into English and
then post back in Spanish?
cul era el nmero del error? Estoy asustado que su ingls es demasiado
pobre para que entienda lo que usted est intentando hacer y cules es el
problema. Puede usted fijar esto en espaol para m, y m voluntad para
tenerla traducida a ingls y despus para fijarla detrs en espaol?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Rsantacruz" <Rsantacruz@.discussions.microsoft.com> wrote in message
news:E6D5EDE0-1481-4FDA-94B6-9C21AA24EB4A@.microsoft.com...
> I have transactional replication with DTS in SQL 2000.
> In the initial snapshop i got de next error (trasnlate fron de spanish) "
The process found invalid column date in the bcp file -path-".
> I review the bcp file but i didn't found spacial characters. In order to
discard DTS problems, the DTS had only the defult transformations that the
SQL creates for it.
> The problem does not appear when i don't use DTS with the same data and
conditions.
> Somebody has anay idea about this error?
> Thank you.
|||Thank you for your time Hilary and sorry for my English.
I have the next Transactional replication problems:
1) I performed transactional replication to Oracle subscriber.
The subscriber was configured using Micrososft OLE DB provider for Oracle, because I need to use DTS to transform the data before applying it to Oracle.
In the initial snatshop I got error (windows error) with distrib.exe:
The instruction at '<address>' referenced memory at '<address>'.
The memory could not be "read"
Click OK to terminate the program.
This problem appears with a table with a few rows. The only that I saw in the bcp file is that, there is some char(255) fields with blanks (like char(13), or returns in Word), when I removed some of this blanks from the bcp file and restart the synchro
nization the things go fine.
When I do the same replication of the same data to SQL subscriber it's fine too.
2) The second problem with other table that I got: having the same conditions as described previously
In the initial snatshop I got error (replication error)
"The process encountered invalid column data in bcp file -PATH-"
Not error number and nothing more in the error description.
And the same, when I saw the bcp file and cut some blanks in field (character field) the things go fine.
With SQL subscriber, it's fine too.
I did not use DTS in this case but the result is the same.
I reinstalled SQL SP3 and Win2000 SP4 and I got the same result.
I don't know if there is a some deficiency with OLE DB providers when you used them with replication.
If you know how to resolve this problem, please say me.
Thank yoo for your time, and sorry for this long post.

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

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!
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!
>

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.aspx?scid=kb;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\20051103135903\spGetCriticalSectionToken_32.sch'
could not be propagated to the subscriber.
The schema script '\\SERVER1\d$\sql
data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\20051103135903\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.aspx?scid=kb;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\20051103135903\spGetCriticalSectionToken_32.sch'
> could not be propagated to the subscriber.
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\20051103135903\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.aspx?scid=kb;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\20051103135903\spGetCriticalSectionToken_32.sch'
> could not be propagated to the subscriber.
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\20051103135903\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!
>

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/defaul...kb;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\
20051103135903\spGetCriticalSectionT
oken_32.sch'
could not be propagated to the subscriber.
The schema script '\\SERVER1\d$\sql
data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\
20051103135903\spGetCriticalSectionT
oken_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 di
d
two things: 1- qualified the server names in source code with [server-na
me]
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/defaul...kb;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\
20051103135903\spGetCriticalSectio
nToken_32.sch'
> could not be propagated to the subscriber.
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\
20051103135903\spGetCriticalSectio
nToken_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/defaul...kb;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\
20051103135903\spGetCriticalSectio
nToken_32.sch'
> could not be propagated to the subscriber.
> The schema script '\\SERVER1\d$\sql
> data\MSSQL\ReplData\unc\SERVER1_DB1_DB1\
20051103135903\spGetCriticalSectio
nToken_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!
>

Problem removing replication

Running SQL Server 2000. I removed the subscription and publication from a
database but the database is still showing that it is being replicated. I
have checked the tables in the distribution database and that database is not
listed. Anyone lese ver have this problem or now of a solution.
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ation/200610/1
The sp_dboption procedure will give you this information. Alternatively you
can use:
select name, databasepropertyex (name,'IsMergePublished') from
master..sysdatabases
select name, databasepropertyex (name,'IsPublished') from
master..sysdatabases
When you use sp_dboption you pass the database name as the parameter.
The output will look something like this:
The following options are set:
published
select into/bulkcopy
merge publish
trunc. log on chkpt.
auto create statistics
auto update statistics
If they are listed, you use sp_dboption to reverse the flag.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
"masmith via droptable.com" <u27472@.uwe> wrote in message
news:6834f742682f8@.uwe...
> Running SQL Server 2000. I removed the subscription and publication from a
> database but the database is still showing that it is being replicated. I
> have checked the tables in the distribution database and that database is
> not
> listed. Anyone lese ver have this problem or now of a solution.
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...ation/200610/1
>
|||Thank you worked wonderful
Paul Ibison wrote:[vbcol=seagreen]
>The sp_dboption procedure will give you this information. Alternatively you
>can use:
>select name, databasepropertyex (name,'IsMergePublished') from
>master..sysdatabases
>select name, databasepropertyex (name,'IsPublished') from
>master..sysdatabases
>When you use sp_dboption you pass the database name as the parameter.
>The output will look something like this:
>The following options are set:
>--
>published
>select into/bulkcopy
>merge publish
>trunc. log on chkpt.
>auto create statistics
>auto update statistics
>If they are listed, you use sp_dboption to reverse the flag.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ation/200610/1

problem pushing subscriber updates to publisher in transactional replication -

I have a primary and secondary servers both running Windows 2000 SP3 with SQL 2000 SP3. I have set up transactional replication with the primary server as publisher and the secondary server has the distributor and subscriber DB. I am testing the scenerio where my primary server goes down and I have to make updates to the secondary server until my primary server comes back up. I am able to update my subscriber database and the transactions go into the MSreplication_queue table to be pushed back to the primary when it comes back up. When I bring the primary server back up and start the queue agent job it starts pushing the transactions over and then stops after 4 or 5 transactions with the error "Failed while applying queued message to publisher". I have attached part of the log file for the agent below

dbserver2.Old_Processing: {? = call dbo.sp_getsqlqueueversion (?, ?, ?, ?)}
dbserver2.Old_Processing: {? = call dbo.sp_replsqlqgetrows (N'DBSERVER', N'Old_Processing', N'Old_Processing')}
[4/15/2004 3:59:47 PM]dbserver2.distribution: exec dbo.sp_helpdistpublisher @.publisher = N'DBSERVER'
Connecting to DBSERVER 'DBSERVER.Old_Processing'
DBSERVER.Old_Processing: {? = call dbo.sp_getqueuedarticlesynctraninfo (N'Old_Processing', 21)}
SQL Command : <exec [dbo].[sp_MSsync_ins_IQ2KProcSystem_1] N'dbserver2', N'Old_Processing', '072175', '2004-03-19 00:00:00.000', 1>
DBSERVER.Old_Processing: {? = call dbo.sp_getqueuedarticlesynctraninfo (N'Old_Processing', 15)}
SQL Command : <exec [dbo].[sp_MSsync_ins_NightlyProcess_1] N'dbserver2', N'Old_Processing', '072175', '2004-03-19 00:00:00.000', '2004-04-15 15:56:44.623000000', 'Begin ProcessIQ2KSystem', 'AB14E5D7-C81D-4A39-A8F5-51F1C48227B0', '17E5D98F-EDF0-41D0-9991-97511B850720', 1>
SQL Command : <exec [dbo].[sp_MSsync_upd_IQ2KProcSystem_1] N'dbserver2', N'Old_Processing', '072175', '2004-03-19 00:00:00.000', 1>
DBSERVER.Old_Processing: {? = call dbo.sp_getqueuedarticlesynctraninfo (N'Old_Processing', 7)}
SQL Command : <exec [dbo].[sp_MSsync_upd_TheatreProcess_1] N'dbserver2', N'Old_Processing', '072175', 1, '2004-03-19 00:00:00.000', 1, NULL, '79A114D6-FF31-4E37-AC2D-90C0A0114F40', '072175', 1, '2004-03-19 00:00:00.000', 0, NULL, 'AF61A098-44A3-45D7-B25B-E8EA9CD464A1', 0x2800, 1>
Failed while applying queued message to publisher
Disconnecting from DBSERVER 'DBSERVER'
Worker Thread 692 : Task Failed
Disconnecting from dbserver2 'dbserver2'
Processed 3 queued trans, 3 cmds, 0 conflicts
Queue Reader aborting

In the sql server logs I am getting this message:
Replication-Replication Transaction Queue Reader Subsystem: agent Repl Queue Reader failed. Failed while applying queued message to publisher.
Error: 14151, Severity: 18, State: 1

Any help would be greatly appreciatedFew suggestions:
Refer to SQLAgent log for further information.
Meanwhile, stopping and restarting SQLServerAgent may allow you to temporarily resolve the problem that you are experiencing.

Did you try to forcefully terminate any replication agents in task manager by any chance?

Finally, running the snapshot agent from the command line may allow you to determine whether it was the snapshot agent that crashed unexpectedly.|||Originally posted by Satya
Few suggestions:
Refer to SQLAgent log for further information.
Meanwhile, stopping and restarting SQLServerAgent may allow you to temporarily resolve the problem that you are experiencing.

Did you try to forcefully terminate any replication agents in task manager by any chance?

Finally, running the snapshot agent from the command line may allow you to determine whether it was the snapshot agent that crashed unexpectedly.

The SQLAgent log did not have any errors in it

Stopping and restarting SQLServerAgent did not allow me to temporarily resolve this problem. I still get the same error.

I did not forcefully terminate any replication agents in task manager.

Should I run the snapshot agent from the command line or the queue agent since the queue agent is what is failing?

I tried running the queue agent from the command line and it failed with the same error as above|||Check whether the KBA [http://support.microsoft.com/default.aspx?scid=kb;EN-US;294970] is any good to you.|||I don't think that is my problem. The only way I have been able to get the queue agent to work again is to either drop and readd the subscription or reinitialize the subscription. Of course when I do this it wipes out any updates that have been done to the subscriber.

Problem publishing. Was Error 21423......

Hi all.
Im trying to set up replication from Enterprise Manager to one of my
databases. I have successfly done it for the Northwind database in this
server but now I get this error when trying to do it for another database.
The complete error message I get when I click on the Finish button of the
wizard is:
Error 21423: You do not have sufficient privileges to view the publication
information. Your administrator may need to fix the PAL role on the publisher
for publication 'database_name'.
The only difference I've found between the Northwind database and this
database is a Role present in Northwind: MSmerge_1C6CDE....something that
looks like a GUID.
Any ideas?
Thanks in advance for your help,
RODOLFO
something is very wrong here. Are you logged on as the system administrator
when you are trying to create this publication? Do you have this problem
with other databases?
The MSMerge_14245 account is used by the PAL, it should be present when you
successfully create a publication.
Hilary Cotter
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
"RODOLFO" <RODOLFO@.discussions.microsoft.com> wrote in message
news:8D8429D9-95D7-4D54-9D4C-4936CECC6F12@.microsoft.com...
> Hi all.
> Im trying to set up replication from Enterprise Manager to one of my
> databases. I have successfly done it for the Northwind database in this
> server but now I get this error when trying to do it for another database.
> The complete error message I get when I click on the Finish button of the
> wizard is:
> --
> Error 21423: You do not have sufficient privileges to view the publication
> information. Your administrator may need to fix the PAL role on the
publisher
> for publication 'database_name'.
> --
> The only difference I've found between the Northwind database and this
> database is a Role present in Northwind: MSmerge_1C6CDE....something that
> looks like a GUID.
> Any ideas?
> Thanks in advance for your help,
> RODOLFO
|||Hi and thanks.
I am logged as the system administrator and Enterprise Manager is using the
sa account. I am able to publish almost every database, but not this one.
"Hilary Cotter" wrote:

> something is very wrong here. Are you logged on as the system administrator
> when you are trying to create this publication? Do you have this problem
> with other databases?
> The MSMerge_14245 account is used by the PAL, it should be present when you
> successfully create a publication.
> --
> Hilary Cotter
> 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
> "RODOLFO" <RODOLFO@.discussions.microsoft.com> wrote in message
> news:8D8429D9-95D7-4D54-9D4C-4936CECC6F12@.microsoft.com...
> publisher
>
>

problem on running replication on pocket pc

hi i tried to view a replication on a pocket pc app that i created. and i used the following code

private void Sync()
{
public string AppPath = System.IO.Path.GetDirectoryName(System.Reflection.Assembly.GetExecutingAssembly().GetName().CodeBase);
SqlCeReplication repl = new SqlCeReplication();

repl.InternetUrl = @."http://naomi/sqlmobile/sqlcesa30.dll";
repl.Publisher = @."Naomi";
repl.PublisherDatabase = @."SQLMobile";
repl.PublisherSecurityMode = SecurityType.DBAuthentication;
repl.PublisherLogin = @."sa";
repl.PublisherPassword = @."<...>";
repl.Publication = @."SQLMobile";
repl.Subscriber = @."SQLMobile";
repl.SubscriberConnectionString = @."Data Source=""" + AppPath + @."\SqlMobile.sdf"";Max Database Size=128;Default Lock Escalation =100;";
try
{
repl.AddSubscription(AddOption.ExistingDatabase);
repl.Synchronize();
}
catch (SqlCeException e)
{
MessageBox.Show(e.ToString());
}

when i run it i keep on getting the error:
The SQL Mobile Subscription already exists. Publisher, PublisherDatabase, and Publication for this subscription should be different from any existing subscription.

However, i can still view the contents of the datagrid that refers to the database subscription.

1. What should i do in order to stop getting the error above?
2. If i edit the contents of the datagrid in the pocket pc app how will i update the replication in the sql server? thanks

With the line of code "repl.AddSubscription(AddOption.ExistingDatabase)" you are effectively trying to add a new subscription to your local SQL Mobile database every time your synchronize. You only need to perform the AddSubscription the first time you synchronize with the server.

What I typically do is use AddOption.CreateDatabase, which dynamically creates the SQL Mobile database (if it does not already exist) the first time synchronization occurs.

-Darren

problem on msmerge_genhistory

anyone that could help me resolve this problem?

Our replication failed when it was rebooted during replication. (by Helpdesk people).
Here are some details I have found on the problem.
ran DBCC CHECKTABLE ('msmerge_genhistory') gave following with these error msg.

Server: Msg 8927, Level 16, State 1, Line 2
Object ID 408440579, index ID 0: The ghosted record count (1) in the header does not match the number of ghosted records (0) found on page (1:4344).
Server: Msg 8928, Level 16, State 1, Line 2
Object ID 408440579, index ID 0: Page (1:4346) could not be processed. See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 2
Table Corrupt: Object ID 408440579, index ID 0, page (1:4346), row 74. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 68 and 0.
Server: Msg 8928, Level 16, State 1, Line 2
Object ID 408440579, index ID 0: Page (1:92534) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 2
Table Corrupt: Object ID 408440579, index ID 0, page (1:92534). Test (m_freeCnt == freeCnt) failed. Values are 4967 and 4970.
Server: Msg 8928, Level 16, State 1, Line 2
Object ID 408440579, index ID 4: Page (1:11748) could not be processed. See other errors for details.
Server: Msg 8944, Level 16, State 1, Line 2
Table Corrupt: Object ID 408440579, index ID 4, page (1:11748), row 83. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 33 and 0.
DBCC results for 'MSmerge_genhistory'.
There are 14755 rows in 349 pages for object 'MSmerge_genhistory'.
CHECKTABLE found 0 allocation errors and 7 consistency errors in table 'MSmerge_genhistory' (object ID 408440579).

select name from sysobjects where id = 408440579 returns MSmerge_genhistory

Tried dbcc with repair_allow_data_loss option and still corrupt table.

Any help is thankfull.Can you do a select from the table?

Whats the primary key?

Can you select a subset?

Can you select all of them (probably not)

Do you have a clean backup?

If you have 1 error, you might have many more...|||I could select from the user tables just the merging job is not going through at all.
it is a system table

Structure:

guidsrc uniqueidentifier
guidlocal uniqueidentifier
pubid uniqueidentifier Nullable
generation int
art_nick int
nicknames varbinary
coldate datetime.

The data inside do have duplicate even tho they are unique.
I can't run count on identifier columns.
SELECT DISTINCT *
FROM original_table
GROUP BY key_value
HAVING COUNT(key_value) > 1
Reason Cannot run count or aggrigate on uniqueidentifier.
Hope this helps.

Edit:
There are no good back up. I just started a month ago here. It is very badly structured environment.|||They set up replication but didn't worry about backups?

Is the subscriber or the publisher hosed?

Or both?|||here is sample data.

guidsrc: {C831F2CB-A997-485E-A5A4-000B1752CFD8}
guidlocal: {ACDD4DD8-998D-41B5-A138-44AAAA4F093B}
pubid: {FB7BFC63-7310-4F07-997C-01379C9346A9}generation 649835
art_nick: 6980021
nicknames: <Binary>
coldate:11/10/2003 5:05:32 PM

guidsrc: {D0D2EF6E-41DB-4F47-920B-00222B86D637}
guidlocal: {D0D2EF6E-41DB-4F47-920B-00222B86D637}
pubid: <NULL>
generation 631726
art_nick: 6980025
nicknames: <Binary>
coldate: 11/2/2003 3:00:22 PM

guidsrc: {B175F50B-3057-4867-9AD6-0026360EF2D6}
guidlocal: {E2D260C9-E9C5-4D48-BD27-8E99ABA8DEAF}
pubid: {FB7BFC63-7310-4F07-997C-01379C9346A9}
generation 634705
art_nick: 6980014
nicknames: <Binary>
coldate: 11/3/2003 8:00:44 PM

As you can see pubid duplicates and there are over 100 records with same pubid.

subscriber is the one with problem.
Thought about droping replication and recreating after fixing so we won't run into more problem. but MIS director is an accountant and not comfortable in doing this.|||Here is the environment.
Around 160 locations setup with merge to 15 regions. (Understandable since remote locations)

The rest all resides in HQ
15 regions setup to 7 collection regions.
15 regions merge with main publisher.
7 Collection regions merge with collection server.
Collection server merge with main publisher.

Is this crazy enough or what.
Edit: Forgot about account server that is merging with collection server.
State dedicated servers replicating in same manner to a seperate server. then that seperate server replicate to the main publisher in state dedicated db.

Problem of realization replication through WEB

Hello

There is a following mistake at replication through WEB

A security error occurred

I try to go through IE which user has specified in the master of creation of the subscriber, in a diagnostic mode

https://Servak/Replication/replisapi.dll?diag

And all works, all certificates fulfil correctly who did not collide{face} in what business? WHERE TO DIG?

The name of the server on the certificate and the one you are using in the URL do not match. Hence the error.

It could also be that the the certificate is issued to machine.domain and you are using only machine in the URL. Please use the domain name and try again.

Match up the names on both and retry. Let me know if you continue to see the error.

|||

Certification all has adjusted as it is told BOL

The circuit has turned out such

http://replication2006.narod.ru/index.html

All the same deduces this mistake A security error occurred

The certificate signed the center of certification which has requested with IIS, has established the server certificate both on a server and on the client, and even having given{allowed} unlimited rights to participants of the circuit, it is impossible. Help! In what there can be a mistake? Where to dig?

|||

Here the text of a mistake from JOB

I enter this URL the address in IE all Ок!!

Help!

Selected row details:

Log Job History (REPL-GisisTerminalClient_RED-ReplTerm-SHEIN-GisisTerminalClient_RED- 0)

Step ID 1
Server SHEIN
Job Name REPL-GisisTerminalClient_RED-ReplTerm-SHEIN-GisisTerminalClient_RED- 0
Step Name Run agent.
Duration 00:00:31

Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
-XSTEPID 1
-XSUBSYSTEM Merge
-XSERVER SHEIN

-XCMDLINE 0
-XCancelEventHandle 00000634
2006-11-14 15:14:12.578 Connecting to Subscriber 'SHEIN'
2006-11-14 15:14:12.906 Connecting to Subscriber 'SHEIN'
2006-11-14 15:14:13.062 The upload message to be sent to Publisher 'REPL' is being generated
2006-11-14 15:14:13.078 The merge process is using Exchange ID '7AA8372B-F9E6-4F43-99AB-7C49614D2528' for this web synchronization session.

2006-11-14 15:14:28.500 A security error occurred

2006-11-14 15:14:28.546 Category:NULL
Source: Merge Process
Number: -2147209329

Message: A security error occurred

2006-11-14 15:14:28.546 Category:NULL
Source: Merge Process(Web Sync Client)
Number: -2147010889
Message: The Merge Agent could not connect to the URL 'https://repl/ReplWeb/replisapi.dll' during Web synchronization. Please verify that the URL, Internet login credentials and proxy server settings are correct and tha

Web server is reachable.

|||

Sorry, I dont understand from your reply whether the name of the server on the certificate matches the one on InternetURL in the merge agent.

I see in the job that you have: 'https://repl/ReplWeb/replisapi.dll'

Is the certificate issued to machine "repl"?

Is there domain name also on the certificate? If so, please try using that in the job parameter.

Have you installed the certificate on the client?

Security error is always a result of mismatch or the client does not trust the certificate.

|||

YES, I do{make} inquiry about receptions of the certificate from a computer repl, on a computer repl it is established IISб I sign the made inquiry in the center of certification and I transfer{pass} on repl signed by the center of certification the certificate and the root certificate cent Ра of certification, I install in IE the root certificate, and the certificate signed IIS I fix{establish} for adjustment{option} of encoding SSL, On the client I transfer{pass} the root certificate of the center of certification and I install it{him} with help IE

IE - tools - internet options - content - certificates - trusted root Certification Authorities - import

For check on the client I collect{type}:

<https://shein/ReplGAI/replisapi.dll?diag>

Any problems does not arise at once the window where it is necessary to enter Login and Password is deduced, I receive page:

http://replication2006.narod.ru/TestReplisapi.html

|||Are you saying the problem is now fixed or still have the issue?|||

No. The problem is!

Load a file, I there on steps have described and have drawn a problem. Thanks big that help me!!!

http://www.replication2006.narod.ru/Problem.rar

problem msde and sql server ce

I don't know how I can make the merge replication or RDA (push - pop) whit
SQL Server CE and MSDE.
Can you give me samples?
thanks
Damiano
you have to build an application using embedded vb/vc or the compact .net
framework, then install the application on SQL CE using active sync or its
ilk.
Then the application will pull a merge subscription or download the data
using RDA.
The SQL CE bol is quite complete with samples, or get ibuyspy.
"YAMNE" <damiano_callegari@.libero.it> wrote in message
news:O3skoV7XEHA.2360@.TK2MSFTNGP10.phx.gbl...
> I don't know how I can make the merge replication or RDA (push - pop) whit
> SQL Server CE and MSDE.
> Can you give me samples?
> thanks
> Damiano
>
|||Damiano,
have a look in SQL BOL for CE
(http://msdn.microsoft.com/library/de...-us/sqlce/htm/
_lce_repl_intro_replication.asp) - there's loads of info on setting up
replication.
As for MSDE, this article
(http://support.microsoft.com/default...;en-us;Q324992) should
help: How to use replication with SQL Server 2000 Desktop Engine (MSDE 2000)
HTH,
Paul Ibison
|||> you have to build an application using embedded vb/vc or the compact .net
> framework, then install the application on SQL CE using active sync or its
> ilk.
Compact .net framework and I use sql server ce in pocket pc emulator

> Then the application will pull a merge subscription or download the data
> using RDA.
I don't know how I can use the merge replicatio between SQL CE and MSDE.
Then using RDA push is OK but Pull give me problems (?)
Where i can find samples?
damiano
|||I'm a little confused by your post.
Here is a sample of using RDA - a pull.
http://msdn.microsoft.com/library/de..._prog_push.asp
Here is a sample using Merge replication - a pull
http://msdn.microsoft.com/library/de...p?frame=t rue
Are you getting an error? It sounds like your question is a basic how to.
Follow the links above. Basically you create your project using the .Net
Compact Framework, and then deploy it to your emulator. Then using your
emulator you launch your compliled code.
Am I missing something here?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"YAMNE" <damiano_callegari@.libero.it> wrote in message
news:eHh$83DYEHA.2344@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
..net[vbcol=seagreen]
its
> Compact .net framework and I use sql server ce in pocket pc emulator
>
> I don't know how I can use the merge replicatio between SQL CE and MSDE.
> Then using RDA push is OK but Pull give me problems (?)
> Where i can find samples?
> damiano
>
|||I have a problem.
I have read the northwindCE sample but I have the MSDE and the replication
configuration fails.
how I can make this sample with msde?
Damiano
|||what error message are you getting?
Are you printing out your error messages in your app?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"YAMNE" <damiano_callegari@.libero.it> wrote in message
news:%236EHOcEYEHA.2140@.TK2MSFTNGP11.phx.gbl...
> I have a problem.
> I have read the northwindCE sample but I have the MSDE and the replication
> configuration fails.
> how I can make this sample with msde?
> Damiano
>