If you get the message "GQ_IesxSeismic::getConnection File doesn't exist: 'IESX_CONFIG:da_info.key' File open failure" in your IESX server log, use the Configuration Tool to check the IESX data store parameter IESX_CONFIG. This parameter should contain the IESX configuration directory. If the directory is valid, try to access the directory using your machine and your account. The problem may be related to file access.

Some installations may get an error in the server log saying "Could not open facilities file." from the IESX server. The runIesx37Server.sh script sets the environment variable OMNIWORKS_PATH equal to GF_PATH. In some setups, that assumption is not true. Since this is not likely to be seen very often in places with commercial GF kits, we have left it up to the installation to change the script as needed.

The reason why we couldn't create Charisma volumes was because the project wasn't configured properly. To solve this problem:

• Start proman
• Connect as dba
• Connect to the proper catalog
  • Highlight the catalog (e.g. GF3_8)
  • Connect
• Select the Disks option and assign ALL disks (Default, Seismic, CPS, CharismaGraphics, Interpretation, Velocity)
• Select the Users option and add All users to each one of the disks, for example
  • Select "All users"
  • Select CPS (Storage Type)
  • Click on the filepath under Storage Type
  • Make sure it appears in the Disk Selection area
  • click Apply
  • perform this for all disks
  • after completing the last one click Cancel; otherwise, it will "clear" the last Storage Type (i.e. Velocity)

If you add a user to the Charisma project after the above steps are completed then you need to add the user to each disk again.

In my IESX data server I am getting the following error;

ERROR: throwing the following exceptionusing the java class:com/openspirit/osp/Osi/Exceptions/DevKitException Error creating volume,no dsl available that qualifies Last methodcalled = GQ_IesxSeismic::createVolumeno dsl available that qualifies

The problem is that you have run out of disk space. To remedy this, try to make some room on the disk that is attempting to create the seismic volume. Then try again - this should solve the problem.

With this problem you may either see none of the projects or they may be split up and appear to be under both IESX and Charisma. The problems is that the OpenSpirit IESX and Charisma Data Store Descriptor (DSD) servers filter out non-IESX/Charisma projects by default, based on filtering logic given to us by GeoFrame. For example, sometimes this logic can cause OpenSpirit to believe that a project contains Charisma data instead of IESX, so it doesn't appear under IESX when creating a project set.

To disable this IESX or Charisma project filtering you must add a new property to the $OSP_HOME/classes/OpenSpirit.properties file in the Solaris master installation. The property allows you to specify one or more data store types that the filtering is to be disabled on. The new property is:

openspirit.DSDService.disableFilter= DS_type1,DS_type2

where DS_type# is one of the following:

• Iesx_3.8
• Iesx_4.0
• Charisma_3.8
• Charisma_4.0

For example, to disable filtering for just IESX 3.8 add the following line to the OpenSpirit.properties file:

openspirit.DSDService.disableFilter= Iesx_3.8

To disable filtering for all versions of IESX and Charisma add the following line to the OpenSpirit.properties file:

openspirit.DSDService.disableFilter= Iesx_3.8,Iesx_4.0,Charisma_3.8,Charisma_4.0

The shared services must be restarted to pick up the new property settings.