.cli file runs when launched from the wizard, but not when double clicked

ASF · Jan 2, 2019

Hi all,

I have an FTView SE application (local station) on a Windows 7 PC that has been in and working fine for about 4 years now. About a month ago, the shortcut to start the client on the desktop stopped working. I deleted and re-created the shortcut - still no good. I deleted the actual .cli file that the shortcut was pointing to, and re-created it with the wizard - still no good. If I select the file in the wizard and click run, it runs fine. But if I double click the .cli file itself (or right click > open, etc) - nothing. No errors, no popups, no additional processes start in task monitor - nothing seems to happen at all.

I've gone through the windows update history looking for any updates installed around the time it stopped working, but there's nothing within about 6 months.

Anyone ever come across this, or have any ideas as to what I could try?

The knowledge base is being manifestly unhelpful since it won't accept search terms shorter than four characters, meaning a search for ".cli file does not work" gives results simply for "file does work". God help the person who needs to search for a PLC instruction!

rdrast · Jan 3, 2019

FIRST: Right click on the .cli file, select "Open With", then "Choose Default Program", then browse to FTView Enterprise DisplayClient.exe file... see if that works... If it doesn't, check your registry... there should be (at least two, but knowing Rockwell, more like 20,223,182) entries in Computer\HKEY_CLASSES_ROOT

The first should just be the ".cli" entry redirector...

Code:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\.cli]
@="Client.Application\\ Active Display Client"

[HKEY_CLASSES_ROOT\.cli\Client.Application]

[HKEY_CLASSES_ROOT\.cli\Client.Application\ Active Display Client]

[HKEY_CLASSES_ROOT\.cli\Client.Application\ Active Display Client\ShellNew]

The second entry is HKEY_CLASSES_ROOT\Client.Application:

Code:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Client.Application]

[HKEY_CLASSES_ROOT\Client.Application\ Active Display Client]
@="Active Display Client"

[HKEY_CLASSES_ROOT\Client.Application\ Active Display Client\DefaultIcon]
@="C:\\Windows\\Installer\\{AA01FF21-A8DA-4301-A87E-8A1ACC463D77}\\_3615D989_B794_44CF_A95B_29262787ECEA,0"

[HKEY_CLASSES_ROOT\Client.Application\ Active Display Client\shell]

[HKEY_CLASSES_ROOT\Client.Application\ Active Display Client\shell\Open]
@="Open"

[HKEY_CLASSES_ROOT\Client.Application\ Active Display Client\shell\Open\command]
@="\"C:\\Program Files (x86)\\Rockwell Software\\RSView Enterprise\\DisplayClient.exe\" \"%1\""
"command"=hex(7):4a,00,2e,00,4c,00,5f,00,5f,00,45,00,31,00,56,00,55,00,39,00,\
  49,00,21,00,29,00,55,00,2b,00,45,00,4d,00,51,00,43,00,4e,00,53,00,45,00,5f,\
  00,43,00,6c,00,69,00,65,00,6e,00,74,00,3e,00,7b,00,41,00,61,00,77,00,32,00,\
  28,00,2c,00,33,00,55,00,3d,00,32,00,45,00,30,00,78,00,2c,00,68,00,27,00,7e,\
  00,5f,00,2c,00,20,00,22,00,25,00,31,00,22,00,00,00,53,00,30,00,7e,00,57,00,\
  25,00,59,00,2d,00,28,00,5f,00,39,00,40,00,38,00,67,00,4b,00,43,00,78,00,57,\
  00,63,00,61,00,38,00,53,00,45,00,5f,00,54,00,65,00,73,00,74,00,5f,00,53,00,\
  65,00,72,00,76,00,65,00,72,00,5f,00,61,00,6e,00,64,00,5f,00,43,00,6c,00,69,\
  00,65,00,6e,00,74,00,3e,00,7b,00,41,00,61,00,77,00,32,00,28,00,2c,00,33,00,\
  55,00,3d,00,32,00,45,00,30,00,78,00,2c,00,68,00,27,00,7e,00,5f,00,2c,00,20,\
  00,22,00,25,00,31,00,22,00,00,00,00,00

