on 07-20-2017 7:23 PM
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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.