none
Could not connect to the System Event Notification Service (SENS) issue on several Windows 7 SP1 systems

    Question

  • Hi All,

    In our pilot group of 15 or so Windows 7 desktops we are experiencing a strange issue I would appreciate your input on:

    In a random fashion, most systems will eventually show us a blue screen at logon (not a bsod b.t.w.) that mentions: "Could not connect to the System Event Notification Service". At this moment further loggin on is not possible; in fact the only remedy seems to be to hard shutdown the system & then after reboot all will be well, for a few days.

    I've been doing a bit of investigation; on three systems I have been able to pin down a consistent set of error messages in the system log at the time of the issue that mention that a number ofservices have unexpectedly ended. (event ID 7031) The services are:

    ·         Group Policy Client service

    ·         IP-Helper service

    ·         Server service

    ·         Multimedia class service

    ·         User Profile service

    ·         Task Scheduler service

    ·         SENS (de welbekende: System Event Notification Service)

    ·         Shell hardware detection service

    ·         Themes service

    ·         WMI service

    I noticed almost all these services rely on RPC to run (except for the Themes service unfortunately).

     

    I have checked the domain controllers: no issues there: nice & clean eventlogs.

    The machines all run based on the same image. Unfortunately the issue is not reproducable (so far); it often takes a number of days to return. I have been told that people feel that 'loggin on quickly'  seems to make the problem appear more often.

    Any suggestions of what might be causing this, and maybe some ideas about what tests to do to confirm the issue or how to investigate further?

    [PWE 10/4/2012] :  This issue was resolved, scroll to the end of this thread to read the details


    Regards, Paul www.servercare.nl

    Friday, June 17, 2011 2:13 PM

Answers

  • Hi Nick,

    I'm not running SP1 but beside that I think I'm in the same situation.

    1. I've AppV client in our build. As you can see in the visual services trace the service sftlist.exe is taking a really long time to start when I get the SENS error. I don't now exactly if this is the cause or if this is the symptom. I even think the SENS error is not the real problem but a symptom.

    2. I don't think I've modified SSLF security settings applied.

    Like you I don't have the LASsrv waring but I do have the Event 1000 for the Lanmanserver service. <guess> And if that one doesn't work something with network connectivity won't start. If that doens't start AppV (Softgrid/SFT) isn't able to load and  the sftlist.exe tries this over and over again </guess>

    Faulting application name: svchost.exe_LanmanServer, version: 6.1.7600.16385, time stamp: 0x4a5bc100 Faulting module name: SSCORE.DLL, version: 6.1.7600.16385, time stamp: 0x4a5bc540 Exception code: 0xc0000005 Fault offset: 0x00001607 Faulting process id: 0x3c0 Faulting application start time: 0x01cd010ebb40fb53 Faulting application path: C:\Windows\system32\svchost.exe Faulting module path: C:\Windows\system32\SSCORE.DLL Report Id: 0d8d3a1c-6d02-11e1-ab2c-2c27d73458c2

    http://support.microsoft.com/kb/2316513 (About Lanmanserver service not able to start and something about PATH variables, I'll compare PATH variables on a working installation and a faulty one).

    http://support.microsoft.com/kb/2590550 (About SSCORE.DLL errors and black/blue backgrounds, I do get those sometime after the SENS error). In this link there is a mention about:

    "You may experience this issue after you install certain applications, for example Microsoft Application Virtualization Client, on the computer. "


    Tuesday, March 20, 2012 7:40 AM

