locked
The winlogon notification subscriber <Profiles> took 142 second(s) to handle the notification event (Logon). RRS feed

  • Question

  • On a number of machines in our AD domain where login is handled by two 2008 servers and the profiles stored on a 2003 Server, we get the following message:

    The winlogon notification subscriber <Profiles> took 142 second(s) to handle the notification event (Logon).

    The time delays may differ but the issue is the same - client computers will sit loading the roaming profile for upwards of 20 minutes.  We have seen this on both Vista and Window 7 64 bit machines.

    If we dump the local roaming profile and the server version and re-synch the problem goes away for a short time but then returns again shortly afterwards(within about 2 weeks).

    Any suggestions?

    Monday, March 28, 2011 3:25 PM

Answers

  • Activate boot logging inside Process Monitor [1] and capture what is going on during boot.

    Now look what happens after winlogon.exe starts.

    Do you see what takes too much time? Look at the duration column.


    André

     


    "A programmer is just a tool which converts caffeine into code"

    Want to install RSAT on Windows 7 Sp1? Check my HowTo: http://www.msfn.org/board/index.php?showtopic=150221
    • Marked as answer by Miya Yao Tuesday, April 5, 2011 7:54 AM
    Monday, March 28, 2011 7:58 PM

All replies

  • Activate boot logging inside Process Monitor [1] and capture what is going on during boot.

    Now look what happens after winlogon.exe starts.

    Do you see what takes too much time? Look at the duration column.


    André

     


    "A programmer is just a tool which converts caffeine into code"

    Want to install RSAT on Windows 7 Sp1? Check my HowTo: http://www.msfn.org/board/index.php?showtopic=150221
    • Marked as answer by Miya Yao Tuesday, April 5, 2011 7:54 AM
    Monday, March 28, 2011 7:58 PM
  • Hi,

    How's going?

    Follow Andre.Ziegler's reply to check the process during boot.

    Download the Process Monitor here: http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx 

    Regards,

    Miya

    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, 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.
    Wednesday, March 30, 2011 6:09 AM
  • Hi,

     

    As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to  reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.

     

    BTW,  we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts.

     

    Regards,

    Miya

    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, 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.
    Monday, April 4, 2011 6:21 AM