Tess via RemoteApp (Remote Desktop Services)

Hi Jon,

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.

Thanks,

David

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)

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?

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!

Hi Jon,

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.

Thanks,

David

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)

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?

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!