Hi all, we are having a bizarre problem on one of our client workstation. Whenever a user tries to open the constituent module on that machine Tess client gets shut down immediately. User can open any other screen or module without any problem. User can also search constituent from Constituent Search screen. Application only fails when user tries to open any constituent details, by selecting a constituent record, from the constituent search screen or from the last six saved constituents from the Constituents menu.
We re-setup Tess client, manually copied all the Tessitura Client and PBVM files on that machine but are still having the same problem. It’s only happening on this particular workstation and for any user and any Tess client (both Live and Test). It’s a relatively new workstation with enough RAM and free hard disk space. All other applications on this machine are also running smoothly.
Have any of you ever encountered this problem or do you have any clue why it’s happening so? Thanks for any help.
Mo
Business Analyst The National Ballet of Canada
Business Analyst
The National Ballet of Canada
Hi Mo
We had a mysterious problem with a particular group of users loading the constituent screen (not crashing, but a slow load), which turned out to be caused by a problem in their constituent header. You might want to switch a test user to a plain vanilla header to check.
Another thing to check in that context, is whether that workstation has competing powerbuilder installations – if another program has installed a different version of the PBVM files, and the Tess PBVM files are not the first ones in the PATH, you can run into conflicts, apparently.
KEN MCSWAIN BUSINESS SOLUTIONS MANAGER
KEN.MCSWAIN@SYDNEYOPERAHOUSE.COM
T+61 2 9250 7876 F+61 2 9251 7821 M+61 418 659 360
I had a very similar problem which affected only one constituent. I tracked the problem eventually to the customised header. Running a trace located the exact bit of code which was failing and exiting the programme. Try starting a trace and then searching for a constituent on that PC.
Good luck.
Debbie
Thanks Ken and Debbie. Yes, it was because of the constituent header. But I am wondering why other users in the same group with the same custom header do not have any problem or why this particular user did not have any problem before; she has been using this machine for long and we did not change the header recently. Anyway, good thing is it’s working now. Thanks again for the insight.
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Mohiuddin Faruqe Sent: Tuesday, September 08, 2009 2:32 PM To: Mohiuddin Faruqe Subject: [Tessitura Technical Forum] Problem with constituent module
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!