Published App fails to launch unless first app in session
book
Article ID: CTX230666
calendar_today
Updated On:
Description
XenApp 7.9 - App fails to launch unless first app in session
In this scenario client is publishing three instances of Access 2010 from his Storefront - one passes the command line argument above. This app will load 100% of the time if it's the first application in the session (opens the session).
- If you open a second application (any published app), after this Access 2010 has been opened - the second app will open 100% of the time.
- Whilst leaving that application open, (keeping the session open) if you close Access and try to open it again it will fail to launch 100% of the time.
- You must log off the session to allow Access to open again.
- If a session is opened with a different application, there is a 1 in 3 chance that Access 2010 will open - most of the time it wont.
- The other two published versions of Access 2010 without the command line arguments will work 100% of the time regardless
- Same issue with app called Eviews8 in Cx environment - follows same behaviour - so not a MS issue or provider specific issue
Resolution
- Logged onto Studio and checked the details of the applications
- Went to Studio > Applications > Application Settings > Location
- It was noted that the troublesome applications used the environment variable %program files% in Path to the executable file rather than the full path - the non-issue applications had a hard path (User had created other versions of Access using the duplicate applications feature.)
- It was suggested to change the env variable to a hard path c:\Program Files\*rest of path*
- Tested & confirmed working - behaviour was no longer reproducible
- To confirm, performed the same operation on the other erroneous application - Eviews8 - again, confirmed no longer an issue and problem behaviour no longer reproducible.
Problem Cause
The troublesome applications used the environment variable %program files% in
Path to the executable file rather than the full path - the non-issue applications had a hard path (User had created other versions of Access using the duplicate applications feature.)
Issue/Introduction
Published app will load 100 of the time if first app launched (thus creating session) - if app is closed cannot be opened again without logging off session and creating new session (by launching app first).
Was this article helpful?
thumb_up
Yes
thumb_down
No