What is locking ntuser.dat

[Guest HDI]

Hi,

 

Sometimes this file is used (locked) by an another process so when you

log on you will get a temporary profile.

 

On each instance where a temporary profile has been used, there are

four successive USERENV errors:

1508 "Windows was unable to load the registry..."

1502 "Windows cannot load the locally stored profile..."

1515 "Windows has backed up the user's profile...."

1511 "Windows cannot find the local profile and is logging you on

with

a temporary profile...."

When I reboot the problem is solved but I hope there is another

solution. Anyone?

 

What is locking this file?

When I see in open files under shared folders there is nothing. Can I

look somewhere else?

 

I use roaming profiles between DC (2003) and terminal server 2003.

 

Thx

[Guest Michael M.]

Re: What is locking ntuser.dat

 

NtUSER.dat is the user portion of the registry.

 

It is equivelent to : HKEY\Current User\*.* and every user has a diffrent

one to store user specific settings.

 

This is normaly caused by a service that is running under a user account

such as Administrator or Mike or whatever, because services continue to

execute even after you log off your session, they can also lock open a file

or registry key.

 

This means with roaming profiles you could end up with more than one

computer opening the same profiles.

 

Have a look at the user accounts all of your services are running (on the

workstations or terminal servers) and if possible try to have them all

running as a system account like "Local System", "Network Service" etc or if

the service is not important disable it.

 

Mike.

 

 

 

"HDI" <hdinf@hotmail.com> wrote in message

news:1184078358.700038.85580@22g2000hsm.googlegroups.com...

> Hi,

>

> Sometimes this file is used (locked) by an another process so when you

> log on you will get a temporary profile.

>

> On each instance where a temporary profile has been used, there are

> four successive USERENV errors:

> 1508 "Windows was unable to load the registry..."

> 1502 "Windows cannot load the locally stored profile..."

> 1515 "Windows has backed up the user's profile...."

> 1511 "Windows cannot find the local profile and is logging you on

> with

> a temporary profile...."

> When I reboot the problem is solved but I hope there is another

> solution. Anyone?

>

> What is locking this file?

> When I see in open files under shared folders there is nothing. Can I

> look somewhere else?

>

> I use roaming profiles between DC (2003) and terminal server 2003.

>

> Thx

>

[Guest HDI]

Re: What is locking ntuser.dat

 

On 10 jul, 18:29, "Michael M." <nos...@mike.com> wrote:

> NtUSER.dat is the user portion of the registry.

>

> It is equivelent to : HKEY\Current User\*.* and every user has a diffrent

> one to store user specific settings.

>

> This is normaly caused by a service that is running under a user account

> such as Administrator or Mike or whatever, because services continue to

> execute even after you log off your session, they can also lock open a file

> or registry key.

>

> This means with roaming profiles you could end up with more than one

> computer opening the same profiles.

>

> Have a look at the user accounts all of your services are running (on the

> workstations or terminal servers) and if possible try to have them all

> running as a system account like "Local System", "Network Service" etc or if

> the service is not important disable it.

>

> Mike.

>

> "HDI" <h...@hotmail.com> wrote in message

>

> news:1184078358.700038.85580@22g2000hsm.googlegroups.com...

>

>

>

> > Hi,

>

> > Sometimes this file is used (locked) by an another process so when you

> > log on you will get a temporary profile.

>

> > On each instance where a temporary profile has been used, there are

> > four successive USERENV errors:

> > 1508 "Windows was unable to load the registry..."

> > 1502 "Windows cannot load the locally stored profile..."

> > 1515 "Windows has backed up the user's profile...."

> > 1511 "Windows cannot find the local profile and is logging you on

> > with

> > a temporary profile...."

> > When I reboot the problem is solved but I hope there is another

> > solution. Anyone?

>

> > What is locking this file?

> > When I see in open files under shared folders there is nothing. Can I

> > look somewhere else?

>

> > I use roaming profiles between DC (2003) and terminal server 2003.

>

> > Thx- Tekst uit oorspronkelijk bericht niet weergeven -

>

> - Tekst uit oorspronkelijk bericht weergeven -

 

I see but this doesn't happen to all the profiles.

 

It happens to new created profiles; after I restarted the server it's

ok or ok for a time. When it still happens after a few reboots I

