Hi all. We implemented Tess v11 via RDS (Windows Server 2008 R2 with SP1 and all available Windows Updates) a few months ago. Though for the most part it's working well there are definitely some issues still lingering or causing problems for end-users, both internal and external (consortium members).
I'm just wondering if any of you doing the same thing (using RDS to deliver Tess) have run into any of the same issues we're seeing. These include:
Credit card transactions timing out and needing to be rerun (swiped again)
Tess crashing upon login
Tess crashing after running okay for a few minutes
Various printer/printing problems
These may not be all the issues we're seeing but they're the ones I can think of right now. Anyone else hosting Tess via RemoteApp/RDS and seeing, or have seen and resolved, these types of issues?
Hi Jon,
We switched from Transcend to Element, which has worked out great for us. Overall it has performed better and has been more reliable, although I do not recall having time-outs like you are describing on a regular basis when we were using Transcend. You may want to open a ticket on the CC time out issue.
I need to clarify regarding printers… Pretty much all of our printers are network printers. Rather than print through a print server, we actually define each printer locally on the RDS server – essentially it becomes its own print server. I’m not necessarily suggesting that is the recommended setup; in fact, I’d prefer to move away from that. But, testing out a printer or too with a local setup via a TCP port rather than going through the print server might be a useful troubleshooting step depending on what issues you are experiencing.
Thanks,
David
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Jon Harrison Sent: Tuesday, October 15, 2013 10:16 AM To: David Frederick Subject: RE: [Tessitura Technical Forum] Tess via RemoteApp (Remote Desktop Services)
Hi David. Thanks for the reply and the information. I'll give your idea about putting the Tess exe in the DEP tab a try. Hopefully it'll cure an ill or two. 8)
Regarding the occasional credit card transaction issue, we are using TranScend. How about you?
I don't know what percentage of our printers are on a print server(s) versus locally attached, but I'd say our entire consortium probably has them all locally attached (that's an assumption). Internally most of our printers, boca and otherwise, are running through a print server with a little more than a handful being locally attached.
From: David Frederick <bounce-davidfrederick9045@tessituranetwork.com> Sent: 10/15/2013 11:46:42 AM
We have been using Tessitura v11 on RDS since we went live on that version, and it has been working well for us overall. In regards to the crashing issues… One thing we did notice is that we’d often have jscript9.dll crashes when using IE 9. We downgraded to IE 8, which helped a little bit, but crashes still continued – just a different DLL. After a lot of troubleshooting with Tessitura, we found that this resolved the majority of our crashing issues:
1. Go to System Properties à Advanced System Settings
2. Click on the Settings button in the Performance section.
3. Go to the Data Execution Prevention tab.
4. Add Tessitura.exe from the client folder users are using.
If that doesn’t seem to help and the crashes you are getting seem to be browser-related, you may want to try adding IE.exe in there as well. I’m not 100% certain, but that could decrease security if you do that. This did not eliminate all crashes for us… We still have a few intermittent ones, but we went down from multiple crashes per day to maybe 2-3 per week.
In regards to the credit card transactions… Are you using Transcend or Element? In regards to printing… We use all local printers with TCP/IP ports and do not go through another print server for anything. I’d prefer not to do that, as we then have to add/change printers on both RDS and our main print server, but it was set up that way a long time ago back on our old 2003 terminal server; I hesitate to change and risk introducing issues.
I hope that helps.
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Jon Harrison Sent: Tuesday, October 15, 2013 9:30 AM To: David Frederick Subject: [Tessitura Technical Forum] Tess via RemoteApp (Remote Desktop Services)
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!
Okay, your printer information makes sense now. That's an interesting idea - setting up each printer on the RDS server(s) so that it becomes a print server. We have 3 print servers but all the Boca's are on 2 of them. I'm sure we won't want to turn the RDS servers into print servers, but maybe if I can get the okay to test and the problems disappear maybe I'll get the green light. Jeez, do I really want to have to manage 5 print servers... 8)
Regarding the credit card issue, I know we're going to look at moving away from TranScend and go with Element, but not for a good little while. Are you providing Tessitura for internal and consortium (external) users? What VPN solution are you using? I'm wondering what piece of our puzzle is causing the issue - the SSL VPN appliance, RDS, etc.
What about random Tessitura disconnects, random Tessitura log offs, Tessitura freezing when looking at any given report? Has anyone here experienced these types of issues when serving Tessitura to the users via RemoteApp (Remote Desktop Services)? We are still seeing this happen randomly to users, though admittedly mostly external (consortium) users.