Troubleshooting

Startup parameters of the program

To avoid problems (also after a correct installation), the program should at least once be started as a privileged user. By default, the system tries to update the registry on program start-up. Possibly occurring errors may be the result of an incorrect program registration (bug in Windows 2000).

 

If the program starts with an error message, add the startup parameter /noreg to the icon starting E3.series to skip the update of the registry on program start.

 

To be able to add this parameter to the start icon on the desktop you have to create a new link from the EXE to the desktop.

 

1. Open the EXPLORER and search for the file E3.series.exe

2. Create a link to this EXE on the desktop

3. Open the properties of the new icon and add the parameter to the destination

    

   C:............\Zuken\E3.series_SE\E3.series.exe /schema /noreg

   /schema is needed to activate the E3.schematic module

   /noreg is needed to suppress the writing to the registry

 

Conversion of large Access databases

The conversion of large databases may result in the error message 'File sharing lock count exceeded (Error 3052).'

 

To avoid that, proceed as follows:

 

Depending on the database access module used, it's possible to increase the value for the MaxLocksPerFile setting in the Windows Registry. This setting's default value is 9500.

 

When using database driver 'Microsoft Jet 4.0 OLE DB Provider', the key is stored in the section

HKEY_LOCAL_MACHINE\Software\Microsoft\jet\4.0\engines\jet4.0

 

When using database driver 'Microsoft Office 12.0 Access Database Engine OLE DB Provider', the key is stored in the section

HKEY_LOCAL_MACHINE\Software\Microsoft\Office\14.0\Access Connectivity Engine\Engines\ACE

 

When using database driver 'Microsoft Jet 3.5 OLE DB Provider', the key is stored in the section

HKEY_LOCAL_MACHINE\Software\Microsoft\jet\4.0\engines\jet3.x

 

Increase the key's value (Example)

MaxLocksPerFile = 30000 (decimal)

 

However, changing this value is not recommended if one of the replicas is located on a NovellNetware server, because the server's maximum record locks per connection is 10000. If both replicas are located on servers running Microsoft Windows NT 4.0 or Microsoft Windows 95 or later, the maximum value of this setting is limited only by available resources.

 

Deletion of the lock file after a program crash

Under Windows 2000, the deletion of the lock file (.lck) after a crash of E3.series may sometimes be impossible. In that case, the process drwtsn32.exe (Dr. Watson) has to be killed to enable deletion of the file.

 

Problem with Oracle databases

In connection with Oracle and an access per ADO OLD provider, texts may sometimes be disordered when displaying the language databases. This happens, when data records containing Unicode strings are read from an Oracle database. Only with the first access are the data records correctly returned.

 

The error can be avoided by reading all data records in one go. This can be done by defining the FetchSize=n parameter in the Connection String. n defines the number of data records to be read with one database access.

 

Regarding the language database, this parameter has to be defined in the registry under

HKEY_CURRENT_USER\Software\Zuken\E3.series\<Version>\Databases\Languages="Provider=OraOLEDB.Oracle.1;...;FetchSize=n"

 

This error might also occur in E3 databases, especially when reading attribute and text type information as well as symbol texts.

 

The Connection Strings for these databases are stored in:

HKEY_CURRENT_USER\Software\Zuken\E3.series\<Version>\ValidDatabases\Database-n\ConnectionString

 

Problem when using Oracle version 11.2.0.1

When using Oracle version 11.2.0.1 the symbols in E3.series are displayed incorrectly. Avoid using this version and use another Oracle version.

 

Definition of ports used for communication between E3. multi-user servers and clients

For each project opened as multi-user application, an E3. multi-user server process is started on the server computer. This process controls the communication for this project with the corresponding clients. This is done via Windows Ports. When a firewall exists between E3. server and E3. client, the ports must be enabled, if necessary. The ports to be used can be defined in the Configure.xml file that is stored in the same directory, in which the E3. server is installed.

 

The first port to be used can be entered in the line

- <Server>
   <FirstPort>4812</FirstPort>

 

When now starting an E3. server process, the system verifies whether this port is already used. If so, the next free port is used, i.e. the "start port" is defined here.

 

Missing Online Help with Server Client Installation

With a server client installation it might happen that the online help within E3.series cannot be displayed.

This can be corrected by the following entries/changes in the registry:

REGEDIT
   -[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp]
      -[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\HHRestrictions]
         -"MaxAllowedZone"=dword:00000001
            -"EnableFrameNavigationInSafeMode"=dword:00000001
      -[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\ItssRestrictions]
         -"MaxAllowedZone"=dword:00000001

 

Problems with Oracle access when E3. installation directory contains brackets

Problems occur, when trying to access Oracle, if the E3.series installation directory contains brackets ( / ). When the user then tries to access multi-user or the component database, the following error message is displayed:

ORA-12154: TNS:could not resolve service name.

 

Problems with numerous simultaneously open applications

When numerous applications are simultaneously opened, errors can occur under Windows, in case the desktop heap's limit has been reached. This means, several applications can no longer be started, dialogs can no longer be opened, error message appear due to lacking memory although sufficient memory is available.

 

When these message disappear after closing several applications, the reason can be the desktop heap. When it is not possible to reasonably reduce the number of simultaneously open applications, the user can increase the desktop heap's limit.

 

To do so, the bold entry in the following registry key must be increased:

HKLM/SYSTEM/CurrentControlSet/Control/Session Manager/SubSystems/Windows

 

Value:

%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,3072,512 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16

 

The second value in the 'Windows SharedSection' (Default: 3072) section should be increased till the required number of applications is running without any problems. According to Microsoft, this value, however, should not be increased as desired, since this may negatively influence the performance (12288 should be possible).

 

 

'Timeout' error when starting E3. and simultaneous saving to SQL Server database

Timeout errors may occur upon starting E3.series, when, for example, another user is simultaneously saving a model from the Database Editor mode to the SQL database.

 

This may be due to a read access to a modified data record being blocked by the SQL server. However, it's possible to change the behaviour when reading modified data records by default through a database option, so that reading operations are no longer blocked but the current version of the data record is provided.

 

The option can be activated as follows:

ALTER DATABASE <database name> SET READ_COMMITTED_SNAPSHOT ON

 

This modification can only be executed when no connection to the database exists. With the option activated, the SQL server creates a new version of the data record when it has been changed. These data record copies are stored in the tempdb database; the versions no longer needed are automatically removed by SQL server.