locked
Server 2008 - Error RRS feed

  • Question

  • Hi,

     

    I've been running a Windows Server 2008 box for about 2 months now (RC1), and today when I logged in started getting the WGA errors, which have reached the point where I cannot do anything on the server.  I was able to find that this morning, a 'UMBus Emulator' driver was installed, however, my other 2008 RC1 box has this installed without any issues.  I was able to get the Diagnostic Report to run, and the results are below - any help is much appreciated!

     

     

    Diagnostic Report (1.7.0069.0):
    -----------------------------------------
    WGA Data-->
    Validation Status: Invalid License
    Validation Code: 50
    Online Validation Code: 0xc004d401
    Cached Validation Code: N/A, hr = 0xc004d401
    Windows Product Key: *****-*****-H463V-674D2-8JFKY
    Windows Product Key Hash: uLs101D2935w9oWBB+oeEAxLgOQ=
    Windows Product ID: 78440-033-0683632-70022
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.0.6001.2.00030112.1.0.004
    CSVLK Server: N/A
    CSVLK PID: N/A
    ID: {FC814051-0C8A-45B2-ADDD-C551522EB403}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.7.59.1
    Signed By: Microsoft
    Product Name: Windows Server (R) 2008 Enterprise
    Architecture: 0x00000000
    Build lab: 6001.longhorn_rc1.071121-2029
    TTS Error: K:20080307105441901-M:20080307030243707-
    Validation Diagnostic:
    Resolution Status: N/A

    WgaER Data-->
    ThreatID(s): N/A, hr = 0x80070002
    Version: N/A, hr = 0x80070002

    Notifications Data-->
    Cached Result: N/A
    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 Data-->
    Office Status: 100 Genuine
    OGA Version: Registered, 1.6.28.0
    Signed By: Microsoft
    Office Diagnostics: 7E90FEE8-198-80004005_025D1FF3-282-80041010_025D1FF3-170-80041010_025D1FF3-171-1_025D1FF3-434-80040154_025D1FF3-178-80040154_025D1FF3-179-2_025D1FF3-185-80070002_025D1FF3-199-3

    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 7.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>{FC814051-0C8A-45B2-ADDD-C551522EB403}</UGUID><Version>1.7.0069.0</Version><OS>6.0.6001.2.00030112.1.0.004</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-8JFKY</PKey><PID>78440-033-0683632-70022</PID><PIDType>5</PIDType><SID>S-1-5-21-791824755-2134645194-79488667</SID><SYSTEM><Manufacturer>MICRO-STAR INTERNATIONAL CO., LTD</Manufacturer><Model>MS-7125</Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies, LTD</Manufacturer><Version>6.00 PG</Version><SMBIOSVersion major="2" minor="3"/><Date>20060522000000.000000+000</Date></BIOS><HWID>4AD73007018400F6</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central Standard Time(GMT-06:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><BRT/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120000-110D-0000-0000-0000000FF1CE}"><LegitResult>121</LegitResult><Name>Microsoft Office SharePoint Server 2007</Name><Ver>12</Ver><Val>6F1A82FDC8AEDA8</Val><Hash>p+nFoRJJ2PN3oYaPqN26YyzMG+8=</Hash><Pid>89462-724-0000016-59287</Pid><PidType>0</PidType></Product></Products></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAO2ymwcAAAAAWmICAAQAuIX0izUBMoDIARhy9171jCizkdIEkQaJZ64GpoMA1qKSEy1s7wmpcJHKFoP8EVSquxJcd0l03P99BBQjdPDwDinTfkQXASERseEf/YQ/1o9+2sd/nK/a1vgsk/oA/SfEX6ot/bnNmgLA1vu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxypUpTYFJ/5Q9EhdGhJKYTJsbJiscvAYWgzyFZ0z79y2BX7mQ2Q7393z5XQ50VXv9mhrKhq4UIi+PwtGQfjOGIjOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=

     

    Thanks,
    Chris

    Friday, March 7, 2008 6:42 PM