delete the account and recreate it and no problems anymore. As you can

see not a good options.

 

So it happens te new created profiles. But why?

[Guest Michael M.]

Re: What is locking ntuser.dat

 

Hmm,

 

I think when you create a new user account the profile will normaly be made

up from as a combination of All users and "Default User"

 

It could be there is some curroption in the "default user" account profile.

mabye you should try recreating a new user template for and copy to

"\default user" and see how that goes.

 

Mike.

 

 

"HDI" <hdinf@hotmail.com> wrote in message

news:1184088059.239851.24950@57g2000hsv.googlegroups.com...

> On 10 jul, 18:29, "Michael M." <nos...@mike.com> wrote:

>> NtUSER.dat is the user portion of the registry.

>>

>> It is equivelent to : HKEY\Current User\*.* and every user has a

>> diffrent

>> one to store user specific settings.

>>

>> This is normaly caused by a service that is running under a user account

>> such as Administrator or Mike or whatever, because services continue to

>> execute even after you log off your session, they can also lock open a

>> file

>> or registry key.

>>

>> This means with roaming profiles you could end up with more than one

>> computer opening the same profiles.

>>

>> Have a look at the user accounts all of your services are running (on the

>> workstations or terminal servers) and if possible try to have them all

>> running as a system account like "Local System", "Network Service" etc or

>> if

>> the service is not important disable it.

>>

>> Mike.

>>

>> "HDI" <h...@hotmail.com> wrote in message

>>

>> news:1184078358.700038.85580@22g2000hsm.googlegroups.com...

>>

>>

>>

>> > Hi,

>>

>> > Sometimes this file is used (locked) by an another process so when you

>> > log on you will get a temporary profile.

>>

>> > On each instance where a temporary profile has been used, there are

>> > four successive USERENV errors:

>> > 1508 "Windows was unable to load the registry..."

>> > 1502 "Windows cannot load the locally stored profile..."

>> > 1515 "Windows has backed up the user's profile...."

>> > 1511 "Windows cannot find the local profile and is logging you on

>> > with

>> > a temporary profile...."

>> > When I reboot the problem is solved but I hope there is another

>> > solution. Anyone?

>>

>> > What is locking this file?

>> > When I see in open files under shared folders there is nothing. Can I

>> > look somewhere else?

>>

>> > I use roaming profiles between DC (2003) and terminal server 2003.

>>

>> > Thx- Tekst uit oorspronkelijk bericht niet weergeven -

>>

>> - Tekst uit oorspronkelijk bericht weergeven -

>

> I see but this doesn't happen to all the profiles.

>

> It happens to new created profiles; after I restarted the server it's

> ok or ok for a time. When it still happens after a few reboots I

> delete the account and recreate it and no problems anymore. As you can

> see not a good options.

>

> So it happens te new created profiles. But why?

>

[Guest HDI]

Re: What is locking ntuser.dat

 

On 10 jul, 19:20, HDI <h...@hotmail.com> wrote:

> On 10 jul, 18:29, "Michael M." <nos...@mike.com> wrote:

>

>

>

>

>

> > NtUSER.dat is the user portion of the registry.

>

> > It is equivelent to : HKEY\Current User\*.* and every user has a diffrent

> > one to store user specific settings.

>

> > This is normaly caused by a service that is running under a user account

> > such as Administrator or Mike or whatever, because services continue to

> > execute even after you log off your session, they can also lock open a file

> > or registry key.

>

> > This means with roaming profiles you could end up with more than one

> > computer opening the same profiles.

>

> > Have a look at the user accounts all of your services are running (on the

> > workstations or terminal servers) and if possible try to have them all

> > running as a system account like "Local System", "Network Service" etc or if

> > the service is not important disable it.

>

> > Mike.

>

> > "HDI" <h...@hotmail.com> wrote in message

>

> >news:1184078358.700038.85580@22g2000hsm.googlegroups.com...

>

> > > Hi,

>

> > > Sometimes this file is used (locked) by an another process so when you

> > > log on you will get a temporary profile.

>

> > > On each instance where a temporary profile has been used, there are

> > > four successive USERENV errors:

> > > 1508 "Windows was unable to load the registry..."

> > > 1502 "Windows cannot load the locally stored profile..."

> > > 1515 "Windows has backed up the user's profile...."

