Debug Error 2749 Transform
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20132010Other VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Installation of this package failed (Service Pack 2 for Microsoft Office Web Apps (KB2687470) 64-bit edition SharePoint > SharePoint 2010 - Setup, Upgrade, Administration and Operations Question 0 Sign in to vote Hi there, On my SharePoint 2010 server I have Office Web Apps 2010 installed (NOT Microsoft Office). When I try to install OWA SP2 (KB2687470) I get this error: --- Logs show some errors atC:\Users\ext.magryan\AppData\Local\Temp\3\Wac Server Setup(2014062009365223A0).log Search "error" (32 hits in 1 files) C:\Users\ext.magryan\AppData\Local\Temp\3\Wac Server Setup(2014062009365223A0).log (32 hits) Line 352: MSI(INFO): 'DEBUG: Error 2749: Transform 9011410409100014.0.6025.1000 invalid for package C:\Windows\Installer\8d4dd82a.msi. Expected product version == 14.0.6025.1000, found product version 14.0.4763.1000.' Line 354: MSI(INFO): 'DEBUG: Error 2749: Transform 9011410409100014.0.6012.1000 invalid for package C:\Windows\Installer\8d4dd82a.msi. Expected product version == 14.0.6012.1000, found product version 14.0.4763.1000.' Line 356: MSI(INFO): 'DEBUG: Error 2749: Transform 9011410409100014.0.6014.1000 invalid for package C:\Windows\Installer\8d4dd82a.msi. Expected product version == 14.0.6014.1000, found product version 14.0.4763.1000.' Line 358: MSI(INFO): 'DEBUG: Error 2749: Transform 9011410409100014.0.6027.1000 invalid for package C:\Windows\Installer\8d4dd82a.msi. Expected product version == 14.0.6027.1000, found product version 14.0.4763.1000.' Line 360: MSI(INFO): 'DEBUG: Error 2749: Transform 9011410409100014.0.6022.1000 invalid for package C:\Windows\Installer\8d4dd82a.msi. Expected product version == 14.0.6022.1000, found product version 14.0.4763.1000.' Line 362: MSI(INFO): 'DEBUG: Error 2749: Transform 9011410409100014.0.6015.1000 invalid for package C:\Windows\Installer\8d4dd82a.msi. Expected product version == 14.0.6015.1000, found product version 14.0.4763.1000.' Line 403: MSI(ACTIONSTART): 'Action 9:36:56: SetSupportErrorTextRetail. ' Line 404: MSI(INFO): 'Action start 9:36:56: SetSupportErrorTextRetail.' Line 405: MSI(INFO): 'Action ended 9:36:56: SetSupportErrorTextRetail. Return value 1.' Line 406: MSI(ACTIONSTART): 'Action 9:36:56: SetSupportErrorTextRetail_PERMISSION. ' Line 407: MSI(INFO): 'Action
on and reload this page. All Places > Business > Endpoint Security > VirusScan Enterprise > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. 4 Replies Latest reply on Jan 21, 2015 4:34 AM by yulasinio VSE 8.8 P4 install enforced every time by the client task yulasinio Jan 13, 2015 9:24 AM We recently updated the virus scan from P2 to P4 and the upgrade went fine on both server and clients, or that's what we thought.Yesterday when I was doing some https://social.technet.microsoft.com/Forums/office/en-US/dd088fc5-8cd4-4f6d-b7de-77ceb37d69e4/installation-of-this-package-failed-service-pack-2-for-microsoft-office-web-apps-kb2687470-64bit?forum=sharepointadminprevious other troubleshooting I noticed some events from MsiInstaller in the EventViewer log. On a closer look I find out that VSE was trying to install, found this strange because I had the correct version. 8.8.0.1247. Scrolling more I've see that this was happening at certain times, 12:00 AM and PM which lead me to check the ePO client task.We have a https://community.mcafee.com/thread/76608?start=0&tstart=0 client task that runs every 12h on each system and install a number of products if they are missing e.g HIPS, SAE, VSE, DLP etc. I've checked that the correct version of VSE was added in the task and it is.Now, why is this happening? Would McAfee agent not verify the versions and skip the install if it's the same?Below is an extract from the log file found on my machine: MSI (s) (CC:38) [15:02:11:594]: Looking for patch transform: Patch1ToPatch4 DEBUG: Error 2749: Transform Patch1ToPatch4 invalid for package C:\WINDOWS\Installer\13da242.msi. Expected product version == 8.8.01000, found product version 8.8.04001. MSI (s) (CC:38) [15:02:11:595]: Skipping validation for patch transform #Patch1ToPatch4. Will not apply because previous transform was invalid MSI (s) (CC:38) [15:02:11:595]: Looking for patch transform: Patch2ToPatch4 1: 2749 2: Patch1ToPatch4 3: C:\WINDOWS\Installer\13da242.msi 4: 8.8.01000 5: 8.8.04001 DEBUG: Error 2749: Transform Patch2ToPatch4 invalid for package C:\WINDOWS\Installer\13da242.msi. Expected product version == 8.8.02004, found product version 8.8.04001. MSI (s) (CC:38) [15:02:11:595]: Skipping validation for patch transform #Patch2ToPatch4. Will not apply because previous transform was invalid MSI (s) (CC:38) [15:02:11:595]: Looking for patch transform: Patch3ToPatch4
do I love patching? Let me count the ways... I have a product developed internally. There are three versions of this product that have been deployed: v1.1.0, v1.1.1, and now v1.2.0. https://community.flexerasoftware.com/archive/index.php?t-114526.html Each of these installs was built using IS 7.0.3, MSI 2.0 basic MSI project. http://www.itninja.com/question/what-does-this-msi-error-mean In order to create the succeeding installs (v1.1.1 and v1.2.0), I started with the previous version's install, changed the version and package code information, grabbed the latest version of the 1 file that changed, and built a new MSI. I am now trying to build a patch for 1.2.0 that will encompass 1.1.0 and debug error 1.1.1. I had numerous Warning (11) and Warning (12) errors in the original patch build; however, thanks to the other developers in the IS Community here I was able to clear them up and my patch builds "pristine" with no errors in the build process. The end of my worries, right? I installed v1.1.1 on to my test machine, full install, clean machine. I then ran the debug error 2749 patch using msiexec /p... and got no visible errors. When I checked the msi log file, it listed the following section with an error: MSI (c) (CC:E4): Looking for storage transform: v110ToUpgraded00 MSI (c) (CC:E4): Validating transform 'v110ToUpgraded00' with validation bits 0x922 MSI (c) (CC:E4): Note: 1: 2749 2: v110ToUpgraded00 3: C:\WINDOWS\Installer\4df4611.msi 4: 1.01.0000 5: 1.02.0000 MSI (c) (CC:E4): 1: 2749 2: v110ToUpgraded00 3: C:\WINDOWS\Installer\4df4611.msi 4: 1.01.0000 5: 1.02.0000 MSI (c) (CC:E4): Note: 1: 2729 DEBUG: Error 2749: Transform v110ToUpgraded00 invalid for package C:\WINDOWS\Installer\4df4611.msi. Expected product version == 1.01.0000, found product version 1.02.0000. I ran the product (just in case) and sure enough, it was still the version I had installed (v1.1.1) not my patched version. I ran the patch install a second time, using the exact same patch file and the exact same command line string (with the exception of the output log file, which I changed in order to capture a different picture for comparison). Again, no errors were visible during the install of the patch; however, I noticed it ran considerably longer than the first run. And, lo and behold, when I ran the product after this second run of the patch, it was the new version (
helpful is this to you? Average Rating 5 97624 views 07/26/2006 Windows Installer (MSI) Windows Installer (MSI) Error Messages Troubleshooting appdeploy-faqs Microsoft Windows Installer The errors returned by the Windows Installer service are unique to MSI setups, each one providing some level of help to specify a problem, check each below for details. Answer Summary: This open question is a holding place for the answer below which provides links to a page detailing each of the internal errors you may encounter when working with Windows Installer. TextThis open question is a holding place for the answer below which provides links to a page detailing each of the internal errors you may encounter when working with Windows Installer.Save summary Cancel 0 Comments [ + ] Show Comments Comments This content is currently hidden from public view. Reason: Member has been banned from the site For more information, visit our FAQ's. This content is currently hidden from public view. Reason: Member has been banned from the site For more information, visit our FAQ's. This content is currently hidden from public view. Reason: Member has been banned from the site For more information, visit our FAQ's. 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 7 -2147287038: %1 could not be found. 13: The data is invalid. 120: This function is not available for this platform. It is only availabl... 258: The wait operation timed out. 1101: Could not open file stream: [2]. System error: [3] 1155: File [1] not found 1259: This error code only occurs when using Windows Installer version 2.0... 1301: Cannot create the file '[2]'. A directory with this name already exis... 1302: Please insert the disk: [2] 1303: The Installer has insufficient privileges to access this directory: ... 1304: Error writing to File: [2] 1305: Error reading from File: [2]; System error code: [3] 1306: The file '[2]' is in use. If you can,