TechTalkz.com Logo Ask the Experts!

Go Back   TechTalkz.com Technology & Computer Troubleshooting Forums > Tech Support Archives > Microsoft > Windows Deployment

USMT: Return Code 12

Windows Deployment

 
 
Thread Tools Display Modes
Unread 28-11-2007, 10:26 AM   #1
Skye Sands
Guest
 
Posts: n/a
USMT: Return Code 12

When deploying a WinXP wim file I created on a Dell Optiplex 170L to a Dell
Optiplex GX 260 both with HAL AACPI, I receive an error when it attempts to
run the ScanState command. Though when the image was deployed to the
Optiplex 170L the error did not occur.

In the USMTCapture.log file located on the GX260’s HD at
c:\minint\smsosd\osdlogs\ it states the following errors.

Warning [0x08040b] State data store failed calling
CoInitializeEx in apartment-threaded mode. (hr = 0x80010106)

Info [0x08087c] SMI engine is not available on this system

Warning [0x08040c] Failed to create SMI engine

Info [0x08040e] State data store is NOT available.

Warning [0x080262] GAC data store failed calling
CoInitializeEx in apartment-threaded mode. (hr = 0x80010106)

Warning [0x08066d] GAC data store: mscoree.dll is not found.
(hr = 0x0000007E)

Info [0x0803b4] COnlineWinNTPlatform:
ComputerName=MININT-L8GASU57

Error [0x0802fa] MigStartUp caught exception: class
Mig:evErrorException: Win32ErrorException: Error(2), Could not find
PROGRAMFILES registry value. This is a critical error..

void __thiscall Mig::CPlatform::BuildSystemEnvironment_NT(class
Mig::IDataStore *,class Mig::CEnvironment *,const class UnBCL::Version &)

Info [0x000000] Leaving MigStartUp method

Error [0x000000] MigStartUp failed with MIGSTATUS 0x4.

Info [0x000000] MIGSTATUS 0x4 means 'MIGSTATUS_EXCEPTION'

Error [0x000000] Unable to start the migration engine
successfully

Error [0x000000] USMT is unable to complete successfully.

Error [0x000000] Internal Error: USMT was unable to start
migration. If you continue to receive this error, contact Customer Service
and Support (CSS).

Info [0x000000] Please see the log file for more details.

Info [0x000000] USMT error Code (status) = 12



The directory specified as the user backup location has been created by OSD
\\sms-distro\userdate\%computername%\USMT the xpmarker.txt has been created
as well, though no usmt.mig was created at all which generally occurs before
the first reboot of the target machine. Any assistance would be very helpful.

Again note that deployment with the exact same Advertisement unchanged
deployed %100 successfully to the model machine the WIM file was built on.

Thank you for you time,

Skye Sands
 
Unread 28-11-2007, 10:26 AM   #2
Tim Mintner (MS)
Guest
 
Posts: n/a
RE: USMT: Return Code 12

Hi Skye,

Can you give a little bit more background on this problems? Are you using
SMS 2003 OSD or SCCM 2007 Beta? Also are you using BDD or just using the
USMT commands nativiely inside of SMS OSD.

Thanks,

Tim

"Skye Sands" wrote:

