Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

sp_addlogin in MSA changed password

5 posts in General Discussion Last posting was on 2012-02-06 06:26:41.0Z
Eisen Posted on 2012-02-03 08:11:13.0Z
Sender: 5ab.4f2b4af8.1804289383@sybase.com
From: Eisen
Newsgroups: sybase.public.rep-server
Subject: sp_addlogin in MSA changed password
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4f2b96a1.1aad.1681692777@sybase.com>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 3 Feb 2012 00:11:13 -0800
X-Trace: forums-1-dub 1328256673 172.20.134.41 (3 Feb 2012 00:11:13 -0800)
X-Original-Trace: 3 Feb 2012 00:11:13 -0800, 172.20.134.41
Lines: 50
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9141
Article PK: 870303

Dear all
I've setup a MSA environment between sybwpmpp00.master
and sybwpmdr00.master. I created a db definition only
replicate system procedures --

create database replication definition master_smo_dbrep
with primary at sybwpmpp00.master
replicate system procedures
go

create subscription master_smo_dr_dbsub
for database replication definition master_smo_dbrep
with primary at sybwpmpp00.master
with replicate at sybwpmdr00.master
without materialization
go

after I check the subscription all valid on both sides. I
use sp_addlogin on primary --
sp_addlogin testuser1,facets,tempdb
go

right soon, I found on the sybwpmdr00,there's a new login
auto created -- name: testuser1. But when I use
testuser1/"facets" to login sybwpmdr00, it failed. With more
research I found the password in
sybwpmdr00.master..syslogins is different to that in
sybwpmpp00.master..syslogins.
--in sybwpmpp00, password is
"0xc0070f9e1bd41d0e5e80ae43e76a427be97bdc5cb8c76cbc8c1a206057a8d68a11b742aaf9938807badf"
but in sybwpmdr00, password is
"0xc0070f9e1bd41d0e5e80ae43e76a427be97bdc5cb8c76cbc8c1a206057a8d68a11b742aaf9938807ba"
-- the last byte disappeared.

I tested it again and again, it's all the same. So once I
hang on the DSI to sybwpmdr00.master and checked the queue
content --
begin transaction
exec sp_addlogin_rep @loginame='testuser1',
@passwd=0xc0070f9e1bd41d0e5e80ae43e76a427be97bdc5cb8c76cbc8c1a206057a8d68a11b742aaf9938807badf
, @defdb='tempdb', @deflanguage=NULL , @fullname=NULL ,
@passwdexp=NULL , @minpwdlen=NULL , @maxfailedlogins=NULL ,
@ auth_mech='ANY'
commit transaction

the password seems to be right in queue. What made the error
in next step? Thanks.

Best Regards
Eisen


Luc Van der Veurst Posted on 2012-02-03 15:31:59.0Z
From: "Luc Van der Veurst" <dba_azvub@hotmail.com>
Newsgroups: sybase.public.rep-server
References: <4f2b96a1.1aad.1681692777@sybase.com>
Subject: Re: sp_addlogin in MSA changed password
Lines: 68
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5931
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
X-Forwarded: by - (DeleGate/5.8.7)
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4f2bfdef$1@forums-1-dub>
Date: 3 Feb 2012 07:31:59 -0800
X-Trace: forums-1-dub 1328283119 10.22.241.152 (3 Feb 2012 07:31:59 -0800)
X-Original-Trace: 3 Feb 2012 07:31:59 -0800, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9142
Article PK: 870304

Hi,

