Hi, I have a web custom screen (ASP.NET based) which runs perfectly ok in a browser. When I added it to Tessitura as a custom screen it renders ok and can pull the details for the current constituent from the local tables without any problem but:
1. On some workstations, anytime we click on a button or list item which does a postback, we get the error shown at the bottom. Setting EnableEventValidation="false" at the page level or in the web config file stops this error on the problem machines but make some controls irresponsive.
2. Clicking on a listbox or a drop down list item doesn’t fire the associated event, we need to select an item by using the up/down arrows and then press enter to make it work. We have seen similar issues in case of some dashboard widgets.
Postback Error when called inside Tessitura as a custom screen or a report:
Sys.WebForms.PageRequestManagerServerErrorException: Invalid postback or call back argument. Event validation is enabled using <pages enableEventValidation=”true”/> in configuration or <%@ PageEnableEventValidation=”true” %> in a page. For security purposes, this feature verifies that arguments to postback or callback events originate from the server control that originally rendered them. If the data is valid and expected use the ClientScriptManager.RegisterForEventValidation method in order to……… Do you want to continue running scripts on the page?
I am using the execute local procedure web API to update the local tables.
Any ideas? Thanks!
Mo
National Ballet of Canada
Thanks Beth for the links. This helped us to sort out some issues with SSRS widgets and custom screens. I never tried this before. For the ASP.NET custom screen issues, I guess I have to take a different approach as suggested by Jon; they get messy once added inside Tessitura.
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Beth Gilliland Sent: Tuesday, December 03, 2013 1:57 PM To: Mohiuddin Faruqe Subject: RE: [Tessitura Technical Forum] Web Custom Screen - Errors
We definitely updated browser emulation to get around some SSRS custom screen issues here at UMS. From my notes:
Tessitura utilizes the IE OLE Browser Control on a workstation to pull that workstation's IE browser:
http://www.tessituranetwork.com/Community/forums/p/5839/18622.aspx#18646
By default, applications using the Web Browser Control are forced to EMULATE IE7 (see last entry in table:
http://msdn.microsoft.com/en-us/library/ee330730%28VS.85%29.aspx#browser_emulation
If you make a registry edit, and tell your machine to emulate IE9 when Tessitura asks for a browser, it works:
http://www.west-wind.com/weblog/posts/2011/May/21/Web-Browser-Control-Specifying-the-IE-Version
(I did exactly as it looks on his first Registry Editor screenshot, but used tessitura.exe)
Not sure if that helps in your situation, Mo, but maybe it will help someone else digging for more info...
Beth
From: Jon Ballinger <bounce-jonballinger5072@tessituranetwork.com> Sent: 12/3/2013 8:28:15 AM
Mo, you may need to set the emulation mode for the browser control. By default it uses a lower version of IE. It can be set via a registry setting HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION or I think you can try doing it thorugh an http header. The header I did not have luck with before.
Another option is to have a place holder page for this screen and its job is only to open a new browser window with the desired web page. This was my last resort for a part that i could not get to work at all inside tessitura,
Jon
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!