ntuser.dat

[FaL]

Archived from groups: microsoft.public.win2000.setup,microsoft.public.win2000.setup_deployment,microsoft.public.win2000.setup_upgrade (More info?)

Hi,

When i run scanstate.exe, i’ve got this message in scanstate.log

Module Error Can’t load registry file C:\Documents and
Settings\uppa7416\ntuser.dat to
S-1-5-21-854245398-789336058-682003330-223746 [ERROR=32 (20h)]
Info Scanstate is exiting.

The profile is a roaming profile.
My session is closed and scanstate is launched with a local
administrator account (not with the user account). If i try to launch
scanstate with the user account, i obtain the same result...

Does anybody have an idea ?

Thx,

FAL

--
Posted using the http://www.windowsforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.windowsforumz.com/Setup---Deploy---Upgrade-ntuser.dat-ftopict276188.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.windowsforumz.com/eform.php?p=876080

 

[Guest]

Archived from groups: microsoft.public.win2000.setup,microsoft.public.win2000.setup_deployment,microsoft.public.win2000.setup_upgrade (More info?)

Hi,

What on earth is "scanstate"? Sounds interesting!

FAL wrote:

> Hi,
>
> When i run scanstate.exe, i’ve got this message in scanstate.log
>
> Module Error Can’t load registry file C:\Documents and
> Settings\uppa7416\ntuser.dat to
> S-1-5-21-854245398-789336058-682003330-223746 [ERROR=32 (20h)]
> Info Scanstate is exiting.
>
> The profile is a roaming profile.
> My session is closed and scanstate is launched with a local
> administrator account (not with the user account). If i try to launch
> scanstate with the user account, i obtain the same result...
>
> Does anybody have an idea ?
>
> Thx,
>
> FAL
>


--
Gerry Hickman (London UK)

 

[Guest]

Archived from groups: microsoft.public.win2000.setup,microsoft.public.win2000.setup_deployment,microsoft.public.win2000.setup_upgrade (More info?)

Excerpt from: User State Migration in Windows XP
http://www.microsoft.com/technet/prodtechnol/winxppro/deploy/usermigr.mspx#EDAA

What's in USMT

The User State Migration Tool consists of two executable files,
ScanState.exe, LoadState.exe, and four migration rule information files
Migapp.inf, Migsys.inf, Miguser.inf, and Sysfiles.inf.

ScanState.exe collects user data and settings based on the information
contained in Migapp.inf, Migsys.inf, Miguser.inf and Sysfiles.inf.
LoadState.exe deposits this user state data on a computer running a
fresh (not upgraded) installation of Windows XP Professional.

User State Migration Tools
http://www.microsoft.com/windowsxp/using/setup/expert/russel_november19.mspx

John

Gerry Hickman wrote:

> Hi,
>
> What on earth is "scanstate"? Sounds interesting!
>
> FAL wrote:
>
>> Hi,
>>
>> When i run scanstate.exe, i’ve got this message in scanstate.log
>>
>> Module Error Can’t load registry file C:\Documents and
>> Settings\uppa7416\ntuser.dat to
>> S-1-5-21-854245398-789336058-682003330-223746 [ERROR=32 (20h)]
>> Info Scanstate is exiting.
>>
>> The profile is a roaming profile. My session is closed and scanstate
>> is launched with a local
>> administrator account (not with the user account). If i try to launch
>> scanstate with the user account, i obtain the same result...
>> Does anybody have an idea ?
>>
>> Thx,
>>
>> FAL
>>
>
>

 

[Guest]

Archived from groups: microsoft.public.win2000.setup,microsoft.public.win2000.setup_deployment,microsoft.public.win2000.setup_upgrade (More info?)

Hi John,

> ScanState.exe collects user data and settings based on the information
> contained in Migapp.inf, Migsys.inf, Miguser.inf and Sysfiles.inf.

OK, suddenly makes sense.

Unfortunately, I've never used these tools so can't be of much help. Out
of interest, does this error occur on EVERY user's NTUSER.DAT on EVERY
machine you test it on? I assume you've checked NTFS on those
files/folders to ensure the Admin account you are using has access?

One other thing to look out for, is that if you have not rebooted the
machine, a number of both Microsoft and 3rd party applications leak open
handles after the user logs off. Check for USERENV errors if you suspect
this.

--
Gerry Hickman (London UK)