locked
Validation Failed After installing Office 2003 SP3 RRS feed

  • Question

  • Recently several of our companies computers have had hard drive crashes due to failure or infected with viruses so we are starting with a fresh XP install are reinstalling office 2003 on the machines.  They are original Microsoft CD's and they are not new copies; we have had the CD's for several years and have had no issues with them.  On one machine I installed the software, installed the Office Genuine Validation tool and opened the office programs with out any issues or errors.  As soon as I installed Office 2003 SP3 on the computer and tried opening Word I received the failed validation message.  Following are the results of the diagnostics that I ran:

    Diagnostic Report (1.9.0011.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Genuine
    Validation Code: 0

    Cached Validation Code: N/A
    Windows Product Key: *****-*****-T6DFB-Y934T-YD4YT
    Windows Product Key Hash: 3g4CZGFEDgbKmn/oB4pa2FZsssU=
    Windows Product ID: 76487-OEM-2211906-00102
    Windows Product ID Type: 2
    Windows License Type: OEM SLP
    Windows OS version: 5.1.2600.2.00010100.3.0.pro
    ID: {C7C8A77C-B099-4584-9DA9-C06FA6266A6D}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.9.40.0
    Signed By: Microsoft
    Product Name: N/A
    Architecture: N/A
    Build lab: N/A
    TTS Error: N/A
    Validation Diagnostic: 025D1FF3-230-1
    Resolution Status: N/A

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

    WGA Notifications Data-->
    Cached Result: 0
    File Exists: Yes
    Version: 1.9.40.0
    WgaTray.exe Signed By: Microsoft
    WgaLogon.dll Signed By: Microsoft

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

    OGA Data-->
    Office Status: 108 Invalid VLK
    Microsoft Office Professional Edition 2003 - 108 Invalid VLK
    OGA Version: Registered, 2.0.48.0
    Signed By: Microsoft
    Office Diagnostics: 025D1FF3-230-1_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.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>{C7C8A77C-B099-4584-9DA9-C06FA6266A6D}</UGUID><Version>1.9.0011.0</Version><OS>5.1.2600.2.00010100.3.0.pro</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-YD4YT</PKey><PID>76487-OEM-2211906-00102</PID><PIDType>2</PIDType><SID>S-1-5-21-1715567821-842925246-1801674531</SID><SYSTEM><Manufacturer>Dell Inc.</Manufacturer><Model>Latitude D830                   </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A14</Version><SMBIOSVersion major="2" minor="4"/><Date>20081211000000.000000+000</Date><SLPBIOS>Dell System,Dell Computer,Dell System,Dell System</SLPBIOS></BIOS><HWID>0AAD3A07018400FA</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification><File Name="WgaTray.exe" Version="1.9.40.0"/><File Name="WgaLogon.dll" Version="1.9.40.0"/><File Name="OGAAddin.dll" Version="2.0.48.0"/></GANotification></MachineData><Software><Office><Result>108</Result><Products><Product GUID="{90110409-6000-11D3-8CFE-0150048383C9}"><LegitResult>108</LegitResult><Name>Microsoft Office Professional Edition 2003</Name><Ver>11</Ver><Val>73EA1C85DC4E500</Val><Hash>ma2K1dTZe2Jy3YFar8dklW5F3Xw=</Hash><Pid>73931-640-3932396-57910</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="11" Result="108"/><App Id="16" Version="11" Result="108"/><App Id="18" Version="11" Result="108"/><App Id="19" Version="11" Result="108"/><App Id="1A" Version="11" Result="108"/><App Id="1B" Version="11" Result="108"/><App Id="44" Version="11" Result="108"/></Applications></Office></Software></GenuineResults> 

    Licensing Data-->
    N/A

    HWID Data-->
    N/A

    OEM Activation 1.0 Data-->
    BIOS string matches: yes
    Marker string from BIOS: 16E68:Dell Inc|16E68:Microsoft Corporation
    Marker string from OEMBIOS.DAT: Dell System,Dell Computer,Dell System,Dell System

    OEM Activation 2.0 Data-->
    N/A

     

    Friday, August 28, 2009 3:45 PM

Answers

  • Hello Jack Lauer,

    Please refer to the snippet of the mgadiag report below:

    OGA Data-->
    Office Status: 108 Invalid VLK
    Microsoft Office Professional Edition 2003 - 108 Invalid VLK

    OGA Version: Registered, 2.0.48.0
    Signed By: Microsoft
    Office Diagnostics: 025D1FF3-230-1_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005

    The report is telling us that a Volume Licensing edition of Office 2003 Pro has been installed on this computer, and that the Product Key used to do the installation is an Invalid Volume Licensing Key.  That means the product key was made with a pirating program called a Key Generator and was never issued by Microsoft, which by defintion makes this a nongenuine installation of Office.  The Office 2003 Pro installations are not properly licensed.

    Since you are using Volume Licensing (VL) media to do your installations of Office, you should ask whomever might be responsible for such activity at your company if they know if the company ever entered into a Volume Licensing Agreement with Microsoft either directly or thru a Microsoft Certified Partner Value Added Reseller (VAR).

    If there was a Volume Licensing Agreement (VLA), but it expired, then the company should talk to their Volume Licensing specialist at Microsoft to find out how to proceed.

    It is also possible that the company purchased Office licenses at retail or preinstalled on the computers (this one is a Dell), and that for reasons of expediency they have been doing installations with VL media and VL keys.  If so, the technical people should refrain from doing so in the future as this is not a supported Office deployment method and now that Office Genuine Advantage (OGA) is functioning, such a deployment method will run afoul of OGA.
    For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxp
    Friday, August 28, 2009 4:04 PM

All replies

  • Hello Jack Lauer,

    Please refer to the snippet of the mgadiag report below:

    OGA Data-->
    Office Status: 108 Invalid VLK
    Microsoft Office Professional Edition 2003 - 108 Invalid VLK

    OGA Version: Registered, 2.0.48.0
    Signed By: Microsoft
    Office Diagnostics: 025D1FF3-230-1_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005

    The report is telling us that a Volume Licensing edition of Office 2003 Pro has been installed on this computer, and that the Product Key used to do the installation is an Invalid Volume Licensing Key.  That means the product key was made with a pirating program called a Key Generator and was never issued by Microsoft, which by defintion makes this a nongenuine installation of Office.  The Office 2003 Pro installations are not properly licensed.

    Since you are using Volume Licensing (VL) media to do your installations of Office, you should ask whomever might be responsible for such activity at your company if they know if the company ever entered into a Volume Licensing Agreement with Microsoft either directly or thru a Microsoft Certified Partner Value Added Reseller (VAR).

    If there was a Volume Licensing Agreement (VLA), but it expired, then the company should talk to their Volume Licensing specialist at Microsoft to find out how to proceed.

    It is also possible that the company purchased Office licenses at retail or preinstalled on the computers (this one is a Dell), and that for reasons of expediency they have been doing installations with VL media and VL keys.  If so, the technical people should refrain from doing so in the future as this is not a supported Office deployment method and now that Office Genuine Advantage (OGA) is functioning, such a deployment method will run afoul of OGA.
    For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxp
    Friday, August 28, 2009 4:04 PM
  • I am curious why it didnt fail validation with the initial install but failed 30 minutes later when SP3 was installed?
    Friday, August 28, 2009 4:12 PM
  • Hello Jack Lauer,

    I don't know for sure.

    The initial installation of the OGA Notifications Utility in and of itself may not execute a communication with the validation servers, but because manual Updates are WGA/OGA gated, subsequent visits to Microsoft Update would by design run that installation of Office thru a validation server check.

    Just speculation--perhaps Darin Smith of MSFT may have more detailed info.
    For great advice on all topics XP, visit http://www.annoyances.org/exec/forum/winxp
    Friday, August 28, 2009 4:24 PM