incorrect scheduled reports

A quick update here,

We (the Network) have been investigating this issue with several licensees for several months and have prepared a hotfix to Tessitura v11.0.4.  This hotfix can be found under the v11.0.4 Post Release Fixes/Patches solution on TASK.  You must be running 11.0.4 to install this hotfix.

This hotfix contains a new version of the Tessitura Report Server and a set of client application files that needs to be replaced in the locally installed Tessitura client folder (most often c:\Program Files\Impresario Client\) on the Report Server machine.   The corresponding instructions for installation are pretty simple to follow.  The client hotfix does not need to be deployed on user's workstations, only on the server where the Tessitura Report Server resides.  If you have an automated mechanism to sync the Report Server’s client files from a master network share, it is advised to disable it for the report server with this fix in place.

The biggest change that has been made (apart from the earlier logging fix and a few other existing minor defects) is that the report output is no longer saved directly to the email output path (where the database server picks up the attachment for sending).  The Report Server now saves first to the local temp folder, then moves the file to the filepath defined in T_DEFAULTS(EMAIL REPORT PATH) or T_DEFAULTS(FILESAVE REPORT PATH).  This, from our testing, alleviates the issue of concurrent reports overwriting each other's output.  The actual issue appears to be related to a single thread process in PBVM (PowerBuilder Virtual Machine) that causes concurrency issues when saving two datawindows (reports) at or near the same time.   By moving the save process from a network share to the local file system, this avoids some delay in network I/O (minimal as it may be).

For RAMP clients affected by this issue, please open a ticket on TASK and we can assist you further.

+Ryan Creps

+Tessitura Network

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Chris Jensen
Sent: Monday, December 17, 2012 6:02 PM
To: Ryan Creps
Subject: Re: [Tessitura Technical Forum] incorrect scheduled reports

Also just to join the chorus, we've run into this, too, though neither often nor with any consistency.

It used to happen more often and we once had a support ticket open for it, but not for >2 years I think.

A quick update here,

We (the Network) have been investigating this issue with several licensees for several months and have prepared a hotfix to Tessitura v11.0.4.  This hotfix can be found under the v11.0.4 Post Release Fixes/Patches solution on TASK.  You must be running 11.0.4 to install this hotfix.

This hotfix contains a new version of the Tessitura Report Server and a set of client application files that needs to be replaced in the locally installed Tessitura client folder (most often c:\Program Files\Impresario Client\) on the Report Server machine.   The corresponding instructions for installation are pretty simple to follow.  The client hotfix does not need to be deployed on user's workstations, only on the server where the Tessitura Report Server resides.  If you have an automated mechanism to sync the Report Server’s client files from a master network share, it is advised to disable it for the report server with this fix in place.

The biggest change that has been made (apart from the earlier logging fix and a few other existing minor defects) is that the report output is no longer saved directly to the email output path (where the database server picks up the attachment for sending).  The Report Server now saves first to the local temp folder, then moves the file to the filepath defined in T_DEFAULTS(EMAIL REPORT PATH) or T_DEFAULTS(FILESAVE REPORT PATH).  This, from our testing, alleviates the issue of concurrent reports overwriting each other's output.  The actual issue appears to be related to a single thread process in PBVM (PowerBuilder Virtual Machine) that causes concurrency issues when saving two datawindows (reports) at or near the same time.   By moving the save process from a network share to the local file system, this avoids some delay in network I/O (minimal as it may be).

For RAMP clients affected by this issue, please open a ticket on TASK and we can assist you further.

+Ryan Creps

+Tessitura Network

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Chris Jensen
Sent: Monday, December 17, 2012 6:02 PM
To: Ryan Creps
Subject: Re: [Tessitura Technical Forum] incorrect scheduled reports

Also just to join the chorus, we've run into this, too, though neither often nor with any consistency.

It used to happen more often and we once had a support ticket open for it, but not for >2 years I think.