Skip to main content
Solved

vpp redownload call timed out <mdmclienterror:72>

  • February 18, 2019
  • 407 replies
  • 1077 views

Show first post

407 replies

Forum|alt.badge.img+18
  • Esteemed Contributor
  • November 21, 2019

Hey all, my Apple SE just sent me a note stating the following:
"Good Morning Gabe,

I just received confirmation that a server side change occurred that should resolve the issue. When you get a chance, could you please test to confirm and circle back with the results?"

I'd assume I will need to clear out all the failed commands and try having them check in again with a recon or a manage. I'll let you know if they actually did solve it.

Gabe Shackney
Princeton Public Schools


KyleEricson
Forum|alt.badge.img+17
  • Valued Contributor
  • November 21, 2019

Tested on 10.15.1 still broken. :(


Forum|alt.badge.img+1
  • New Contributor
  • November 21, 2019

We are experiencing the same issues. I am putting in a ticket with apple. For us it has been going off and on for the last 6 months.


Forum|alt.badge.img+1
  • New Contributor
  • November 21, 2019

Not working for us. Still doing the recon/policy/cancel-all shuffle to get VPP apps to install.


KyleEricson
Forum|alt.badge.img+17
  • Valued Contributor
  • November 21, 2019

Apple updated my case. I tried their idea and didn't work as I didn't have the file they asked me to remove.

From Apple#####

We deployed a server side fix yesterday, 11-20-2019, that we hope will serve to mitigate this behavior.

There are two parts to the effort to solve the behavior, this server side fix, and potential changes to macOS in the future.

Before you attempt to push/update the apps on the macOS system, I would recommend taking the following actions first.

  1. sudo rm -r /var/root/Library/com.apple.appstore/CommerceRequestCache

  2. Reboot the Mac

  3. Retry updating/installing the macOS app(s)


easyedc
Forum|alt.badge.img+16
  • Esteemed Contributor
  • November 21, 2019

So I heard maybe Apple is saying this is fixed? Anyone else seeing it resolved on their end?


Forum|alt.badge.img+1
  • New Contributor
  • November 21, 2019

@kericson, I think the path you have is missing a level. I found the file in /var/root/Library/Caches/com.apple.appstore. I tried to delete it and reboot but I still am getting the VPP time out error 72.


KyleEricson
Forum|alt.badge.img+17
  • Valued Contributor
  • November 21, 2019

@TxAg Thanks that's what Apple had sent me. I didn't think it would fix the issue even if I had the right path, thanks for confirming that.


Forum|alt.badge.img+5
  • New Contributor
  • November 21, 2019

Looks like it's working again for me. Let's wait and see if it also works when there is an App update.


Forum|alt.badge.img+6
  • New Contributor
  • November 21, 2019

I also got pinged by Apple support that they've resolved the issue on their end. I ran a few tests and it seems to be fixed but I'd need to observe a bit longer to be 100%.


Forum|alt.badge.img+3
  • New Contributor
  • November 22, 2019

Looks like were still seeing the issue for machines on 10.14.6 and 10.15.1 . :/


Forum|alt.badge.img+5
  • Contributor
  • November 22, 2019

Yeah still not working 10.15.1 here either. Logged a job with Jamf (as Excel and PowerPoint auto-updated, Remote Desktop, Outlook, Word, OneNote did not).

Did the usual things to get it working again, but we're still relying on workarounds rather than the issue being fixed. Guess we'll find out again in another month!


KyleEricson
Forum|alt.badge.img+17
  • Valued Contributor
  • November 22, 2019

@GregE Lol yeah this is still broken..Maybe it will be fixed in macOS 10.16 Red Wood.


ikhlasberrazi
Forum|alt.badge.img+2
  • New Contributor
  • November 22, 2019

After adjusting our firewall to allow all incoming traffic from the Apple IP range 17.0.0.0/8 issues were resolved. The previous role *.apple.com was not sufficient anymore.


Forum|alt.badge.img+1
  • New Contributor
  • November 22, 2019

Just found a solution to this problem (vpp redownload call timed out <mdmclienterror:72>) which I thought I'd share in case anyone else has the same (or similar) setup in their networking.

So I've been trawling through log files looking for hints, taking tcpdumps and tracing network flows, and in the end decided to bypass every bit of our infrastructure piece by piece until I could find what was causing the problem, and it appears to be IBMs Quad Nine (9.9.9.9) DNS Resolver Service (in my case), connecting to our "guest wifi" i thought would solve the problem, but it didn't, upon closer inspection I saw that my DNS had been set to 9.9.9.9, the second i switched it over to 8.8.8.8 (Ciscos' offering) all the apps that I'd been having problems with immediately started to download.

So it appears that in this case something is being blocked upstream by Quad Nine (and perhaps other DNS providers) that is needed for this to work, I don't know what, and as its a "free" service, I don't expect to get any mileage out IBM in trying to investigate.

Hope this helps someone, check your DNS resolvers and check what your network team are doing, whether they are going straight to internet, or via an upstream resolver.


Forum|alt.badge.img+7
  • Contributor
  • November 22, 2019

this has suddenly resolved itself for me today...


Forum|alt.badge.img+9
  • Valued Contributor
  • November 22, 2019

Hey, I just got an email from Apple support.....
It may be fixed.

We have a good news to share with you today about this case. Our Product Engineering updated that this issue should have been addressed by the server side fix deployed today. Being a server side change, macOS 10.15.x is not required in order to pick up the fix. Please test in your environment and verify the result.

So, let's hope this did the trick.


Forum|alt.badge.img+1
  • New Contributor
  • November 22, 2019

Im still getting the issue today.


KyleEricson
Forum|alt.badge.img+17
  • Valued Contributor
  • November 22, 2019

Same still broken.


Forum|alt.badge.img+9
  • Contributor
  • November 22, 2019

Still broken here too


Forum|alt.badge.img+9
  • Valued Contributor
  • November 22, 2019

Yeah, still broken for me too.... grrr


Forum|alt.badge.img+1
  • New Contributor
  • November 22, 2019

It appears to be working for me.


Forum|alt.badge.img+12
  • Valued Contributor
  • November 22, 2019

Thats wonderful the fix is for 10.15 and up, what about all my clients on 10.14.6 that are all broken? shakes fist


Forum|alt.badge.img+9
  • Contributor
  • November 22, 2019

It is not fixed in 10.15.1! I just enrolled 2 MacBooks (almost) at the same time. One has errors, the other does not.


KyleEricson
Forum|alt.badge.img+17
  • Valued Contributor
  • November 22, 2019

Yeah not seeing anything fixed on 10.14.6 or 10.15.1