Loading...
 

ObjectStore

ObjectStore

Error message
ObjectStore internal error
Unknown architecture code 46 (err_internal)
Example
architecture_code_46.jpg
Possible cause
It is tried to work with an ObjectStore 7.3 and 2013.0 clients in parallel.
Troubleshooting
To enable ObjectStore 2013.0 and 7.3 clients to work in parallel, a change must be made to the start script. Instruction

Error message
ObjectStore internal error
VirtualAlloc failed to allocate at any address
Example
errorm2.JPG
Possible cause
Please check the environment variable OS_AS_SIZE.

There may be several causes for this message, which differ in the details of the error message:

  • The parameter is not correct (87): The environment variable is not set correctly
  • There is not enough memory available for this command (8): The contiguous main memory is not sufficient.
Troubleshooting
See OS_AS_SIZE, Address Space

Error message
The connection to the server was broken
Example
errorm4.JPG
Possible cause and troubleshooting
FAQ entry

Error message
system exception
Error 763 - CORBA: General error occurred
Example
error003.gif
Possible cause
Please check whether a CORBA Naming Service is started and available in the network.
Troubleshooting
See CORBA documentation.

Error message
ClassiX needs a very long time (e.g. 2 minutes) at some/all workstations to start
Possible cause
To find the files needed to start ClassiX, Windows first searches all directories defined in the Windows environment variable PATH before searching in the ClassiX directories. If the PATH also contains network paths, the search may take a long time
Troubleshooting
In the start batch file, please note that the definition of the ClassiX environment variable CX_PATH starts with the CX_BIN and the Windows PATH is appended at the very end.
Example:

SET CX_PATH=%CX_BINclick="javascript:toggle_dynamic_var(";");" title="Click to edit dynamic variable: ;">No value assignedCX_BIN%\ACETAO\TAO; %PATH%

Another possible cause
The ClassiX schema files are first searched for in directories located on a computer that does not run an ObjectStore server
Troubleshooting
Check that the schema files are the reason for the delays
  1. In the ClassiX logfile the last line during the waiting period is an entry with the content "ReloadMetainfo" (if necessary the log level in the Logging.ini for cx.txn must be increased to TRACE)
  2. Check where to find the schema files (schema_b.adb, schema_m.adb and schema_o.adb). To do this, set the environment variable OS_DEBUG_LOCATOR_FILE=1 and OS_STDOUT_FILE to the name of a log file and start ClassiX. In the logfile you will find the paths in which the search is done.

Possible solutions:

  • Install an ObjectStore server on the computer where the schema files are first searched for
  • If the CWD (current working directory) is located on another computer that is not running an ObjectStore server, change the shortcut or working directory to one that is either running an ObjectStore server or to a local directory.
  • Set OS_SCHEMA_PATH to the path where the schema files are located, on which an ObjectStore-Server is running (OS_SCHEMA_PATH is searched before the entries in the PATH)
  • Set the path where the schema files are located to the beginning of PATH
  • Patch the ClassiX DLLs with the ObjectStore utility ossetasp so that they contain the full path to the schema files (not recommended)

Error message
Avira reports a TR/Crypt.XPACK.Gen virus during the ObjectStore 7.3 installation
Possible cause
Other virus scanners do not report an alarm, it is most likely a false positive.
Troubleshooting
Include the affected files o7osjisc_jdk_g.dll and o7osjisc_jdk.dll in a whitelist or use another virus scanner. For security reasons, disabling the virus scanner is not recommended.

Operational business