Fix: ConfigMgr 2007 OSD deployments fail with error: 0x800700B7 in loadstate.log

Fix: ConfigMgr 2007 OSD deployments fail with error: 0x800700B7 in loadstate.log

  • Comments 2
  • Likes

toolsignHi everyone, David Smith here.  I’m a Senior Support Engineer here on the ConfigMgr team and I recently came across an interesting issue that I thought might be worth a mention here on our blog.  In this case, an Operating System Deployment (OSD) using System Center Configuration Manager 2007 SP2 would fail and in the loadstate.log file we would see the following:

2011-12-13 13:40:19, Error [0x080000] There was an error while calling CreateProfile. Error: 0x800700B7
2011-12-13 13:40:19, Error [0x000000] Error 0 creating profile for user domain\user1 (source user domain\user1)
2011-12-13 13:40:19, Info [0x000000] Failed.[gle=0x00000006]
2011-12-13 13:40:19, Info [0x000000] A Windows Win32 API error occurred
Windows error 0 description: The operation completed successfully.[gle=0x00000006]
2011-12-13 13:40:19, Info [0x000000] USMT Completed at 2011/12/13:13:40:19.782[gle=0x00000057]

NOTE In your log you will see an actual User ID. 

The issue would happen in a refresh scenario where, for example, you might be migrating from Windows XP to Windows 7 and repurposing the old hardware.  It should also happen in all version of ConfigMgr 2007, not just SP2.

After doing a little troubleshooting we found that the WIM image contained a partial user profile named domain\user1, meaning that the reference computer had been joined to the domain and user1 had logged onto the machine.  In this situation, when we refreshed the computer of domain\user1 it would fail with the above error but when we refreshed the computer of domain\user2 it would succeed.

To fix this issue, we rebuilt the reference computer ensuring that no partial user profiles existed, and then captured it again creating a new WIM image.  Once we did this everything worked as expected.

To ensure that no profiles exist you should clean out all profiles through the control panel and then remove whatever is left in the registry key below:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

Hope this helps!

David Smith | Senior Support Engineer

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

App-V Team blog: http://blogs.technet.com/appv/
AVIcode Team blog: http://blogs.technet.com/b/avicode
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
OOB Support Team blog: http://blogs.technet.com/oob/
Opalis Team blog: http://blogs.technet.com/opalis
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
SCMDM Support Team blog: http://blogs.technet.com/mdm/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • 7777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777777

  • Hi,

    I have run into this very same issue, but unfortunately I do not have the ability to rebuild the original XP machine from scratch, as there was a lot of user data involved. Does anyone know how to recover the files from the .mig?