[installation-issues] [Issue 103111] Error #1330 aborts instal ling OOo 3.1.0 on XP Pro SP2
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=103111 --- Additional comments from echos...@openoffice.org Tue Jul 21 04:54:23 + 2009 --- Created an attachment (id=63660) OOo Setup.exe parameter overrides MS WinVerifyTrust func - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@installation.openoffice.org For additional commands, e-mail: issues-h...@installation.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[installation-issues] [Issue 103111] Error #1330 aborts instal ling OOo 3.1.0 on XP Pro SP2
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=103111 --- Additional comments from echos...@openoffice.org Tue Jul 21 03:56:18 + 2009 --- The problem is, incredibly, a service defect within the Microsoft function WinVerifyTrust. (It shows up for Windows version 5.1 build 2600.xpsp_sp2_rtm.040803-2158: Service Pack 2, which presumably must be older than the known working build xpsp_sp2_qfe.070227-2300 identified in a Heath Stewart blog at MSDN). My proposed solution is to provide a custom parameter to OOo Setup.exe (such as, /trusted) to enable a Microsoft flag which, according to MSDN, the function WinVerifyTrust subfunction MsiGetFileSignatureInformation uses to decide whether the result is reported as a fatal error or a warning that can be ignored. Scan the OOo setup component's final Windows source code for "MsiGetFileSignatureInformation" and if present then this solution should work. Alternatively, perhaps the proposed OOo Setup.exe /trusted parameter can be used to override the default action by deleting the cabinet entry in the MsiDigitalSignature table. http://msdn2.microsoft.com/en-us/library/aa370121(VS.85).aspxdetails MsiGetFileSignatureInformation function "Remarks When requesting only the certificate context, an invalid hash in the digital signature does not cause MsiGetFileSignatureInformation to return a fatal error. To return a fatal error for an invalid hash, set the MSI_INVALID_HASH_IS_FATAL flag in the dwFlags parameter. The certificate context and hash information is extracted from the file by a call to WinVerifyTrust. The ppcCertContext parameter is a duplicate of the signer certificate context from the signature. It is the responsibility of the caller to call CertFreeCertificateContext to free the certificate context when finished. Note that MsiGetFileSignatureInformation requires the presence of the Wintrust.dll file on the system." - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@installation.openoffice.org For additional commands, e-mail: issues-h...@installation.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[installation-issues] [Issue 103111] Error #1330 aborts instal ling OOo 3.1.0 on XP Pro SP2
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=103111 --- Additional comments from echos...@openoffice.org Mon Jun 29 09:29:47 + 2009 --- Correction: I could try installing not the same DEV300m50 but a newer development release to see if the newer "OOO-DEV.cab" file produces error #1330. Overall, this issue should be affecting many other XP Pro SP2 users but apparently it isn't. That tends to argue in favor of a localized MSI database problem. Perhaps my Windows REGISTRY database is being used by MSI to install digital signatures for the OOo cab files. I don't know this yet. But if it is then an export of the branches for a working OOo v3.1 could be imported into my XP to enable me to install OOo v3.1. That would confirm the true location of the defect: either local to my system or else in the OOo installation code. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@installation.openoffice.org For additional commands, e-mail: issues-h...@installation.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[installation-issues] [Issue 103111] Error #1330 aborts instal ling OOo 3.1.0 on XP Pro SP2
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=103111 --- Additional comments from echos...@openoffice.org Mon Jun 29 08:10:43 + 2009 --- There is one other possibility: if the msi installer maintains a database of previously installed cab files and keeps a persistent digital signature for each. I had not installed the "OOO-DEV.cab" previously. If this is the ultimate source of the problem then there should not be any difference revealed in the handling behaviour for the two cab files: openofficeorg1.cab and the newer development "OOO-DEV.cab". Regardless, I have a correctly installed OOo v3.2 now from the DEV300m50 build 9406. I am happy now but still concerned about the future releases exhibiting the same defect. I may try to re-install the same DEV300m50 and see if it fails to install after the successful first install. That would localize the defective handling to just my MSI installation so I could re-install MSI or update it. I am not yet aware of any updated MSI v3.1 that you indicated. The MS KnowledgeBase indicated I have the most up-to-date for XP Pro SP2. Perhaps you are getting yours from a different source. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@installation.openoffice.org For additional commands, e-mail: issues-h...@installation.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[installation-issues] [Issue 103111] Error #1330 aborts instal ling OOo 3.1.0 on XP Pro SP2
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=103111 --- Additional comments from echos...@openoffice.org Mon Jun 29 07:26:11 + 2009 --- I don't think it is related to msi. My msiexec version is 3.1.4000.1823 but I have the 3.1 (v2) installed which the MS KnowledgeBase shows "Note: Only the binary for the Msi.dll file is updated. The version number is 3.1.4000.2435. All other binaries of the Windows Installer 3.1 (v2) package remained unchanged and are version 3.1.4000.1823". I can activate logging for the msi and then attempt to install OOo v3.1 as a last resort. * But the defect location is now easily isolated with the info I supplied in the attachment for DEV300m50 build 9406. The reason is the install script for OOo v3.1 with JRE failed for both cab files but now for DEV300m50 it fails for only one cab file. The defective cab file handling for Data1.cab was evidently unchanged. However the defective cab file handling for openofficeorg1.cab was changed into a correct handling behavior for "OOO-DEV.cab" (can't remember the exact cab name here). That is the solution. It must be discernable from comparing the two install scripts (scp2 code) for OOo which I have not done. (I don't have the code for the scripts to compare them.) My XP system is stable and I have not experienced this defect before. This new behavior proves it is not directly related to msi -- the defect must be in the OOo installation script which later becomes platform specific to msi. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@installation.openoffice.org For additional commands, e-mail: issues-h...@installation.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[installation-issues] [Issue 103111] Error #1330 aborts instal ling OOo 3.1.0 on XP Pro SP2
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=103111 --- Additional comments from echos...@openoffice.org Sat Jun 27 07:27:07 + 2009 --- Created an attachment (id=63242) Partial correction to this issue found with DEV300m50 build 9406 - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@installation.openoffice.org For additional commands, e-mail: issues-h...@installation.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[installation-issues] [Issue 103111] Error #1330 aborts instal ling OOo 3.1.0 on XP Pro SP2
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=103111 Issue #|103111 Summary|Error #1330 aborts installing OOo 3.1.0 on XP Pro SP2 Component|Installation Version|OOO310m11 Platform|PC URL| OS/Version|Windows XP Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|DEFECT Priority|P2 Subcomponent|code Assigned to|of Reported by|echosoft --- Additional comments from echos...@openoffice.org Thu Jun 25 23:19:55 + 2009 --- Error message #1330 aborts installing OOo 3.1.0 (build OOO310_m11) with or without JRE on XP Pro version 2002 (Service Pack 2). Downloads have valid MD5. Prior OOo version 3.0.1 installs correctly for this Dell 533 MHz Intel Celeron PC having 256 MB of RAM. I disabled firewall and virus/spy protection before running the downloaded executable(s) or the extracted setup.exe installer from drive E:. I selected a custom install simply to specify my non-default path is to E: (Fat32) hard drive instead of C: (NTFS). (Same defect problem occurs regardless of whether I specify the default complete install to/from desktop; or whether I change my user organization data; or I choose to install for all users or not.) 1) Installation Wizard aborts with error message #1330 when almost finished. STATUS: "Copying new files" DIALOG TITLE: "OpenOffice.org 3.1 Installation Wizard" (normal text): "Error 1330: A file that is required cannot be installed because the cabinet file E:\oo 3.1.0\Install310\openoffice1.cab has an invalid digital signature. This may indicate that the cabinet file is corrupt." 2) Installer reverts to its initial state (except that my previously installed OOo version 3.0.1 remains extracted but uninstalled). This item merely shows it is a controlled abort although not 100% satisfactory. STATUS: "Rolling back action" DIALOG TITLE: "OpenOffice.org 3.1 Installation Wizard" (bold text): "Installation Wizard Completed" (normal text): "The wizard was interrupted before OpenOffice.org 3.1 could be completely installed. Your system has not been modified. To complete installation at another time, please run setup again. Click Finish to exit the wizard." md5sum.exe shows identical valid MD5: 7bc4c7cba1753aa4fa26b68630dc955a OOo_3.1.0_Win32Intel_install_en-US.exe The installer reports error #1330 for: openofficeorg1.cab md5sum.exe shows identical valid MD5: 88b6edeb5df6d6bc63bc63ce4d4910af OOo_3.1.0_Win32Intel_install_wJRE_en-US.exe The installer reports two error #1330's for: 1st: Data1.cab (Java Runtime Environment JRE-1.6-013) 2nd: openofficeorg1.cab - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@installation.openoffice.org For additional commands, e-mail: issues-h...@installation.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
