none
Software Licensing service will not start 32bit Server 2008. The system cannot find the file specified. RRS feed

  • Question

  • Hi,

    First of all apologies if this is in the wrong place but I couldn’t find a Server 2008 specific forum. I believe the Vista/2008 kernel are the same anyway.

    I have had had a good trawl around the net and tried the usual fixes but nothing has helped.

    I have been building a Server 2008 Standard 32bit SP2 Domain Controller. It was activated and working fine until this Monday when it started complaining that an unauthorised change was made to Windows.

    The error in that message is:

    Error:0xC0000022
    Description:
    (Access Denied)
    A program has requested access to an object, but has not been granted those access rights,

    After digging into this it became clear the Software Licensing service wouldn't start:

    (cmd output)

    net start slsvc
    The Software Licensing service is starting.
    The Software Licensing service could not be started.

    A system error has occurred.

    System error 2 has occurred.

    The system cannot find the file specified.


    I've looked at the announcement on this forum (Fix for ‘Software Licensing service Has Stopped’ on some Vista 64bit systems) but the registry entry for the service is ok. I have tried updating the registry with the entries in the forum announcement anyway but to no avail.

    I have rebooted several times and in safe mode but I can't get the service started.

    I have used System File Checker but it finds no error.

    I have tried unchecking the read only bit on the System32 folder as I read that would help but it hasn’t resolved it.

    I have tried renaming C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\SoftwareLicensing\tokens.dat but that has not halped.

    I have tried using slmgr.vbs but I get an accessed enied error anytime I try to run it.

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

    Cached Validation Code: N/A, hr = 0x80070426
    Windows Product Key: N/A, hr=0x80070005
    Windows Product Key Hash: N/A, hr=0x80070005
    Windows Product ID: 55041-339-8706905-76255
    Windows Product ID Type: 7
    Windows License Type: Volume KMS Server
    Windows OS version: 6.0.6002.2.00020110.2.0.007
    ID: {E9CCB6D8-7A6B-4FC6-85B5-DC4D8F8B86FE}(3)
    Is Admin: Yes
    TestCab: 0x0
    WGA Version: Registered, 1.9.9.1
    Signed By: Microsoft
    Product Name: Windows Server (R) 2008 Standard
    Architecture: 0x00000000
    Build lab: 6002.lh_sp2rtm.090410-1830
    TTS Error: M:20090929095814359-
    Validation Diagnostic:
    Resolution Status: N/A

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

    WGA 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: 100 Genuine
    Microsoft Office Access Runtime (English) 2007 - 121
    OGA Version: N/A, 0x80070002
    Signed By: N/A, hr = 0x80070002
    Office Diagnostics: 77F760FE-153-80070002_7E90FEE8-175-80070002_77F760FE-153-80070002_7E90FEE8-175-80070002_025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3

    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>{E9CCB6D8-7A6B-4FC6-85B5-DC4D8F8B86FE}</UGUID><Version>1.9.0011.0</Version><OS>6.0.6002.2.00020110.2.0.007</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-BBBBB</PKey><PID>55041-339-8706905-76255</PID><PIDType>7</PIDType><SID>S-1-5-21-353477749-1917718557-271466184</SID><SYSTEM><Manufacturer>GBT___</Manufacturer><Model>AWRDACPI</Model></SYSTEM><BIOS><Manufacturer>Award Software International, Inc.</Manufacturer><Version>F9</Version><SMBIOSVersion major="2" minor="3"/><Date>20040909000000.000000+000</Date></BIOS><HWID>72330500018400F2</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120000-001C-0409-0000-0000000FF1CE}"><LegitResult>121</LegitResult><Name>Microsoft Office Access Runtime (English) 2007</Name><Ver>12</Ver><Val>A6DF1BF2503CD6C</Val><Hash>dTTDvXHN4cR0t+IYAOhhFudJX58=</Hash><Pid>00000-694-0010114-62793</Pid><PidType>2</PidType></Product></Products><Applications/></Office></Software></GenuineResults> 

    Spsys.log Content: U1BMRwEAAAAAAQAABAAAAA8LAAAAAAAAWmICAORfS5Oe4jky1T/KARhy9171jCizkdIEkQaJZ65i+Y/IbMe7OhC08SQD9hQrFsXCi0fjJ4pmSyI9U5wIjlF0H9Oh+hJEw7XKSAShRbdDFIkWGnyD5KE+vuFyTyYX1mjkjzXhcq94m48ceJqGOPu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxypUpTYFJ/5Q9EhdGhJKYTJsbJiscvAYWgzyFZ0z79y0OKm53Bw867hHNE43WvZqUI0Rf1MqA3D5sWfEw7WeNfzOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeu2XislzXqsoVoBQJ89ToT2j5BL1uBwljfNYgT2WqQ5CdRdB/TofoSRMO1ykgEoUW3KFQUY9f++QzlsIQBgIJFQtZo5I814XKveJuPHHiahjj7tVLwe28YiH1BLYCERqYZDkmvhBlGHDl+f1L5AB51ccqVKU2BSf+UPRIXRoSSmEybGyYrHLwGFoM8hWdM+/ctDipudwcPOu4RzRON1r2alCNEX9TKgNw+bFnxMO1njX8zkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGHL3XvWMKLOR0gSRBolnrtl4rJc16rKFaAUCfPU6E9ocVcKXK38aEebvY6RhZLGtUXQf06H6EkTDtcpIBKFFt5Bnx4AKjfCQ+lpAQwcFlOrWaOSPNeFyr3ibjxx4moY4+7VS8HtvGIh9QS2AhEamGQ5Jr4QZRhw5fn9S+QAedXHKlSlNgUn/lD0SF0aEkphMmxsmKxy8BhaDPIVnTPv3LQ4qbncHDzruEc0Tjda9mpQjRF/UyoDcPmxZ8TDtZ41/M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDBhy9171jCizkdIEkQaJZ67G2Eji4spE0PC7NCtAVf0sdZ6vSPcQpFI0ai6tF/hGtVF0H9Oh+hJEw7XKSAShRbeHBP+QlaSbigRK2XXlGhjk1mjkjzXhcq94m48ceJqGOPu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxypUpTYFJ/5Q9EhdGhJKYTJsbJiscvAYWgzyFZ0z79y0OKm53Bw867hHNE43WvZqUI0Rf1MqA3D5sWfEw7WeNfzOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeuDyoEKm++je5XXSzXBydtpw/vTWcAivkR90aWiBzHWZ1RdB/TofoSRMO1ykgEoUW31ZxcV36IvtrKWXGZ0lMx8dZo5I814XKveJuPHHiahjj7tVLwe28YiH1BLYCERqYZDkmvhBlGHDl+f1L5AB51ccqVKU2BSf+UPRIXRoSSmEybGyYrHLwGFoM8hWdM+/ctDipudwcPOu4RzRON1r2alCNEX9TKgNw+bFnxMO1njX8zkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGHL3XvWMKLOR0gSRBolnrj+JMdgySmSqtVijh6bx94PWOSW0aNcyify7NOAKHCLpUXQf06H6EkTDtcpIBKFFt1fNe5vwbkFxAgg87pTYuhHWaOSPNeFyr3ibjxx4moY4+7VS8HtvGIh9QS2AhEamGQ5Jr4QZRhw5fn9S+QAedXHKlSlNgUn/lD0SF0aEkphMmxsmKxy8BhaDPIVnTPv3LQ4qbncHDzruEc0Tjda9mpQjRF/UyoDcPmxZ8TDtZ41/M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDBhy9171jCizkdIEkQaJZ66VntI5D5eh3sPkGHSKiQVLmvHbhqiFeBUjv7NXE0wOdVF0H9Oh+hJEw7XKSAShRbcykuP5xAmUC6lLsFhwNuY21mjkjzXhcq94m48ceJqGOPu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxypUpTYFJ/5Q9EhdGhJKYTJsbJiscvAYWgzyFZ0z79y0OKm53Bw867hHNE43WvZqUI0Rf1MqA3D5sWfEw7WeNfzOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeuxthI4uLKRNDwuzQrQFX9LJC6gJJ3AIJAFRec26dvvBFRdB/TofoSRMO1ykgEoUW3GJe+vPjlMUv2ZTM70XRxA9Zo5I814XKveJuPHHiahjj7tVLwe28YiH1BLYCERqYZDkmvhBlGHDl+f1L5AB51ccqVKU2BSf+UPRIXRoSSmEybGyYrHLwGFoM8hWdM+/ctDipudwcPOu4RzRON1r2alCNEX9TKgNw+bFnxMO1njX8zkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGHL3XvWMKLOR0gSRBolnrqsQm+V55+JpnFBiPLj+TzKrr0saQ2aw/ZzcEPS5iNdAUXQf06H6EkTDtcpIBKFFty3PYdus3ew5/RCPDB/Vnl/WaOSPNeFyr3ibjxx4moY4+7VS8HtvGIh9QS2AhEamGQ5Jr4QZRhw5fn9S+QAedXHKlSlNgUn/lD0SF0aEkphMmxsmKxy8BhaDPIVnTPv3LQ4qbncHDzruEc0Tjda9mpQjRF/UyoDcPmxZ8TDtZ41/M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDBhy9171jCizkdIEkQaJZ67ZeKyXNeqyhWgFAnz1OhPaPv5fX8X0l2UiJwkot2r9L1F0H9Oh+hJEw7XKSAShRbcnP3DLNlzBLUNYHSYO3HBO1mjkjzXhcq94m48ceJqGOPu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxypUpTYFJ/5Q9EhdGhJKYTJsbJiscvAYWgzyFZ0z79y0OKm53Bw867hHNE43WvZqUI0Rf1MqA3D5sWfEw7WeNfzOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeu2XislzXqsoVoBQJ89ToT2hfdGg6b13R7QSK7yBvkUdJRdB/TofoSRMO1ykgEoUW3XNtWzbHsvh7Cqipgc/gEwdZo5I814XKveJuPHHiahjj7tVLwe28YiH1BLYCERqYZDkmvhBlGHDl+f1L5AB51ccqVKU2BSf+UPRIXRoSSmEybGyYrHLwGFoM8hWdM+/ctDipudwcPOu4RzRON1r2alCNEX9TKgNw+bFnxMO1njX8zkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGHL3XvWMKLOR0gSRBolnrj0BopUbM9ZyCA/aKTB1XDy0izEGW233/yR/+0o+UwfvUXQf06H6EkTDtcpIBKFFtyItQlgbzQGMYch0JedWNWzWaOSPNeFyr3ibjxx4moY4+7VS8HtvGIh9QS2AhEamGQ5Jr4QZRhw5fn9S+QAedXHKlSlNgUn/lD0SF0aEkphMmxsmKxy8BhaDPIVnTPv3LQ4qbncHDzruEc0Tjda9mpQjRF/UyoDcPmxZ8TDtZ41/M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDBhy9171jCizkdIEkQaJZ66QdWLpmzaXLrCpXtHN25TGgU7+SgxxZFGp+8nZeuT4hVF0H9Oh+hJEw7XKSAShRbceC10ZoS3oC/ZsQRWs5Z0U1mjkjzXhcq94m48ceJqGOPu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxypUpTYFJ/5Q9EhdGhJKYTJsbJiscvAYWgzyFZ0z79y0OKm53Bw867hHNE43WvZqUI0Rf1MqA3D5sWfEw7WeNfzOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeuqxCb5Xnn4mmcUGI8uP5PMhgQAJeSd/3a0OeRECUm/jpRdB/TofoSRMO1ykgEoUW3x5OtC0mtHNV2HSzQ3MPhNdZo5I814XKveJuPHHiahjj7tVLwe28YiH1BLYCERqYZDkmvhBlGHDl+f1L5AB51ccqVKU2BSf+UPRIXRoSSmEybGyYrHLwGFoM8hWdM+/ctDipudwcPOu4RzRON1r2alCNEX9TKgNw+bFnxMO1njX8zkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGHL3XvWMKLOR0gSRBolnrpWe0jkPl6Hew+QYdIqJBUsCqn7VG2SW1Rclj3NoSceNUXQf06H6EkTDtcpIBKFFt58FoFPMxjedHjrDTsC4sg/WaOSPNeFyr3ibjxx4moY4+7VS8HtvGIh9QS2AhEamGQ5Jr4QZRhw5fn9S+QAedXHKlSlNgUn/lD0SF0aEkphMmxsmKxy8BhaDPIVnTPv3LQ4qbncHDzruEc0Tjda9mpQjRF/UyoDcPmxZ8TDtZ41/M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDBhy9171jCizkdIEkQaJZ66rEJvleefiaZxQYjy4/k8ypxgUAkvAoCBp1mFaF8+E+VF0H9Oh+hJEw7XKSAShRbe9ugbs2aYOW2QbRWGtYw3A1mjkjzXhcq94m48ceJqGOPu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxypUpTYFJ/5Q9EhdGhJKYTJsbJiscvAYWgzyFZ0z79y0OKm53Bw867hHNE43WvZqUI0Rf1MqA3D5sWfEw7WeNfzOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeue3LJ8TKbSKC9Cs1j1VLxm7Ao06ybQhg2z0OHUOQtAXdRdB/TofoSRMO1ykgEoUW3AMGPevSfbyKNFyJbaAv4vdZo5I814XKveJuPHHiahjj7tVLwe28YiH1BLYCERqYZDkmvhBlGHDl+f1L5AB51ccqVKU2BSf+UPRIXRoSSmEybGyYrHLwGFoM8hWdM+/ctDipudwcPOu4RzRON1r2alCNEX9TKgNw+bFnxMO1njX8zkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGHL3XvWMKLOR0gSRBolnrpWe0jkPl6Hew+QYdIqJBUsdwy8Pp4V4as0ccUz+IU6uUXQf06H6EkTDtcpIBKFFt2uzsEqzxRcZulFoIBWsEDLWaOSPNeFyr3ibjxx4moY4+7VS8HtvGIh9QS2AhEamGQ5Jr4QZRhw5fn9S+QAedXHKlSlNgUn/lD0SF0aEkphMmxsmKxy8BhaDPIVnTPv3LQ4qbncHDzruEc0Tjda9mpQjRF/UyoDcPmxZ8TDtZ41/M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDBhy9171jCizkdIEkQaJZ64PKgQqb76N7lddLNcHJ22n4wpQ6aSBMSRjeLdZQgcsllF0H9Oh+hJEw7XKSAShRbcp5aIjJJgHkWG5iBzO4DZq1mjkjzXhcq94m48ceJqGOPu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxypUpTYFJ/5Q9EhdGhJKYTJsbJiscvAYWgzyFZ0z79y0OKm53Bw867hHNE43WvZqUI0Rf1MqA3D5sWfEw7WeNfzOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwYcvde9Ywos5HSBJEGiWeu2XislzXqsoVoBQJ89ToT2nV0Kq0CfuRfDV8UqlAy20lRdB/TofoSRMO1ykgEoUW3HuMhmb+CWH17nTUMUqMB19Zo5I814XKveJuPHHiahjj7tVLwe28YiH1BLYCERqYZDkmvhBlGHDl+f1L5AB51ccqVKU2BSf+UPRIXRoSSmEybGyYrHLwGFoM8hWdM+/ctDipudwcPOu4RzRON1r2alCNEX9TKgNw+bFnxMO1njX8zkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMGHL3XvWMKLOR0gSRBolnrqsQm+V55+JpnFBiPLj+TzKqgkSG4NSxmtCCSO9xknK5UXQf06H6EkTDtcpIBKFFt+yY9rWkWXd9tk3BBEcmJmzWaOSPNeFyr3ibjxx4moY4+7VS8HtvGIh9QS2AhEamGQ5Jr4QZRhw5fn9S+QAedXHKlSlNgUn/lD0SF0aEkphMmxsmKxy8BhaDPIVnTPv3LQ4qbncHDzruEc0Tjda9mpQjRF/UyoDcPmxZ8TDtZ41/M5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDBhy9171jCizkdIEkQaJZ67o/noG/tJT9DA6DpalePoSg6toZ/WuHB525+EEF92F/lF0H9Oh+hJEw7XKSAShRbcT3jUi/aRoc/0Uh2svbTI01mjkjzXhcq94m48ceJqGOPu1UvB7bxiIfUEtgIRGphkOSa+EGUYcOX5/UvkAHnVxypUpTYFJ/5Q9EhdGhJKYTJsbJiscvAYWgzyFZ0z79y0OKm53Bw867hHNE43WvZqUI0Rf1MqA3D5sWfEw7WeNfzOQ1ifb1stzrqx+w3WNaAwzkNYn29bLc66sfsN1jWgMM5DWJ9vWy3OurH7DdY1oDDOQ1ifb1stzrqx+w3WNaAw=

    Licensing Data-->
    Software Licensing service is not running.

    HWID Data-->
    HWID Hash Current: MAAAAAEAAgABAAEAAgABAAAAAQABAAEAJJQ8uPL9rHDixwKhYhqUfv6szuMOxJbF

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes, but no SLIC table
    Windows marker version: N/A
    OEMID and OEMTableID Consistent: N/A
    BIOS Information:
      ACPI Table Name OEMID Value OEMTableID Value
      APIC   GBT     AWRDACPI
      FACP   GBT     AWRDACPI


    Has anyone got any ideas about this?

    I'm wondering what the 'The system cannot find the file specified' message means. The service has a path to the exe as C:\Windows\system32\SLsvc.exe which is the correct path. so I can't see how that can be the file it can't find.

    Does anyone have a definitive list of the files / registry entries that SLsvc needs?

    Wednesday, September 30, 2009 2:13 PM

