/build/static/layout/Breadcrumb_cap_w.png

error while installation of office compatibillity pack

Hi,
I am trieng to install office 2007 compatibillity pack on user's machine, but I am getting error saying :

"Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package." below is the log file. I took access of user's machine twice, if again I take access, he will screw me. [:@]

possibillity 1: may be office 2003 latest service pack is not there. I am checking other possibilities. suggestions please.

0 Comments   [ + ] Show comments

Answers (7)

Posted by: anonymous_9363 14 years ago
Red Belt
0
I took access of user's machine twice, if again I take access, he will screw meForgive me, but testing on user's live machines is idiocy. For pity's sake, download and install MS's Virtual PC or Sun's VirtualBox. They're both free (VB is GNU, IIRC) and you can have as many user or packaging machines as memory and disk space will allow.

Office SP3 is recommended but not required to install the Compatibility Pack. http://www.microsoft.com/downloads/details.aspx?FamilyId=941B3470-3AE9-4AEE-8F43-C6BB74CD1466&displaylang=en#Requirements
Posted by: abking99 14 years ago
Second Degree Blue Belt
0
Yes, but on my test machine, I am able to install it. On my test machine office 2003 with service pack2 is present. So getting confused what to do.
Posted by: anonymous_9363 14 years ago
Red Belt
0
Most of the virtualisation tools allow you to import machines and create a virtual machine from the image. Do that, rename it, join it to another domain (if you don't have rights to add machines to your existing one) and test.

My guess would be that the Office installation data is screwed on that machine. Windows Installer log information? Event Viewer? ProcMon? Have you used ANY of those tools yet? How do I already know the answer to that question?
Posted by: abking99 14 years ago
Second Degree Blue Belt
0

=== Verbose logging started: 03.09.2009 15:37:34 Build type: SHIP UNICODE 3.01.4000.2805 Calling process: C:\WINNT\system32\msiexec.exe ===
MSI (c) (80:94) [15:37:34:073]: Resetting cached policy values
MSI (c) (80:94) [15:37:34:073]: Machine policy value 'Debug' is 0
MSI (c) (80:94) [15:37:34:073]: ******* RunEngine:
******* Product: \\smsww0pri-chbs\packages$\Office2007_CompatibilityPack-12.0.6021-US-001\O12Conv.msi
******* Action:
******* CommandLine: **********
MSI (c) (80:94) [15:37:34:135]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (c) (80:94) [15:37:34:135]: Machine policy value 'DisableUserInstalls' is 0
MSI (c) (80:94) [15:37:34:291]: Entering MsiProvideComponentFromDescriptor. Descriptor: ZftgKcJ+v9&.OnoCK'1xHCL_Accessories_NISCore>}C5KO$?V=?TyYiSCtS.h, PathBuf: AFE764, pcchPathBuf: AFE760, pcchArgsOffset: AFE6C0
MSI (c) (80:94) [15:37:34:307]: MsiProvideComponentFromDescriptor is returning: 0
MSI (c) (80:94) [15:37:34:463]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (80:94) [15:37:34:463]: SOFTWARE RESTRICTION POLICY: Verifying package --> '\\smsww0pri-chbs\packages$\Office2007_CompatibilityPack-12.0.6021-US-001\O12Conv.msi' against software restriction policy
MSI (c) (80:94) [15:37:34:463]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (c) (80:94) [15:37:34:463]: SOFTWARE RESTRICTION POLICY: \\smsww0pri-chbs\packages$\Office2007_CompatibilityPack-12.0.6021-US-001\O12Conv.msi is not digitally signed
MSI (c) (80:94) [15:37:34:541]: SOFTWARE RESTRICTION POLICY: \\smsww0pri-chbs\packages$\Office2007_CompatibilityPack-12.0.6021-US-001\O12Conv.msi is permitted to run at the 'unrestricted' authorization level.
MSI (c) (80:94) [15:37:34:541]: Cloaking enabled.
MSI (c) (80:94) [15:37:34:541]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (80:94) [15:37:34:557]: End dialog not enabled
MSI (c) (80:94) [15:37:34:557]: Original package ==> \\smsww0pri-chbs\packages$\Office2007_CompatibilityPack-12.0.6021-US-001\O12Conv.msi
MSI (c) (80:94) [15:37:34:557]: Package we're running from ==> C:\TEMP\5781fa.msi
MSI (c) (80:94) [15:37:34:573]: APPCOMPAT: looking for appcompat database entry with ProductCode '{90120000-0020-0409-0000-0000000FF1CE}'.
MSI (c) (80:94) [15:37:34:573]: APPCOMPAT: no matching ProductCode found in database.
MSI (c) (80:94) [15:37:34:573]: MSCOREE not loaded loading copy from system32
MSI (c) (80:94) [15:37:34:588]: Opening existing patch 'C:\WINNT\Installer\59be9a.msp'.
MSI (c) (80:94) [15:37:34:588]: Note: 1: 2203 2: C:\WINNT\Installer\59be9a.msp 3: -2147287038
MSI (c) (80:94) [15:37:34:588]: Couldn't find local patch 'C:\WINNT\Installer\59be9a.msp'. Looking for it at its source.
MSI (c) (80:94) [15:37:34:588]: Resolving Patch source.
MSI (c) (80:94) [15:37:34:588]: User policy value 'SearchOrder' is 'nmu'
MSI (c) (80:94) [15:37:34:588]: User policy value 'DisableMedia' is 0
MSI (c) (80:94) [15:37:34:588]: Machine policy value 'AllowLockdownMedia' is 0
MSI (c) (80:94) [15:37:34:588]: SOURCEMGMT: Media enabled only if package is safe.
MSI (c) (80:94) [15:37:34:588]: SOURCEMGMT: Looking for sourcelist for product {02B5A17B-01BE-4BA6-95F1-1CBB46EBC76E}
MSI (c) (80:94) [15:37:34:588]: SOURCEMGMT: Adding {02B5A17B-01BE-4BA6-95F1-1CBB46EBC76E}; to potential sourcelist list (pcode;disk;relpath).
MSI (c) (80:94) [15:37:34:588]: SOURCEMGMT: Now checking product {02B5A17B-01BE-4BA6-95F1-1CBB46EBC76E}
MSI (c) (80:94) [15:37:34:588]: SOURCEMGMT: Media is enabled for product.
MSI (c) (80:94) [15:37:34:588]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (c) (80:94) [15:37:34:588]: SOURCEMGMT: Processing net source list.
MSI (c) (80:94) [15:37:34:588]: Note: 1: 1402 2: UNKNOWN\Net 3: 2
MSI (c) (80:94) [15:37:34:588]: Note: 1: 1706 2: -2147483647 3: xlconv.MSP
MSI (c) (80:94) [15:37:34:588]: SOURCEMGMT: Processing media source list.
MSI (c) (80:94) [15:37:34:588]: SOURCEMGMT: Resolved source to: 'xlconv.MSP'
MSI (c) (80:94) [15:38:06:838]: Note: 1: 1314 2: xlconv.MSP
MSI (c) (80:94) [15:38:06:838]: Unable to create a temp copy of patch 'xlconv.MSP'.
This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.
\\smsww0pri-chbs\packages$\Office2007_CompatibilityPack-12.0.6021-US-001\O12Conv.msi
MSI (c) (80:94) [15:38:06:838]: Note: 1: 1708
MSI (c) (80:94) [15:38:06:838]: Note: 1: 2729
MSI (c) (80:94) [15:38:06:838]: Note: 1: 2729
MSI (c) (80:94) [15:38:06:838]: Product: Compatibility Pack for the 2007 Office system -- Installation failed.

MSI (c) (80:94) [15:38:06:838]: MainEngineThread is returning 1635
=== Verbose logging stopped: 03.09.2009 15:38:06 ===
Posted by: turbokitty 14 years ago
6th Degree Black Belt
0
The installer for this acts really weirdly. Call out the path to the MSI and the MSP from your command line:

msiexec /i "\\smsww0pri-chbs\packages$\Office2007_CompatibilityPack-12.0.6021-US-001\O12Conv.msi" PATCH="\\smsww0pri-chbs\packages$\Office2007_CompatibilityPack-12.0.6021-US-001\O12Convsp2-en-us.msp" /qn /l*v C:\CompatPatck_Off07.log REBOOT=ReallySuppress
Posted by: abking99 14 years ago
Second Degree Blue Belt
0
But I do not have msp file with me. I have only msi given in the source. In source I get following things. This is the complete source, nothing is missing.

O12Conv.msi
O12Conv.cab
README.HTM
Catalog folder
Posted by: anonymous_9363 14 years ago
Red Belt
0
Gosh...I wonder why the install log says that it is unable to make a temporary copy of the patch file...
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