Incorrect RSI User Login Name or Password

The primary Replication Server logs in to the replicate Replication Server using the Replication Server Interface (RSI) login name and password. The RSI user login name and password are created by rs_init and are also required when you create a route to the replicate Replication Server.

If there is a problem with the login name and password at the replicate Replication Server, the primary Replication Server logs one of these errors:

I. 2006/06/23 14:29:43. RSI: Trying to connect to
'eastRS'.
E. 2006/06/23 14:29:43. ERROR #1028 RSI(eastRS) -
seful/cm.c(3463)   Message from server: Message: 14021,
State 0, Severity 12 -- 'Invalid login attempted by user
'Rep_Server_rsi''.
E. 2006/06/23 14:29:44. ERROR #1027 RSI(eastRS)- 
seful/cm.c(3463)   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. 2006/06/23 14:29:44. ERROR #13045 RSI(eastRS) -
seful/cm.c(3467)   Failed to connect to server 'eastRS'
as user 'REP_Server_rsi'. See CT-Lib and/or server error
messages for more information.
E. 2006/06/23 14:29:44. ERROR #4044 RSI(eastRS) -
i/rsiint.c(329)   RSI for 'eastRS': Shutting down due
to an exception.

To repair this problem:

Retrieve the RSI user login name and password from the Replication Server System Database (RSSD) of the primary Replication Server by using isql to execute this query on the RSSD:
```
select username, password 
 from rs_maintusers, rs_sites 
 where name = remote_RS_name and destid = id
```
remote_RS_name is the destination Replication Server name.

id is the destination Replication Server’s site ID.

If you have password encryption, you cannot access the password by executing a query.
Perform one of these actions:
- Use the alter route command to change the password for the primary Replication Server to the RSI user password, which you retrieved in the previous step.
- Use the alter user command to change the password for the login name at the replicate Replication Server. Then use the resume route command to resume the route.