none
Office 2003 not activating on imaged PC RRS feed

  • Question

  • We recently had to re-image a machine from another one on the network.  Windows and MS Project activated but Office Professional 2003 did not.  The machine is not Internet connected so we used the telephone.  All details entered ok but then it says "please confirm this is Office for Mac" which it is not. Speaking to an agent they said they couldn't pull up a product against our validation key.  So it looks like the generated validation key is incorrect.  We have done a reinstall and get the same problem.  Below are the mgadiag results:

    Thanks,

    Chris

    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Status: Genuine
    Validation Code: 0
    Cached Validation Code: N/A
    Windows Product Key: *****-*****-V742H-FMMWX-6YFK3
    Windows Product Key Hash: 4GvjBUOLVm0dzjFvQyykokNKE8U=
    Windows Product ID: 76487-OEM-2255365-20413
    Windows Product ID Type: 3
    Windows License Type: OEM System Builder
    Windows OS version: 5.1.2600.2.00010100.3.0.pro
    ID: {94A66570-D264-41BC-B0C5-9D0F9D5AFB3C}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: Registered, 1.3.254.0
    Signed By: Microsoft
    Product Name: N/A
    Architecture: N/A
    Build lab: N/A
    TTS Error: N/A
    Validation Diagnostic: 025D1FF3-230-1_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005_E2AD56EA-765-800a_E2AD56EA-766-197_E2AD56EA-148-80004005_16E0B333-89-80004005_78155E4D-232-80004005
    Resolution Status: N/A

    Vista WgaER Data-->
    ThreatID(s): N/A
    Version: N/A

    Windows XP Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    File Exists: No
    Version: N/A, hr = 0x80070002
    WgaTray.exe Signed By: N/A, hr = 0x80070002
    WgaLogon.dll Signed By: N/A, hr = 0x80070002

    OGA Notifications Data-->
    Cached Result: N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002
    OGAExec.exe Signed By: N/A, hr = 0x80070002
    OGAAddin.dll Signed By: N/A, hr = 0x80070002

    OGA Data-->
    Office Status: 101 Not Activated
    Microsoft Office Professional Edition 2003 - 101 Not Activated
    Microsoft Office Project Standard 2003 - 100 Genuine
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 7E90FEE8-198-80004005_025D1FF3-230-1_3E121E02-555-80004005_3E121E02-277-80004005_3E121E02-555-80004005_3E121E02-277-80004005

    Browser Data-->
    Proxy settings: proxy101.igs.r.mil.uk:8080
    User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Win32)
    Default Browser: C:\Program Files\Internet Explorer\iexplore.exe
    Download signed ActiveX controls: Prompt
    Download unsigned ActiveX controls: Disabled
    Run ActiveX controls and plug-ins: Allowed
    Initialize and script ActiveX controls not marked as safe: Disabled
    Allow scripting of Internet Explorer Webbrowser control: Disabled
    Active scripting: Allowed
    Script ActiveX controls marked as safe for scripting: Allowed

    File Scan Data-->

    Other data-->
    Office Details:
    <GenuineResults>
      <MachineData>
        <UGUID> {94A66570-D264-41BC-B0C5-9D0F9D5AFB3C} </UGUID>
        <Version> 1.9.0027.0 </Version>
        <OS>5.1.2600.2.00010100.3.0.pro</OS>
        <Architecture>x32</Architecture>
        <PKey>*****-*****-*****-*****-6YFK3</PKey>
        <PID>76487-OEM-2255365-20413</PID>
        <PIDType>3</PIDType>
        <SID>S-1-5-21-563212676-1771505803-1747580256</SID>
        <SYSTEM>
          <Manufacturer>INTELR</Manufacturer>
          <Model>AWRDACPI</Model>
        </SYSTEM>
        <BIOS>
          <Manufacturer>Phoenix Technologies, LTD</Manufacturer>
          <Version>6.00 PG</Version>
          <SMBIOSVersion major="2" minor="3"/><Date>20060706000000.000000+000</Date>
        </BIOS>
        <HWID>13933CE701848063</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID>
        <TimeZone>GMT Standard Time(GMT+00:00)</TimeZone>
        <iJoin>1</iJoin>
        <SBID><stat>2</stat>
          <msppid></msppid>
          <name>Kontron America</name>
          <model></model>
        </SBID>
        <OEM/><GANotification/>
      </MachineData>
      <Software>
        <Office>
          <Result>101</Result>
          <Products><Product GUID="{91110409-6000-11D3-8CFE-0150048383C9}">
            <LegitResult>101</LegitResult>
            <Name>Microsoft Office Professional Edition 2003</Name>
            <Ver>11</Ver>
            <Val>9444B8A097EA778</Val>
            <Hash>ESbW1c5JldTMCoxRxO4PgCMhnG8=</Hash>
            <Pid>70145-OEM-5795664-49505</Pid>
            <PidType>5</PidType>
          </Product>
          <Product GUID="{913A0409-6000-11D3-8CFE-0150048383C9}">
            <LegitResult>100</LegitResult>
            <Name>Microsoft Office Project Standard 2003</Name>
            <Ver>11</Ver><Val>7C0FE031816ADF8</Val>
            <Hash>MpSxNVf8MKQmizpOUhQQr2ytWe0=</Hash>
            <Pid>72076-764-1996755-55584</Pid><PidType>1</PidType>
          </Product>
          </Products>
          <Applications>
          <App Id="15" Version="11" Result="101"/>
          <App Id="16" Version="11" Result="101"/>
          <App Id="18" Version="11" Result="101"/>
          <App Id="19" Version="11" Result="101"/>
          <App Id="1A" Version="11" Result="101"/>
          <App Id="1B" Version="11" Result="101"/>
          <App Id="3A" Version="11" Result="100"/>
          <App Id="44" Version="11" Result="101"/>
          </Applications>
        </Office>
      </Software>
    </GenuineResults> 

    Licensing Data-->
    N/A

    Windows Activation Technologies-->
    N/A

    HWID Data-->
    N/A

    OEM Activation 1.0 Data-->
    BIOS string matches: no
    Marker string from BIOS: N/A
    Marker string from OEMBIOS.DAT: N/A, hr = 0x80004005

    OEM Activation 2.0 Data-->
    N/A

    Friday, July 27, 2012 10:38 AM

