App-V Not Correctly Re-Pointing DLL Paths in Registry
Using the App-V 4.6 SP1 sequencer, we have sequenced an App-V package using a Wise Installer setup.exe
The only modifications to the package is overwriting 3 files in the virtual install folder (we use I: if it makes a difference), an exe and an ini file with paths to the DB etc.
No problems there
However, on running the program it fails with an error.
The vendor reports that the error is because it cannot find some ADS OLE DB dll fil.
On checking the virtual registry path, the path is [cant remember the exact path, it was someone beginning with %CSIDL_COMMON_APPDATA% and possibly \Microsoft Application Virtualization Sequencer\Scratch?? ]
When we change it to %SFT_MNT%\AIS LIMS\AISLIMS\ADSOLEDB.DLL it works
Surely we dont need to do this? The sequencer is obviously changing the path that would be created in a normal physical install, but its doing it incorrectly.
Any advice please!?
The only modifications to the package is overwriting 3 files in the virtual install folder (we use I: if it makes a difference), an exe and an ini file with paths to the DB etc.
No problems there
However, on running the program it fails with an error.
The vendor reports that the error is because it cannot find some ADS OLE DB dll fil.
On checking the virtual registry path, the path is [cant remember the exact path, it was someone beginning with %CSIDL_COMMON_APPDATA% and possibly \Microsoft Application Virtualization Sequencer\Scratch?? ]
When we change it to %SFT_MNT%\AIS LIMS\AISLIMS\ADSOLEDB.DLL it works
Surely we dont need to do this? The sequencer is obviously changing the path that would be created in a normal physical install, but its doing it incorrectly.
Any advice please!?
0 Comments
[ + ] Show comments
Answers (14)
Please log in to answer
Posted by:
mcompton69
12 years ago
OK, so i re-ran the sequencer and the incorrect path in full is:
%CSIDL_COMMON_APPDATA%\Microsoft\Application Virtualization Sequencer\Package Root\AIS LIMS + PDF Writer\AISLIMS\ADSOLEDB.DLL
If i manually edit the package so that all the references to this file ready %SFT_MNT%\AIS LIMS\AISLIMS\ADSOLEDB.DLL then it works.
However, there may be other dlls that have incorrect paths also - i have no confidence in the package if i must correct find and replace these incorrect paths. and i cannot beleive that this isnt just a case of a setting or something in the seqeuencer at the time of creating the package that is wrong.
PLEASE HELP!!
%CSIDL_COMMON_APPDATA%\Microsoft\Application Virtualization Sequencer\Package Root\AIS LIMS + PDF Writer\AISLIMS\ADSOLEDB.DLL
If i manually edit the package so that all the references to this file ready %SFT_MNT%\AIS LIMS\AISLIMS\ADSOLEDB.DLL then it works.
However, there may be other dlls that have incorrect paths also - i have no confidence in the package if i must correct find and replace these incorrect paths. and i cannot beleive that this isnt just a case of a setting or something in the seqeuencer at the time of creating the package that is wrong.
PLEASE HELP!!
Posted by:
mcompton69
12 years ago
SOLVED:
Firstly, I found this page which describes the problem in detail: http://kirxblog.wordpress.com/2011/05/13/defective-component-registration-with-4-6-sp1-sequencer/
Then I found this post which go through an exchange between App-V users and MS: http://www.appvirtguru.com/viewtopic.php?f=9&t=4117
Then I read there is a hotfix specifically for this issue! Hurrah http://support.microsoft.com/kb/2571168/en-us
I will try and see if sequencing after installing the hotfix solves this issue and post back if it does NOT.
Firstly, I found this page which describes the problem in detail: http://kirxblog.wordpress.com/2011/05/13/defective-component-registration-with-4-6-sp1-sequencer/
Then I found this post which go through an exchange between App-V users and MS: http://www.appvirtguru.com/viewtopic.php?f=9&t=4117
Then I read there is a hotfix specifically for this issue! Hurrah http://support.microsoft.com/kb/2571168/en-us
I will try and see if sequencing after installing the hotfix solves this issue and post back if it does NOT.
Posted by:
mcompton69
12 years ago
Uninstalled the 4.6 SP1 sequencer (4.6.1.20870), installed the hotfix 3 sequencer (4.6.1.30091) which is the latest sequencer version, but it still does not sequence correctly.
Come on Microsoft - pull your fat, rich fingers out and fix your product!!!!!!!!![:@]
I cannot believe they have identified the problem - so long ago, yet its still not fixed. I think it shows their commitment to App-V - which the basically bought up from Software grid rather than writing themselves.
Posted by:
vkleiner
12 years ago
May it´s worth a try to use a seperate drive if you don´t already have done it ...
Posted by:
pjgeutjens
12 years ago
Have you tried sequencing the app to the VFS, so installing to C:\ instead of I:\ in your case during the capture process?
Posted by:
mcompton69
12 years ago
ORIGINAL: vkleiner
May it´s worth a try to use a seperate drive if you don´t already have done it ...
I install into the I: drive which is created by the App-V Seuqencer installation - is that what you mean?
Posted by:
mcompton69
12 years ago
ORIGINAL: pjgeutjens
Have you tried sequencing the app to the VFS, so installing to C:\ instead of I:\ in your case during the capture process?
No, not yet, but I am not a long time user or expert of App-V by any stretch of the imagination - Why would I install to the C: drive instead of the App-V drive (I:). That goes against specific App-V instructions - in fact there is a little balooon popup saying dont install on C: do it on I:?!?!
What benefit would that bring, surely there is LESS chance the package will work that way?
Posted by:
vkleiner
12 years ago
Hi,
use a dedicated drive instead a simulated by the Sequencer.
Deinstall the Sequencer Software, create a new drive in your OS by add a new harddisk: physikal / virtual drive for VMware Workstation or Virtual PC / or take a 4GB free partition and set drive lette to I:.
Install the Sequencer again and use this seperate drive as virtual drive. In the selection during setup, your drive I is showen as local disk.
You also can sequence to C: drive - see nice article on kirx blog: to-q-or-not-to-q-that-is-the-question
/vkleinerde
use a dedicated drive instead a simulated by the Sequencer.
Deinstall the Sequencer Software, create a new drive in your OS by add a new harddisk: physikal / virtual drive for VMware Workstation or Virtual PC / or take a 4GB free partition and set drive lette to I:.
Install the Sequencer again and use this seperate drive as virtual drive. In the selection during setup, your drive I is showen as local disk.
You also can sequence to C: drive - see nice article on kirx blog: to-q-or-not-to-q-that-is-the-question
/vkleinerde
Posted by:
mcompton69
12 years ago
ORIGINAL: pjgeutjens
Have you tried sequencing the app to the VFS, so installing to C:\ instead of I:\ in your case during the capture process?
@pjgeutjens
I tried what you recommended.
I did not work, because there are no files in C:\Program Files\... whcih are referenced in the package, just as expected!
Thank you for wasting my time.
Posted by:
mcompton69
12 years ago
ORIGINAL: kkaminsk
Just curious, which client version is deployed?
This has been tested on 4.6.1.20870 and 4.6.1.30111 with indentical result.
Posted by:
Rheuvel
12 years ago
ORIGINAL: vkleiner
Hi,
use a dedicated drive instead a simulated by the Sequencer.
Deinstall the Sequencer Software, create a new drive in your OS by add a new harddisk: physikal / virtual drive for VMware Workstation or Virtual PC / or take a 4GB free partition and set drive lette to I:.
Install the Sequencer again and use this seperate drive as virtual drive. In the selection during setup, your drive I is showen as local disk.
This will indeed solve the above issue. I have encountered a similar situation before (only not with the MS sequencer but a 3rd party sequencing tool)
"%CSIDL_COMMON_APPDATA%\Microsoft\Application Virtualization Sequencer\Package Root\..." is the substitute path the sequencer creates on installation if the driver letter you select doesn't exist already.
Some actions see right through the substitute path. By avoiding the use of a substitute path there won't be any problem.
Posted by:
pjgeutjens
12 years ago
I tried what you recommended.
I did not work, because there are no files in C:\Program Files\... whcih are referenced in the package, just as expected!
Thank you for wasting my time.
It was only a suggestion... I don't remember twisting your arm.
Anyway, I'll let the others help you, hope you find a solution.
PJ
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.