Step 1: Testing the connection with the database.
Via E3Studio, right-click your application’s database server, and then access this object’s properties. On Settings tab, select Test Connection option. If the connection to the database is successful, ignore Step 2.
Step 2: Has the database reached its limit?
If so, communication between E3 and the database will be interrupted, which will cause *.e3i and *.e3o files to be generated. Check whether it is possible to either back up the data stored in the database or create a new database so that E3 can resume recording data normally.
Step 3: Connection test: decompressing *.e3i and *e3o files.
After performing Step 3 and checking for a successful connection to the database, check out which version of E3 is installed and how big (in disk space) are *.e3i and *.e3o files. With this information, you can perform one of the procedures listed below:
a) Elipse E3 version 3.2 build 263 or lower:
– If the files are larger than 4GB, they will not be decompressed in the database, because in these versions, *.e3i and *.e3o files cannot decompress data in the database. In this case, please contact Elipse Software’s nearest technical support.
– If the files are smaller than 4GB, when communication with the database resumes, *.e3i and *.e3o files will decompress the data in the DB.
b) Elipse E3 version 3.2 build 264 or higher:
– When communication with the database resumes, *.e3i and *.e3o files will decompress the data in the DB.
Step 4: Will *.e3i and *.e3o files continue to be generated? Will they still store data?
If these files are still being generated even after the procedures above have been performed, this means there is still a connection error between E3 and the database server.
For further information, please refer to Elipse Software’s nearest technical support.
