I've been having a problem for a few weeks now, where the tessitura client will randomly crash. I'm not able to recreate it. When a user recreates the steps it took to have the crash, then tessitura will sometimes crash and sometimes it won't.
I'm running terminal services, specifically server 2008 remote apps. I've tried this on xp machines also and got the same results. I've recently tried setting up a new server with nothing installed but windows updates, microsoft office 2007, and tessitura to rule out the possibility of antivirus or some other program conflicting with tessitura. most of the crashes seem to happen around subscription orders, but that's also because that's where most of the owrk is being done now.
Has this happened to anyone else and does anyone have a solution?
Hi there,
I have experienced similar problems when running the client in one of the modules for a long time and doing large tasks. For instance, when in season manager and applying hold codes in bulk to multiple performances without exiting Season Manager. Gradually, the application slows down to a crawl as you apply more and more holds and subsequently crashes to desktop without any messaging.
One workaround to this issue is occasionally switching to another module (e.g. ticketing orders, constituents, etc). This seems to clear what appears to be some form of memory leak and it carries on working without issue for a while.
You mentioned that it happens around subscription orders, which carry out multiple operations, so that would certainly fit the bill!
good luck!
It sounds similiar, but I'm not sure it's the same thing. When mine crashes, nothing slows down. In fact, it's really snappy and then when it crashes, the crash is very instantaneous. Thanks for the reply, this is really annoying our users. Any other ideas?
Are you running it on a 64 bit computer? If so that might be your issue. I may not have the details completely correct but I believe Powerbuilder isn't 100% compatible with 64 bit and the area that shows up most is in ticket sales. We've kept our box office and call center on 32 bit for this reason.
No, it's 32 bit. I'm running some on xp 32 bit and some on a 32 bit terminal server running server 2008 remote apps. I'm running SQL traces right now to send to tessitura help desk. Hopefully I'll know something from that. Any other ideas?
I don't know what version you are running, but in version 10.0, not 10.01 make sure that the people have the default salutation type, as when you add new address or e-mail address, and if that does not exist the application will close out. Also if you are running a report, and choose a list and then sort the list section, the application will close out on you.
One more thought - it could be a network issue and not a Tessitura issue. We had something on our network that was interfering and would crash people out randomly whenever Tessy tried to 'talk back' to the database (seating was a big area for this). It took quite a bit of diagnosis to figure out so hopefully this isn't the case for you.
we haven't had any network issues for awhile. I'm running a sql trace and I did get Error:208, Severity: 16, State: 0. does that mean anything to anyone? We're also running version 10.0.0.1
We're using QAS so wouldn't that supply the salutations with the address?