Home > Event Id > Event Id 6006 Winlogon

Event Id 6006 Winlogon


As per Microsoft: "This event is written during an expected restart or shutdown after the user initiates the restart or shutdown by clicking Start and then clicking Shut Down, or by Type Success User Domain\Account name of user/service/computer initiating event. See image for a reference point. 2 This discussion has been inactive for over a year. EventID 6009 - Microsoft (R) Windows (R) %1 %2 %3 %4. have a peek here

Log Type: Windows Event Log Uniquely Identified By: Log Name: System Filtering Field Equals to Value OSVersion Windows 2000Windows XPWindows 2003 Source EventLog EventId 6006 Field Matching FieldDescriptionStored inSample Value DateTime Even with 5 minutes per server (to check the logs and other parameters), it may take an hour to make sure that everything is ok and no "red lights" are blinking The problem seems to just apply to me, regardless of where I log on. See example of private comment Links: Event id 6005 from Winlogon Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links... http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows%20Operating%20System&ProdVer=5.2&EvtID=6006&EvtSrc=EventLog&LCID=1033

Event Id 6006 Winlogon

Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? Application, Security, System, etc.) LogName Security Category A name for a subclass of events within the same Event Source. Join Now Hi guys,   I am having trouble with my own work comp here - however it seems to be more related to my profile or something. Mark Reply Subscribe RELATED TOPICS: Winlogon notification subscriber error - taking 605 seconds to boot Welcome Screen hangs: Winlogon error took X seconds to logon.

Not a member? It occurs during a shutdown. Creating your account only takes a few minutes. Profile Hive Cleanup Tool The only thing I found is that it was due to Synchronous Application of Group Policy.

http://www.microsoft.com/downloads/details.aspx?FamilyId=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en" He is running Windows 7. Details Event ID: Source: We're sorry There is no additional information about this issue in the Error and Event Log Messages or Knowledge Base databases at this time. x 14 EventID.Net Self-explanatory. http://www.eventid.net/display-eventid-6006-source-EventLog-eventno-155-phase-1.htm About Advertising Privacy Terms Help Sitemap × Join millions of IT pros like you Log in to Spiceworks Reset community password Agree to Terms of Service Connect with Or Sign up

Event 6005 and 6006 are in most cases recorded together. Event Id 6006 Dfsr Replication Join the community Back I agree Powerful tools you need, all for free. When we installed the updates on our DC's the problem was gone and logging on went back to normal. * * * Verify if there are some logon scripts applied to Description Special privileges assigned to new logon.

Event Id 6006 Slow Logon

See MSW2KDB for additional information about this event. Some google searches brought up resutls about possible problems with GPOs or that maybe Windows is looking for printer drivers on logon, but I can't see why. Event Id 6006 Winlogon Join the community Back I agree Powerful tools you need, all for free. Event Id 6006 Windows 10 Event ID 6009 followed immediately by an event id 6005 is pretty much Windows starting up.

If so, temporarily disable the policy or remove the logon scripts to check the result. * * * In my case, a user had a 10-minuted delay before every logon. navigate here I didn't think you would respond so fast ;) Try this: http://windows.microsoft.com/en-US/Windows7/Fix-a-corrupted-user-profile   here's the referral page: http://social.technet.microsoft.com/Forums/en-US/w7itproperf/thread/5828f9ba-40fe-4034-8902-f69e07a270a2 0 Jalapeno OP Mr.Snooch May 6, 2010 at 10:30 UTC So normally look for this pattern. 6009 and 6005 same time stamp, system just started. 6013 - system has been up for a day or more, time in seconds. 6006 - EventID 6006 - The Event log service was stopped. Windows Event Id 6009

Category Logon/Logoff Comments You must be logged in to comment Home Event ID 6006 - Winlogon problems by Mr.Snooch on May 6, 2010 at 10:08 UTC | Windows 5 Next: Does Hurrah! No more Event IDs 6005 and 6006! http://3ecommunications.net/event-id/event-id-6005-winlogon.html I don't believe this would be appropriate for a roaming profile even if it is on an applicable server. 0 Mace OP Texkonc May 6, 2010 at 3:32

All rights reserved. The Winlogon Notification Subscriber Profiles Is Taking Long Time To Handle The Notification Event Recommend Us Quick Tip Connect to EventID.Net directly from the Microsoft Event Viewer!Instructions Customer services Contact usSupportTerms of Use Help & FAQ Sales FAQEventID.Net FAQ Advertise with us Articles Managing logsRecommended Concepts to understand: What is a Windows Service Pack?

Join the Community!

Hive cleanup does indeed normally work on all our XP clients though, so typical it's on this machine. I have been on Win7 for around 3/4 months now but this has only Recommend Us Quick Tip Connect to EventID.Net directly from the Microsoft Event Viewer!Instructions Customer services Contact usSupportTerms of Use Help & FAQ Sales FAQEventID.Net FAQ Advertise with us Articles Managing logsRecommended The "Applying computer settings" message delay decreased from 4 minutes to 20 seconds. Windows Event Id 1074 The actual reason was very trivial and not related to hardware at all.

My bad. Login here! By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. this contact form And in this particular case the user did not have the permissions required to connect to the network share.

Since all the lookups were timing out, it caused logins to be very slow, like 15 minutes long. This is found under Computer Configuration\Policies\Administrative Templates\System\Scripts User Information Only an Email address is required for returning users. User RESEARCH\Alebovsky Computer Name of server workstation where event was logged. Source Security Type Warning, Information, Error, Success, Failure, etc.

Keeping an eye on these servers is a tedious, time-consuming process.