Home > Citrix > XenApp: Application launch fails via Citrix client/web interface

XenApp: Application launch fails via Citrix client/web interface

Error:

—————————

Farming MIS APP

—————————

Run-time error ’372′:

Failed to load control ‘ucFldCostTab’ from .  Your version of  may be outdated.  Make sure you are using the version of the control that was provided with your application.

—————————

OK

—————————

 

Symptoms:

  1. Application launches fine for the administrative user accounts both locally and via Citrix client/web interface
  2. Application Launch via Citrix web interface  results in the above shown Run-time error ’372′ for any other accounts
  3. Works fine when you add the failing account to administrators group

 

Troubleshooting:

  1. Run Procmon on the XenApp server
  2. Launch the application as non-admin user account to reproduce the error case
  3. Go through procmon logs to figure out access denied errors
  4. Look for the events whose path refers to other users profile locations

 

Debug Logging:

 

Before:

C:>reg query “HKEY_LOCAL_MACHINESOFTWAREClassesTypeLib{6FBA474E-43AC-11CE-9A0E-00AA0062BB4C}1.0win32″ /s

HKEY_LOCAL_MACHINESOFTWAREClassesTypeLib{6FBA474E-43AC-11CE-9A0E-00AA0062BB4C}1.0win32

(Default)    REG_SZ    C:Userslocal-adminWINDOWSSYSINFO.OCX

C:>

 

Re-registration command:

 

C:>regsvr32 “C:Program Files (x86)Common FilesFarmingMISSYSINFO.OCX”

C:>

 

After:

 

C:>reg query “HKEY_LOCAL_MACHINESOFTWAREClassesTypeLib{6FBA474E-43AC-11CE-9A0E-00AA0062BB4C}1.0win32″ /s

HKEY_LOCAL_MACHINESOFTWAREClassesTypeLib{6FBA474E-43AC-11CE-9A0E-00AA0062BB4C}1.0win32
(Default)    REG_SZ    C:Program Files (x86)Common FilesFarmingMISSYSINFO.OCX

C:>

 

Fix:

  1. In my case, I figured out the issue is due to some Class files installed under administrator user profile thus works for any other admin users
  2. I moved the files to central place where all users/applications have access to the files and then re-registered the files using regsvr32

 

 

 

Categories: Citrix Tags:
  1. No comments yet.
  1. No trackbacks yet.