Answers

  • Hello armibewob,


     Your issue is not a Software Licensing Service has Stopped (and won't restart) issue. 

    In the Reg Fix steps in the Announcement, it first give 3 criteria to know if you have the SLS has stopped issue. your Diagnostic Report does not fit the third criteria.

    C) Diagnostic Report Does Not show any numbers after line "TTS Error:"
     

    'TTS Error' means "Tamper Time Stamp Error" and the one showing in your Diagnostic Report starts with an "M" which means your Vista is suffering from a Mod-Auth Tamper and not an SL Service has stopped issue. (This is why the Reg Fix did not work for you)

    Note the Software Licensing Service does stop (by design) when it encounters a Tamper. So when there is a Tamper event, a TTS Error is created and the SL Service is supposed to stop and the issue is usually a Mod-Auth Tamper.  But if there is no tamper event (and as such, no TTS Error in the Diagnostic Report) and the SL Service Stops (and won't restart), then that is a Software Licensing Service has Stopped (and won't restart) issue.

    Please see the below information regarding this type of Mod-Auth Tamper:

    Vista is in, what we call a 'Mod-Auth' Tamper state.  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 caused by a running program that is incompatible with Vista.

     

      Because there is No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, we know that your issue is an 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 Vista does not allow, which by definition, means it is incompatible with Vista.

    NOTE: We have seen an increase in this type of issue and we believe it is unlikely that software writers are still making programs that are incompatible with Vista. Instead, we believe that a majority of the issues are being caused by Malware that are doing the same things (on purpose) as incompatible programs do (by accident).

     

      In addition to why a Mod-Auth occurs, it's also important to understand how Vista detects a Mod-Auth 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 Mod-Auth  State and it could take some time for the Mod-Auth to be detected. The important point to note is that the moment Vista detects the Mod-Auth, you know that the program that is causing the Mod-Auth, 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:
    2009       09        29             0958                 14359-

     

    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 09/29 

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

    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 09/28/2009, 09/27/2009 and 09/26/2009  (or around the date the issue first occurred)

      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 at some time in the past, but didn’t run it till now, 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.

     

    Note: Since everyone has different programs installed on their computer, it is extremely hard for support to figure out what program is causing the problem, but if you still need assistance in identifying the Incompatible Program, please create a no cost support request at http://go.microsoft.com/fwlink/?linkid=52029

    Also Note: it has been found that Malware, such as Viruses and Trojans, can also be incompatible with Vista and can cause an In Memory Mod-Auth. A number of users (that were experiencing your same issue) have confirmed that a Malware infection was the cause. If you follow the above steps and cannot find a program that is causing the Mod-Auth, you may want to investigate if a Virus, Worm or Trojan may be to blame. You can contact PC Safety, which is a Microsoft group, which provides free assistance with Malware infections. I encourage you to use the ‘Windows Live Safety Scan for Windows Vista’ (http://onecare.live.com/site/en-us/center/whatsnew.htm) before contacting PC Safety.

    PC Safety:

    http://www.microsoft.com/protect/support/default.mspx

    http://onecare.live.com/site/en-us/center/whatsnew.htm

    Thank you,
    Darin MS
    • Marked as answer by Darin Smith MS Wednesday, September 30, 2009 6:49 PM
    Wednesday, September 30, 2009 6:47 PM

All replies

  • Hello armibewob,


     Your issue is not a Software Licensing Service has Stopped (and won't restart) issue. 

    In the Reg Fix steps in the Announcement, it first give 3 criteria to know if you have the SLS has stopped issue. your Diagnostic Report does not fit the third criteria.

    C) Diagnostic Report Does Not show any numbers after line "TTS Error:"
     

    'TTS Error' means "Tamper Time Stamp Error" and the one showing in your Diagnostic Report starts with an "M" which means your Vista is suffering from a Mod-Auth Tamper and not an SL Service has stopped issue. (This is why the Reg Fix did not work for you)

    Note the Software Licensing Service does stop (by design) when it encounters a Tamper. So when there is a Tamper event, a TTS Error is created and the SL Service is supposed to stop and the issue is usually a Mod-Auth Tamper.  But if there is no tamper event (and as such, no TTS Error in the Diagnostic Report) and the SL Service Stops (and won't restart), then that is a Software Licensing Service has Stopped (and won't restart) issue.

    Please see the below information regarding this type of Mod-Auth Tamper:

    Vista is in, what we call a 'Mod-Auth' Tamper state.  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 caused by a running program that is incompatible with Vista.

     

      Because there is No Mismatched files listed under the "File Scan Data-->" line of your Diagnostic Report, we know that your issue is an 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 Vista does not allow, which by definition, means it is incompatible with Vista.

    NOTE: We have seen an increase in this type of issue and we believe it is unlikely that software writers are still making programs that are incompatible with Vista. Instead, we believe that a majority of the issues are being caused by Malware that are doing the same things (on purpose) as incompatible programs do (by accident).

     

      In addition to why a Mod-Auth occurs, it's also important to understand how Vista detects a Mod-Auth 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 Mod-Auth  State and it could take some time for the Mod-Auth to be detected. The important point to note is that the moment Vista detects the Mod-Auth, you know that the program that is causing the Mod-Auth, 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:
    2009       09        29             0958                 14359-

     

    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 09/29 

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

    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 09/28/2009, 09/27/2009 and 09/26/2009  (or around the date the issue first occurred)

      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 at some time in the past, but didn’t run it till now, 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.

     

    Note: Since everyone has different programs installed on their computer, it is extremely hard for support to figure out what program is causing the problem, but if you still need assistance in identifying the Incompatible Program, please create a no cost support request at http://go.microsoft.com/fwlink/?linkid=52029

    Also Note: it has been found that Malware, such as Viruses and Trojans, can also be incompatible with Vista and can cause an In Memory Mod-Auth. A number of users (that were experiencing your same issue) have confirmed that a Malware infection was the cause. If you follow the above steps and cannot find a program that is causing the Mod-Auth, you may want to investigate if a Virus, Worm or Trojan may be to blame. You can contact PC Safety, which is a Microsoft group, which provides free assistance with Malware infections. I encourage you to use the ‘Windows Live Safety Scan for Windows Vista’ (http://onecare.live.com/site/en-us/center/whatsnew.htm) before contacting PC Safety.

    PC Safety:

    http://www.microsoft.com/protect/support/default.mspx

    http://onecare.live.com/site/en-us/center/whatsnew.htm

    Thank you,
    Darin MS
    • Marked as answer by Darin Smith MS Wednesday, September 30, 2009 6:49 PM
    Wednesday, September 30, 2009 6:47 PM
  • Thankyou that is very helpful!

    I had a copy of Kaspersky AntiVirus 6 on the server at the time which was stopping the system booting so i removed it. I belive that would be the cause of the problem.

    If I have sucessfully removed the offending software I assume the error won't go away until the Tmaper detction process runs again? is there a way to force oit to run manually?

    Thanks
    Thursday, October 1, 2009 12:12 PM
  • Hello Armibewob,

     Reboot Vista, if the program that was causing the problem has been removed, the Mod-Auth error would not show after a reboot.

    Thank you,
    Darin MS
    Thursday, October 1, 2009 6:56 PM
  • I'm still having some trouble with this. After removing all ptoential problem software and rebooting the TS Error reamins the same.

    Would you expect the TTS timestamp to update each time the offending profcess is detected?
    Friday, October 2, 2009 6:55 AM
  • Hi,

    Just in case anyone else is having this problem I ended up calling MS support who talked me through tracking down and fixing some corrupt registry entries. The version of Kaspersky I had installed was not fully compatible with Server 2008 and had damaged the installation. MS Support were very helpful and fixed the problem quickly.

    Thanks

    Gareth

    Solar Panel Installers - Hestia Solar
    Friday, March 25, 2011 8:48 AM