Skip to Content
avatar image
-1
Former Member

sp_password_rep

Hi,

I am using master database replication with ASE 15.7 SP 130

Replication Server/15.7.1/EBF 23940 SP205

DSI for master database is down.

I. 2015/07/19 07:31:38. ...... connected to server 'M20_live_lq' as user 'master_maint'.

E. 2015/07/19 07:31:38. ERROR #1028 DSI EXEC(122(1) M20_live_lq.master) - \generic\useful\cm.c(5052)

Message from server: Message: 4002, State 1, Severity 14 -- 'Login failed.

'.

E. 2015/07/19 07:31:38. ERROR #1027 DSI EXEC(122(1) M20_live_lq.master) - \generic\useful\cm.c(5052)

Open Client Client-Library error: Error: 67175468, Severity 4 -- 'ct_connect(): protocol specific layer: external error: The attempt to connect to the server failed.'.

E. 2015/07/19 07:31:38. ERROR #13045 DSI EXEC(122(1) GACWAREUNITEDR.master) - \generic\useful\cm.c(5056)

Failed to connect to server 'M20_live_lq' as user 'cbasa'. See CT-Lib and/or server error messages for more information.

I. 2015/07/19 07:31:38. The DSI thread for database 'M20_live_lq.master' is shutdown.

rs_helpexception is showing the below:

exec sp_password_rep @caller_password=NULL , @new_password=0xc007410aebb5792521c550387fe379df6f573a90a10adfc5eecca0a99e9f159c3c0f088fede5ee48ed6f, @loginame='cbasa', @immediate=0

I am changing the password on Active using an application, invoking sp_password.

How can I correct this situaion?

Regards,

Elio

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

5 Answers

  • avatar image
    Former Member
    Jul 20, 2017 at 07:56 PM

    Marc, that is not my log and I am not able to paste it here because I am working remotely. The fact here is that I am having the same problem shown in this error log. I found this (and is the same situation) but never found how to solve it, I do not know what to do. Every time an user changes the password the thread is going down so I need to fix it manually.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      This happen to a different person and you gave an explanation but I do not know how the other Marc solved the situation.

  • avatar image
    Former Member
    Jul 20, 2017 at 11:40 PM

    Yes, it is a MSA. I have synchronized syslogins table in all 3 replicate sites. Thanks, taking a look to the guide. I appreciate your help.

    How does the other Marc fixed the problem?

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 20, 2017 at 06:48 PM

    For immediate relief you can do the change on replicate by hand and skip the transaction.

    I have not used master database replication so far.

    But what caught my attention was caller password shown as null in the rs_helpexception output.

    That may be also the reason of connection failure for "sa" (or equivalent) account connecting to execute sp_password on replicate side.

    As an FYI : sp_password may be get obsoleted in preference to "alter login" in the later ASE versions. So you may want to change the calls from your application.

    HTH

    Avinash

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 20, 2017 at 07:40 PM

    Are you sure this is an issue?

    1 - Your errorlog entries are showing a datetime stamp from July 19, 2015 ... 2015 ... 2 years ago!

    2 - Other than what I assume is an edit of the database name (from 'GACWAREUNITEDR' to 'M20_live_Iq' - you missed an edit) and login name (from 'evenseno3397' to 'cbasa'), it looks like you've cut-n-pasted, almost word-for-word (right down to the same title for your post, the same exact ASE version, errorlog datetime stamps and message text, varbinary value of @new_password, etc), what Marc Daccache posted back on July 21, 2015 re: sp_password_rep

    If you are in fact having a problem with master db replication then I suggest you provide the contents of *your* errorlog (and not a cut-n-paste-n-edited copy of someone else's post from 2 years ago).

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 20, 2017 at 08:18 PM

    If only I had a nickel for every time someone's said "I'm having the same problem as ...", just to find they don't have the same problem :-)

    Without the contents from the errorlog in question we have to *assume* the problems are identical, but if they're not identical then possible solutions a) may not address the issue or b) may cause more harm than good.

    At this point ... and assuming this is a MSA setup ... I'd recommend verifying the requirements and setup steps outlined in SRS Admin Guide Vol 1, Replicating the Master database in an MSA environment. [My bet is on the syslogins table not being in sync.]

    NOTE: Yes, I've got master database replication working in several locations (based on the steps outlined in that link), and password changes (via sp_password or alter login) are working just fine.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Yes, it is a MSA. I have synchronized syslogins table in all 3 replicate sites. Thanks, taking a look to the guide. That is the guide I use to set up master database for replication.

      How does the other Marc fixed the problem?

      I appreciate your help.