Search
Report Types:
Products
Updates
Logs
Bugs
Files
Encounters:
Only Reports that have Encounters
Encounters must contain resolution
Home
Products
Updates
Logs
Bugs
Files
Sign In
Create an Account
Action Links
Create a Product Report
Create a Update/Patch Report
Create a Log/Event Report
Create a Bug Report
Create a File Report
Recent Search Results
No Search results are currently available to display.
Your last search results will be displayed here for the duration of your browser session.
Latest Reports
Windows Application Event ID 4, MSExchange Configuration Cmdlet - Management Console, Error
Your system is low on virtual memory.
Code 43: Windows has stopped this device because it has reported problems
RUNDLL Error Loading ...
Test
Service Pack KB976932 SP1
Microsoft-Windows-Backup/Operational Error Backup 5
Can not delete file - Access Denied - No Security Tab
Important KB2467023 Fix
VMware View 4.5
...
6
7
8
9
10
...
Bug Report
Print
Edit This Record
Create New
Revision
2
Summary
Windows cannot load the locally stored profile.
Average Threat Rating
Average Threat Rating Help
X
Loading...
Encounters
More Info
Related Content
Alert Me
Discuss
Add Your Encounter
Hide Encounters without Resolutions
tfenner
Posts: 66
3/24/2011
Revision
1
Threat Rating:
Contains Resolution:
After installing Citrix ICA client, this message began to appear.
Use this article to enable User Environment Debug Logging:
http://support.microsoft.com/kb/221833
When the message appears again, locate the following log file: %SystemRoot%\Debug\UserMode\Userenv.log
Look for errors = found Error 32 in my log, which is a Error_Sharing_Violation. This means something had already opened my User registry hive and was restricting my logon process from accessing it in a way it needed to.
Microsoft support engineer had me capture a trace of the logon with Process Monitor, by selecting Enable Boot Logging from the Options menu. I then rebooted and attempted to recreate this issue. After getting the message, I opened Process Monitor and it offered to convert the boot log to a standard log, located here: %SystemRoot%\Procmon.pmb.
The information within showed that a Citrix process was activating directly before the winlogon process, making it appear that it was doing something it shouldn't.
Upon further research, there are articles on how to workaround this issue:
Citrix:
http://support.citrix.com/article/CTX118226
Microsoft:
http://support.microsoft.com/kb/969100/en-us
Peer Reviews (0)
Peer Review Help
X
Loading...
No reviews have been post for this Encounter
Post a Peer Review:
tfenner
Posts: 66
3/24/2011
Revision
1
Threat Rating:
Contains Resolution:
A quick reboot and all is well again.
Peer Reviews (0)
Peer Review Help
X
Loading...
No reviews have been post for this Encounter
Post a Peer Review:
Copyright (c) 2011
About Us
Contact Us
Privacy
Disclaimer
FAQs