> > > 1511 "Windows cannot find the local profile and is logging you on

> > > with

> > > a temporary profile...."

> > > When I reboot the problem is solved but I hope there is another

> > > solution. Anyone?

>

> > > What is locking this file?

> > > When I see in open files under shared folders there is nothing. Can I

> > > look somewhere else?

>

> > > I use roaming profiles between DC (2003) and terminal server 2003.

>

> > > Thx- Tekst uit oorspronkelijk bericht niet weergeven -

>

> > - Tekst uit oorspronkelijk bericht weergeven -

>

> I see but this doesn't happen to all the profiles.

>

> It happens to new created profiles; after I restarted the server it's

> ok or ok for a time. When it still happens after a few reboots I

> delete the account and recreate it and no problems anymore. As you can

> see not a good options.

>

> So it happens te new created profiles. But why?- Tekst uit oorspronkelijk bericht niet weergeven -

>

> - Tekst uit oorspronkelijk bericht weergeven -

 

Btw not all new created profiles, eg: one out of ten.

[Guest Jeff Pitsch]

Re: What is locking ntuser.dat

 

have you downloaded adn installed UPHCLEAN from microsoft?

 

Jeff Pitsch

Microsoft MVP - Terminal Server

Citrix Technology Professional

Provision Networks VIP

 

Forums not enough?

Get support from the experts at your business

http://jeffpitschconsulting.com

 

HDI wrote:

> Hi,

>

> Sometimes this file is used (locked) by an another process so when you

> log on you will get a temporary profile.

>

> On each instance where a temporary profile has been used, there are

> four successive USERENV errors:

> 1508 "Windows was unable to load the registry..."

> 1502 "Windows cannot load the locally stored profile..."

> 1515 "Windows has backed up the user's profile...."

> 1511 "Windows cannot find the local profile and is logging you on

> with

> a temporary profile...."

> When I reboot the problem is solved but I hope there is another

> solution. Anyone?

>

> What is locking this file?

> When I see in open files under shared folders there is nothing. Can I

> look somewhere else?

>

> I use roaming profiles between DC (2003) and terminal server 2003.

>

> Thx

>

[Guest HDI]

Re: What is locking ntuser.dat

 

On 10 jul, 20:34, "Michael M." <nos...@mike.com> wrote:

> Hmm,

>

> I think when you create a new user account the profile will normaly be made

> up from as a combination of All users and "Default User"

>

> It could be there is some curroption in the "default user" account profile.

> mabye you should try recreating a new user template for and copy to

> "\default user" and see how that goes.

>

> Mike.

>

> "HDI" <h...@hotmail.com> wrote in message

>

> news:1184088059.239851.24950@57g2000hsv.googlegroups.com...

>

>

>

> > On 10 jul, 18:29, "Michael M." <nos...@mike.com> wrote:

> >> NtUSER.dat is the user portion of the registry.

>

> >> It is equivelent to : HKEY\Current User\*.* and every user has a

> >> diffrent

> >> one to store user specific settings.

>

> >> This is normaly caused by a service that is running under a user account

> >> such as Administrator or Mike or whatever, because services continue to

> >> execute even after you log off your session, they can also lock open a

> >> file

> >> or registry key.

>

> >> This means with roaming profiles you could end up with more than one

> >> computer opening the same profiles.

>

> >> Have a look at the user accounts all of your services are running (on the

> >> workstations or terminal servers) and if possible try to have them all

> >> running as a system account like "Local System", "Network Service" etc or

> >> if

> >> the service is not important disable it.

>

> >> Mike.

>

> >> "HDI" <h...@hotmail.com> wrote in message

>

> >>news:1184078358.700038.85580@22g2000hsm.googlegroups.com...

>

> >> > Hi,

>

> >> > Sometimes this file is used (locked) by an another process so when you

> >> > log on you will get a temporary profile.

>

> >> > On each instance where a temporary profile has been used, there are

> >> > four successive USERENV errors:

> >> > 1508 "Windows was unable to load the registry..."

> >> > 1502 "Windows cannot load the locally stored profile..."

> >> > 1515 "Windows has backed up the user's profile...."

> >> > 1511 "Windows cannot find the local profile and is logging you on

> >> > with

> >> > a temporary profile...."

