Hello all,
Over the past few months when we start Tessitura it takes a while before the application loads (after putting in the login information). I'm wondering if this has something to do with indexes, transaction logs, fragmentation, etc. Does anyone have any ideas?
Gloria
Take a look at your printers. I know this sounds weird but Tessitura does something to detect all of the attached and network printers and validate them when it starts. Any chance that you added a new printer or new driver around the time the issue started occuring?
-Rich
What type of thing am I looking for with the printers?
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Rich Tepper Sent: Tuesday, December 15, 2009 1:17 PM To: Gloria Ormsby Subject: Re: [Tessitura Technical Forum] Performance Issue
From: Gloria Ormsby <bounce-gloriaormsby5026@tessituranetwork.com> Sent: 12/15/2009 11:41:26 AM
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!
That is hard to quantify. Like Amanda said... Make sure that they all still exist and you don't have any network printers pointing to a nonexistant shared device. Then think back... Have you added any new printers in the past several months. Find a workstation that is exhibiting the issue and try deleting the printers one by one starting Tess after each deletion. if one of them solves the problem then you have found your culprit. Once you find it check to see if there is a new driver available. If it is an HP printer try using the HP PCL universal driver instead. I have had good luck with that recently. Most of the time when I have had an issue in the past it was with an HP printer using a Microsoft driver that was included with the OS instead of the a driver from HP but you may find your issue to be something different. Hopefully this helps.