Results 1 to 3 of 3
  1. #1
    Star Lounger
    Join Date
    Jan 2001
    Location
    Wilmington, NC
    Posts
    52
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Windows Installer error on XPSP1(Win2K Server SP3)

    I'm walking through an administrative installation of Office XP on a W2KSP3 Server administrative share point. I haven't deployed it yet, and am attempting to install the Office Service Packs before doing so. I downloaded and ran the Windows Installer 2.0 per Microsofts instructions, but when running the Service Pack update from the command line the install log file gives DEBUG Error 2746 transform 1tto1u invalid for package WINNTinstaller90e860e.msi expected product (blah), found product (blah). I've searched this and the Windows forum, as well as MS Knowledge Base, but no joy.
    Any ideas much appreciated.
    Mark

  2. Get our unique weekly Newsletter with tips and techniques, how to's and critical updates on Windows 7, Windows 8, Windows XP, Firefox, Internet Explorer, Google, etc. Join our 480,000 subscribers!

    Excel 2013: The Missing Manual

    + Get this BONUS — free!

    Get the most of Excel! Learn about new features, basics of creating a new spreadsheet and using the infamous Ribbon in the first chapter of Excel 2013: The Missing Manual - Subscribe and download Chapter 1 for free!

  3. #2
    New Lounger balbright's Avatar
    Join Date
    Nov 2001
    Posts
    13
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Windows Installer error on XPSP1(Win2K Server SP3)

    Mark,
    I looked at my log file for the installation Office 2000 Excel admin update finally (See post (190874)).. I am having the same Debug Error 2746. I will let you know if I find out anything.


    Berri

  4. #3
    Star Lounger
    Join Date
    Jan 2001
    Location
    Wilmington, NC
    Posts
    52
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Windows Installer error on XPSP1(Win2K Server SP3)

    Hi Berri,
    Thanks for the note. One of the message lines indicated that the Windows Installer(?) product it found had a higher (and therefore presumably more recent version number) than that of the version it was expecting. My current guess is that this resulted from .NET framework having been previously installed on the same server. I'm going to have to wipe the server for other reasons, so probably will not be able to follow this up to much, and hope to not replicate the problem when I get to that point in the re-install!
    Mark

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •