Loading...

Error messages during installation or start-up

Error messages during installation or start-up

Error message
ObjectStore internal error Unknown architecture code 46. (err_internal)
Example

Possible cause
An attempt is made to work in parallel with an ObjectStore 7.3 and 2013.0 client.
Troubleshooting
In order for 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

Possible cause
Please check the environment variable OS_AS_SIZE. There can be several causes for this message, which differ in the detail 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 working memory is not sufficient.
Troubleshooting
See OS_AS_SIZE, Address Space

Error message
The connection to the server was broken
Example

Possible cause and troubleshooting
FAQ entry

Error message
system exception Error 763 - CORBA: General error occurred
Example

Possible cause
Please check if a CORBA Naming Service is started and reachable in the network.
Troubleshooting
See the documentation on CORBA.

Error message
ClassiX takes a long time (e.g. 2 minutes) to start at some/all workstations.
Possible cause
In order 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 network paths are also included in the PATH, the search can take a very long time.
Troubleshooting
In the start batch file, note that the definition of the ClassiX environment variable CX_PATH begins with the CX_BIN and the Windows PATH is appended at the very end. Example: SET CX_PATH=%CX_BIN%;%CX_BIN%\ACETAO\TAO;%PATH%
Other possible cause
The ClassiX schema files are first searched for in directories located on a computer on which no ObjectStore server is running.
Troubleshooting
Check whether the schema files are the reason for the delays In the ClassiX log file, the last line during the wait is an entry with the content "ReloadMetainfo" (if necessary, the log level in the logging.ini for cx.txn must be increased to TRACE) Check where the schema files (schema_b.adb, schema_m.adb and schema_o.adb) are searched for. 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 log file you will find the paths in which the search is carried out. Possible solutions: Install an ObjectStore server on the computer on which the schema files are searched first. If the CWD (current working directory) is on another machine 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 for 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 virus TR/Crypt.XPACK.Gen during the ObjectStore 7.3 installation.
Possible cause
Other virus scanners do not report an alert, it is most likely a false positive.
Troubleshooting
Whitelist the affected files o7osjisc_jdk_g.dll and o7osjisc_jdk.dll or use another virus scanner. For security reasons, deactivating the virus scanner is not recommended.

Search