Post

2 followers Follow
0
Avatar

DBvisit Standby on Windows service account and ownership

Recently installed DBvisit Standby on a pair of Windows 2012R2 servers. Installed Standby with my personal windows domain account. Replication was working, no issues. Installed the Central Console on the first (pimrary) server. Everything worked with Central Console application. Management decided to run dbvisit under a new separate domain service account called srv-dbvisit. Sysadmin created new account and then updated the dbvnet, dbserver and dbagent services to use the new srv-dbvisit service account, on both servers. When I run .\dbvctl -d <ddc> status on both primary and standby it apears to show that they are in sync and functioning but Central Console application is not to be able to reach or control either primary or standby .  Changing the dbserver back to use my login, does not work either. Any suggestions?

thanks!

John Kelly Answered

Please sign in to leave a comment.

1 comment

0
Avatar

These are usually trickier to solve and requires more in depth analysis.

As a starting point we would recommend :

1. Check  if all processes and services are started and running stable - dbvnet, dbvagent, dbvserver (console)

2. Checking the Windows Environment pre-requisites - see the document link below :

https://dbvisit.atlassian.net/wiki/spaces/DS8QSG/pages/104431667/Installing+Dbvisit+Standby#InstallingDbvisitStandby-2.5.WindowsEnvironmentPre-requisites

3. Provide the dbvserver.log

Charmaigne Bezuidenhout 0 votes
Comment actions Permalink