> When deploying a WinXP wim file I created on a Dell Optiplex 170L to a Dell
> Optiplex GX 260 both with HAL AACPI, I receive an error when it attempts to
> run the ScanState command. Though when the image was deployed to the
> Optiplex 170L the error did not occur.
>
> In the USMTCapture.log file located on the GX260’s HD at
> c:\minint\smsosd\osdlogs\ it states the following errors.
>
> Warning [0x08040b] State data store failed calling
> CoInitializeEx in apartment-threaded mode. (hr = 0x80010106)
>
> Info [0x08087c] SMI engine is not available on this system
>
> Warning [0x08040c] Failed to create SMI engine
>
> Info [0x08040e] State data store is NOT available.
>
> Warning [0x080262] GAC data store failed calling
> CoInitializeEx in apartment-threaded mode. (hr = 0x80010106)
>
> Warning [0x08066d] GAC data store: mscoree.dll is not found.
> (hr = 0x0000007E)
>
> Info [0x0803b4] COnlineWinNTPlatform:
> ComputerName=MININT-L8GASU57
>
> Error [0x0802fa] MigStartUp caught exception: class
> Mig:evErrorException: Win32ErrorException: Error(2), Could not find
> PROGRAMFILES registry value. This is a critical error..
>
> void __thiscall Mig::CPlatform::BuildSystemEnvironment_NT(class
> Mig::IDataStore *,class Mig::CEnvironment *,const class UnBCL::Version &)
>
> Info [0x000000] Leaving MigStartUp method
>
> Error [0x000000] MigStartUp failed with MIGSTATUS 0x4.
>
> Info [0x000000] MIGSTATUS 0x4 means 'MIGSTATUS_EXCEPTION'
>
> Error [0x000000] Unable to start the migration engine
> successfully
>
> Error [0x000000] USMT is unable to complete successfully.
>
> Error [0x000000] Internal Error: USMT was unable to start
> migration. If you continue to receive this error, contact Customer Service
> and Support (CSS).
>
> Info [0x000000] Please see the log file for more details.
>
> Info [0x000000] USMT error Code (status) = 12
>
>
>
> The directory specified as the user backup location has been created by OSD
> \\sms-distro\userdate\%computername%\USMT the xpmarker.txt has been created
> as well, though no usmt.mig was created at all which generally occurs before
> the first reboot of the target machine. Any assistance would be very helpful.
>
> Again note that deployment with the exact same Advertisement unchanged
> deployed %100 successfully to the model machine the WIM file was built on.
>
> Thank you for you time,
>
> Skye Sands

 
Unread 28-11-2007, 10:26 AM   #3
Skye Sands
Guest
 
Posts: n/a
RE: USMT: Return Code 12

Well I have found my resolution. This error was being caused because the
MiniNT folder still existed with the OSD log files in it.

If I removed that folder all went through fine. Thank you for your
response. On to the next problem.

Skye

"Tim Mintner (MS)" wrote:

> Hi Skye,
>
> Can you give a little bit more background on this problems? Are you using
> SMS 2003 OSD or SCCM 2007 Beta? Also are you using BDD or just using the
> USMT commands nativiely inside of SMS OSD.
>
> Thanks,
>
> Tim
>
> "Skye Sands" wrote:
>
> > When deploying a WinXP wim file I created on a Dell Optiplex 170L to a Dell
> > Optiplex GX 260 both with HAL AACPI, I receive an error when it attempts to
> > run the ScanState command. Though when the image was deployed to the
> > Optiplex 170L the error did not occur.
> >
> > In the USMTCapture.log file located on the GX260’s HD at
> > c:\minint\smsosd\osdlogs\ it states the following errors.
> >
> > Warning [0x08040b] State data store failed calling
> > CoInitializeEx in apartment-threaded mode. (hr = 0x80010106)
> >
> > Info [0x08087c] SMI engine is not available on this system
> >
> > Warning [0x08040c] Failed to create SMI engine
> >
> > Info [0x08040e] State data store is NOT available.
> >
> > Warning [0x080262] GAC data store failed calling
> > CoInitializeEx in apartment-threaded mode. (hr = 0x80010106)
> >
> > Warning [0x08066d] GAC data store: mscoree.dll is not found.
> > (hr = 0x0000007E)
> >
> > Info [0x0803b4] COnlineWinNTPlatform:
> > ComputerName=MININT-L8GASU57
> >
> > Error [0x0802fa] MigStartUp caught exception: class
> > Mig:evErrorException: Win32ErrorException: Error(2), Could not find
> > PROGRAMFILES registry value. This is a critical error..
> >
> > void __thiscall Mig::CPlatform::BuildSystemEnvironment_NT(class
> > Mig::IDataStore *,class Mig::CEnvironment *,const class UnBCL::Version &)
> >
> > Info [0x000000] Leaving MigStartUp method
> >
> > Error [0x000000] MigStartUp failed with MIGSTATUS 0x4.
> >
> > Info [0x000000] MIGSTATUS 0x4 means 'MIGSTATUS_EXCEPTION'
> >
> > Error [0x000000] Unable to start the migration engine
> > successfully
> >
> > Error [0x000000] USMT is unable to complete successfully.
> >
> > Error [0x000000] Internal Error: USMT was unable to start
> > migration. If you continue to receive this error, contact Customer Service
> > and Support (CSS).
> >
> > Info [0x000000] Please see the log file for more details.
> >
> > Info [0x000000] USMT error Code (status) = 12
> >
> >
> >
> > The directory specified as the user backup location has been created by OSD
> > \\sms-distro\userdate\%computername%\USMT the xpmarker.txt has been created
> > as well, though no usmt.mig was created at all which generally occurs before
> > the first reboot of the target machine. Any assistance would be very helpful.
> >
> > Again note that deployment with the exact same Advertisement unchanged
> > deployed %100 successfully to the model machine the WIM file was built on.
> >
> > Thank you for you time,
> >
> > Skye Sands

 
Unread 28-11-2007, 10:26 AM   #4
Tim Mintner (MS)
Guest
 
