0% found this document useful (0 votes)
25 views6 pages

CSIAgent XML Format Errors

The document logs the execution of the ScanState tool for user state migration, detailing the command line used and system information. Several warnings and errors are reported, including issues with loading user class hives and invalid XML formats. Additionally, multiple duplicate manifest identities are noted, indicating potential conflicts during the migration process.

Uploaded by

b3njmi1njedi
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
25 views6 pages

CSIAgent XML Format Errors

The document logs the execution of the ScanState tool for user state migration, detailing the command line used and system information. Several warnings and errors are reported, including issues with loading user class hives and invalid XML formats. Additionally, multiple duplicate manifest identities are noted, indicating potential conflicts during the migration process.

Uploaded by

b3njmi1njedi
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd

2022-11-02 11:43:40, Info [0x000000] SCANSTATE.

EXE[gle=0x000000b7]
2022-11-02 11:43:40, Info [0x000000] USMT Started at
2022/11/02:11:43:40.996
2022-11-02 11:43:40, Info [0x000000] Command line: C:\
ScanState_amd64\[Link] /Apps /Genconfig:C:\Recovery\OEM\pbr_config.xml
2022-11-02 11:43:40, Info [0x000000] Starting the migration
process
2022-11-02 11:43:41, Warning [0x080000] User class hive loading
error, ignoring. Hive path:C:\Users\Default\AppData\Local\Microsoft\Windows\
[Link], error: 2
2022-11-02 11:43:43, Info [0x000000] Host system information:
OS version: 10.0.19045
Architecture: x64
Manufacturer: Dell Inc.
Model : Latitude 5490
AoAc (connected standby) : No
BIOS name : 1.18.0
BIOS version : 1.18.0
BIOS release date : 20210910000000.000000+000
Total memory : 8589934592
Processor manufacturer : GenuineIntel
Processor name : Intel(R) Core(TM) i5-8350U CPU
@ 1.70GHz
Processor caption : Intel64 Family 6 Model 142
Stepping 10
Processor architecture : (null)
Processor clock : 1896

2022-11-02 11:43:43, Info [0x000000] System information:


Computer name: DESKTOP-5PFEAH6
Machine SID: S-1-5-21-1520432077-2238795982-
1316278361
OS version: 10.0.19045
Language: en-US
Architecture: 64-bit

Drives:
E: Type: Removable
D: Type: Fixed, Bus type: USB, Hotplug: Yes
C: Type: Fixed, Bus type: SATA, Hotplug: No

Users:
DESKTOP-5PFEAH6\Default User, administrator:
No, interactive: No, logged on: No, has profile: Yes
DESKTOP-5PFEAH6\WDAGUtilityAccount,
administrator: No, interactive: No, logged on: No, has profile: No
DESKTOP-5PFEAH6\Administrator, administrator:
Yes, interactive: Yes, logged on: Yes, has profile: Yes
DESKTOP-5PFEAH6\Guest, administrator: No,
interactive: Yes, logged on: No, has profile: No
DESKTOP-5PFEAH6\DefaultAccount, administrator:
No, interactive: No, logged on: No, has profile: No

2022-11-02 11:43:43, Info [0x000000] Examining the system to


discover the migration units

2022-11-02 11:43:43, Warning [0x080000] User class hive loading


