User's Manual

HP StorageWorks File System Extender Software user guide 245
Communication problems
Description CORBA cannot be initialized. After invocation of an FSE command, the following error is
reported:
Consolidated FSE system or FSE server specific
6000 Cannot initialize CORBA ORB. 'CORBA::COMM_FAILURE'
FSE client specific
Failed to initialize CORBA
Explanation Possible reason for this problem may be that omniNames is not running on the consolidated
FSE system or FSE server and, consequently, its host is not accessible to the FSE client.
Workaround Proceed as follows:
1. On the consolidated FSE system or FSE server, verify the status of the CORBA Naming
Service daemon (service) (omniNames).
Linux specific
Run the command omniNames --status and inspect its output. If omniNames is not
running, invoke the command omniNames --start or omniNames --restart as
appropriate.
Windows specific
Use the Services tool to check the status of the omniORB CORBA Naming Service, and to
start it, if it is not running.
2. On the FSE client, verify the settings specified in the omniORB.cfg file.The location of the
file is platform-dependent.
Linux specific
On Linux platform, omniORB.cfg is located in the directory /etc/opt/fse.
Windows specific
On Windows platform, omniORB.cfg is located in the directory %InstallPath%\etc.
The value of %InstallPath% depends on the choice made in the FSE installation process.
It defaults to C:\Program Files\Hewlett-Packard\FSE.
3. Check the network connection between the FSE client and the FSE server. For this purpose,
you can use the tool fse_net.