I am having a difficult time with an issue that our support staff won't support (as they will not support Vista). I am able to log into our domain without any issue, however, when I go home and log into my domain account (disconnected), everything works great. I log out that night, redock my computer on our domain network and BLAMO, I get loaded into a TEMP profile.
When I look under the event view, I get the following messages. There are 3 others that follow it, relating to this event, however, I don't want to spam the threads unless you deem it necessary.
Log Name: Application
Source: Microsoft-Windows-User Profiles Service
Date: 6/3/2009 6:53:21 AM
Event ID: 1508
Task Category: None
Level: Error
Keywords:
User: SYSTEM
Computer: xxx
Description:
Windows was unable to load the registry. This problem is often caused by insufficient memory or insufficient security rights.
DETAIL - The process cannot access the file because it is being used by another process.
for C:\Users\xxx\ntuser.dat
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-User Profiles Service" Guid="{89B1E9F0-5AFF-44A6-9B44-0A07A7CE5845}" />
<EventID>1508</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2009-06-03T11:53:21.416184400Z" />
<EventRecordID>2156</EventRecordID>
<Correlation ActivityID="{02CFD900-F800-0000-E482-E0C041E4C901}" />
<Execution ProcessID="112" ThreadID="304" />
<Channel>Application</Channel>
<Computer>xxx/Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData Name="EVENT_REGLOADKEYFAILED">
<Data Name="Error">The process cannot access the file because it is being used by another process.
</Data>
<Data Name="File">C:\Users\xxx\ntuser.dat</Data>
</EventData>
</Event>
I'm just frustrated that I can't get support and most of the search articles I came across had to do with local accounts. I did make a backup of the "functioning" profile, in hopes to restore that once everything is back to normal.
I've logged in as a local admin to the box and renamed the "corrupt" profile in hopes that it would simply be rebuilt when I logged back into my domain account. However, when I did that, it STILL logged into the TEMP profile...grr!
Thanks in advanced, Aaron