error, ignoring. Hive path:C:\Users\Default\AppData\Local\Microsoft\Windows\
[Link], error: 2
2022-11-02 11:43:43, Error [0x080831] CSIAgent: Invalid xml format:
FormatException: "script" attribute is mandatory. class Mig::CMXEMerge *__cdecl
Mig::CMXEMigrationXml::LoadMerge(class UnBCL::XmlNode *,int,class
Mig::CMXEMigrationXml *,class Mig::CMXEXmlComponent *)
2022-11-02 11:43:44, Warning [0x080000] No implementation of
IDiscovery->Discover found for Plugin={ServerPath="%SYSTEM32%\migration\
[Link]", CLSID={1562F08D-A49B-4B9E-887C-BB97F6E719AC},
ThreadingModel=Apartment}
2022-11-02 11:43:45, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-BTH-USER
2022-11-02 11:43:45, Error [0x080831] CSIAgent: Invalid xml format:
FormatException: Callback entry point
[Link]("wlansvc", "128") not found. __cdecl
Mig::CMXEScriptCaller::CMXEScriptCaller(class UnBCL::String *,class
Mig::CMXEMigrationXml *,class Mig::CMXEXmlComponent *)
2022-11-02 11:43:45, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-Authentication-AuthUI-Component
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-MMDeviceAPI
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists
[Link]
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-Web-Services-for-Management-Core
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-Security-NGC-LocalAccountMigPlugin
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-X509CertificateEnrollment
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-Type1-Fonts
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-DeviceMetadataRetrievalClient
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
OneCore-CloudExperienceHost-API
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
OneCore-TileDataRepository
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-PeerDist-Upgrade
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-Holographic-DisplayThrottling
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-TerminalServices-Gateway-Package
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-Feedback-Service
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-Security-Fido-CredProv
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-Shell-Sounds
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-Volsnap
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-MediaPlayer-Core
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-TaskScheduler-Service
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-Profsvc
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-Winsock-Core-Infrastructure-other-MinWin
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-HelpAndSupport
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-SystemMaintenanceService
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-Power-EnergyEstimationEngine
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-HAL
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-MFMPEG2SrcSnk
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-WinMDE
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-Flighting-Settings
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-eudcedit
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-DeviceRegistration
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
SenseClient-Service
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-ErrorReportingFaults
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-IE-AdminKitBranding
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-ManagementRegistration
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-MFSrcSnk
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-SystemSettings-VideoSettingsHandlers
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-IE-PDM-Configuration
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-MFPlat
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-ErrorReportingCore
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-sysdm
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-IE-ClientNetworkProtocolImplementation
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-MSMPEG2VDEC
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-Rights-Management-Client-v1-API
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-SecurityCenter-Core
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-RasServer
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-propsys
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-TerminalServices-Gateway-UI-Package
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-mmsys
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-WMPNSS-Service
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-TerminalServices-Role-Package
2022-11-02 11:43:46, Warning [0x08092b] CSIAgent: Duplicate manifest
identity exists [Link]
Windows-Runtime-Windows-Media
2022-11-02 11:43:47, Warning [0x0803ea] Registry location HCKU\
software\microsoft\accessibility is considered invalid in the current context
2022-11-02 11:43:47, Warning [0x0803ea] Registry location HCKU\
software\microsoft\accessibility is considered invalid in the current context
2022-11-02 11:43:47, Warning [0x0803ea] Registry location HCKU\
software\microsoft\accessibility is considered invalid in the current context
2022-11-02 11:43:47, Warning [0x0803ea] Registry location HCKU\
software\microsoft\accessibility is considered invalid in the current context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location
HKEY_LOCAL_MACHINE\Software\Microsoft\Cellular\Sms\Router is considered invalid in
the current context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location
HKEY_LOCAL_MACHINE\Software\Microsoft\Cellular\Sms\Router is considered invalid in
the current context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SmsRouter\State is considered
invalid in the current context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SmsRouter\State is considered
invalid in the current context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SmsRouter\State is considered
invalid in the current context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SmsRouter\State is considered
invalid in the current context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location
HKEY_LOCAL_MACHINE\Software\Microsoft\Cellular\Sms\Router is considered invalid in
the current context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location
HKEY_LOCAL_MACHINE\Software\Microsoft\Cellular\Sms\Router is considered invalid in
the current context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location
HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Nocontrol\LedAlert [State] is
considered invalid in the current context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location
HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Nocontrol\LedAlert [State] is
considered invalid in the current context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location
HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Nocontrol\LedAlert [Intensity] is
considered invalid in the current context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location
HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Nocontrol\LedAlert [Intensity] is
considered invalid in the current context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location
HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Nocontrol\LedAlert [Period] is
considered invalid in the current context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location
HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Nocontrol\LedAlert [Period] is
considered invalid in the current context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location
HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Nocontrol\LedAlert [DutyCycle] is
considered invalid in the current context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location
HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Nocontrol\LedAlert [DutyCycle] is
considered invalid in the current context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location
HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Nocontrol\LedAlert [CycleCount] is
considered invalid in the current context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location
HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Nocontrol\LedAlert [CycleCount] is
considered invalid in the current context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\
Credential Providers\{8FD7E19C-3BF7-489B-A72C-846AB3678C96}\V2\KnownUsers is
considered invalid in the current context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\
Credential Providers\{8FD7E19C-3BF7-489B-A72C-846AB3678C96}\V2\KnownUsers is
considered invalid in the current context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location HKCU\
Software\Microsoft\TPG\HWRCustomization is considered invalid in the current
context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location HKCU\
Software\Microsoft\TPG\HWRCustomization is considered invalid in the current
context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location HKCU\
Software\Microsoft\Windows\CurrentVersion\Appx\PurgeList is considered invalid in
the current context
2022-11-02 11:43:48, Warning [0x0803ea] Registry location HKCU\
Software\Microsoft\Windows\CurrentVersion\Appx\PurgeList is considered invalid in
the current context
2022-11-02 11:43:48, Info [0x000000] Producing the configuration
file C:\Recovery\OEM\pbr_config.xml
2022-11-02 11:43:48, Error [0x000000] Unreleased mig unit navigator
interface during user release
2022-11-02 11:43:48, Error [0x000000] Unreleased mig unit navigator
interface during user release
2022-11-02 11:43:48, Error [0x000000] Unreleased mig unit navigator
interface during user release
2022-11-02 11:43:48, Error [0x000000] Unreleased mig unit navigator
interface during user release
2022-11-02 11:43:48, Error [0x000000] Unreleased mig unit navigator
interface during user release
2022-11-02 11:43:48, Info [0x000000] Success.[gle=0x00000091]
2022-11-02 11:43:48, Info [0x000000] USMT Completed at
2022/11/02:11:43:48.693[gle=0x00000091]
2022-11-02 11:43:48, Info [0x000000]
----------------------------------- USMT ERROR SUMMARY
-----------------------------------
2022-11-02 11:43:48, Info [0x000000] No error in migration process
is recorded.

