PENDING Updates scan completion received, result = 0x80240438

[gafoorgk]

Hi,

I need help on a strange SCCM issue. I got 4 VLANs as;

1. VLAN1 - Servers where SCCM.domain.com is sitting (Configuration Manager 2010 running on Win2016).
2. VLAN2 - Set of domain-joined Win10 clients.
3. VLAN3 - Set of non-domain-joined (workgroup) Win2012R2 servers
4. VLAN4 - Set of non-domain joined (workgroup) Win2019 servers

Software deployment, updates deployment, etc. works well on VLAN1, VLAN2 and VLAN3. But updates deployment do not work on VLAN4. Following are the extract from related log files;

UpdateHandler.log

Successfully initiated scan. UpdatesHandler 12/21/2020 11:24:50 PM 12980 (0x32B4)
Successfully initiated scan. UpdatesHandler 12/21/2020 11:24:50 PM 11360 (0x2C60)
Updates scan completion received, result = 0x80240438. UpdatesHandler 12/21/2020 11:24:54 PM 11360 (0x2C60)
Updates scan completion received, result = 0x80240438. UpdatesHandler 12/21/2020 11:24:59 PM 11300 (0x2C24)
Updates scan completion received, result = 0x80240438. UpdatesHandler 12/21/2020 11:25:03 PM 12980 (0x32B4)

UpdatesDeployment.log

Job error (0x80240438) received for assignment ({BFCA7E3B-5C27-4D43-BA59-48E6701FBB60}) action UpdatesDeploymentAgent 12/21/2020 11:26:07 PM 12980 (0x32B4)
Updates will not be made available UpdatesDeploymentAgent 12/21/2020 11:26:07 PM 12980 (0x32B4)
CUpdatesAssignment::RaiseStateMessage, ulMessageId = -1073730068 UpdatesDeploymentAgent 12/21/2020 11:26:07 PM 12980 (0x32B4)
CUpdatesAssignment::RaiseStateMessage, hrError = -2145123272 UpdatesDeploymentAgent 12/21/2020 11:26:07 PM 12980 (0x32B4)
Raised assignment (TopicID) ({BFCA7E3B-5C27-4D43-BA59-48E6701FBB60}) state message successfully. TopicType = Evaluate, StateId = 3, StateName = ASSIGNMENT_EVALUATE_FAILED, StateCriticality = 1 UpdatesDeploymentAgent 12/21/2020 11:26:07 PM 12980 (0x32B4)

Here are the steps I already tried;

1. Made sure SCCM.domain.com is pointing to the right IP in hosts file
2. I tried browsing https://SCCM.domain.com:8531/ClientWebService/client.asmx from all VLANs
   It returns some data from VLAN1, 2 & 3. But it throws error from VLAN4.
   Checked all firewalls on both ends and logs are saying traffics are received very well.
   Tried disabling firewall from both end as well and made sure no f/w in between, but the result is same.
3. Tried running 'netsh winhttp reset proxy' though it is direct connection (no proxy) - just hitting the wall
   Still same issue.
4. Re-installed the client and restarted servers.
   Still same issue.
5. Checked the boundary settings. VLAN4 is also added there and is a member of only boundary group, where other VLANs are also members.
6. Stopped Windows Update in one of the server in VLAN4, cleaned folder C:\Windows\SoftwareDistribution\DataStore, started service again, but issue remains.

Is there anything else I need to try or am I missing anything here?

Thanks in advance

 

[Prajwal Desai]

Does the machines in VLAN4 get the application deployments ?. Are the clients showing as active and receiving the policy from MP regularly ?.

 

[gafoorgk]

Yes Prajwal, the computers in VLAN4 do get application deployment, gets client updated whenever SCCM is updated, policies are getting updated and these computers are showing active in SCCM. Everything looks same as in the computers in VLAN3.

Only issue is that software update scan returns error code and is not happening, thus they're not installed.

When I tried browsing https://SCCM.domain.com:8531/ClientWebService/client.asmx, I monitored the traffic. I do see SCCM getting request and responding just like for any other machines, but then I don't know what happens.

 

[gafoorgk]

Does the machines in VLAN4 get the application deployments ?. Are the clients showing as active and receiving the policy from MP regularly ?.

Hi,

The issue is resolved after using few network traffic monitoring tools. Issue was that network team recently put this specific VLAN in DMZ, which introduced one more firewall in the middle. It was letting the traffic reach SCCM, but response was somehow dying in the firewall itself. Informed network team and they resolved the issue.

Thanks,