Hi all,

I am currently packaging FileFormatConverters.exe, which is used as an compatibility pack for office 2007. This is a product of Microsoft. The setup contains an MSI. I extracted the MSI from the exe. When i tried to extract the files from MSI it fails. I used the "/a" attribute along with the Msiexec command. The installer initiates and vanishes immediately. Can anyone help on this.

Thanks in advance.


bye,
Ayyavu
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Hi.
I have seen this with other msi-files from MS. It usualy automatic unpacks somewere on the computer you start the command on.
Look in the temp folder or in the root of C: for a new folder.

/M.N
Answered 04/24/2007 by: Mackan75
Orange Belt

Please log in to comment
0
ayyavu,

I believe that the admin installation of this MSI fails as all of the files are in the O12Conv.cab.

The .MSI file is only the database (no files are contained), which is why an admin installation doesn't work.

You can extract the files from the .CAB file - See below for a list of where they all live when installed:

PFILES=Program Files



PFILES

24/04/2007 12:00 <DIR> .
24/04/2007 12:00 <DIR> ..
24/04/2007 12:00 <DIR> COMMON
24/04/2007 12:00 <DIR> MSOFFICE
0 File(s) 0 bytes

PFILES\COMMON

24/04/2007 12:00 <DIR> .
24/04/2007 12:00 <DIR> ..
24/04/2007 12:00 <DIR> MSSHARED
24/04/2007 12:00 <DIR> SHAREDVS
0 File(s) 0 bytes

PFILES\COMMON\MSSHARED

24/04/2007 12:00 <DIR> .
24/04/2007 12:00 <DIR> ..
24/04/2007 12:00 <DIR> OFFICE11
24/04/2007 12:00 <DIR> OFFICE12
0 File(s) 0 bytes

PFILES\COMMON\MSSHARED\OFFICE11

24/04/2007 12:00 <DIR> .
24/04/2007 12:00 <DIR> ..
24/04/2007 12:00 <DIR> 1033
26/10/2006 13:41 1,422,088 msxml5.dll
1 File(s) 1,422,088 bytes

PFILES\COMMON\MSSHARED\OFFICE11\1033

24/04/2007 12:00 <DIR> .
24/04/2007 12:00 <DIR> ..
26/10/2006 13:41 91,912 msxml5r.dll
1 File(s) 91,912 bytes

PFILES\COMMON\MSSHARED\OFFICE12

24/04/2007 12:00 <DIR> .
24/04/2007 12:00 <DIR> ..
24/04/2007 12:00 <DIR> 1033
24/04/2007 12:00 <DIR> Cultures
27/10/2006 15:26 16,870,712 MSO.DLL
26/10/2006 20:13 932,688 msoshext.dll
26/10/2006 13:56 757,008 MSPTLS.DLL
27/10/2006 15:18 1,658,152 OGL.DLL
27/10/2006 15:12 1,082,144 RICHED20.DLL
5 File(s) 21,300,704 bytes

PFILES\COMMON\MSSHARED\OFFICE12\1033

24/04/2007 12:00 <DIR> .
24/04/2007 12:00 <DIR> ..
26/10/2006 14:31 80,696 xlsrvintl.dll
1 File(s) 80,696 bytes

PFILES\COMMON\MSSHARED\OFFICE12\Cultures

24/04/2007 12:00 <DIR> .
24/04/2007 12:00 <DIR> ..
26/10/2006 14:02 2,331,920 OFFICE.ODF
1 File(s) 2,331,920 bytes

\PFILES\COMMON\SHAREDVS

24/04/2007 12:00 <DIR> .
24/04/2007 12:00 <DIR> ..
24/04/2007 12:00 <DIR> VS7DEBUG
0 File(s) 0 bytes

PFILES\COMMON\SHAREDVS\VS7DEBUG

24/04/2007 12:00 <DIR> .
24/04/2007 12:00 <DIR> ..
24/04/2007 12:00 <DIR> Windows
0 File(s) 0 bytes
PFILES\COMMON\SHAREDVS\VS7DEBUG\Windows

24/04/2007 12:00 <DIR> .
24/04/2007 12:00 <DIR> ..
24/04/2007 12:00 <DIR> winsxs
0 File(s) 0 bytes

