Tessitura Client on Windows 7

Thank you – we are at 12.1.2 and we found we get this error with our remaining XP clients.

Bob

Hi Bob,

We were using version 11 at the time but have since upgraded to 12.1.2. We did two things that seemed to fix the issue.

1. We set the "Max Pool Size" attribute in the Tessitura Connection string. Out of the box this is omitted from the connection string so it defaults to something like 100 I think. Can find more info on it here http://www.tessituranetwork.com/tlcc/2014/Presentations/13-K_Administering_Services_Layer.pptx
2. We put a cap on the amount of Memory SQL Server was allowed to use. By default this is some stupidly huge number, which isn't a problem for your average database but due to tessitura's size SQL Server will keep trying to allocate resources that don't exist if you don't set a cap. Here is a handy guide http://sqlserverperformance.wordpress.com/2009/10/29/suggested-max-memory-settings-for-sql-server-20052008/

We also considered clearing out out old redundant session data to try and trim the fat a little but so far the effort outweighs the time I have available to do this.

Hope this is of some use.

Huw

Hello,

What version of Tessitura are you using?  We are having the same issue but with version 12.1.2 with our XP clients. Do you ever identify the slow down.

Bob

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!

Thank you – we are at 12.1.2 and we found we get this error with our remaining XP clients.

Bob

Hi Bob,

We were using version 11 at the time but have since upgraded to 12.1.2. We did two things that seemed to fix the issue.

1. We set the "Max Pool Size" attribute in the Tessitura Connection string. Out of the box this is omitted from the connection string so it defaults to something like 100 I think. Can find more info on it here http://www.tessituranetwork.com/tlcc/2014/Presentations/13-K_Administering_Services_Layer.pptx
2. We put a cap on the amount of Memory SQL Server was allowed to use. By default this is some stupidly huge number, which isn't a problem for your average database but due to tessitura's size SQL Server will keep trying to allocate resources that don't exist if you don't set a cap. Here is a handy guide http://sqlserverperformance.wordpress.com/2009/10/29/suggested-max-memory-settings-for-sql-server-20052008/

We also considered clearing out out old redundant session data to try and trim the fat a little but so far the effort outweighs the time I have available to do this.

Hope this is of some use.

Huw

Hello,

What version of Tessitura are you using?  We are having the same issue but with version 12.1.2 with our XP clients. Do you ever identify the slow down.

Bob

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!