Error : The Client cannot launch two applications in the same suite that uses different setting files
I got this error while sequencing "Quest Software TOAD" application.
ORACLE is a dependency for this application. I have edited the OSD file of TOAD and added the dependencies tag.
The SoftGrid Client could not launch QuestSoftware
TOAD 901 ENG 9.0.1.8.
The Client cannot launch two applications in the
same suite that use different settings files. Please
report the following error code to your System
Administrator.
Error code: 450260-0E806104-0000120A
Note: I get this error only after multiple launches... Not sure whether this hint will help tho...
Answers
I suspect you have two different OSDs with the same SUITE tag and have tried to launch them both. The error occurs when the client detects that two applications have the same SUITE name but reference different CP files. It won't let the second application launch as part of the first suite because the CP file describes a different (and likely incompatible) virtual environment. Note that in 4.5, the SUITE name is no longer mandatory. Take a look at the OSDs currently being used.
/Chris
You would need to delete the <PACKAGE NAME="******_*****_**_**"/> tag from the OSD file.
As mentioned earlier in APP-V 4.5 the suite name(PACKAGE NAME IS NO LONGER MANDATORY).
J.Caleb Kirubakaran- Marked As Answer byJ Caleb Kirubakaran1 Tuesday, October 20, 2009 8:17 PM
All Replies
I suspect you have two different OSDs with the same SUITE tag and have tried to launch them both. The error occurs when the client detects that two applications have the same SUITE name but reference different CP files. It won't let the second application launch as part of the first suite because the CP file describes a different (and likely incompatible) virtual environment. Note that in 4.5, the SUITE name is no longer mandatory. Take a look at the OSDs currently being used.
/Chris
Chris,
I want to be clear on that last point...
The SUITE tag, in prior releases, was mandatory and needed to be unique between packages.
You are saying that in 4.5 the tag is now optional and need not be included in any package?
Your post seems to imply that this tag is now *almost* completely ignored by the client. I am guessing that in the absense of a Suite tag, the client does something like use the package GUID for it's internal nefarious purposes, for which this user may have run afowl.
With 4.5 is there any good reason to include the Suite tag in newly generated packages? Are there other (negative) impacts such as client refresh detection of an updated OSD ono the server, or other such nonsense?
thanks!
Hi Tim. Yes, this is a departure from earlier versions. The SUITE is entirely optional in 4.5 and does not need to be unique if included. The client uses the package GUID internally for all package and virtual environment management. For the few externally visible package identifiers that used to display the suite name (such as might be found in client management console), we construct a suitable replacement out of the application name and version. So it is really just there for backwards compatibility, there is no good reason to continue to use it in 4.5.
/Chris
- Thanks.
You would need to delete the <PACKAGE NAME="******_*****_**_**"/> tag from the OSD file.
As mentioned earlier in APP-V 4.5 the suite name(PACKAGE NAME IS NO LONGER MANDATORY).
J.Caleb Kirubakaran- Marked As Answer byJ Caleb Kirubakaran1 Tuesday, October 20, 2009 8:17 PM