Answers

  • The solution was to delete the licence file, in this case:

    %AllUsersProfile%\Application Data\Microsoft\Office\Data\Opa11.dat

    And then run a repair install - Office 2003 doesn't have an option to simply change the product key, but you can repair the installation, that generates a new licence file which in turn generates a new validation ID which was accepted by the telephone activation service.

    • Marked as answer by Chris_PCSG Friday, August 3, 2012 8:47 AM
    Friday, August 3, 2012 8:46 AM

All replies

  • I'll ping someone with a lot more knowledge of Office problems than me - but you may wish to post in the specialist Office forums, rather than an XP forum.

    Either http://answers.microsoft.com/en-us/office

    or http://social.technet.microsoft.com/Forums/en/category/officeitpro

    should be able to help


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

    Friday, July 27, 2012 12:26 PM
    Moderator
  • Thanks Noel.  I've not resolved this yet although someone suggested changing the computer SID and then trying again.  I think I'll try that later today as no other answers seem to be forthcoming.

    Chris

    Tuesday, July 31, 2012 2:50 PM
  • Good luck with it - I've had no response from my contact (I may a wrong address, since my address book got mangled by a crash in WLM a few weeks back)

    I really have no clue with Office 2010, and very little with 2003 (and not much more with 2007<g>)

    I have heard it said that uninstalling, running the removal tool and then reinstalling can clear blockages in the activation process. It may be worth a try.


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

    Tuesday, July 31, 2012 3:04 PM
    Moderator
  • The solution was to delete the licence file, in this case:

    %AllUsersProfile%\Application Data\Microsoft\Office\Data\Opa11.dat

    And then run a repair install - Office 2003 doesn't have an option to simply change the product key, but you can repair the installation, that generates a new licence file which in turn generates a new validation ID which was accepted by the telephone activation service.

    • Marked as answer by Chris_PCSG Friday, August 3, 2012 8:47 AM
    Friday, August 3, 2012 8:46 AM
  • Thanks for posting that, Chris - and well done!

    Good luck.


    Noel Paton | Nil Carborundum Illegitemi | CrashFixPC | The Three-toed Sloth

    Friday, August 3, 2012 9:05 AM
    Moderator
  • Hello Chris_PCSG,

    Yes, one of the troubleshooting steps for Office 2003 activation problems is to close Office, delete the product activation .dat file and then reopen Office---Office will prompt for activation and generate a new .dat file.

    Covered in Method 2 here:  http://support.microsoft.com/kb/903275

    Unfortunately, even though your activation issue seems to have been cleared up, this particular installation of Office 2003 Professional is still nongenuine.

    Referring to:

    <Name>Microsoft Office Professional Edition 2003</Name>
            <Ver>11</Ver>
            <Val>9444B8A097EA778</Val>
            <Hash>ESbW1c5JldTMCoxRxO4PgCMhnG8=</Hash>
            <Pid>70145-OEM-5795664-49505</Pid>
            <PidType>5</PidType>

    We see that the Office 2003 Professional license in question is an OEM license, and as we all know, OEM licenses are valid only on the computer on which the license was first activated.  OEM licenses are not permitted to be moved to or activated on any other computer.  Imaging an existing installation of OEM software and then laying down that image on another computer is a violation of the OEM End User Licensing Agreement (EULA) and makes this installation of Office 2003 Professional nongenuine.

    By the way, the above OEM license restriction applies to the Windows installation, too, so this computer's installation of Windows XP Pro is nongenuine for the same reason.


    Monday, August 6, 2012 3:58 AM
  • Hi Dan,

    Perhaps you misunderstand the situation.  Each computer came with it's own licence and product key clearly displaying the microsoft genuine label as required.  Now after running for 5 years or so, these workstations have various new software installed, software updates applied including SP1,2,3, and customizations have been made.  We don't maintain image backups of every workstation but all workstations run the same software build.  So who wouldn't image an identical workstation rather than starting again from scratch in this situation?  Once the image has been applied then the destination workstation loses it activation at which point we put in that computer's genuine product key and activate the workstation.

    So then, unless I am mistaken, the workstation has been successfully recovered and there has been no contravention of the EULA.

    Many thanks,

    Chris

    Monday, August 6, 2012 7:20 AM
  • Helo Chris_PCSG,

    The siutation as described is not specifically permitted by the OEM EULA so therefore by definition it is not permitted.

    Oh, don't get me wrong, I realize that what you described is pretty common in small to midsize organizations:  they don't realize (or cannot get across to management) that to be fully compliant when using images they need to be using a Volume License, which is the only Windows Operating System and Office Application Suite license that permits imaging.  But of course VLs cost money....

    And most smaller organizations won't run into the technical problems that can develop when the same image is used for a boatload of workstations; here's an article explaining why.  http://blogs.technet.com/b/markrussinovich/archive/2009/11/03/3291024.aspx

    However, the bottom line is still this:  The Microsoft-supported method for deploying the OEM license is the OEM Preinstallation Kit (OPK) using Sysprep.

    Monday, August 6, 2012 12:55 PM