Restore User State failed – 00004005
Posted by Jarvis on May 8, 2008
I’ve been troubleshooting an issue with Computer Associations in SCCM. The issue that I have seen multiple times is that the state capture appears to run successfully…there is a USMT file of the size that I expect in the State Migration Point folder. However when I run the state restore, it fails very early in the process. As it is requesting the state store, it fails out with a message that states:
Task Sequence: Restore User State has failed with the error code (0×00004005). Please contact your system administrator or helpdesk operator.
Well…I am my system administrator, and this error is bothering me!
Once I dig into the smsts.log file, I see these errors:
SMP request to “SCCM.fqdn” failed with error: E_SMPERROR_RESTORING_CLIENTID_NOT_FOUND (207)
Request to SMP ‘SCCM.fqdn’ failed with error (Code 0×80004005). Trying next SMP.
FALSE, HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\smpclient.cpp,1698)
Failed to find an SMP that can serve request after trying 4 attempts.
pClientRequestToSMP->Execute(migInfoFromMP.saSMPs), HRESULT=80004005 …
ExecuteRestoreRequestToSMP failed (0×80004005).
ExecuteRestoreRequest(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\main.cpp,80)
OSDSMPClient finished: 0×00004005
Process completed with exit code 16389
I’m taking a wild guess here…and I could be wrong…I’ll be posting on Technet and updating this post when I find out more. My guess is that this is tied to when I created the computer association linking the old computer with the new one. This is a side-by-side migration…replacing a user’s old computer with a new one. I ran the capture TS on her old computer. The errors above are on her new one. I am wondering if it matters when the computer association linking the old to the new is created. I forgot to create that association until after the capture TS had already run on her old computer. That capture TS created an “in-place” association for her old computer. After the capture was complete, I created a side-by-side association. Both of these are tied to the same state location.
I may be completely wrong here (certainly wouldn’t be the first time), but is there anything that the State Capture TS puts into what it uploads that restricts what it will restore to? I.E. does the side-by-side association need to exist before running the Capture TS for it to be able to restore to the new computer?
Another possibility that will be determined when I get the smsts.log off of the old computer (laptop…user has it off site today) is if it fits into the discussion of this thread…where the status message is not received by the site server that the capture process is complete…so the state is not recorded as completed.
[Update: I got the log file from the user this morning. It does fit that thread above. I'm posting to TechNet to see if I can get an answer as to how to automatically resolve this issue. I've seen it happen way too frequently.]
Jon Lambert said
This error usually occurs when the computer association is created AFTER the source machine had it’s user state backed up. Computer associations must be made before user state is ‘stored’. Hope this helps.
Jarvis said
Thanks for that comment Jon. That seems to confirm my original “wild guess” that I had earlier dismissed…and had crossed out in the post until this morning.