There might also be the following entries in Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes.
The first should just be the ".cli" entry redirector...
Here is my registry export for that...

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.cli]
@="Client.Application\\ Active Display Client"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.cli\Client.Application]

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.cli\Client.Application\ Active Display Client]

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\.cli\Client.Application\ Active Display Client\ShellNew]

The second entry is the actual redirect target, and shows in the same \Classes hive under "\Client.Application". Here is my registry file for that:

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Client.Application]

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Client.Application\ Active Display Client]
@="Active Display Client"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Client.Application\ Active Display Client\DefaultIcon]
@="C:\\Windows\\Installer\\{AA01FF21-A8DA-4301-A87E-8A1ACC463D77}\\_3615D989_B794_44CF_A95B_29262787ECEA,0"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Client.Application\ Active Display Client\shell]

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Client.Application\ Active Display Client\shell\Open]
@="Open"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Client.Application\ Active Display Client\shell\Open\command]
@="\"C:\\Program Files (x86)\\Rockwell Software\\RSView Enterprise\\DisplayClient.exe\" \"%1\""
"command"=hex(7):4a,00,2e,00,4c,00,5f,00,5f,00,45,00,31,00,56,00,55,00,39,00,\
  49,00,21,00,29,00,55,00,2b,00,45,00,4d,00,51,00,43,00,4e,00,53,00,45,00,5f,\
  00,43,00,6c,00,69,00,65,00,6e,00,74,00,3e,00,7b,00,41,00,61,00,77,00,32,00,\
  28,00,2c,00,33,00,55,00,3d,00,32,00,45,00,30,00,78,00,2c,00,68,00,27,00,7e,\
  00,5f,00,2c,00,20,00,22,00,25,00,31,00,22,00,00,00,53,00,30,00,7e,00,57,00,\
  25,00,59,00,2d,00,28,00,5f,00,39,00,40,00,38,00,67,00,4b,00,43,00,78,00,57,\
  00,63,00,61,00,38,00,53,00,45,00,5f,00,54,00,65,00,73,00,74,00,5f,00,53,00,\
  65,00,72,00,76,00,65,00,72,00,5f,00,61,00,6e,00,64,00,5f,00,43,00,6c,00,69,\
  00,65,00,6e,00,74,00,3e,00,7b,00,41,00,61,00,77,00,32,00,28,00,2c,00,33,00,\
  55,00,3d,00,32,00,45,00,30,00,78,00,2c,00,68,00,27,00,7e,00,5f,00,2c,00,20,\
  00,22,00,25,00,31,00,22,00,00,00,00,00

If you copy those into a text editor, and save them with a .reg extension, they can be autoloaded to the registry hive, but I'd personally just go and compare what you have to that to see if something is missing.

---

Another reason to love Ignition.

rdrast · Jan 3, 2019

As an aside, the HKEY_CLASSES_ROOT key is supposed to be obsolete, and was only used in Windows 3.1/3.11, and was supposed to be dropped completely in favor the the HKEY_LOCAL_MACHINE\SOFTWARE\Classes entries, but because of laziness of applications programmers, the HKEY_CLASSES_ROOT key remains today.

ASF · Jan 3, 2019

Incredible. Do I want to know how on earth you found/learned all of this?

The first point about choosing the correct application did the trick. Not sure how the file association got broken, but it's fixed now.

And yes, I'm a recently converted Ignition fanboy. Working on talking some major clients around to it as well

Thanks!

rdrast · Jan 4, 2019

ASF said:
Incredible. Do I want to know how on earth you found/learned all of this?

The first point about choosing the correct application did the trick. Not sure how the file association got broken, but it's fixed now.

And yes, I'm a recently converted Ignition fanboy. Working on talking some major clients around to it as well

Thanks!

A long time ago, I spent a lot of time writing installers for my Windows software for clients.

.cli file runs when launched from the wizard, but not when double clicked

ASF

Lifetime Supporting Member

rdrast

Lifetime Supporting Member

rdrast

Lifetime Supporting Member

ASF

Lifetime Supporting Member

rdrast

Lifetime Supporting Member

Similar Topics