RE: [Tessitura Administration & IT] Best Practices in RAMP downloads. Output Sets

I don't have issues saving large files either. But I do have some times intermittent hiccups with batch printing tickets. Has anyone run into that same issue before?

On Feb 13, 2018 4:55 PM, Sara Nemeth wrote:

[cid:Tessitura_2D00_Network_2D00_logo_5F00_1500x421-png_2D00_150x42-png@tessituranetwork.com] Update from Tessitura Network

[cid:4TYNTXAXLZ5T-jpg_2D00_70x70x2-jpg@tessituranetwork.com]

Sara Nemeth

Hi Tom,

We're on RAMP using Citrix and I regularly run large output sets and save them to my local drives without issue. I'd suggest contacting RAMP support as this seems unusual. Best of luck!

Sara

View online

You received this notification because you subscribed to the forum. To unsubscribe from only this thread, go here.

Flag this post as spam/abuse.

[https://community.tessituranetwork.com/notification/read?NotificationId=246690f2-41f0-4443-9687-97abb387c115]

  • Sara,

    Would you walk me through the steps that you use for downloading outputsets?

    We have found some multi-steps processes seem to work OK. But they are hard for end users to understand. However, the more straight foward process to save as a MS Excel to the local drive seems to be causing us problems.

    Thanks for any more details you can provide.

    P.S. We have opened this issue with the RAMP staff as well. 

  • I can use some help with batch printing tickets also.  Never had a problem until last year after we moved to Ramp.  The batch would just stop printing, but the tickets would all indicate as printed.  It drove us crazy all season.  Luckily our season is very short.  Any one know of a solution?

    Lee Ann Allison
    Lake Tahoe Shakespeare Festival
    Lee@tahoebard.com

    Sent from my Sprint phone.

    ----- Reply message -----
  • Users here reported when working on a project where they were printing a batch to file for a production, it super crapped out midway through when they tried to save directly onto the network share (our print to file showed as printed but the actual file showed only some of the tickets - like the box office batch prints have been). When they saved it to their local drive (C drive), no issue.
     
  • Hi Robert,

    We initially had problems printing tickets to our BOCAs after converting from 2X to Citrix. It happened whenever Citrix timed out - whether we were batch printing or printing just one order. RAMP suggested we implement some exclusions in our AV software (Webroot) which helped. Once Webroot released an update we were able to eliminate the exclusions and haven't had any problems since.

    Sara

  • Thanks Sara, I will try this fix.
     
  • Former Member
    Former Member $organization in reply to Sara Nemeth

    When did the Webroot update happen.  I would like to get rid of the exclusion as well.