Jump to content


miiike

Failure on Request State Store

Recommended Posts

I continue on getting the following error when trying to request a state store in a capture task sequence.

 

The error that I am seeing on the SCCM when running the task sequence from the computer.

 

SMS State Migration Point failed to read the SignedSerializedSMPKey from the registry on computer SCCM. Possible reasons are SMP certificate is not yet signed by Site Server.

 

 

Additionally the SMSTS.log from the client has the following

 

Received 1298 byte response.	OSDSMPClient	4/7/2010 3:47:07 PM	1256 (0x04E8)
SMP request to "SCCM" failed with error: E_SMPERROR_ENCRYPTKEY_EMPTY (103)	OSDSMPClient	4/7/2010 3:47:07 PM	1256 (0x04E8)
0, HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2564)	OSDSMPClient	4/7/2010 3:47:07 PM	1256 (0x04E8)
ClientKeyRequestToSMP failed (0x80004005).	OSDSMPClient	4/7/2010 3:47:07 PM	1256 (0x04E8)
ClientKeyRequestToSMP( m_sSMPServer, m_uPort, m_ClientInfo, sKeyInfo ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\smpclient.cpp,1743)	OSDSMPClient	4/7/2010 3:47:07 PM	1256 (0x04E8)
ClientRequestToSMP::DoRequest failed. error = (0x80004005).	OSDSMPClient	4/7/2010 3:47:07 PM	1256 (0x04E8)
Request to SMP 'SCCM' failed with error (Code 0x80004005). Trying next SMP.	OSDSMPClient	4/7/2010 3:47:07 PM	1256 (0x04E8)
FALSE, HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\smpclient.cpp,1698)	OSDSMPClient	4/7/2010 3:47:07 PM	1256 (0x04E8)
Failed to find an SMP that can serve request after trying 4 attempts.	OSDSMPClient	4/7/2010 3:47:07 PM	1256 (0x04E8)
pClientRequestToSMP->Execute(migInfoFromMP.saSMPs), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2713)	OSDSMPClient	4/7/2010 3:47:07 PM	1256 (0x04E8)
ExecuteCaptureRequestSMP failed (0x80004005).	OSDSMPClient	4/7/2010 3:47:07 PM	1256 (0x04E8)
ExecuteCaptureRequestToSMP(migInfoFromMP), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2755)	OSDSMPClient	4/7/2010 3:47:07 PM	1256 (0x04E8)
ExecuteCaptureRequest failed (0x80004005).	OSDSMPClient	4/7/2010 3:47:07 PM	1256 (0x04E8)
ExecuteCaptureRequest(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\osdsmpclient\main.cpp,72)	OSDSMPClient	4/7/2010 3:47:07 PM	1256 (0x04E8)
OSDSMPClient finished: 0x00004005	OSDSMPClient	4/7/2010 3:47:07 PM	1256 (0x04E8)
Process completed with exit code 16389	TSManager	4/7/2010 3:47:07 PM	3532 (0x0DCC)
!--------------------------------------------------------------------------------------------!	TSManager	4/7/2010 3:47:07 PM	3532 (0x0DCC)
Failed to run the action: Request State Store. 
Unknown error (Error: 00004005; Source: Unknown)	TSManager	4/7/2010 3:47:07 PM	3532 (0x0DCC)

 

This is SCCM SP2 R2 on a Server 2008 R2. I have already checked all pre-reqs for WebDav and IIS, have removed and reinstalled the State Store (several times), and have run a Site Reset with the Network Access Acccount and the Admin account.

 

It seems that I may just be missing some sort of registry key? I thought doing a Site Reset would fix this but no go.

Share this post


Link to post
Share on other sites


what are the share permissions on the SMP folder itself, perhaps they are too restrictive ?

Share this post


Link to post
Share on other sites

what are the share permissions on the SMP folder itself, perhaps they are too restrictive ?

What permissions should it have?

 

I have Authenticaed Users with a Speical permission of Read Attributes. Local Service, Administrators and System have Full control.

Share this post


Link to post
Share on other sites

give everyone full access as a test just to rule out ntfs and share permissions

Share this post


Link to post
Share on other sites

give everyone full access as a test just to rule out ntfs and share permissions

Nope. Still gettin the same errors.

 

Oh, I also verified that neither the server or the client has KB 974571 on it. Although the server did at one time.

Share this post


Link to post
Share on other sites

Nope. Still gettin the same errors.

 

Oh, I also verified that neither the server or the client has KB 974571 on it. Although the server did at one time.

Any ideas? I'm at a loss :/

Share this post


Link to post
Share on other sites

can i see your task sequence ? export it to xml and upload it here

Share this post


Link to post
Share on other sites

can i see your task sequence ? export it to xml and upload it here

Here you go.

 

Should there not be some registry key in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SMP\ for the SMP somewhere?

 

I've scanned every directory under there and don't see any key that looks like it's for the SMP. Maybe this is my problem?

 

I've also removed the SMP, deleted the SMP certificate from the Certificate snap-in, then reinstalled the SMP and let the cert get regenerated and no luck with that either.

capture.xml

Share this post


Link to post
Share on other sites

Here you go.

 

Should there not be some registry key in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SMP\ for the SMP somewhere?

 

I've scanned every directory under there and don't see any key that looks like it's for the SMP. Maybe this is my problem?

 

I've also removed the SMP, deleted the SMP certificate from the Certificate snap-in, then reinstalled the SMP and let the cert get regenerated and no luck with that either.

 

