/build/static/layout/Breadcrumb_cap_w.png

Another Quicktime problem

A new version of QT is available 7.4.5. My steps to manage this software is to run the exe and grab the files that are extracted to the temp folder. I then run the following command on the msi to create an admin install point at a temporary network location: msiexec.exe /a C:\quicktime.msi I then move the msi and the extracted files to their permanent location where they are accessed by UNC path and not a mapped drive letter.

Here's the weird problem and I've been doing this with all the previous versions without any issues until now. Somehow the network drive letter I used originally is getting added to the msi(is this possible?). When I try and run the msi it will fail with an error unless I have the original drive letter mapped even though all the required files are located at the location I'm running the install from. Here is the error section of the logged install:

MSI (s) (5C:70) [16:53:40:171]: Note: 1: 1327 2: J:\
Action start 16:53:40: CostFinalize.
MSI (s) (5C:70) [16:53:40:171]: Product: QuickTime -- Error 1327. Invalid Drive: J:\

Error 1327. Invalid Drive: J:\

When I do a search in the MSI using ORCA I cannot find any reference to J:\ so where is this coming from?[:@]

I've never had an issue like this with any of the other vendor MSI programs I create a network install point from.

0 Comments   [ + ] Show comments

Answers (3)

Posted by: gmorgan618 16 years ago
Blue Belt
0
Check your directory table for the J: entry, or try setting ROOTDRIVE=C:\ in the Property Table

Is this installation of Quicktime already on the machine, could be picking up cached data.

Just some thoughts.
Posted by: anonymous_9363 16 years ago
Red Belt
0
[cough]ProcMon!

Did someone say "ProcMon"?

Seriously, use ProcMon to see what file and registry activity is occuring. I'm pretty sure you'll find it's picking this up from a previous install's registry entry.
Posted by: joedown 16 years ago
Third Degree Brown Belt
0
There was no entry for J: in the MSI. I tried to install on another workstation that has never had any version of QT installed and it had the same error. Very strange. I ended up doing an admin install on a PC with no network drives mapped. This seems to have fixed the issue although QT does not ask where you want to do you admin install so just dumps everything at the root of the local drive[8|] This has to be the most obstinate vendor msi I have to deal with. What makes it worse is that it seems to come up every month or so because of security vulnerabilites discovered [:@]
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