Common questions

Powered by AI

The document reveals various challenges encountered during the migration process using USMT, such as user class hive loading errors indicated by 'error: 2' when attempting to load certain paths like C:\Users\Default\AppData\Local\Microsoft\Windows\UsrClass.dat . Additionally, there are multiple warnings of 'Duplicate manifest identity' related to different components such as Microsoft-Windows-Authentication-AuthUI-Component and Microsoft-Windows-MMDeviceAPI . There are also issues with XML formatting, such as 'Invalid xml format' and missing callback entry points, like 'MigXmlHelper.SendServiceControlCode("wlansvc", "128") not found' . Furthermore, registry locations for certain settings, like HKEY_LOCAL_MACHINE\Software\Microsoft\Cellular\Sms\Router, are considered invalid in the current context .

The system's environment described in the document includes hardware details such as it being a Dell Latitude 5490 with an Intel Core i5-8350U CPU and 8GB of total memory . The system runs on Windows 10 OS version 10.0.19045 with a 64-bit architecture . Software-wise, the various entries pertaining to class hives, plugins, registry locations, and installed components like Microsoft Windows MMDeviceAPI and TerminalServices indicate a complex environment possibly supporting extensive user and enterprise functionalities . However, multiple warnings about invalid contexts and duplicate manifest identities suggest potential inconsistencies or configuration issues within this environment .

The migration process begins with the execution of Scanstate.exe using specified command line parameters, indicating the initiation of the migration process and configuration file creation . Detailed warnings and errors are logged, marking various challenges such as 'User class hive loading error' and 'Invalid xml format' . System examination follows to identify migration units, and despite numerous warnings, the process proceeds to success as indicated by final log entries confirming the production of configuration files like C:\Recovery\OEM\pbr_config.xml and final success logs . The process reflects the typical flow of execution, error logging, and final status confirmation within migration operations .

Duplicate manifest identity warnings are significant because they may indicate potential conflicts or redundancies in the system files and components being migrated. These warnings, referring to numerous Microsoft components like Microsoft-Windows-TerminalServices-Gateway-Package and Microsoft-Windows-SecurityCenter-Core , suggest that the migration tool detects multiple identical entries or configurations. This could lead to problems such as inconsistent settings being applied post-migration or redundant files consuming unnecessary storage space . Identifying and resolving these duplications ensures a cleaner, conflict-free migration and optimal system functionality.

Despite the numerous warnings and errors encountered, the document reports a successful completion of the USMT process with an end timestamp of 2022/11/02:11:43:48.693, as indicated by the log entry "Success.[gle=0x00000091]" and the summary stating 'No error in migration process is recorded' . This indicates that the process logic accounts for non-critical warnings and is configured to report successful completion unless there are fatal errors that would impact the final output file or interfere significantly with operation .

Insights from the document suggest that user management is multi-tiered with different roles and permissions . The presence of accounts such as Administrator, Default User, WDAGUtilityAccount, and others, with variations in interactivity and current login status, indicate a structured approach to managing access and actions on the system . The configuration supports scenarios like remote administration or non-interactive background functionalities (WDAGUtilityAccount) while ensuring security by limiting unnecessary administrative access (Guest, Default User). Such organization reflects a balance between functionality and security, pivotal for effective user management in corporate settings .

The document describes the system as running OS version 10.0.19045 with a 64-bit architecture, manufactured by Dell on a Latitude 5490 model . It lists several user accounts on the system: Default User, WDAGUtilityAccount, Administrator, Guest, and DefaultAccount, with varying levels of administrative privileges and login status . The Administrator is the primary account with administrative rights and is logged on interactively, while other accounts have no admin rights and are not logged on interactively .

The document illustrates that registry-related warnings, such as invalid contexts for registry locations like HCKU\ software\microsoft\accessibility, are frequent during migration . These are consistently logged with warnings indicating their non-critical nature in terms of process continuation. The repetition of these warnings suggests that while they do not halt the migration, they may signify necessary post-migration checks or corrections to ensure all registry settings align with expected configurations for optimal performance and stability .

The 'invalid XML format' errors, including missing mandatory attributes like 'script' and callback entry points such as 'MigXmlHelper.SendServiceControlCode("wlansvc", "128") not found' , suggest critical issues in the configuration files used by the migration process. These errors likely hinder the process's ability to execute certain configure or update scripts essential for successful migration. This could result in incomplete data transfer, system inconsistencies, or functionality disruptions in migrated systems, demanding thorough debugging and correction of XML configurations before proceeding with migrations .

BIOS information, such as the version and release date (1.18.0, released on 20210910), plays a critical role in understanding the migration system's capabilities. It indicates the basic system firmware, affecting hardware initialization and potentially influencing compatibility with newer software and migration tools. BIOS settings might also affect security protocols during migration. The document's inclusion of BIOS details allows assessing whether system updates might be necessary pre-migration to ensure compatibility and avoid migration disruptions due to outdated firmware .

You might also like