anyone solved this problem? we have the same issue. :(

Share this post


Link to post
Share on other sites

update thread please, with solution, 3 of ye had it surely one of ye could bother to post resolution.

Share this post


Link to post
Share on other sites

Managed to get this issue resolved.

 

I used a different copy of Win7, also Enterprise,Volume License,x64,SP1.

 

Not sure what the difference is, one works and the other doesn't.

Share this post


Link to post
Share on other sites

Hello,

I apologize for posting on an old topic, but this fits the issue I have been having recently. It sounds like you got the issue resolved however I am unable to resolve mine.

 

I am trying to run a Re-Image task sequence (Windows 7 to Windows7). I have multuple error codes in the smsts.log file. The main one that I believe is causing the issues is "Failed to run the action: Request State Store. The request is not supported. Error: 80070032" But I also have the 80004005 error. Attached is my task sequence and the log file. Hopefully you can provide some insight because I am at a loss.

 

The SMP storage has "everyone" set to full control right now as a test, therefore I know it's not a SMP permissions issue.

 

Thanks in advance for any help, it's much appreciated.

smsts.log

Re-Image Task Sequence.xml

Share this post


Link to post
Share on other sites

Although not necessarily a solution, I have noticed that checking the "When no local distribution point is available, use a remote distribution point." box under the Distribution Points tab for the deployment of the task sequence resolves the error that no SMPs are found.

 

My initial thought is to be careful with that check box though, as you may find your systems using a DP that is across a slow link.

Share this post


Link to post
Share on other sites

Although not necessarily a solution, I have noticed that checking the "When no local distribution point is available, use a remote distribution point." box under the Distribution Points tab for the deployment of the task sequence resolves the error that no SMPs are found.

 

My initial thought is to be careful with that check box though, as you may find your systems using a DP that is across a slow link.

 

Thanks, Devtrends! I did 2 changes:

 

Set the option you suggest about "When no local distribution point is available, use a remote distribution point." and also I set Full Control NTFS permission to the "Local Service" account to the folder set as the backup/restore folder. Then it all began working.

 

As I did 2 changes, I am not sure if both are needed or just 1 of them, but anyway, this solved it and I don't want to touch now to re-test. :)

 

Regards,

 

Jose Angel Rivera

Share this post


Link to post
Share on other sites

 

Thanks, Devtrends! I did 2 changes:

 

Set the option you suggest about "When no local distribution point is available, use a remote distribution point." and also I set Full Control NTFS permission to the "Local Service" account to the folder set as the backup/restore folder. Then it all began working.

 

As I did 2 changes, I am not sure if both are needed or just 1 of them, but anyway, this solved it and I don't want to touch now to re-test. :)

 

Regards,

 

Jose Angel Rivera

I've had similar issue. Adding LOCAL SERVICE with Full Control to the store fixes it for me, but every 24 hours SCCM resets the permissions.

Share this post


Link to post
Share on other sites

Folks, I dug deeper in the issue.

My Client is on a subnet that is properly in the boundary group of the server below.

So,

Client : 192.168.51.150
SMP: 192.168.51.50

These are properly bordered in the SMP role, but still the smsts.log fails with:

Number of local SMP's = 0    OSDSMPClient    23/02/2018 03:39:40    2080 (0x0820)

 

SMP Location Info = 
<SMPLocationInfo>
    <Sites>
        <Site>
            <SMPSite SiteCode="XX1" MasterSiteCode="XX1" SiteLocality="REMOTE">
            <LocationRecords>
                <LocationRecord>
                    <ADSite Name="SITE1"/>
                        <IPSubnets>
                            <IPSubnet Address="192.168.51.0"/>
                            <IPSubnet Address=""/>
                        </IPSubnets>
            <ServerName>http://server.company.intern.com</ServerName>
                </LocationRecord>
            </LocationRecords>
            </SMPSite>
        </Site>
    </Sites>
</SMPLocationInfo>

 

So, I changed the Task Sequence to be allowed to fallback on a Remote DP and that worked so this is the root of the problem.

Possible causes:

a. The client is in two Boundary Groups, one via the AD Site and one via the IP Subnet 
b. Dual network interfaces exist on the client so it gets confused
 

I will look into both issues.

 

--

Alex

Share this post


Link to post
Share on other sites

And yes, this is now resolved.

On the Boundary Group, I had only added the local DP (which carries the SMP role as well) and lives in the same subnet.
I hadn't added the main Site System which is over WAN and is holding the Primary Site server role and the MP.
I don't know if this is the proper way to set this up, but this has now solved the problem.

BUT, if the secondary host (the Primary Site Server) is also a DP and SMP, then the client could possibly choose that one as a DP?

Any help here appreciated.

 

Alex

Site-System-Servers.png

Share this post


Link to post
Share on other sites

I found the following that happens on 1610 and seems like a bug which Microsoft acknowledged.

https://social.technet.microsoft.com/Forums/en-US/7bfdd65e-d81f-447c-a132-3df9f2b296c7/client-fails-to-request-user-state-store-no-local-smp-found?forum=configmanagerosd

Removing the Failback boundary group from the Boundary, solves the problem.

Just tested it and verified that this bug is still there.

--

Alex

Share this post


Link to post
Share on other sites

Hi all;

I was having this issue as well so I started googling every error in the smsts.log file.   I came up with this: https://social.technet.microsoft.com/Forums/ie/en-US/0ef77026-cd92-4453-b32d-3833fcf2d0b8/request-state-store-problems-with-windows-10-usmt?forum=configmanagergeneral&prof=required .

Running the PowerShell command fixed my problem.  A few days later I encountered a second computer that was doing something similar and again I ran this script and it worked.

Hope it helps.

WD

Share this post


Link to post
Share on other sites

Any concrete solution for this?

this issue still persist on sccm cb 1806.

I can confirm that this is being caused by the 'failover relationships' set for a boundary group.

smp is set to 'local' when the option for 'failover relationships' is disabled.

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...