Hi,
I support a fat client application, which my client is running through citrix. I'm trying to establish whether citrix can be the cause of the following situation.
Unfortunately, I'm not au fait with citrix, so please bear with me.
According to my client they have 2 ways of accessing the application viz. gaining access to the published application via Citrix Network neighbourhood, or clicking on an icon on the desktop, which launches the published application.
The application had a bug in the launch executable, which had been fixed early March. No problems. The licensing for the application is held in the ini file, which expired in the end of March. An updated ini file was provided.
This is the issue:
When clicked on the published icon on the desktop, the NT (W2k) login appears, the users default login and domain settings are correct, user types in password, all is fine, but then it just disappears. Back to seeing an icon on desktop, nothing launched (next would have been the application login screen).
However, when accessing through Citrix network neighbourhood, the application launches successfully.
Two things to consider before I proceed:
1.) The new executable had been working file prior to the new ini file.
2.) When the application licenses expired, the "non launching of the application" was the first indication that something was amiss. The application does generate an error when licenses have expired. In this instance, it did not. Only when the client accessed the application as a fat client did the error display, hence we could start troubleshooting.
The current situation is that the published application on the desktop does not launch with the new exe and ini file in combination, BUT DOES LAUNCH with the new ini file and OLD EXE.
My contention is that if the application launches through network neighbourhood, with new ini file and new exe, and as a fat client, then the issue is with citrix, not the application.
However, my clients view is that he left the office one day, all was working, entered it the next day, eventually discovered my application had an issue, had the ini corrected, MADE NO changes to the citrix set up, and it does not work (published icon on the desktop that is). So my application is the problem.
The Questions:
1.) Based on the summary of events above, could citrix in any way influence either the ini or exe (or both)?
2.) May I have opinions from the forum members please.
Metaframe 1.8
W2K
Oracle 8i
Regards
Warren
I'd rather be stupid for 5 minutes than for the rest of my life.
I support a fat client application, which my client is running through citrix. I'm trying to establish whether citrix can be the cause of the following situation.
Unfortunately, I'm not au fait with citrix, so please bear with me.
According to my client they have 2 ways of accessing the application viz. gaining access to the published application via Citrix Network neighbourhood, or clicking on an icon on the desktop, which launches the published application.
The application had a bug in the launch executable, which had been fixed early March. No problems. The licensing for the application is held in the ini file, which expired in the end of March. An updated ini file was provided.
This is the issue:
When clicked on the published icon on the desktop, the NT (W2k) login appears, the users default login and domain settings are correct, user types in password, all is fine, but then it just disappears. Back to seeing an icon on desktop, nothing launched (next would have been the application login screen).
However, when accessing through Citrix network neighbourhood, the application launches successfully.
Two things to consider before I proceed:
1.) The new executable had been working file prior to the new ini file.
2.) When the application licenses expired, the "non launching of the application" was the first indication that something was amiss. The application does generate an error when licenses have expired. In this instance, it did not. Only when the client accessed the application as a fat client did the error display, hence we could start troubleshooting.
The current situation is that the published application on the desktop does not launch with the new exe and ini file in combination, BUT DOES LAUNCH with the new ini file and OLD EXE.
My contention is that if the application launches through network neighbourhood, with new ini file and new exe, and as a fat client, then the issue is with citrix, not the application.
However, my clients view is that he left the office one day, all was working, entered it the next day, eventually discovered my application had an issue, had the ini corrected, MADE NO changes to the citrix set up, and it does not work (published icon on the desktop that is). So my application is the problem.
The Questions:
1.) Based on the summary of events above, could citrix in any way influence either the ini or exe (or both)?
2.) May I have opinions from the forum members please.
Metaframe 1.8
W2K
Oracle 8i
Regards
Warren
I'd rather be stupid for 5 minutes than for the rest of my life.