Micrsoft Office File Convertor MSI
Has anyone been successfully able to make an msi out of the file converter (converts from 2007 to 2003 so one can edit files created in office 2007). I tried and received 158 warnings in my package regarding Undefined CLSID, Undefined typelib, Undefined ProgID, etc. I tried to install it anyways and when trying to open a file it give the error Converter could not save file.
Thanks for any help ahead of time.
-James
Thanks for any help ahead of time.
-James
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
anonymous_9363
16 years ago
I couldn't say for sure but I'd be *very* surprised if the converter weren't already supplied as an MSI. Although you may run an EXE to begin with, I'd guess an MSI is being created and run.
Run the EXE again and, before selecting any option, search your hard drive for MSIs. They will normally be written to one of the TEMP folders, either beneath your profile or %SYSTEMROOT%\Temp.
If so, the usual applies: never mess with vendor MSIs, but use transform(s) to make any changes you require.
Run the EXE again and, before selecting any option, search your hard drive for MSIs. They will normally be written to one of the TEMP folders, either beneath your profile or %SYSTEMROOT%\Temp.
If so, the usual applies: never mess with vendor MSIs, but use transform(s) to make any changes you require.
Posted by:
AB
16 years ago
Run FileFormatConverters.exe and the MSI and cab file extract to C:\Program Files\MSECache\O2007Cnv\1033
Regards,
Alan
Regards,
Alan
Posted by:
Jamezor
16 years ago
Awesome, it was exactly where you said it would be, thanks for the help.
James
James
Posted by:
fmonfort
16 years ago
FileFormatConverters.exe /extract:YourPath
Did you have try to deploy it with SMS 2003 ? I'm trying ... msiexec.exe process start but keep in task and don't finish package installation.
Did you have try to deploy it with SMS 2003 ? I'm trying ... msiexec.exe process start but keep in task and don't finish package installation.
Posted by:
anonymous_9363
16 years ago
Turn on MSI logging on a target workstation and, when MSIExec seems to have hung, kill it then check out what the last log entry is. That should give you a clue as to what's happening.
Enable MSI Logging:
[font="courier new"]REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer]
"Logging"="voicewarmup"
This will create .LOG files in %SYSTEMROOT%\Temp. The names will be prefixed 'MSI' followed a random 5-character string.
Enable MSI Logging:
[font="courier new"]REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer]
"Logging"="voicewarmup"
This will create .LOG files in %SYSTEMROOT%\Temp. The names will be prefixed 'MSI' followed a random 5-character string.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.