All replies

  • Hi,

     

    This issue can be caused by the some GP extention. The third-party programs and additional Microsoft services that install client-side extensions register those components in the GPExtension.

     

    Please go to gp to see if some applications or service extention is causing error.

     

    If so, please take permission to delete the related registry key under gp extention.

     

    Before you modify the registry, please make a backup for your registry first, you can refer to the following link:

    http://windows.microsoft.com/en-us/windows7/Back-up-the-registry

     

    Please login safe mode with local admin and check the registry key under HKLM\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon\GPExtensions to delete it.

     

    Reference:

     

    Identifying Group Policy Client-Side Extensions

     

    Regards,

     

    Sabrina

     

    TechNet Subscriber Support in forum.

     

    If you have any feedback on our support, please contact tngfb@microsoft.com


    This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Edited by Sabrina Shen Tuesday, June 21, 2011 4:48 AM
    • Marked as answer by Sabrina Shen Wednesday, June 29, 2011 2:32 AM
    • Unmarked as answer by Paul Weterings Tuesday, January 17, 2012 10:06 AM
    Monday, June 20, 2011 5:20 AM
  • Hi Sabrina,

     

    Thanks for picking this up. Do you have some background information that tells me a bit more about what this registry key does? I've tried to bing it (and google as well ;-) but could not really find much more info. (besides what appears to be ancient 2000 info)

     

    thanks!

     


    Regards, Paul www.servercare.nl
    Monday, June 20, 2011 10:12 AM
  • Hi,

     

    Sorry for not clarifying it. I have edited my previous post.

     

    Regards,

     

    Sabrina

     

    TechNet Subscriber Support in forum.

     

    If you have any feedback on our support, please contact tngfb@microsoft.com


    This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Tuesday, June 21, 2011 4:50 AM
  • Hi, 

     

    I was wondering how everything is going. If anything is unclear, please let me know. It is my pleasure to be of assistance. 

     

    Regards, 

    Sabrina

    TechNet Subscriber Support in forum.

     

    If you have any feedback on our support, please contact tngfb@microsoft.com


    This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Thursday, June 23, 2011 2:25 AM
  • Thanks Sabrina,

     

    I have asked one of our technicians to modify one of the systems that seem affected. Unfortunately the problem only occurs sporadically, so we'll have to give it a few weeks..

     


    Regards, Paul www.servercare.nl
    Thursday, June 23, 2011 7:03 AM
  • Did you find any solution to this problem ?

    Thursday, September 22, 2011 1:40 PM
  • Sorry for the late reply Andreas.

     

    No, we still have the issue. Unfortunately Sabrina's suggestion did not fix it.


    Regards, Paul www.servercare.nl
    • Proposed as answer by Alaa88 Friday, November 25, 2011 11:38 PM
    Wednesday, November 02, 2011 3:39 PM
  • Solve the problem of Could not connect to the System Event Notification Service
    Run the following commands and see if it helps
    Login to Vista as Administrator
    a. Click on Start and in the search bar type “cmd.exe” (without quotes).
    b. Right click on cmd.exe and click on Run as Administrator.
    c. In the command prompt type the following commands and press Ente
    Netsh winsock reset
    Exit Command Prompt and restart the computer
    Friday, November 25, 2011 11:39 PM
  • Hi Alaa88

     

    That was the first thing we googled, unfortunately it didn't fix the issue. Still investigating...


    Regards, Paul www.servercare.nl
    Friday, November 25, 2011 11:42 PM
  • Hi Paul,

     

    Are you deploying Printers to your domain through Preference Policy?

    If yes it may be that one security group where you are targeting a printer  may be part of Members and Member Of which will create a loop and kill the SENS service.

     

    Monday, January 09, 2012 10:33 AM
  • Hi 1338,

    Thanks for responding, sorry for my late reply (been on vacation). Yes, we actually do use that.

    I've asked one of our guys to look into your theory & see if we might have such loops.

    I'll post back of course if this turns out to be the case!

     

     


    Regards, Paul www.servercare.nl
    Tuesday, January 17, 2012 10:05 AM
  • did you find a resolution for this? seeing similar problems.
    Wednesday, February 15, 2012 8:32 PM
  • Nope, we still have the problem

    Regards, Paul www.servercare.nl

    Wednesday, February 15, 2012 8:35 PM
  • are you using SEP?
    Wednesday, February 15, 2012 9:01 PM
  • SEP?

    Regards, Paul www.servercare.nl

    Wednesday, February 15, 2012 9:03 PM
  • sorry. Symantec endpoint protection
    Wednesday, February 15, 2012 9:18 PM
  • Hi all,

    we seem to be experiencing the same issue. We are also in a pilot where we roll out W7 SP1 and getting several users which occasionally get this error. A reboot solves this issue. I did find several links referring to a netsh winsock reset, updating audio drivers, deleting logs etc. But none seem to work. We do use Endpoint Encryption by McAfee as to vern9898 last remark. Has anyone found a solution to this issue?

    Friday, February 24, 2012 9:59 AM
  • Hi Paul

    I am experiencing the exact same issue in my company. It's driving me up the wall. We are rolling out Windows 7 - and when a user logs on the desktop appearance is different , and the error appears from the notification area. A reboot fixes the issue  but I cannot replicate the issue. A user could be using the pc for a few weeks , and then one day the message will appear.  To confirm , I am rolling out Windows 7 Enterprsise 32bit.


    Can I also say , this is happening on newly imaged pcs. I use a scripted install - so each pc gets Windows 7 installed at the file level.
    Monday, February 27, 2012 10:44 AM
  • I am the guy Paul talks to about settings in our environment.

    To answer an older question about the use of SEP, we use Forefront Client Security (FCS).

    Also, we deploy our 64bit Windows 7 Entperise clients using SCCM 2007 R3.

    Domain Controllers are 2008 R2 SP1 almost fully patched (SCCM client sometimes takes a while before it sees new updates, even after a forced cycle). Domain and Forest run 2008 level.

    Tuesday, February 28, 2012 3:57 PM
  • We are now also experiencing this issue on our desktops, which have no Endpoint Encryption. The problem seems to spread. We logged an incident with MS, hopefully they will come up with a solution.

    Next to the SENS error we are now also getting : The service User Profile Service prohibits the logon. The RPC failed and did not execute.

    In some cases we noticed that waiting 5-10 minutes and try to logon again that a logon is than successful.

    Friday, March 02, 2012 8:21 AM
  • The "The service User Profile Service prohibits the logon. The RPC failed and did not execute" is that a displayed error or one in the event log? I haven't seen that one here yet.

    Friday, March 02, 2012 9:04 AM
  • Its roughly translated from Dutch, but its a displayed error when trying to logon. (prohibits or prevents).

    A reboot / cold boot still always solves the issue.

    Friday, March 02, 2012 9:07 AM
  • When I logged on this morning I has the SENS error again, and upoon checking my event logs I do see a message about the User Profile Service-service. And a bunch of others, which will all retry to restart the service in 120000 or 60000 milliseconds.

    They all unexpectably stopped.

    To give an idea of the time it takes all in all (translating from Dutch to English in most cases):

    9:49:37 3191 Application Virtualization Client: Clientlogfile (path to sftlog.txt) initialised

    9:49:47 45056 LsaSrv: Logon cache was disabled. Intermittent authentication failures may result during periods of network latency or interrupts. Please contact your system administrator.

    9:50:05 20604: MOM failed to monitor memory usage of the MOM process. Error value: 0x800706BE

    9:50:05 3057: The Application Virtualization Client Core initialized correctly.

    9:50:12 7031: All of the services mentioned by Paul Weterings terminated unexpectedly, and will restart in 120000 or 60000 milliseconds

    9:50:15 6004 and 6003 warnings. Message is either "The winlogon notification subscriber <Profiles> was unavailable to handle a critical notification event." (6003) or can't handle a critical notification event (6004). The same goes for <GPClient>.

    From 9:50:28 till 9:50:33 this goes on a few more times for <GPClient>.

    After this I get back to the logon screen, where I turn the computer off and on again.
    Upon the reboot I can login fine.

    The only warning that troubles me then is the "45056 LsaSrv: Logon cache was disabled. Intermittent authentication failures may result during periods of network latency or interrupts. Please contact your system administrator."

    Friday, March 02, 2012 9:41 AM
  • We do have the same messages in the event logs all stating:

    All of the <service> terminated unexpectedly and will restart in 120000 or 60000 milliseconds

    Friday, March 02, 2012 10:23 AM
  • Would it make sense to compare the RSOP information of a system having issues from Tom & René & Fergieman?

    Since the three of us seem to have a similar issue, lets see what we can do to find a similar cause?

    Since the issue always seems to occur at logon, my gut feeling sais it's group policy related (as Sabrina's initial response also indicates). Maybe we can pinpoint a GPO setting we have in common. Or test systems with the GPO's removed.

    What do you think?


    Regards, Paul www.servercare.nl

    Friday, March 02, 2012 10:42 AM
  • Sounds alright to me. I will get working on it.

    The test system with all GPO's removed. Do you mean simply placing them in a OU with block inheritance, or really a new installed system with it's computer account placed in the OU with block inheritance before the deployment?

    I ask this since removing GPO's isn't the same as actually getting rid of them.

    Friday, March 02, 2012 10:48 AM
  • Thanks Tom,

    If you want to you can zip the info up & E-Mail it to me. It kind of depends if René & Fergieman are 'in' also ;-) (otherwise there's not much to compare ;-)

    I can zip it all up & send the combined info back to you guys & we can do some investigating...


    Regards, Paul www.servercare.nl

    Friday, March 02, 2012 11:02 AM
  • I will send you the email with the attachement now.

    Friday, March 02, 2012 11:15 AM
  • I'll get on it as well. But will be beginning of next week. Thank you for taking the time Paul. Hopefully something will show up from the collected information.
    Friday, March 02, 2012 1:10 PM
  • Quick question....is anyone appling old policies created with AD2003 ?

    Monday, March 05, 2012 1:08 PM
  • Last year we went to a completely new AD structure when we migrated to Windows 7.
    The AD was already at 2008, and all new OU's have GPO's on them made during the migration project.

    I am doubting slightly about the Default Domain Policy though. It may be a copy of the old one, which I think it is, but I am not 100% sure anymore.

    Our current Default Domain Policy doesn't hold a lot of settings. Most of them are split in Computer/User GPO's set on the Desktops and Mobiles OU's, and Users OU GPO.
    Monday, March 05, 2012 1:21 PM
  • This fixed my problem!  Thanks a lot.
    Wednesday, March 07, 2012 6:08 PM
  • This fixed my problem!  Thanks a lot.
    What did you do?
    Wednesday, March 07, 2012 8:19 PM
  • Info send to your mail account mentioned on your website Paul.
    Thursday, March 08, 2012 10:03 AM
  • Thanks Gents, I have received Tom & René's RSOP's now, still waiting on Fergieman's. Once I have them all I'll send a zipfile to you guys containing the lot.


    Regards, Paul www.servercare.nl

    Thursday, March 08, 2012 10:07 AM
  • I just read through this conversation as I have had this problem for the past few months on my Home PC. It seems to be happening permanently now every time I log on. It is a nuisance as I logon as the Administrator so everyone else in the family has to use my account as well. I really would like to solve the problem but am not a techie although I am not a complete computer novice. I have tried resetting the Winsock and that did work but now seems to have stopped doing so.

    I realise I am somewhat out of my league in this forum but if anyone can give me some straightforward guidance to solve this I would be immensely grateful. 

    Sunday, March 11, 2012 6:14 PM
  • I do have the exact same issue, so I won't describe everything again. We are currently running Windows 7 (without SP1 afaik), most of the Windows 7 systems are configured to connect to a Virtual Desktop Environment. On those systems I've never experienced the SENS error.

    Besides these 'Thin Clients' we have about 40 laptops and some other Rich Clients. On about 10 systems we've had the SENS error, but not on a regular bases. I'm creating a new installation for 15 new computers, on these systems the SENS error occurs a lot, but isn't predictable or reproducible.  For example, I wanted to make a boot trace using xbootmgr and restarted 3 systems over and over again without getting the SENS error. At one point I decided these systems won't give the SENS error, I shutdown the computer, placed it at a users desk, booted the system and there the SENS error popped again.

    As someone else already mentioned, it looks like it has something to do with 'logging in to fast'. Winlogon is already there, but services on which a successful domain logon depends aren't started yet.

    I checked my groups and Group Policies. I've reinstalled several machines using WDS with different settings including:

    > Removing partitions of the old installation
    > Removing the computer object from AD before reinstalling
    > Unjoin and Rejoin the Domain.
    > Removed some 'suspicious'/legacy group policies

    Next step for me:

    Install new system using my WDS 'task sequence'. This sequence places the new computer objects in our Desktops OU, I think I'll change it to the default buildin Computers OU. And manually place/add the computer object in the appropriate OU, carefully documenting when it goes wrong..

    Last but not least

    I've created a batch script (the name script is an overstatement) doing the netsh winsock reset on computer shutdown, using gpedic.msc. It helps a bit, I think. Or I instructed the users of the new systems really well.. (Wait until the disk activity light stops flashing).

    System information of the systems on which the error occurs most:

    • Windows 7
    • using Windows Deployment Services
      In the WDS task sequence I'm doing a Windows Update after the sequence is done
      (but I'll take about 4 reboots before all updates are installed. First update is an update of Windows Update (maybe it has to do with that?)
      In the WDS task sequence I'm installing Symantec EndPoint Protection 12, but I've had the SENS error with EndPoint Protection 11 also)
    • HP 6200 Small Form Factor, ATI Videocard (DVI/DisplayPort).
    • Windows Defender is disabled
    • Afaik I don't have 'weird' GPO's
    • My EventLog looks like the one Tom Heusink posted except 45056 LsaSrv, I've (most of the time) a svchost_LanManServer failure on an unknown module..

    Because most of the people reacting in this thread are Dutch, it shouldn't have anything to do with being Dutch?


    Tuesday, March 13, 2012 10:25 AM
  • Thanks for your contribution Harm-Jan! I have just sent our combined RSOP's to the people who sent them to me, so we can check what may be in common. Some of them are pretty big though, so this may end up to be quite a task.

    Harm-Jan is staring to do some elimination of possible causes, which is good. It would be nice if someone could set up a system in an OU where  hardly any group policies are applied. This woulod give us something to test with.

    Another thing is: how do we succesfully test the issue?; as many people have stated; it doesn't seem to occur all the time. 

    b.t.w. May Dutch people in this conversation... coincidence?

    René, you logged the issue with Microsoft; any news on that one yet?


    Regards, Paul www.servercare.nl

    Wednesday, March 14, 2012 8:13 AM
  • Settings up the OU isn't a problem, but I think it will be a problem after that because of our PKI infrastructure.

    I would have to look in to it when I have the time. Kinda busy here with DirectAccess related stuff.
    Too much that doesn't feel done yet in so much software from Microsoft.

    The testing will indeed be difficult, as there is no reproduction procedure.
    All I can think of is set a delayed start on the affected services, since when those are not started we get the SENS warning. Maybe we can trigger it that way.

    Wednesday, March 14, 2012 8:55 AM
  • DisplayPort
    At one point I've had the weird idea it had something to do with connecting the monitor using a DisplayPort adapter. Well that isn't it, just had an SENS error connecting with DVI to the monitor.

    OU/GroupPolicy

    I don't think it has something to do with my OU's/GPO's. Today I installed a machine joining the Domain in the build-in Computers OU in Active Directory.

    Logging in to the computer directly after the WDS installation completed causes a beautiful SENS error. I did a boot trace using xbootmgr but after the boot trace I didn't get the SENS error. I moved the computer to the OU in which (under normal circumstances) it should be. Did an gpupdate and started a boot trace again. No SENS error. Did an other gpupdate, rebooted and received the same message again, did a xbootmgr trace no message.

    I think a trace using xbootmgr delayes the bootup exactly that much that all services do have time to start before login.. So I don't think it will help me that much. I did se a lot of messages about Windows Defender 'pending' startups, so maybe I'll look into that.

    Wednesday, March 14, 2012 5:01 PM
  • I work in a school, we have had windows 7 deployed for well over 2 years and we are now starting to see this happen more and more often.  before i would see this once in a blue moon but over the last couple of weeks its happening much more frequently.
    Friday, March 16, 2012 10:11 AM
  • Hello everybody,

    I almost gave up on my boot tracing, but decided to give it another go. I've successfully did a boottrace with the SENS error. We're using a batch-script to install Novell Groupwise 8.02HP2 with some additional programs:

    • Microsoft Visual C++ 2005
    • Microsoft WSE 3.0
    • MSXML 4.0 SP2

    At the moment I suspect the Visual C++ redistributable to cause this issue, I'm not entirely sure about it, so I'll check that again when I've more time.

    I've compared two boottrace summary logs (xml files) and it's really hard to figure it out, there is a lot of information in those trace files. Maybe it has to do with mpnotify.exe, which has something to do with winlogon ánd Visual C++

    In my default image Visual C++ 2008 is installed, the installation script for Groupwise installs the Visual C++ 2005 redistributable runtime and after this installation I'll get the SENS error.

    Well, because I've thought several times that I'd figured it out, so I don't have high hopes..

    Monday, March 19, 2012 3:54 PM
  • On the left is the services trace with the SENS error. On the right the services trace without sens.

    Monday, March 19, 2012 4:45 PM
  • Last but not least... I've created a summary xml based on the trace boot files (etl) and found that there is an other difference between the two files. In the boottrace summary of the one with the SENS error there is a lot of diskIO:

      F:\SENS\summary_boot_withsens.xml (12 hits)
    	Line 216:             <file name="msyhbd.ttf" readBytes="14603264" readOps="447" readTime="132" writeBytes="0" writeOps="0" writeTime="0"
    	Line 218:             <file name="msjhbd.ttf" readBytes="14270464" readOps="438" readTime="146" writeBytes="0" writeOps="0" writeTime="0"
    	Line 228:             <file name="malgunbd.ttf" readBytes="4515328" readOps="139" readTime="44" writeBytes="0" writeOps="0" writeTime="0"
    	Line 236:             <extension name=".ttf" readBytes="55236096" readOps="1753" readTime="1096" writeBytes="0" writeOps="0" writeTime="0"
    	Line 377:             <file name="ARIALUNI.TTF" readBytes="23316992" readOps="723" readTime="537" writeBytes="0" writeOps="0" writeTime="0"
    	Line 381:             <file name="simkai.ttf" readBytes="11785216" readOps="362" readTime="331" writeBytes="0" writeOps="0" writeTime="0"
    	Line 383:             <file name="simfang.ttf" readBytes="10576384" readOps="325" readTime="239" writeBytes="0" writeOps="0" writeTime="0"
    	Line 385:             <file name="simhei.ttf" readBytes="9752064" readOps="300" readTime="300" writeBytes="0" writeOps="0" writeTime="0"
    	Line 387:             <file name="MSMINCHO.TTF" readBytes="9089536" readOps="283" readTime="128" writeBytes="0" writeOps="0" writeTime="0"
    	Line 391:             <file name="kaiu.ttf" readBytes="5199360" readOps="165" readTime="65" writeBytes="0" writeOps="0" writeTime="0"
    	Line 401:             <extension name=".ttf" readBytes="73357312" readOps="2410" readTime="2697" writeBytes="0" writeOps="0" writeTime="0"
    	Line 405:             <extension name=".TTF" readBytes="41235456" readOps="1353" readTime="1159" writeBytes="0" writeOps="0" writeTime="0"
    

    In one of the other treads about SENS somebody mentioned WIndows font cache services... ttf are fonts.. Need to check that to..


    Monday, March 19, 2012 4:56 PM
  • Hi all,

    We're seeing a similar intermittent error here - we're only at early test/pilot stage with Windows 7 SP1.  Agree with the observation that it's to do with "logging in too quickly".  My event logs when it happens look similar to Tom's above.  However rather than the 45056 LSAsrv warning, we get an Event 1000 for the Lanmanserver service reporting as a faulting application.  The 6004 and 6003 warnings report for Profiles, GPclient and also sens.

    A couple of thoughts:

    1. We have the AppV client in our build - I see Tom does too.  Are other people affected using AppV?

    2. We've got modified versions of the Microsoft SSLF security settings applying - historically these almost always turn out to be at the root of any weird behaviour! Anyone else using these?

    3.  I'm Scottish not Dutch, so it's definitely not your nationality!

    Glad to find that others are having this frustrating issue - if I find anything useful I'll report it back here.

    Nicky

    Monday, March 19, 2012 5:28 PM
  • Hi Nick,

    I'm not running SP1 but beside that I think I'm in the same situation.

    1. I've AppV client in our build. As you can see in the visual services trace the service sftlist.exe is taking a really long time to start when I get the SENS error. I don't now exactly if this is the cause or if this is the symptom. I even think the SENS error is not the real problem but a symptom.

    2. I don't think I've modified SSLF security settings applied.

    Like you I don't have the LASsrv waring but I do have the Event 1000 for the Lanmanserver service. <guess> And if that one doesn't work something with network connectivity won't start. If that doens't start AppV (Softgrid/SFT) isn't able to load and  the sftlist.exe tries this over and over again </guess>

    Faulting application name: svchost.exe_LanmanServer, version: 6.1.7600.16385, time stamp: 0x4a5bc100 Faulting module name: SSCORE.DLL, version: 6.1.7600.16385, time stamp: 0x4a5bc540 Exception code: 0xc0000005 Fault offset: 0x00001607 Faulting process id: 0x3c0 Faulting application start time: 0x01cd010ebb40fb53 Faulting application path: C:\Windows\system32\svchost.exe Faulting module path: C:\Windows\system32\SSCORE.DLL Report Id: 0d8d3a1c-6d02-11e1-ab2c-2c27d73458c2

    http://support.microsoft.com/kb/2316513 (About Lanmanserver service not able to start and something about PATH variables, I'll compare PATH variables on a working installation and a faulty one).

    http://support.microsoft.com/kb/2590550 (About SSCORE.DLL errors and black/blue backgrounds, I do get those sometime after the SENS error). In this link there is a mention about:

    "You may experience this issue after you install certain applications, for example Microsoft Application Virtualization Client, on the computer. "


    Tuesday, March 20, 2012 7:40 AM
  • One of the actions we got advised by MS was to set the following:

    Application Virtualization Client service to Manual Startup
    System Event Notification Service to Started Automatic

    I've done this now for 2 users whom experience this issue often. Waiting for feedback.

    Tuesday, March 20, 2012 8:58 AM
  • Harm-Jan, I think you've cracked it - http://support.microsoft.com/kb/2590550 describes our most common issue more or less exactly.  I'll try applying this hotfix to our machines - I have the luxury of still being in test with no "real" users so can be a bit hotfix-happy!  Will let you know how it goes.
    Tuesday, March 20, 2012 10:26 AM
  • That one does indeed seem like a hotfix for our problem, assuming everyone uses the App-V client.

    "This issue occurs when a new drive is added to the system while background services are still starting.  The most common example of this is with Microsoft Application Virtualization Client."

    The drive is the hidden Q: drive that is utilized by the App-V client.

    I will give this hotfix a go on a couple of machines here.

    Tuesday, March 20, 2012 1:14 PM
  • Same here. I spoke with MS. And we'll test it here as well.
    Tuesday, March 20, 2012 1:28 PM
  • Well.. I think this hotfix solved my issue. I've added the hotfix to the WIM file using the following procedure:

    http://myitforum.com/cs2/blogs/brandonlinton/archive/2010/06/28/how-to-offline-patch-a-wim-image-using-dism.aspx

    I've done a clean installation on one of my untouched/installed systems and didn't get the SENS error.

    Wednesday, March 21, 2012 3:08 PM
  • Thanks for your valuable feedback Harm-Jan -and- Nick (as they say in Dutch: "Goed Bezig";-)

    Look's like we're all using App-V, so lets make sure we test this & confirm here.

    Once we're all in agreement this is the fix I'll make sure to mark your post as the answer for this thread (which is getting close to being one year old! Lets put this to bed! ;-)


    Regards, Paul www.servercare.nl



    Thursday, March 22, 2012 10:04 AM
  • It's official!

    A number of people (three ; representing separate organisations) have reported that the patch Harm-Jan mentioned fixed the issue, which is appearantly associated with the use of App-V. The patch is (as mentioned above):  http://support.microsoft.com/kb/2590550


    Regards, Paul www.servercare.nl



    Tuesday, April 10, 2012 8:22 AM
  • As discusses by mail, we will roll out the hotfix this week on all clients, and add it to the deployment package in SCCM.

    Thanks all very much!

    Tuesday, April 10, 2012 8:44 AM
  • Hi All,

    Well done on your investigation, I can add my hat to the ring as another with AppV client as part of our Windows 7 task sequence has seen this issue appear today on a newly built machine.

    Will test hotfix and advise, but looks like you have all worked to find the likely solution. New laptops have SSD's so login times are VERY quick in comparison to existing hardware. 

    Thanks again.

    -Andrew

    Monday, May 07, 2012 3:37 AM