PFILES\COMMON\SHAREDVS\VS7DEBUG\Windows\winsxs

24/04/2007 12:00 <DIR> .
24/04/2007 12:00 <DIR> ..
24/04/2007 12:00 <DIR> 3kfkwlwq.lm8
24/04/2007 12:00 <DIR> Policies
0 File(s) 0 bytes

PFILES\COMMON\SHAREDVS\VS7DEBUG\Windows\winsxs\3kfkwlwq.lm8

24/04/2007 12:00 <DIR> .
24/04/2007 12:00 <DIR> ..
26/10/2006 13:40 7,441 8.0.50727.42.cat
26/10/2006 13:40 712 8.0.50727.42.policy
2 File(s) 8,153 bytes

PFILES\COMMON\SHAREDVS\VS7DEBUG\Windows\winsxs\Policies

24/04/2007 12:00 <DIR> .
24/04/2007 12:00 <DIR> ..
24/04/2007 12:00 <DIR> 2kfkwlwq.lm8
0 File(s) 0 bytes

PFILES\COMMON\SHAREDVS\VS7DEBUG\Windows\winsxs\Policies\2kfkwlwq.lm8

24/04/2007 12:00 <DIR> .
24/04/2007 12:00 <DIR> ..
26/10/2006 13:40 7,441 8.0.50727.42.cat
26/10/2006 13:40 712 8.0.50727.42.policy
2 File(s) 8,153 bytes

PFILES\MSOFFICE

24/04/2007 12:00 <DIR> .
24/04/2007 12:00 <DIR> ..
24/04/2007 12:00 <DIR> Office12
0 File(s) 0 bytes

PFILES\MSOFFICE\Office12

24/04/2007 12:00 <DIR> .
24/04/2007 12:00 <DIR> ..
24/04/2007 12:00 <DIR> 1033
26/10/2006 21:13 14,674,216 excelcnv.exe
26/10/2006 21:13 72,472 excelcnvpxy.dll
26/10/2006 20:12 396,592 Moc.exe
26/10/2006 20:42 8,423,224 OARTCONV.DLL
26/10/2006 21:08 1,764,112 PPCNV.DLL
26/10/2006 21:07 67,920 PPCNVCOM.EXE
26/10/2006 21:07 17,680 PPCNVPXY.DLL
30/09/2006 02:17 79,772 PPCPRTID.XML
27/10/2006 15:11 4,235,560 Wordcnv.dll
27/10/2006 15:11 26,904 Wordcnvpxy.cnv
26/10/2006 20:49 509,200 Wordcnvr.dll
27/10/2006 15:11 21,264 Wordconv.exe
30/09/2006 02:17 79,748 XLCPRTID.XML
13 File(s) 30,368,664 bytes

PFILES\MSOFFICE\Office12\1033

24/04/2007 12:00 <DIR> .
24/04/2007 12:00 <DIR> ..
26/10/2006 21:07 925,488 PPINTL.DLL
01/11/2004 17:56 12,288 PROTTPLN.PPT
01/11/2004 17:56 8,704 PROTTPLN.XLS
01/11/2004 17:56 12,288 PROTTPLV.PPT
01/11/2004 17:56 8,704 PROTTPLV.XLS
26/10/2006 21:17 1,744,184 XLINTL32.DLL
26/10/2006 21:17 37,688 XLLEX.DLL
7 File(s) 2,749,344 bytes

WINDOWS

24/04/2007 12:00 <DIR> .
24/04/2007 12:00 <DIR> ..
24/04/2007 12:00 <DIR> FONTS
0 File(s) 0 bytes

WINDOWS\FONTS

