I am seeing the following conflict message in a merge replication
system.
Statler is the subscriber (also, remote distributor) and
EMGSQL1 is the publisher
The row was updated at Statler.Caryn but could not be updated
at emgsql1.caryn. Can not update Tlightbox because TlightboxFile
exists.
Column Conflight WinnerConflict Loser
lightbox_id19881988
member_id10531053
lb_nameCustomerCustwomer
create_dt5/13/2005 12:00:00 am5/13/2005 12:00:00 AM
last_mod_dt
expiration_dt8/11/2005 12:00:00 am8/11/2005 12:00:00 am
email_check{74434092-E95F-40B6-9211-99700DB
rowguidrowguid_valueidentical
the table definition for tlightbox is:
CREATE TABLE [dbo].[TLightBox] (
[lightbox_id] [int] IDENTITY (1, 1) NOT FOR REPLICATION NOT NULL ,
[member_id] [int] NULL ,
[lb_name] [varchar] (255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[create_dt] [datetime] NULL ,
[last_mod_dt] [datetime] NULL ,
[expiration_dt] [datetime] NULL ,
[email_check] [uniqueidentifier] NULL ,
[rowguid] uniqueidentifier ROWGUIDCOL NOT NULL
) ON [PRIMARY]
GO
CREATE TABLE [dbo].[TLightboxFile] (
[lightbox_id] [int] NOT NULL ,
[modeltalent_id] [int] NOT NULL ,
[rank] [int] NULL ,
[rowguid] uniqueidentifier ROWGUIDCOL NOT NULL
) ON [PRIMARY]
GO
These tables are on both servers.
Any Ideas?
Thanks
Dave
what is the relationship between TLightBox and TLightBoxFile?
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
"David Gresham" <gresham@.panix.com> wrote in message
news:d62p39$lks$1@.reader1.panix.com...
> I am seeing the following conflict message in a merge replication
> system.
> Statler is the subscriber (also, remote distributor) and
> EMGSQL1 is the publisher
> The row was updated at Statler.Caryn but could not be updated
> at emgsql1.caryn. Can not update Tlightbox because TlightboxFile
> exists.
> Column Conflight Winner Conflict Loser
> lightbox_id 1988 1988
> member_id 1053 1053
> lb_name Customer Custwomer
> create_dt 5/13/2005 12:00:00 am 5/13/2005 12:00:00 AM
> last_mod_dt
> expiration_dt 8/11/2005 12:00:00 am 8/11/2005 12:00:00 am
> email_check {74434092-E95F-40B6-9211-99700DB
> rowguid rowguid_value identical
>
> the table definition for tlightbox is:
> CREATE TABLE [dbo].[TLightBox] (
> [lightbox_id] [int] IDENTITY (1, 1) NOT FOR REPLICATION NOT NULL ,
> [member_id] [int] NULL ,
> [lb_name] [varchar] (255) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
> [create_dt] [datetime] NULL ,
> [last_mod_dt] [datetime] NULL ,
> [expiration_dt] [datetime] NULL ,
> [email_check] [uniqueidentifier] NULL ,
> [rowguid] uniqueidentifier ROWGUIDCOL NOT NULL
> ) ON [PRIMARY]
> GO
>
> CREATE TABLE [dbo].[TLightboxFile] (
> [lightbox_id] [int] NOT NULL ,
> [modeltalent_id] [int] NOT NULL ,
> [rank] [int] NULL ,
> [rowguid] uniqueidentifier ROWGUIDCOL NOT NULL
> ) ON [PRIMARY]
> GO
>
> These tables are on both servers.
>
> Any Ideas?
> Thanks
>
> Dave
>
|||In article <ek417yCWFHA.2960@.TK2MSFTNGP15.phx.gbl>,
Hilary Cotter <hilary.cotter@.gmail.com> wrote:
>what is the relationship between TLightBox and TLightBoxFile?
>
I just looked at the tables in question and there is no
defined releationship set between them. The only relationship
defined for TlightBox was for another table called TMember
with MemberID as the relationship column.
>"David Gresham" <gresham@.panix.com> wrote in message
>news:d62p39$lks$1@.reader1.panix.com...
>
|||Just seeing if I had given you all the info you needed for
this question. This database is a legacy database where
the original developers are no longer around. There
are no fk's that would join the two tables in question.
Sincerely,
Dave Gresham
In article <ek417yCWFHA.2960@.TK2MSFTNGP15.phx.gbl>,
Hilary Cotter <hilary.cotter@.gmail.com> wrote:
>what is the relationship between TLightBox and TLightBoxFile?
>--
>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
>"David Gresham" <gresham@.panix.com> wrote in message
>news:d62p39$lks$1@.reader1.panix.com...
>
|||Your problem does not make a whole lot of sense. the best approach is to try
to repro it.
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
"David Gresham" <gresham@.panix.com> wrote in message
news:d6algu$st6$1@.reader1.panix.com...
> Just seeing if I had given you all the info you needed for
> this question. This database is a legacy database where
> the original developers are no longer around. There
> are no fk's that would join the two tables in question.
> Sincerely,
>
> Dave Gresham
>
> In article <ek417yCWFHA.2960@.TK2MSFTNGP15.phx.gbl>,
> Hilary Cotter <hilary.cotter@.gmail.com> wrote:
>
Showing posts with label distributor. Show all posts
Showing posts with label distributor. Show all posts
Saturday, 25 February 2012
Sunday, 12 February 2012
Configuring Distributor
I keep getting the error message:
An error occurred during decryption.
There is no remote user 'distributor_admin' mapped to local user '(null)'
from the remote server 'repl_distributor'.
Changed database context to 'master'. (Microsoft SQL Server, Error: 15466)
I have tried a local server account (as BOL describes), I have tried using
my own SQL account (that has sa priviliges of course), I have even tried the
domain account that runs SQL Agent service (despite the note right there on
the screen that recommends not to!). I get this error at the end of all the
steps whether I try to create a new publication or if I try to configure the
publisher.
ANY help would be appreciated!!
Is this SQL 2005? And is it part of an upgrade? SQL Server 2000 used a
remote server called repl_distributor which uses the distributor admin
account. In SQL Server 2005 this has been replaced by a linked server. In
some cases I have seen the upgrade of a replication topology with a remote
distributor does not work successfully.
In my cases I had to add the linked server and password manually, IIRC.
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
"mrdj" <mrdj@.discussions.microsoft.com> wrote in message
news:A3B17D13-3D6F-4B84-970A-F8FDDCB16144@.microsoft.com...
>I keep getting the error message:
> An error occurred during decryption.
> There is no remote user 'distributor_admin' mapped to local user '(null)'
> from the remote server 'repl_distributor'.
> Changed database context to 'master'. (Microsoft SQL Server, Error: 15466)
> I have tried a local server account (as BOL describes), I have tried using
> my own SQL account (that has sa priviliges of course), I have even tried
> the
> domain account that runs SQL Agent service (despite the note right there
> on
> the screen that recommends not to!). I get this error at the end of all
> the
> steps whether I try to create a new publication or if I try to configure
> the
> publisher.
> ANY help would be appreciated!!
|||It is a fresh install. Add a linked serer to what? could you send me the
details of adding the linked sever I am completely lost.
"Hilary Cotter" wrote:
> Is this SQL 2005? And is it part of an upgrade? SQL Server 2000 used a
> remote server called repl_distributor which uses the distributor admin
> account. In SQL Server 2005 this has been replaced by a linked server. In
> some cases I have seen the upgrade of a replication topology with a remote
> distributor does not work successfully.
> In my cases I had to add the linked server and password manually, IIRC.
> --
> 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
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:A3B17D13-3D6F-4B84-970A-F8FDDCB16144@.microsoft.com...
>
>
|||Check to ensure there is a linked server called repl_distributor and it uses
the security context of distributor_admin
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
"mrdj" <mrdj@.discussions.microsoft.com> wrote in message
news:D77607EC-1CA2-4D9E-8822-F4DCAA1D4976@.microsoft.com...[vbcol=seagreen]
> It is a fresh install. Add a linked serer to what? could you send me the
> details of adding the linked sever I am completely lost.
> "Hilary Cotter" wrote:
|||I tried adding the linked server and it STILL failed! But I'm making progess
because now I know exactly where the error is occuring, when adding the
linked server:
Msg 15466, Level 16, State 2, Procedure sp_addlinkedsrvlogin, Line 91
An error occurred during decryption.
Funny, I tried looking up this error number when all this first happened
(notice below, the text is a little different from my original error) and I
got nothing in my serarch results from Microsoft. I was able to get this to
work on another server, so at least I know it is some internal setting
specific to this server...Any ideas?
REALLY appreciate your help so far!!
"Hilary Cotter" wrote:
> Check to ensure there is a linked server called repl_distributor and it uses
> the security context of distributor_admin
> --
> 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
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:D77607EC-1CA2-4D9E-8822-F4DCAA1D4976@.microsoft.com...
>
>
|||Hilary,
Should this linked server be created on the distributor, or the subscriber,
or both? I am seeing a similar error when trying to setup replication in my
production environment, although it worked fine in test (currently being
rebuilt, so I have no comparison to use atm). I am thinking this might be a
part of my problem.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uoTqv58THHA.3592@.TK2MSFTNGP03.phx.gbl...
> Check to ensure there is a linked server called repl_distributor and it
uses[vbcol=seagreen]
> the security context of distributor_admin
> --
> 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
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:D77607EC-1CA2-4D9E-8822-F4DCAA1D4976@.microsoft.com...
the[vbcol=seagreen]
In
>
An error occurred during decryption.
There is no remote user 'distributor_admin' mapped to local user '(null)'
from the remote server 'repl_distributor'.
Changed database context to 'master'. (Microsoft SQL Server, Error: 15466)
I have tried a local server account (as BOL describes), I have tried using
my own SQL account (that has sa priviliges of course), I have even tried the
domain account that runs SQL Agent service (despite the note right there on
the screen that recommends not to!). I get this error at the end of all the
steps whether I try to create a new publication or if I try to configure the
publisher.
ANY help would be appreciated!!
Is this SQL 2005? And is it part of an upgrade? SQL Server 2000 used a
remote server called repl_distributor which uses the distributor admin
account. In SQL Server 2005 this has been replaced by a linked server. In
some cases I have seen the upgrade of a replication topology with a remote
distributor does not work successfully.
In my cases I had to add the linked server and password manually, IIRC.
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
"mrdj" <mrdj@.discussions.microsoft.com> wrote in message
news:A3B17D13-3D6F-4B84-970A-F8FDDCB16144@.microsoft.com...
>I keep getting the error message:
> An error occurred during decryption.
> There is no remote user 'distributor_admin' mapped to local user '(null)'
> from the remote server 'repl_distributor'.
> Changed database context to 'master'. (Microsoft SQL Server, Error: 15466)
> I have tried a local server account (as BOL describes), I have tried using
> my own SQL account (that has sa priviliges of course), I have even tried
> the
> domain account that runs SQL Agent service (despite the note right there
> on
> the screen that recommends not to!). I get this error at the end of all
> the
> steps whether I try to create a new publication or if I try to configure
> the
> publisher.
> ANY help would be appreciated!!
|||It is a fresh install. Add a linked serer to what? could you send me the
details of adding the linked sever I am completely lost.
"Hilary Cotter" wrote:
> Is this SQL 2005? And is it part of an upgrade? SQL Server 2000 used a
> remote server called repl_distributor which uses the distributor admin
> account. In SQL Server 2005 this has been replaced by a linked server. In
> some cases I have seen the upgrade of a replication topology with a remote
> distributor does not work successfully.
> In my cases I had to add the linked server and password manually, IIRC.
> --
> 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
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:A3B17D13-3D6F-4B84-970A-F8FDDCB16144@.microsoft.com...
>
>
|||Check to ensure there is a linked server called repl_distributor and it uses
the security context of distributor_admin
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
"mrdj" <mrdj@.discussions.microsoft.com> wrote in message
news:D77607EC-1CA2-4D9E-8822-F4DCAA1D4976@.microsoft.com...[vbcol=seagreen]
> It is a fresh install. Add a linked serer to what? could you send me the
> details of adding the linked sever I am completely lost.
> "Hilary Cotter" wrote:
|||I tried adding the linked server and it STILL failed! But I'm making progess
because now I know exactly where the error is occuring, when adding the
linked server:
Msg 15466, Level 16, State 2, Procedure sp_addlinkedsrvlogin, Line 91
An error occurred during decryption.
Funny, I tried looking up this error number when all this first happened
(notice below, the text is a little different from my original error) and I
got nothing in my serarch results from Microsoft. I was able to get this to
work on another server, so at least I know it is some internal setting
specific to this server...Any ideas?
REALLY appreciate your help so far!!
"Hilary Cotter" wrote:
> Check to ensure there is a linked server called repl_distributor and it uses
> the security context of distributor_admin
> --
> 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
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:D77607EC-1CA2-4D9E-8822-F4DCAA1D4976@.microsoft.com...
>
>
|||Hilary,
Should this linked server be created on the distributor, or the subscriber,
or both? I am seeing a similar error when trying to setup replication in my
production environment, although it worked fine in test (currently being
rebuilt, so I have no comparison to use atm). I am thinking this might be a
part of my problem.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uoTqv58THHA.3592@.TK2MSFTNGP03.phx.gbl...
> Check to ensure there is a linked server called repl_distributor and it
uses[vbcol=seagreen]
> the security context of distributor_admin
> --
> 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
>
> "mrdj" <mrdj@.discussions.microsoft.com> wrote in message
> news:D77607EC-1CA2-4D9E-8822-F4DCAA1D4976@.microsoft.com...
the[vbcol=seagreen]
In
>
configuring a publishing and distribution wizard
I am having a problem with configuring publiushed and distributor .i am
selecting the option to make the local server its own distibutor.
After competing the task, I am getting an enterprise manager error stating
that
Sql server manager could not configure the "SQLSERVER' as distibutore for
"SQLSERVER'
error 18483 could not connect th the server 'SQLSERVER' becouse
Distibutor_admin' is ot defined as a remote login at the server...
Need help!!
what happens if you do a select @.@.servername on the local server?
"Sam" <Sam@.discussions.microsoft.com> wrote in message
news:7B19D769-EFF7-4DB6-A2F0-9CBEE75BCC6D@.microsoft.com...
>I am having a problem with configuring publiushed and distributor .i am
> selecting the option to make the local server its own distibutor.
> After competing the task, I am getting an enterprise manager error stating
> that
> Sql server manager could not configure the "SQLSERVER' as distibutore for
> "SQLSERVER'
> error 18483 could not connect th the server 'SQLSERVER' becouse
> Distibutor_admin' is ot defined as a remote login at the server...
> Need help!!
|||As Hilary is alluding to, the @.@.servername valiable is probably incorrect.
If this is the case, you will need to run the sp_addserver procedure with
the local parameter to set it correctly. You may also need to run
sp_dropserver as well.
After doing this, you will need to stop and restart SQL Server for the
change to take effect.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Hi Guys,
I have tried the sp_addserver and sp_dropserver procedure, restarted the
server and i still have the sa me issue
"Rand Boyd [MSFT]" wrote:
> As Hilary is alluding to, the @.@.servername valiable is probably incorrect.
> If this is the case, you will need to run the sp_addserver procedure with
> the local parameter to set it correctly. You may also need to run
> sp_dropserver as well.
> After doing this, you will need to stop and restart SQL Server for the
> change to take effect.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>
|||what happens when you issue a select @.@.servername now
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Sam" <Sam@.discussions.microsoft.com> wrote in message
news:E443C6F1-24E8-4074-98CD-388AA6529D0E@.microsoft.com...[vbcol=seagreen]
> Hi Guys,
> I have tried the sp_addserver and sp_dropserver procedure, restarted the
> server and i still have the sa me issue
>
> "Rand Boyd [MSFT]" wrote:
incorrect.[vbcol=seagreen]
with[vbcol=seagreen]
rights.[vbcol=seagreen]
selecting the option to make the local server its own distibutor.
After competing the task, I am getting an enterprise manager error stating
that
Sql server manager could not configure the "SQLSERVER' as distibutore for
"SQLSERVER'
error 18483 could not connect th the server 'SQLSERVER' becouse
Distibutor_admin' is ot defined as a remote login at the server...
Need help!!
what happens if you do a select @.@.servername on the local server?
"Sam" <Sam@.discussions.microsoft.com> wrote in message
news:7B19D769-EFF7-4DB6-A2F0-9CBEE75BCC6D@.microsoft.com...
>I am having a problem with configuring publiushed and distributor .i am
> selecting the option to make the local server its own distibutor.
> After competing the task, I am getting an enterprise manager error stating
> that
> Sql server manager could not configure the "SQLSERVER' as distibutore for
> "SQLSERVER'
> error 18483 could not connect th the server 'SQLSERVER' becouse
> Distibutor_admin' is ot defined as a remote login at the server...
> Need help!!
|||As Hilary is alluding to, the @.@.servername valiable is probably incorrect.
If this is the case, you will need to run the sp_addserver procedure with
the local parameter to set it correctly. You may also need to run
sp_dropserver as well.
After doing this, you will need to stop and restart SQL Server for the
change to take effect.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Hi Guys,
I have tried the sp_addserver and sp_dropserver procedure, restarted the
server and i still have the sa me issue
"Rand Boyd [MSFT]" wrote:
> As Hilary is alluding to, the @.@.servername valiable is probably incorrect.
> If this is the case, you will need to run the sp_addserver procedure with
> the local parameter to set it correctly. You may also need to run
> sp_dropserver as well.
> After doing this, you will need to stop and restart SQL Server for the
> change to take effect.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>
|||what happens when you issue a select @.@.servername now
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Sam" <Sam@.discussions.microsoft.com> wrote in message
news:E443C6F1-24E8-4074-98CD-388AA6529D0E@.microsoft.com...[vbcol=seagreen]
> Hi Guys,
> I have tried the sp_addserver and sp_dropserver procedure, restarted the
> server and i still have the sa me issue
>
> "Rand Boyd [MSFT]" wrote:
incorrect.[vbcol=seagreen]
with[vbcol=seagreen]
rights.[vbcol=seagreen]
Subscribe to:
Posts (Atom)