Strange status when configuring Fail Safe on Windows 2008 R2
edited Jul 29, 2020 5:16PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 3 commentsAnswered
1) I am not sure if this the correct forum for this question, but it is the closest match that I could discern.
2) I am configuring Oracle FailSafe on a 2-node Windows 2008 R2 X64 cluster. I installed the base components, then installed FailSafe. When I try to validate the FailSafe cluster, I get errors about class not registered. No specific information about which class is not registered. When I run the fssrv /getsecurity report, it tells me that the user I specified does not have "logon as batch" privileges. I verified that the Policy does include this user for Allow logon as batch. The report also showed an error attempting to verify that DCOM was enabled. The message is:
2) I am configuring Oracle FailSafe on a 2-node Windows 2008 R2 X64 cluster. I installed the base components, then installed FailSafe. When I try to validate the FailSafe cluster, I get errors about class not registered. No specific information about which class is not registered. When I run the fssrv /getsecurity report, it tells me that the user I specified does not have "logon as batch" privileges. I verified that the Policy does include this user for Allow logon as batch. The report also showed an error attempting to verify that DCOM was enabled. The message is:
0