Hello All,
Have a bit of a problem with one application that we are publishing on our xen app servers.
The application was and still is running on our old Windows 2000, Metaframe Xp farm without issue. Now we are migrating all the legacy apps to our newish Xenapp 5 farm.
The issue we are having with the application on the new farm is that it only stays active for exactly 68 seconds. Looking at citrix, its seems it is logging the session off as normal. If, from within the application, you for instance, are able to launch excel from within, the application will stay open and behave as normal.
I must admit, this is an inhouse application(written in power builder), but since it doesnt falter on the old citrix farm, they are pointing fingers at Xen App. Publishing office on the same servers works without a hitch, so its only this one application with the issue.
Has anyone come across anything similar, and know of a possible fix?
Regards
Mark
So, does the application sit there and then close itself after 68 seconds, even if you're using it?
Why is it called "Common Sense"? It doesn't seem all that common!
Yep, sure does. Doesnt matter if you let it sit, or use it.
The only odd thing is, if I create a cmd file, that launches the app, and put a pause at the end of the script, the app will stay open for as long as you want. Of course, they dont want a command prompt sitting there, while the app is running.
Any ideas?
This sounds like one of those apps that uses a "launcher" to load a child process and run that. The problem usually ends up being that once the "launcher" finished doing it's job, the session thinks the executable is done (which it is) and shuts down. Sometimes the child process gets missed so the session doesn't recognize that it needs to stick around. Have you tried using something like Process Explorer or Process Monitor to see what's going on on the server side?
Dan
That shouldn't be the problem. We have a program that does just that... launches another .exe and then closes. The program stays open. Procmon would definitely show what is going on though. If all else fails just launch it with a "start <drive>:\<path>executable.exe" command. That should launch the app and close the command window.