Is enVision 4.1 Patch 9 stable? Looking to resolve issues with failed reports...

Discussion created by Moondoggy on May 8, 2013
Latest reply on May 15, 2013 by Moondoggy

We currently are running enVision 4.1 patch 5, but have been experiencing reporting issues.


We are considering upgrading to 4.1 patch 9, and we are wondering what other user's experiences are with patch 9.  We had issues with patch 6, and we were considering patch 7 when it was withdrawn, so we dropped back to patch 5.


We are having more and more report failures, and enVision support is recommending that we upgrade to patch 9.

In the pi_webserver.log file, we are seeing hundreds (maybe thousands) of errors like this:

May 7, 2013 7:39:23 PM com.opensystems.privatei.util.Logger:WARNING: LoadTable Error: ***Table: rw_tmp_windows_531 ***Error: 0 ***SQL: JZ0C0: Connection is already closed.


Occassionally we see messages like this:

May 7, 2013 7:39:23 PM com.opensystems.privatei.util.Logger:SEVERE: exception

java.sql.SQLException: JZ0C0: Connection is already closed.

at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(

at com.sybase.jdbc2.jdbc.SybConnection.checkConnection(

at com.sybase.jdbc2.jdbc.SybConnection.createStatement(

at com.opensystems.privatei.persist.DB.createTempLogin(

at com.opensystems.privatei.reporting.AbstractReportJob.checkQuery(


at com.opensystems.privatei.reporting.AbstractReportJob.generateReport(

at com.opensystems.privatei.reporting.AbstractReportJob.generateReport(

at com.opensystems.privatei.reporting.ScheduledReportJob.generateReport(



Does anyone had success in resolving problems like this?


What are your experiences with enVision 4.1 patch 9?