My Oracle Support Banner

FS-10751, FS-10755: in Fail Safe Manager Running Verify Cluster or Moving Group (Doc ID 108442.1)

Last updated on OCTOBER 13, 2019

Applies to:

Oracle Fail Safe - Version 3.0 to 3.4.2
Microsoft Windows (32-bit)
Microsoft Windows Itanium (64-bit)
Microsoft Windows x64 (64-bit)
***Checked for relevance on 22-11-2011***


Symptoms

Problem Description


When using Fail Safe Manager to Verify Cluster or Move Group or certain other operations, you may encounter one or more of the following errors:

Error: FS-10750 Text: Node %s failed to create a class factory on local node %s
Cause: The class factory cannot be created.
Action: Make sure that Oracle Fail Safe Server is installed with Administrator privileges on all clusternodes and make sure it is installed to run under the same account on all cluster nodes. To check the account used, click Start, then Programs, then Oracle-<Oracle_Home>, then Oracle Fail Safe Security Setup.

Error: FS-10751 Text: Node %s failed to create a class factory on remote node %s
Cause: The class factory cannot be created on a remote node.
Action: Make sure that Oracle Fail Safe Server is installed with Administrator privileges on all clusternodes and make sure it is installed to run under the same account on all cluster nodes. To check the account used, click Start, then Programs, then Oracle-<Oracle_Home>, then Oracle Fail Safe Security Setup.

Error: FS-10755 Text: Error creating the %s COM object
Cause: The Oracle Fail Safe Server failed to create a COM object.
Action: Check the Windows NT event log for messages.

Error: FS-10752 Text: The COM class factory cannot create an instance of the object
Cause: The COM class factory cannot create an instance of the object.
Action: Check the Windows NT event log for messages.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
 Problem Description
Changes
Cause
Solution
 1. First rerun the Oracle Fail Safe Security Setup:
 
2. Next, check the Application Log and System Log on each node.
 
3. Upgrade Fail Safe Version
 
 Should the problem persist, the most common reasons are:
 A. User logon for Cluster and or OFS Service
 B. Directory Permissions
 C. 'Logon on as a batch job' Privileges
 D. DCOM has been disabled

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.