SOLVED Failed to get information for MP Error 80072f78

Status
Not open for further replies.

Davidsig

Member
7
0
1
Hi.
We have a problem on 2 sites where machines boot to winpe and then after preparing network they reboot.
This behavior is only on the remote locations where there are distribution points. this works fine in the main location where the site server is. It would be nice to have another set of eyes look at the attached logs to see what I am missing.

Thanks.
 

Attachments

  • smsts.log
    34.2 KB · Views: 12
Solution
Just wanted to update. The problem has been solved. Turned out the network team did not know of/or thought it did not matter bur there was a network layer antivirus protection enabled from the main office out to the sites where the distribution points ware.
So I have been chasing a ghost for weeks trying to figure out a problem the network team did not know about.

but hey, I mastered pxe boot while on it so I guess that counts for something.... (and never belive the network team when they try to tell you it's not the network, it's always the network ;) )

Thank you for your help, you can mark this thread as solved.

Davíð
OP
Davidsig

Davidsig

Member
7
0
1
Thanks Prajwal.
I am redistributing the os packages now will then do the other packages when that finishes.
(redistributing would be the way to go or do I have to delete the content first and then distribute again ?)

I am fairly confident after much testing that this is a pxe problem but still I see the same error in the pxe log on the DP regarding failed winhttp.
Yesterday I tried removing pxe role and enable again but no luck. There is this error on the dp smspxe log that strikes me as something that is not right and is similar to smsts.log. It appears over and over again, sometimes with less than a minute between...:

smspxe.log says:
failed to receive response with winhttp; 80072f78
Failed to get information for MP: http://sccm.servername.com. 80072f78.
 
OP
Davidsig

Davidsig

Member
7
0
1
One quick obsrevation, I checked for a site bindings for https on the default site on the mp and there is no certifficate selected ther for https. could this be the provlem ?
 
OP
Davidsig

Davidsig

Member
7
0
1
I'm still struggling with this issue.

Do you have any way to troubleshoot why the communication brakes down with the MP when the machine is in winpe ?

I belive that to be the issue from this section in the smsts.log:
upload_2017-6-7_12-47-56.png

Thanks.
Davíð
 

Prajwal Desai

Forum Owner
Staff member
3,637
441
183
0x80072F78 - ERROR_HTTP_INVALID_SERVER_RESPONSE - The server response could not be parsed. Meaning that something between the client and MP site breaks this response and this could be firewalls. If there is any Antivirus and IPS protection, try disabling it and see if it works.

if the above one did not work, try the steps mentioned in the below screenshot ?.

upload_2017-6-7_21-2-15.png
 
OP
Davidsig

Davidsig

Member
7
0
1
I have tried turning off the antivirus on the server as well as ask the network guy if there is anything inbetween the server and the client that can do something with the packet. he is absolutely sure that there is no such thing.
Checked if the sms agent host was running and it was, for good measure i restarted the service and tested again but all was the same.

one thing that I am wondering, I see that spiceworks desktop webserver is running on the distribution point. (not the MP) can this be the problem ?

If not, then I am open to ideas on what to try next.

Thanks.
Davíð
 
OP
Davidsig

Davidsig

Member
7
0
1
Just wanted to update. The problem has been solved. Turned out the network team did not know of/or thought it did not matter bur there was a network layer antivirus protection enabled from the main office out to the sites where the distribution points ware.
So I have been chasing a ghost for weeks trying to figure out a problem the network team did not know about.

but hey, I mastered pxe boot while on it so I guess that counts for something.... (and never belive the network team when they try to tell you it's not the network, it's always the network ;) )

Thank you for your help, you can mark this thread as solved.

Davíð
 
Solution
Status
Not open for further replies.