Posts: n/a
RE: USMT: Return Code 12

Well I love those type of problems.

Please let us know if you run into any additional problems.

"Skye Sands" wrote:

> Well I have found my resolution. This error was being caused because the
> MiniNT folder still existed with the OSD log files in it.
>
> If I removed that folder all went through fine. Thank you for your
> response. On to the next problem.
>
> Skye
>
> "Tim Mintner (MS)" wrote:
>
> > Hi Skye,
> >
> > Can you give a little bit more background on this problems? Are you using
> > SMS 2003 OSD or SCCM 2007 Beta? Also are you using BDD or just using the
> > USMT commands nativiely inside of SMS OSD.
> >
> > Thanks,
> >
> > Tim
> >
> > "Skye Sands" wrote:
> >
> > > When deploying a WinXP wim file I created on a Dell Optiplex 170L to a Dell
> > > Optiplex GX 260 both with HAL AACPI, I receive an error when it attempts to
> > > run the ScanState command. Though when the image was deployed to the
> > > Optiplex 170L the error did not occur.
> > >
> > > In the USMTCapture.log file located on the GX260’s HD at
> > > c:\minint\smsosd\osdlogs\ it states the following errors.
> > >
> > > Warning [0x08040b] State data store failed calling
> > > CoInitializeEx in apartment-threaded mode. (hr = 0x80010106)
> > >
> > > Info [0x08087c] SMI engine is not available on this system
> > >
> > > Warning [0x08040c] Failed to create SMI engine
> > >
> > > Info [0x08040e] State data store is NOT available.
> > >
> > > Warning [0x080262] GAC data store failed calling
> > > CoInitializeEx in apartment-threaded mode. (hr = 0x80010106)
> > >
> > > Warning [0x08066d] GAC data store: mscoree.dll is not found.
> > > (hr = 0x0000007E)
> > >
> > > Info [0x0803b4] COnlineWinNTPlatform:
> > > ComputerName=MININT-L8GASU57
> > >
> > > Error [0x0802fa] MigStartUp caught exception: class
> > > Mig:evErrorException: Win32ErrorException: Error(2), Could not find
> > > PROGRAMFILES registry value. This is a critical error..
> > >
> > > void __thiscall Mig::CPlatform::BuildSystemEnvironment_NT(class
> > > Mig::IDataStore *,class Mig::CEnvironment *,const class UnBCL::Version &)
> > >
> > > Info [0x000000] Leaving MigStartUp method
> > >
> > > Error [0x000000] MigStartUp failed with MIGSTATUS 0x4.
> > >
> > > Info [0x000000] MIGSTATUS 0x4 means 'MIGSTATUS_EXCEPTION'
> > >
> > > Error [0x000000] Unable to start the migration engine
> > > successfully
> > >
> > > Error [0x000000] USMT is unable to complete successfully.
> > >
> > > Error [0x000000] Internal Error: USMT was unable to start
> > > migration. If you continue to receive this error, contact Customer Service
> > > and Support (CSS).
> > >
> > > Info [0x000000] Please see the log file for more details.
> > >
> > > Info [0x000000] USMT error Code (status) = 12
> > >
> > >
> > >
> > > The directory specified as the user backup location has been created by OSD
> > > \\sms-distro\userdate\%computername%\USMT the xpmarker.txt has been created
> > > as well, though no usmt.mig was created at all which generally occurs before
> > > the first reboot of the target machine. Any assistance would be very helpful.
> > >
> > > Again note that deployment with the exact same Advertisement unchanged
> > > deployed %100 successfully to the model machine the WIM file was built on.
> > >
> > > Thank you for you time,
> > >
> > > Skye Sands

 
 

Thread Tools
Display Modes



< Home - Windows Help - MS Office Help - Hardware Support >


New To Site? Need Help?

All times are GMT. The time now is 11:39 PM.


vBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO
Copyright © 2005-2013, TechTalkz.com. All Rights Reserved - Privacy Policy
Valid XHTML 1.0 Transitional