Database Error 2725
here. Post Reply Print view Search Advanced search 24 posts 1 2 Next epohl Posts: 35 Joined: Tue Nov 28, 2006 10:18 am Error 2725 during Installation Quote Postby epohl » Tue Dec 12, 2006 3:47 pm So in doing a test installation I'm getting the following error message in the "Validating Install" portion: "The installer has encountered an unexpected error installing the package. This may indicate a problem with this package. The error code is 2725." The installer log (and Google) tell me that error 2725 means "Invalid database tables", but that's maddeningly short of the information I need. Does that refer to tables in the database that I'm installing? If so, which ones? Any help anyone might be able to provide would be greatly appreciated. I can supply the installer log or excerpts thereof if needed. Thanks, Eric Top MichaelNesmith Posts: 3452 Joined: Thu Dec 22, 2005 7:17 pm Contact: Contact MichaelNesmith Website Quote Postby MichaelNesmith » Tue Dec 12, 2006 5:43 pm That's odd, at a minimum we'll probably need your setup, and information on your test system to troubleshoot the error. This will require a support ticket as the process will be research intensive. Try to weak your setup and see what lines in your MSIcode script cause this problem. If you can pinpoint the issue, then a support ticket won't be required, if I can isolate the problem as an issue in InstallAware itself. Michael Nesmith InstallAware Home of The Next Generation MSI Installer Get your free copy today - http://www.installaware.com/ Top epohl Posts: 35 Joined: Tue Nov 28, 2006 10:18 am Quote Postby epohl » Wed Dec 13, 2006 8:44 am Thanks for the quick response. Is there a good way pinpoint the problem other than temporarily removing installer tasks until it works? Install the logger plugin that gets mentioned from time to time? Sorry for what are probably basic questions but I'm fairly new at the whole installer thing. Thanks, Eric Top MichaelNesmith Posts: 3452 Joined: Thu Dec 22, 2005 7:17 pm Contact: Contact MichaelNesmith Website Quote Postby MichaelNesmith » Wed Dec 13, 2006 11:30 am I'm afraid not, Eric. Despite the tediousness, it w
Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ "Error 2725: Invalid database tables" error while uninstalling a patch We use wix installer 3.0 to build MSIs and MSPs. We have the product installed with msi and has a bunch of patches (MSPs) installed on it. We build the latest patch and installed on the top of that. Installing works fine and the product also http://www.installaware.com/forums/viewtopic.php?t=1580 works fine. The problem is that we can't uninstall that patch. It gives the error "Error 2725: Invalid database tables". We confirmed that uninstalling worked fine for the previous patches. The command I am using to uninstall the patch is (first GUID is the product GUID and 2nd is the patch GUID) the following. http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/quot-Error-2725-Invalid-database-tables-quot-error-while-uninstalling-a-patch-td5637050.html Same command works fine for the earlier patches. Msiexec /I {E793D01E-8222-4f65-A718-2A94891A0E46} MSIPATCHREMOVE={B4025760-B524-4B4F-BFAA-EE5941F55F18} /qb /norestart /l*vx uninstall_patch.log Can someone help me? Thanks. -Pramodh. The related log is: MSI (s) (0C:1C) [13:22:51:678]: Note: 1: 2262 2: MsiPatchHeaders 3: -2147287038 MSI (s) (0C:1C) [13:22:51:678]: Note: 1: 2262 2: Patch 3: -2147287038 MSI (s) (0C:1C) [13:22:51:678]: Note: 1: 2262 2: MsiPatchHeaders 3: -2147287038 MSI (s) (0C:1C) [13:22:51:678]: Note: 1: 2205 2: 3: MsiAssembly MSI (s) (0C:1C) [13:22:51:678]: Note: 1: 2228 2: 3: MsiAssembly 4: SELECT `MsiAssembly`.`Attributes`, `MsiAssembly`.`File_Application`, `MsiAssembly`.`File_Manifest`, `Component`.`KeyPath` FROM `MsiAssembly`, `Component` WHERE `MsiAssembly`.`Component_` = `Component`.`Component` AND `MsiAssembly`.`Component_` = ? MSI (s) (0C:1C) [13:22:51:678]: Transforming table Component. MSI (s) (0C:1C) [13:22:51:678]: Note: 1: 2262 2: Component 3: -2147287038 MSI (s) (0C:1C) [13:22:51:678]: Transforming table Component. MSI (s) (0C:1C) [13:22:51:678]: Note: 1: 2262 2: Component 3: -2147287038 MSI (s) (0C:1C) [13:22:51:678]: Transforming table Component. MSI (s) (0C:1C) [13:22:51:678]: Note: 1: 2262 2: Component 3: -2147287038 MSI (s) (0C:1C) [13:22:51:678]: Transforming table Component. MSI (s) (0C:1C) [13:22:51
on SQL ServerWhere is this place located?All Places SAP on SQL Server 17 Replies Latest reply: Feb 27, 2015 12:57 PM by Bhupal Kotla Database compression on SAP BW using MSCOMPRESS Thomas Kjelsrud Sep 15, 2010 3:24 PM Currently Being Moderated Hi.We have tried out https://scn.sap.com/thread/1784828 the brand new DB compression tool from SAP, MSSCOMPRESS, on our BW Sandbox system running on Windows Server 2008 and MS SQL Server 2008. Information on the tool can be found in note 1459005 - Enabling index compression for SQL Server and 1488135 - Database compression for SQL Server.It reduced the DB size from 145 GB to 43 GB, so we are please with that side of the story. On the other database error side, it turns out that our BW consultant is unable to get any useful information out of the system. We performed a page compression on both data and indexes. Having a look at a cube after the compression, we get a lot of "Dimension XYZ is not posted in InfoCube" warning messages. Has anyone encountered this issue with the new MSSCOMPRESS tool? I am aware that the tool has only been available for database error 2725 a few days, but I am sure we are not the first to try it out.Any input would be of interest.Kind Regards,Thomas 7165Views Re: Database compression on SAP BW using MSCOMPRESS Leslie Moser Sep 15, 2010 7:34 PM (in response to Thomas Kjelsrud) Currently Being Moderated Hello Thomas,I work with the team that wrote this report. Can you please open a customer message in BW-SYS-DB-MSS? We would very much like to investigate this.___________________________Leslie MoserDeveloper, Microsoft Platforms U.S.Netweaver Development ToolsSAP Labs, LLC Alert Moderator Like (0) Re: Database compression on SAP BW using MSCOMPRESS Thomas Kjelsrud Sep 20, 2010 12:40 PM (in response to Leslie Moser) Currently Being Moderated Hi.It turns out that the issue was related to an inorrect state of the BW sandbox system before the compression was started. The result were therefore not reliable.We did the compression in the development system instead, and here everything works as intented. The db savings are mindblowing, from approx. 300 GB to 67 GB. We have also tried it out in our ERP Sandbox which is a pretty recent system copy from production, and we went from 2,1 TB to 466 GB. Impressive! Good work, you guys!One thing:One batch prosess for all tables used about 84 hours to complete, which is way too much time.Therefore we are planni