PENDING Failed to end search job. Error = 0x80244022 ; But IIS is running and optimize

[Robo]

Hello,

i got a new mecm and got this error on a few clients "Failed to end search job. Error = 0x80244022" in the WUhandler but IIS is running and optimize. The Clients are in the status unknown.
Checked the IIS and optimize him.
Checked the clients and done a troubleshooting, sfc scan and a manual update but still this problem.
I got few clients in the same network with the same configuration and they have no errors and get their updates.

I have no idea whats going on here.

Have a nice weekend!

 

[Stanley Road]

Hello,

i got a new mecm and got this error on a few clients "Failed to end search job. Error = 0x80244022" in the WUhandler but IIS is running and optimize. The Clients are in the status unknown.
Checked the IIS and optimize him.
Checked the clients and done a troubleshooting, sfc scan and a manual update but still this problem.
I got few clients in the same network with the same configuration and they have no errors and get their updates.

I have no idea whats going on here.

Have a nice weekend!

are you able to browse to http://<SUP>:8530 & http://<SUP>:8531 when this is happening?

 

[Robo]

are you able to browse to http://<SUP>:8530 & http://<SUP>:8531 when this is happening?

yes. The machines are Citrix VDIs, persistent. There was a sysprep on them.
The Clients show on MECM but not on WSUS.

 

[Stanley Road]

yes. The machines are Citrix VDIs, persistent. There was a sysprep on them.
The Clients show on MECM but not on WSUS.

Just to confirm, you can browse those urls from the failing clients and you can ping wsus server by netbios name alone? From the clients?

 

[Stanley Road]

yes. The machines are Citrix VDIs, persistent. There was a sysprep on them.
The Clients show on MECM but not on WSUS.

Just to confirm, you can browse those urls from the failing clients and you can ping wsus server by netbios name alone? From the clients

Just to confirm, you can browse those urls from the failing clients and you can ping wsus server by netbios name alone? From the clients?

And can you ping the client netbios name from the sus server?

 

[Robo]

Just to confirm, you can browse those urls from the failing clients and you can ping wsus server by netbios name alone? From the clients

And can you ping the client netbios name from the sus server?

Yes I can ping from wsus or from client.

When I browse the URL:8530 there is Error 403 - Forbidden: Access is denied.
This Error is the same at a client that works with MECM.

 

[Robo]

Yes I can ping from wsus or from client.

When I browse the URL:8530 there is Error 403 - Forbidden: Access is denied.
This Error is the same at a client that works with MECM.

When I run this http://server.domain.local:8530/selfupdate/iuident.cab it download a file with all Informations

 

[Stanley Road]

Yes I can ping from wsus or from client.

When I browse the URL:8530 there is Error 403 - Forbidden: Access is denied.
This Error is the same at a client that works with MECM.

OK fix that first and then try again.

 

[Robo]

OK fix that first and then try again.

A Client which get his Updates and has no errors got the same 403 Error.
Iam not 100% sure, that I should fix it.
When I browse from SUP to this URL there is also this Error.
How fix that?

 

[Robo]

A Client which get his Updates and has no errors got the same 403 Error.
Iam not 100% sure, that I should fix it.
When I browse from SUP to this URL there is also this Error.
How fix that?

The Client check with http://<WSUSSERVERort>/iuident.cab also works.

 

[Stanley Road]

 

[Robo]

View attachment 7497

I know, thats why I described it im my first Post, that I have checked the IIS and optimize him
What Else should I check or do. Remember its only about 20 clients from about 40.

 

[Stanley Road]

I know, thats why I described it im my first Post, that I have checked the IIS and optimize him
What Else should I check or do. Remember its only about 20 clients from about 40.

That's 50%. Maybe check iis logs, read what it says on page 403 / 503. Compare succesful client logas against unsuccessful client logs. look for succesful clients in iis logs and compare non successful.

 

[Robo]

That's 50%. Maybe check iis logs, read what it says on page 403 / 503. Compare succesful client logas against unsuccessful client logs. look for succesful clients in iis logs and compare non successful.

I have also done this. No errors in IIS logs.