...
This command should be run on both the primary and standby servers to test the connectivity going both ways.
Resolution 4 – Ensure all Dbvisit and Bitvise software is running from the same account
Ensure that the Dbvisit software and the Bitvise software are all installed and running under the same Windows user account. This includes the following software and components:
- Dbvisit Standby
- Dbvserver - This runs as a Windows Service and is a lightweight web server that allows Dbvisit Standby to be managed through a web interface (GUI). Ensure the Dbvserver service logs on as the same windows account as all the Dbvisit and Bitvise software.
- Bitvise WinSSHD - A Windows SSH2 server
- Bitvise Tunnelier - A Windows SSH2 client
Resolution 5 – Ensure Windows accounts are similar
...
Ensure the Windows user accounts are similar between the primary and the standby server. Both user accounts must be either domain accounts (within the same domain) or single user accounts.It is not possible to run Dbvisit Standby using a Windows domain account on the primary server and on the standby server run Dbvisit Standby using a standalone Windows user account or vice versa. This is a requirement of WinSSHD to establish a secure and trusted connection.If the standby server is not part of the same domain as the primary server, then the WinSSHD settings are a little different. The account in WinSSHD on the standby server should then be a virtual account and group. Please see http://www.bitvise.com/wug-accounts for more information and http://www.dbvisit.com/forums/showthread.php?p=2865
Resolution
...
6 – Please contact Dbvisit support.
Before contacting Dbvisit support please ENSURE that you have followed above instructions carefully! They have worked for all customers.
...