Can you first check the parameters of sp_addlogin_rep ?
In master db :
sp_help sp_addlogin_rep
(it shouldn't find the procedure there)
in sybsystemprocs_db :
sp_help sp_addlogin_rep

Is @passwd defined as varbinary(256) ?

Luc.


First thing I woud check

<Eisen> wrote in message news:4f2b96a1.1aad.1681692777@sybase.com...
> Dear all
> I've setup a MSA environment between sybwpmpp00.master
> and sybwpmdr00.master. I created a db definition only
> replicate system procedures --
>
> create database replication definition master_smo_dbrep
> with primary at sybwpmpp00.master
> replicate system procedures
> go
>
> create subscription master_smo_dr_dbsub
> for database replication definition master_smo_dbrep
> with primary at sybwpmpp00.master
> with replicate at sybwpmdr00.master
> without materialization
> go
>
> after I check the subscription all valid on both sides. I
> use sp_addlogin on primary --
> sp_addlogin testuser1,facets,tempdb
> go
>
> right soon, I found on the sybwpmdr00,there's a new login
> auto created -- name: testuser1. But when I use
> testuser1/"facets" to login sybwpmdr00, it failed. With more
> research I found the password in
> sybwpmdr00.master..syslogins is different to that in
> sybwpmpp00.master..syslogins.
> --in sybwpmpp00, password is
> "0xc0070f9e1bd41d0e5e80ae43e76a427be97bdc5cb8c76cbc8c1a206057a8d68a11b742aaf9938807badf"
> but in sybwpmdr00, password is
> "0xc0070f9e1bd41d0e5e80ae43e76a427be97bdc5cb8c76cbc8c1a206057a8d68a11b742aaf9938807ba"
> -- the last byte disappeared.
>
> I tested it again and again, it's all the same. So once I
> hang on the DSI to sybwpmdr00.master and checked the queue
> content --
> begin transaction
> exec sp_addlogin_rep @loginame='testuser1',
> @passwd=0xc0070f9e1bd41d0e5e80ae43e76a427be97bdc5cb8c76cbc8c1a206057a8d68a11b742aaf9938807badf
> , @defdb='tempdb', @deflanguage=NULL , @fullname=NULL ,
> @passwdexp=NULL , @minpwdlen=NULL , @maxfailedlogins=NULL ,
> @ auth_mech='ANY'
> commit transaction
>
> the password seems to be right in queue. What made the error
> in next step? Thanks.
>
> Best Regards
> Eisen


Eisen Posted on 2012-02-06 06:04:34.0Z
Sender: 562.4f2f6cb1.1804289383@sybase.com
From: Eisen
Newsgroups: sybase.public.rep-server
Subject: Re: sp_addlogin in MSA changed password
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4f2f6d72.584.1681692777@sybase.com>
References: <4f2bfdef$1@forums-1-dub>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 5 Feb 2012 22:04:34 -0800
X-Trace: forums-1-dub 1328508274 172.20.134.41 (5 Feb 2012 22:04:34 -0800)
X-Original-Trace: 5 Feb 2012 22:04:34 -0800, 172.20.134.41
Lines: 78
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9144
Article PK: 870306

Hi Luc
Thanks for your reply. Yes. the parameter for
sp_addlogin_rep is varbinary(256)

Best Regards
Eisen

> Hi,
>
> Can you first check the parameters of sp_addlogin_rep ?
> In master db :
> sp_help sp_addlogin_rep
> (it shouldn't find the procedure there)
> in sybsystemprocs_db :
> sp_help sp_addlogin_rep
>
> Is @passwd defined as varbinary(256) ?
>
> Luc.
>
>
> First thing I woud check
> <Eisen> wrote in message
> > news:4f2b96a1.1aad.1681692777@sybase.com... Dear all
> > I've setup a MSA environment between sybwpmpp00.master
> > and sybwpmdr00.master. I created a db definition only
> > replicate system procedures --
> >
> > create database replication definition master_smo_dbrep
> > with primary at sybwpmpp00.master
> > replicate system procedures
> > go
> >
> > create subscription master_smo_dr_dbsub
> > for database replication definition master_smo_dbrep
> > with primary at sybwpmpp00.master
> > with replicate at sybwpmdr00.master
> > without materialization
> > go
> >
> > after I check the subscription all valid on both sides.
> > I use sp_addlogin on primary --
> > sp_addlogin testuser1,facets,tempdb
> > go
> >
> > right soon, I found on the sybwpmdr00,there's a new
> > login auto created -- name: testuser1. But when I use
> > testuser1/"facets" to login sybwpmdr00, it failed. With
> > more research I found the password in
> > sybwpmdr00.master..syslogins is different to that in
> > sybwpmpp00.master..syslogins.
> > --in sybwpmpp00, password is
> >
> "0xc0070f9e1bd41d0e5e80ae43e76a427be97bdc5cb8c76cbc8c1a206
> > 057a8d68a11b742aaf9938807badf" but in sybwpmdr00,
> > password is
> "0xc0070f9e1bd41d0e5e80ae43e76a427be97bdc5cb8c76cbc8c1a206
> > 057a8d68a11b742aaf9938807ba" -- the last byte
> disappeared. >
> > I tested it again and again, it's all the same. So once
> > I hang on the DSI to sybwpmdr00.master and checked the
> > queue content --
> > begin transaction
> > exec sp_addlogin_rep @loginame='testuser1',
> >
> @passwd=0xc0070f9e1bd41d0e5e80ae43e76a427be97bdc5cb8c76cbc
> > 8c1a206057a8d68a11b742aaf9938807badf , @defdb='tempdb',
> > @deflanguage=NULL , @fullname=NULL , @passwdexp=NULL ,
> > @minpwdlen=NULL , @maxfailedlogins=NULL , @
> > auth_mech='ANY' commit transaction
> >
> > the password seems to be right in queue. What made the
> > error in next step? Thanks.
> >
> > Best Regards
> > Eisen
>
>


"Mark A. Parsons" <iron_horse Posted on 2012-02-04 00:53:36.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: sybase.public.rep-server
Subject: Re: sp_addlogin in MSA changed password
References: <4f2b96a1.1aad.1681692777@sybase.com>
In-Reply-To: <4f2b96a1.1aad.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4f2c8190@forums-1-dub>
Date: 3 Feb 2012 16:53:36 -0800
X-Trace: forums-1-dub 1328316816 10.22.241.152 (3 Feb 2012 16:53:36 -0800)
X-Original-Trace: 3 Feb 2012 16:53:36 -0800, vip152.sybase.com
Lines: 57
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9143
Article PK: 870307

What happens if you manually run the sp_addlogin_rep command in the RDS?

What happens if you perform the equivalent 'create login' command (see source code for sp_addlogin_rep) in the RDS?

On 02/03/2012 01:11, Eisen wrote:
> Dear all
> I've setup a MSA environment between sybwpmpp00.master
> and sybwpmdr00.master. I created a db definition only
> replicate system procedures --
>
> create database replication definition master_smo_dbrep
> with primary at sybwpmpp00.master
> replicate system procedures
> go
>
> create subscription master_smo_dr_dbsub
> for database replication definition master_smo_dbrep
> with primary at sybwpmpp00.master
> with replicate at sybwpmdr00.master
> without materialization
> go
>
> after I check the subscription all valid on both sides. I
> use sp_addlogin on primary --
> sp_addlogin testuser1,facets,tempdb
> go
>
> right soon, I found on the sybwpmdr00,there's a new login
> auto created -- name: testuser1. But when I use
> testuser1/"facets" to login sybwpmdr00, it failed. With more
> research I found the password in
> sybwpmdr00.master..syslogins is different to that in
> sybwpmpp00.master..syslogins.
> --in sybwpmpp00, password is
> "0xc0070f9e1bd41d0e5e80ae43e76a427be97bdc5cb8c76cbc8c1a206057a8d68a11b742aaf9938807badf"
> but in sybwpmdr00, password is
> "0xc0070f9e1bd41d0e5e80ae43e76a427be97bdc5cb8c76cbc8c1a206057a8d68a11b742aaf9938807ba"
> -- the last byte disappeared.
>
> I tested it again and again, it's all the same. So once I
> hang on the DSI to sybwpmdr00.master and checked the queue
> content --
> begin transaction
> exec sp_addlogin_rep @loginame='testuser1',
> @passwd=0xc0070f9e1bd41d0e5e80ae43e76a427be97bdc5cb8c76cbc8c1a206057a8d68a11b742aaf9938807badf
> , @defdb='tempdb', @deflanguage=NULL , @fullname=NULL ,
> @passwdexp=NULL , @minpwdlen=NULL , @maxfailedlogins=NULL ,
> @ auth_mech='ANY'
> commit transaction
>
> the password seems to be right in queue. What made the error
> in next step? Thanks.
>
> Best Regards
> Eisen


Eisen Posted on 2012-02-06 06:26:41.0Z
Sender: 562.4f2f6cb1.1804289383@sybase.com
From: Eisen
Newsgroups: sybase.public.rep-server
Subject: Re: sp_addlogin in MSA changed password
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4f2f72a1.667.1681692777@sybase.com>
References: <4f2c8190@forums-1-dub>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 5 Feb 2012 22:26:41 -0800
X-Trace: forums-1-dub 1328509601 172.20.134.41 (5 Feb 2012 22:26:41 -0800)
X-Original-Trace: 5 Feb 2012 22:26:41 -0800, 172.20.134.41
Lines: 72
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9145
Article PK: 870308

Hi Mark
Thanks for your reply. It's interesting that -- when I
use that sp_addlogin_rep on 2012-02-03, the last byte
disapeared, but when I used the same command today, the last
byte exists...
So I tested with RS again with same username and password
-- today, all correct.

Best Regards
Eisen

> What happens if you manually run the sp_addlogin_rep
> command in the RDS?
>
> What happens if you perform the equivalent 'create login'
> command (see source code for sp_addlogin_rep) in the RDS?
>
>
>
> On 02/03/2012 01:11, Eisen wrote:
> > Dear all
> > I've setup a MSA environment between
> > sybwpmpp00.master and sybwpmdr00.master. I created a db
> > definition only replicate system procedures --
> >
> > create database replication definition master_smo_dbrep
> > with primary at sybwpmpp00.master
> > replicate system procedures
> > go
> >
> > create subscription master_smo_dr_dbsub
> > for database replication definition master_smo_dbrep
> > with primary at sybwpmpp00.master
> > with replicate at sybwpmdr00.master
> > without materialization
> > go
> >
> > after I check the subscription all valid on both sides.
> > I use sp_addlogin on primary --
> > sp_addlogin testuser1,facets,tempdb
> > go
> >
> > right soon, I found on the sybwpmdr00,there's a new
> > login auto created -- name: testuser1. But when I use
> > testuser1/"facets" to login sybwpmdr00, it failed. With
> > more research I found the password in
> > sybwpmdr00.master..syslogins is different to that in
> > sybwpmpp00.master..syslogins.
> > --in sybwpmpp00, password is
> >
> "0xc0070f9e1bd41d0e5e80ae43e76a427be97bdc5cb8c76cbc8c1a206
> > 057a8d68a11b742aaf9938807badf" but in sybwpmdr00,
> > password is
> "0xc0070f9e1bd41d0e5e80ae43e76a427be97bdc5cb8c76cbc8c1a206
> > 057a8d68a11b742aaf9938807ba" -- the last byte
> disappeared. >
> > I tested it again and again, it's all the same. So once
> > I hang on the DSI to sybwpmdr00.master and checked the
> > queue content --
> > begin transaction
> > exec sp_addlogin_rep @loginame='testuser1',
> >
> @passwd=0xc0070f9e1bd41d0e5e80ae43e76a427be97bdc5cb8c76cbc
> > 8c1a206057a8d68a11b742aaf9938807badf , @defdb='tempdb',
> > @deflanguage=NULL , @fullname=NULL , @passwdexp=NULL ,
> > @minpwdlen=NULL , @maxfailedlogins=NULL , @
> > auth_mech='ANY' commit transaction
> >
> > the password seems to be right in queue. What made the
> > error in next step? Thanks.
> >
> > Best Regards
> > Eisen