V.12 in Consortia

Eric,

We are looking at moving our consortium to v12 in the next few weeks. Can you let me know what issues you have found and are struggling with as possibly related to the consortia?

Thank you.

Randall A. Mitchell
Director of Information Systems | The Phoenix Symphony | Tel. (602) 452-0440 | Mobile. (602) 796-9323 | Fax. (602) 253-1772
RMitchell@PHOENIXSYMPHONY.ORG | www.phoenixsymphony.org

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Eric Williams
Sent: Monday, May 12, 2014 9:20 AM
To: Randall A. Mitchell
Subject: [Tessitura Technical Forum] V.12 in Consortia

Hello,

The Kansas City Tessitura Consortium upgraded to Tessitura v.12.0.3 last week and we've encountered some glitches along the way.  Some problems are to be expected with any new version upgrade but I'm wondering if our issues are consortium related.  If you've upgraded to v.12 (whether standalone or in consortium), what has been your experience?

Many thanks,

ERIC 

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!

Randy,

TIM is the key. You have to have everything absolutely correct. Go over it with a fine tooth comb. I highly recommend preparing your TIM configuration before the upgrade (test or live).  The good news about TIM is that it lets you uninstall most everything. So if something goes awry you can uninstall that component and do it over. Other things I learned…

Don’t upgrade more than one component at a time.

Read all the documents carefully and follow the directions in each step.

If you use Transcend you have to upgrade it to v4 to work with v12.

Plan where you are going to organize the upgrade files. It should be a shared network drive.

Plan, plan, plan!

I’ve upgraded our test environment and I’m launching in live on 5/19. I am going to do one more test upgrade before then.

Gloria

I mis-spoke. You are right it is v3.

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Beth Hawryluk
Sent: Monday, May 12, 2014 1:57 PM
To: Gloria Ormsby
Subject: RE: [Tessitura Technical Forum] V.12 in Consortia

Gloria,

I'm intrigued by your comment about going to V4 of Transcend. We've upgraded to V12 successfully with V3 and I (very recently) spoke with someone at Intrix who told me V3 was the latest version. I'm wondering if I have been misinformed...

Thanks!

I’m glad you did!

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Beth Hawryluk
Sent: Monday, May 12, 2014 2:41 PM
To: Gloria Ormsby
Subject: RE: [Tessitura Technical Forum] V.12 in Consortia

Excellent. Just wanted to be sure! Thanks :)

Hi all,

We are a consortium that went live with v12 in January. Most of the issues we experienced were not necessarily related to being a consortium; however, here are two that I remember that may be worth looking out for:

1.       We spent some time mapping solicitors to workers.  I may have just made an error somewhere along the way, but somehow, all of our workers ended up tagged with both a control grouped worker type and one that was not control grouped. Consequently, until we fixed this, everyone in the consortium was seeing all workers – even those that did not apply to their company.

2.       We have had issues with some orders causing a Tessitura crash because the order had a control grouped email address linked to it, but it was an email address the particular person loading the order did not have access to. I can’t recall what the previous v11 behavior was, but it definitely was not a Tessitura crash. I believe those issues will be fixed in 12.1. If you are a consortium with some shared box office functions, this is one you may potentially run into.

If I think of others, I’ll post another reply to this thread.

Thanks,

David

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Eric Williams
Sent: Monday, May 12, 2014 12:06 PM
To: David Frederick
Subject: Re: [Tessitura Technical Forum] V.12 in Consortia

And we're very grateful for the help! 

My boss is asking me whether the issues we've encountered are attributable to our consortium environment...hence my query.  To complicate matters, our consortium has several control groups and we are also dealing with the results of past customization.   

Many of our problems appear to have been related to security objects....once permissions were assigned, it was possible to fix issues.  

Price types have had a few hiccups, some related to security and one issue still being diagnosed.   

Acknowledgement letter reports needed to be tweaked because "Mail Purpose" is replaced by "Address Purpose."  Not a difficult fix but necessary. 

We ran into a problem with v.12 playing well with TNEW and web sales went offline briefly....again, the problem was quickly dealt with but not without some angst. 

There have been some login and report server difficulties, quickly addressed by RAMP.  We've also encountered some problems with getting some pre-Tessitura legacy data (ticketing, contributions) to display.

We ran TIM several times and did a lot of testing prior to the upgrade.  We thought everything was ready for the upgrade.  We expected some glitches. Just wondering if our experience was because we're in a consortium.