24/04/2007 12:00 <DIR> .
24/04/2007 12:00 <DIR> ..
11/09/2006 12:12 352,736 CALIBRI.TTF
11/09/2006 12:12 351,544 CALIBRIB.TTF
11/09/2006 12:12 362,524 CALIBRII.TTF
11/09/2006 12:12 367,620 CALIBRIZ.TTF
26/09/2006 21:12 1,090,456 CAMBRIA.TTC
26/09/2006 21:12 331,916 CAMBRIAB.TTF
09/08/2006 14:14 336,812 CAMBRIAI.TTF
09/08/2006 14:13 326,024 CAMBRIAZ.TTF
09/08/2006 14:13 161,644 CANDARA.TTF
09/08/2006 14:13 164,904 CANDARAB.TTF
09/08/2006 14:13 167,764 CANDARAI.TTF
09/08/2006 14:13 165,928 CANDARAZ.TTF
19/12/2005 12:27 98,520 CONSOLA.TTF
19/12/2005 12:27 100,436 CONSOLAB.TTF
19/12/2005 12:27 104,144 CONSOLAI.TTF
19/12/2005 12:27 110,268 CONSOLAZ.TTF
09/08/2006 14:13 313,880 CONSTAN.TTF
09/08/2006 14:13 317,724 CONSTANB.TTF
09/08/2006 14:13 306,000 CONSTANI.TTF
09/08/2006 14:13 313,044 CONSTANZ.TTF
09/08/2006 14:13 205,016 CORBEL.TTF
09/08/2006 14:13 210,788 CORBELB.TTF
09/08/2006 14:13 209,852 CORBELI.TTF
09/08/2006 14:13 217,308 CORBELZ.TTF
24 File(s) 6,686,852 bytes




Hope this is what you are looking for, installing the MSI with the usual command line switches will use the files in the .CAB file to install.

Thanks,

Dunnpy
Answered 04/24/2007 by: dunnpy
Red Belt

Please log in to comment
0
Hi,

Thanks Mackan75 and Dunnpy for your reply.

Is there any reason as why those files are not extracting with /a switch.

I am placing the CAB and MSI file under the same location while extracting.

Thanks,
Ayyavu.
Answered 04/24/2007 by: ayyavu
Senior Yellow Belt

Please log in to comment
0
ayyavu,

The point I was making was that there are no files in the .MSI file.

Trying to extract files from an .MSI file that has no files in it will extract nothing.
The files are external to the MSI in a .CAB file.


Get it?
Got it?
Good!

[:)]

Thanks,

Dunnpy
Answered 04/24/2007 by: dunnpy
Red Belt

Please log in to comment
0
hi..

just want to add..

sometimes files are extracted to the first network drive it will detect...

^_^
Answered 04/25/2007 by: monster
Senior Yellow Belt

Please log in to comment
0
Hi Ayyavu,
the /a switch can't work with this MSI package, because it lacks the AdminExecuteSequence table.
But the big question is: What are trying to do with an admin install of this package? It gives you nothing then the raw files!

However, it's easy to add this table and make it work:
Use ORCA for the following procedures:
Open sequence.msi from the installer SDK and export the AdminExecuteSequence table. Close this MSI.
Open the 'O12Conv.msi' and import this table from the textfile created in the previous action.
That's all! Now call: msiexec /a O12Conv.msi TARGETDIR=YourDir
Regards, Nick
Answered 04/25/2007 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
you can try setting INSTALLDIR property to guide it where you want. This "sometimes" works.
Answered 04/26/2007 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
Hi Dunnpy,
The point I was making was that there are no files in the .MSI file.

really sorry to write this, but you are wrong with your assumption here.
Installation files are never stored directly in the MSI database.
There is a special case, where they are stored sort of in the MSI, when a CAB file is embedded as a stream.
Where and how the source files are stored beside an MSI is decided mainly through the directory, file and media tables.

See:
http://msdn2.microsoft.com/en-us/library/aa368295.aspx
http://msdn2.microsoft.com/en-us/library/aa369279.aspx
http://msdn2.microsoft.com/en-us/library/aa369801.aspx

Regards, Nick
Answered 04/28/2007 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
nheim,

Point taken... was trying to keep it short and sweet and understandable for a new board member.

A lot of us have to work during the day too, and don't have time to research MSDN for the kind of answer you have supplied.

Thanks,

Dunnpy
Answered 04/30/2007 by: dunnpy
Red Belt

Please log in to comment
0
Hi Dunnpy,
didn' want to offend you, but it doesn't help to understand things even for a newbie, if you point errors to an incorrect reason.
However, you were very helpfull with publishing the directory structure and that you could simply extract the files from the CAB.
But this method will not work for the most of the MSI's, because the files in the CAB's are stored with the filekey and not there real name.

And finally: IMHO, if you do not look up those things in the originators doc's, it's not possible to understand, how those things really work.

Regards, Nick
Answered 04/30/2007 by: nheim
Tenth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity