incorrect scheduled reports

Actually, we’ve done a bit more investigating, and we realise that a large number of reports (including the ‘wrong’ ones) were all scheduled to go out at the same time.  We think that that’s what’s causing it, but would love to hear other’s thoughts J

Cheers,

Kathleen

Hi everyone,

We’ve had a very strange instance where some of our scheduled reports have been generated and sent out, but when people open the attachment, it’s an entirely different report from what they were expecting (some people received a sales report when they were expecting a membership report, for example).  Has anyone else experienced something like this or have any ideas what might cause it?

Cheers,

Kathleen

Click here to report this email as spam.

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Yes!  We have experienced this for quite a while now.  We have had a ticket open for months.  I recommend you do the same.  What we’ve done to try to ameliorate this is encourage our users to not schedule their reports at the direct top or bottom of the hour (choose 5:17 am or something).  We have also dropped our max polling rate to 5.  Still, it happens whenever two or more reports are scheduled to run and email at the exact same time.

I’m sorry you’re having this problem, but am relieved to hear it’s not just us!

We have been working with Nancy (as she mentions above) on the same issue.  If you open a support ticket on TASK we can assist you in troubleshooting.

Yes, we experienced that same problem. I have a TASK ticket opened up on the issue. For us, it seems to be related to the same report scheduled multiple times at the same time and running concurrently. One job appears to be “stealing” the output from another job.

For now, we set concurrent reports to 1 and I also asked people to try and avoid scheduling the same report at the exact same time. At this point, that seems to have resolved the issue, but we’re hoping Tessitura will fix this bug soon.

Thanks,

David

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Beth Hawryluk
Sent: Monday, December 17, 2012 11:08 AM
To: David Frederick
Subject: RE: [Tessitura Technical Forum] incorrect scheduled reports

Just to chime in - we recently started having this problem as well but it was resolved by changing the time of one of the reports so they weren't running at the same time. Since it's no longer an issue I won't open a support ticket but wanted to mention that there are at least 3 of us that have experienced it! :)

Thanks, everyone!  Good to know ( I suppose!) it’s not just us…

Cheers,

Kathleen

Yes, we experienced that same problem. I have a TASK ticket opened up on the issue. For us, it seems to be related to the same report scheduled multiple times at the same time and running concurrently. One job appears to be “stealing” the output from another job.

For now, we set concurrent reports to 1 and I also asked people to try and avoid scheduling the same report at the exact same time. At this point, that seems to have resolved the issue, but we’re hoping Tessitura will fix this bug soon.

Thanks,

David

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.