Problem Reports During Installation

Problem report
ObjectStore internal error
VirtualAlloc failed to allocate at any address
Example
 
Potential cause
Please check environment variable OS_AS_SIZE.

There are several potential causes for this message. These causes show differences in problem report details.

  • The parameter is incorrect (87): the environment variable has not been set correctly
  • There is not enough memory available for this command (8): The connected memory is not enough.

 
Fix
OS_AS_SIZE, Address Space

 

Problem report
 The server refused the connection (err_server_refused_connection)
Example
 
Potential cause
Der ObjectStore server is either not active, or it cannot be accessed via network.
Fix
Enter:

ping <server-name>

in a DOS box. It provides the server IP address <ip-addresse>. If there is no answer (time-out), the computer - on which the database server runs - is not accessible in the network: Please create a connection first!

Enter:

ossvrping <server-name>

in a DOS box. With this, it is possible to check whether the Objectstore database server is active or not. If it is not active, it needs to be started.

To speed up the process of finding the database server, it is possible to edit the file <winnt-instverz.>\system32\ drivers\etc\hosts. with a text editor (such as NotePad). If there is no file available, it needs to be generated (attention: NO file extension, for missing extension, NotePad adds .Txt by default, therefore also enter the terminal ‚.‘.).

Enter the following row at the end:

<ip-address> <server-name>
Other potential cause
Windows Firewall blocks the Port, which the client requires to respond to the ObjectStore server.
Fix
The Port 51031 TCP has to be released in the client firewall setting (firewall exceptions). For more details please read Firewall Administration.

   

Problem report
system exception
Error 763 - CORBA: general error occurred
Example
 
Potential cause
Please check, if a CORBA Naming Service has been started in the network and is now available.
Fix
Read CORBA documentation.

Problem report
In some/all  working stations, ClassiX takes a very long time (e.g. 2 minutes) to start.
Potential cause
To find all files that are needed for the ClassiX start, Windows searches through all directories, which are defined in the environment variable PATH, before it searches in the ClassiX directories. If network paths have also been integrated in PATH, the search can take a very long time.
Fix
In the start batch file, it needs to be considered, that the definition of the environment variable CX_PATH starts with the CX_BIN, wheras PATH is at the very end.

Example:

SET CX_PATH=%CX_BIN%;%CX_BIN%\ACETAO\TAO;%PATH%