Answers

  • Hello chrisbandr,

     

      My expertise is with Vista and I have had very little experiance with Server 2008. But if the information presented in the Diagnostic Report from a Server 2008 means the same as one from a Vista computer, then it would appear that your Server is experiencing an In Memory Mod-Auth tamper.

     

    (NOTE: the below information is targeted to Vista, so specific steps may not be applicable to Server 2008, but the underlying methodology should still be valid in helping resolve the issue)

       

    There are 2 types of Mod-Auth tampers.

     

    1) A critical system file was modified On Disk - What this means is that the file, located on the hard drive, was modified in some way. This can be caused by a malicious program (spyware, malware, virus) or by manual file modification (by a user of the system). There is also a very small chance that an Update may fail in mid-update and cause this type of issue. As a safety mechanism, Updates are made so that if they fail, they roll back any updating that was done before the failure, but there is an off-chance that the roll back did not occur.

     

    2) A critical system file was modified In Memory - What this means is the file itself (on the hard drive) is un-modified, but the code, from that file, running in the system, was modified in some way. and is usually caused by a running program that is incompatible with Vista.

     

    Because there are No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, your issue is a In Memory Mod-Auth and therefore caused by an incompatible program. This means there is a program install and Running that is trying to access parts of the OS that the OS does not allow which, by definition, means it is incompatible with the OS.

     

    In addition to why a Tamper occurs, it's also important to understand how Vista detects the Tamper event. There is a Service that runs in Vista that detects a Tamper to a Critical System file. But this Service runs randomly, so if you were to install an incompatible program and run it, Vista (most likely) would not immediately enter a Tamper State and it could take some time for the Tamper to be detected. The important point to note is that the moment Vista detects the Tamper, you know that the program that caused the tamper, is currently running.

     

    Below I have provided a number of steps to help you identify the program that is causing the tamper:
     
      First, go to
    http://support.microsoft.com/kb/931699/ and confirm that you do not have any of the programs known to cause this type of issue.
     
      Second, in your Diagnostic report above, you can see the line that starts with 'TTS Error:' followed by a bunch numbers: M:xxxxxxxxxxxxxxxxx- This is the Tamper Time Stamp and it breaks down like this:

     

        (year)  (month) (day) (time in 24format) (millisecond)
    M:2008       03           07            0302                   43707-

     

    Note, I also see a "K" type Tamper Time Stamp. The “K“ stands for Kernel Mode tamper. This is a minor tamper and is most likey directly related to the Mod-Auth tamper. Once you remove the program that is causing the Mod-Auth tamper, I believe that the Kernel mode tamper will stop as well .


    Now that you know the time of the tamper, you can now try to connect that time with a program.

    1) Login to Vista and select the option that launches an Internet Browser

    2) Type into the browser address bar: %windir%\system32\perfmon.msc and hit Enter

    3) When asked if you want to Open or Save this file, select Open

    4) In the left hand panel, click Reliability Monitor

    5) Click on the “System Stability Chart” above the date 03/07 

    6) Below the chart, in the “System Stability Report” section look at the report titled "Software (Un)Installs for 03/07/2008 "

    7) Look for any program that shows "Application Install" in the 'Activity' column.

    8) Since the process that detects Tampers runs randomly, it can take up to 3 days for the process to detect the tamper and set Vista to a Tamper State. Because of this, please repeat steps 5) thru 7) for the dates 03/06/2008, 03/05/2008 and 03/04/2008 

     

      This could tell you what programs were installed on or around the Tamper date and should help you narrow down the possible programs that could be causing the issue . Unfortunately, if you installed the program (say) on 09/01/2007, but you didn't run (and, hence, prompted the tamper state)  till 03/07/2008 , this process may not be helpful.  The removal of any application you may have installed recently could go a long way to troubleshooting this issues as well since it may fall outside of the 3 day time frame described above.

      Just to reiterate: The important point to note is that the moment Vista detects the Tamper, you know that the program that caused the tamper, is currently running.

     

    You may also want to post your issue in the Server 2008 forums at http://forums.microsoft.com/TechNet/default.aspx?ForumGroupID=161&SiteID=17 or got to http://support.microsoft.com for additional support options and resources.

     

    Thank you,

    Darin Smith

    WGA Forum Manager

    Wednesday, March 12, 2008 8:35 PM