We are seeing startup exception errors for *some* users on *some* Terminal servers. ALL users use the same master ini and startup.bat. The error is "Null object reference at line 21 in function af_set_local_config_file of object impresario", and it happens immediately before the login screen even appears.
I can avoid the error if I log onto the Terminal Server as a different user first, then into the application with the problem user's credentials. This tells me that the issue has to do with the files/config on the Terminal Server directly. However, I have resynced files and even rebuilt the problem user's profile, but nothing has solved the problem. I'm stumped! Anybody see this error?
I think this is the error you get when the .ini file isnt available.
Do you think its possible the logon script hasnt finished running before the terminal services application starts. (Im assuming windows terminal services application)
If its possible, could you change the program that starts to be a batch/command file which checks for the .ini file before running e.g.
tessitura.exe t:\live.ini
Wayne
Thanks for responding! Once on the TS, my user can get to the ini without issue, so that doesn’t appear to be the problem.
Nancy Sheleheda
Sr. Director of Application Development and Support Services
The Pittsburgh Cultural Trust
803 Liberty Avenue
Pittsburgh, PA 15222
412-456-1387
sheleheda@trustarts.org
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Wayne Evans Sent: Thursday, September 11, 2014 7:20 PM To: Sheleheda, Nancy Subject: Re: [Tessitura Technical Forum] Inconsistent Startup Exception Error
From: Nancy Sheleheda <bounce-nancysheleheda3263@tessituranetwork.com> Sent: 9/11/2014 3:10:21 PM
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! ______________________________________________________________________ This email has been scanned by the Symantec Email Security service. For more information please visit: http://www.symanteccloud.com ______________________________________________________________________
To any future people who run across the issue, here's the resolution that works for me, for now:
I suspect my user's ini was corrupted. I deleted the offending users' ini and copied a known 'good' ini, renaming it to be the offending user's ini. Updated the hostname to be the offending user's hostname and voila!
I'm coming up with the exact same problem! Were you on version 12 when this issue came up?