When sequencing FolioView 2012 or 2015 with AppV5 SP3, launching the application after sequencing generates an error:
No object handler is registered for this object type.
This error seems to appear because VFS either isn’t fully loaded by the time Views.exe is loaded so the program/dlls actually traverse down a non-virtual path, or they somehow break the AppV bubble and don’t find whatever it is they are looking for. To correct this issue, you need to create a symbolic link to the VFS’d program directory from where the actual directory is supposed to reside. For instance, I sequenced FolioView to:
C:\Program Files (x86)\CIHI
To produce the error, I launch my command like so (this is what AppV5 automatically puts into the shortcut):
%ALLUSERSPROFILE%\Microsoft\AppV\Client\Integration\C05CC38A-D146-442B-B97F-89E8867DF0CE\Root\VFS\ProgramFilesX86\CIHI\CIHI_PUB_2015\Cihi32\Views.exe -L1033 -cSoftware\CIHI\2015\ICD10\English -i”\\fileserver\CTX_APPS\FolioView2015\cci_2015_eng.sdw”
I then get the error message.
If I mklink /d “C:\Program Files (x86)\CIHI” D:\AppVData\PackageInstallationRoot\C05CC38A-D146-442B-B97F-89E8867DF0CE\0CA628F4-AC24-4981-9B52-DA
Then launch the application via the ‘native’ path:
“C:\Program Files (x86)\CIHI\CIHI_PUB_2015\Cihi32\Views.exe” -L1033 -cSoftware\CIHI\2015\ICD10\English -i”\\q9-v-citrix-lif1.healthy.bewell.ca\CTX_APPS\FolioView2015\cci_2015_eng.sdw”
It works without any error messages and without issue.
Here’s a short clip of the error and the ‘fix’:
I did a stack trace of the error message and it comes up like so:
There are several calls that appear to look for files (nfomgr4, fcctrl4, mpr, davInt) that maybe generating the error message, but, I am not skilled enough at WinDBG at this time to be able to dig deeper. Either way, there appears to be a limitation within AppV5 that prevents this program from operating correctly. The same program works in AppV 4.6 without issue though, so it appears AppV5 sill has some work to go to get full compatibility with PITA applications.
Here’s the application working fine in AppV 4.6. The application was installed identically for both AppV versions.