> >> > When I reboot the problem is solved but I hope there is another

> >> > solution. Anyone?

>

> >> > What is locking this file?

> >> > When I see in open files under shared folders there is nothing. Can I

> >> > look somewhere else?

>

> >> > I use roaming profiles between DC (2003) and terminal server 2003.

>

> >> > Thx- Tekst uit oorspronkelijk bericht niet weergeven -

>

> >> - Tekst uit oorspronkelijk bericht weergeven -

>

> > I see but this doesn't happen to all the profiles.

>

> > It happens to new created profiles; after I restarted the server it's

> > ok or ok for a time. When it still happens after a few reboots I

> > delete the account and recreate it and no problems anymore. As you can

> > see not a good options.

>

> > So it happens te new created profiles. But why?- Tekst uit oorspronkelijk bericht niet weergeven -

>

> - Tekst uit oorspronkelijk bericht weergeven -

 

If there is corruption shouldn't it be for all the created profiles

and not for a few ones?

[Guest Helge Klein]

Re: What is locking ntuser.dat

 

If a file or registry key is opened by some process (be it an

application or a service) then tools like oh.exe or Process Explorer

can show you which process has opened a specific handle. I recommend

the free Process Explorer from Sysinternals. Download it here:

 

http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/ProcessExplorer.mspx

 

When you have started ProcMon press CTRL+F and type "NTUSER.DAT" into

the search box. You will get a list of processes that have files

called "NTUSER.DAT" open.

 

I hope this helps.

 

Helge

 

On 10 Jul., 20:34, "Michael M." <nos...@mike.com> wrote:

> Hmm,

>

> I think when you create a new user account the profile will normaly be made

> up from as a combination of All users and "Default User"

>

> It could be there is some curroption in the "default user" account profile.

> mabye you should try recreating a new user template for and copy to

> "\default user" and see how that goes.

>

> Mike.

>

> "HDI" <h...@hotmail.com> wrote in message

>

> news:1184088059.239851.24950@57g2000hsv.googlegroups.com...

>

> > On 10 jul, 18:29, "Michael M." <nos...@mike.com> wrote:

> >> NtUSER.dat is the user portion of the registry.

>

> >> It is equivelent to : HKEY\Current User\*.* and every user has a

> >> diffrent

> >> one to store user specific settings.

>

> >> This is normaly caused by a service that is running under a user account

> >> such as Administrator or Mike or whatever, because services continue to

> >> execute even after you log off your session, they can also lock open a

> >> file

> >> or registry key.

>

> >> This means with roaming profiles you could end up with more than one

> >> computer opening the same profiles.

>

> >> Have a look at the user accounts all of your services are running (on the

> >> workstations or terminal servers) and if possible try to have them all

> >> running as a system account like "Local System", "Network Service" etc or

> >> if

> >> the service is not important disable it.

>

> >> Mike.

>

> >> "HDI" <h...@hotmail.com> wrote in message

>

> >>news:1184078358.700038.85580@22g2000hsm.googlegroups.com...

>

> >> > Hi,

>

> >> > Sometimes this file is used (locked) by an another process so when you

> >> > log on you will get a temporary profile.

>

> >> > On each instance where a temporary profile has been used, there are

> >> > four successive USERENV errors:

> >> > 1508 "Windows was unable to load the registry..."

> >> > 1502 "Windows cannot load the locally stored profile..."

> >> > 1515 "Windows has backed up the user's profile...."

> >> > 1511 "Windows cannot find the local profile and is logging you on

> >> > with

> >> > a temporary profile...."

> >> > When I reboot the problem is solved but I hope there is another

> >> > solution. Anyone?

>

> >> > What is locking this file?

> >> > When I see in open files under shared folders there is nothing. Can I

> >> > look somewhere else?

>

> >> > I use roaming profiles between DC (2003) and terminal server 2003.

>

> >> > Thx- Tekst uit oorspronkelijk bericht niet weergeven -

>

> >> - Tekst uit oorspronkelijk bericht weergeven -

>

> > I see but this doesn't happen to all the profiles.

>

> > It happens to new created profiles; after I restarted the server it's

> > ok or ok for a time. When it still happens after a few reboots I

> > delete the account and recreate it and no problems anymore. As you can

> > see not a good options.

>

> > So it happens te new created profiles. But why?