- #CITRIX PUBLISHED APPLICATION NOT LAUNCHING SOFTWARE#
- #CITRIX PUBLISHED APPLICATION NOT LAUNCHING WINDOWS#
The location of cmstart.exe of the third party software is “C:\Program Files (x86)\ThirdParty\Bin\cmstart.exe”. This is the modified environment path variable after the third party software installation on a XenApp 6.0 server. (x86)\Common Files\Citrix\System32\ C:\Program Files (x86)\Microsoft SQL Server\100\Tools\īinn\ C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\ ” %SystemRoot%\System32\Citrix\IMA C:\Program Files (x86)\Citrix\system32 C:\Program Files WindowsPowerShell\v1.0\ C:\Program Files (x86)\Citrix\system32\ C:\Program Files (x86)\Ĭitrix\System32\Citrix\IMA C:\Program Files (x86)\Citrix\System32\Citrix\IMA\Subsystems “%SystemRoot%\system32 %SystemRoot% %SystemRoot%\System32\Wbem %SYSTEMROOT%\System32\ The location of cmstart.exe of XenApp 6.0 is “C:\Program Files (x86)\Citrix\system32\cmstart.exe”. This is the default environment path variable before the third party software installation on a XenApp 6.0 server. So the variables provided by the third party software get the priority. XenApp does the same to locate cmstart.exe for published application launch process. One common reason for XenApp to locate the wrong cmstart.exe is because the third party software might have modified the environment path variables to point to its own cmstart.exe. By using the wrong version of cmstart.exe the launch process breaks. Because XenApp uses an executable named cmstart.exe for the launch of published applications, it might confuse and locate the cmstart.exe of the third party software instead.
One of the possible causes for this issue is that the third party software installation utilizes an executable file named cmstart.exe and modifies the environment variables to point to that executable.
#CITRIX PUBLISHED APPLICATION NOT LAUNCHING WINDOWS#
Note: In a XenDesktop 7 App Edition scenario on Windows Server 2012, CtxHide.exe will not be present on the system, and does not need to be included in this registry update.įollowing is an example of the AppSetup Value Data: CtxHide.exe UsrLogon.Cmd,cmstart.exeįollowing are two causes for this error to occur: Cause 1 There are no commas placed between CtxHide.exe and UsrLogon.Cmd. If not already present, add the data value cmstart.exe after Cmd separated by a comma.Īdd the data value CtxHide.exe before the data value UsrLogon.Cmd. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon Open the Registry Editor and go to the following registry key: NOTE: Duplication of any values in this key will lead to application and desktop launch failures. \Microsoft SQL Server\100\Tools\Binn\ C:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\ ” Solution 2Ĭomplete the following steps to add values to the AppSetup String Value and resolve the issue:Ĭaution! Refer to the Disclaimer at the end of this article before using Registry Editor. \Common Files\Citrix\System32\ C:\Program Files (x86)\ThirdParty\Bin\ C:\Program Files (x86) %SystemRoot%\System32\Citrix\IMA C:\Program Files (x86)\Citrix\system32 C:\Program Files (x86) \Citrix\System32\Citrix\IMA C:\Program Files (x86)\Citrix\System32\Citrix\IMA\Subsystems \WindowsPowerShell\v1.0\ C:\Program Files (x86)\Citrix\system32\ C:\Program Files (x86) “%SystemRoot%\system32 %SystemRoot% %SystemRoot%\System32\Wbem %SYSTEMROOT%\System32 After the change, XenApp locates the correct version of cmstart.exe. In the PATH Environment variable, Move the location of the third party software variables after the XenApp variables.
0 kommentar(er)
