Since my original post, the linked thread has been updated. After turning on
debug logging, we also found that there was a bad App-V 4.6 package that was
jamming things up. Since we no longer needed this application, we uninstalled
it from all machines and our SAS application has started to deploy properly
again.
For reference, after turning on debug logging, the CAS log was now spammed by
the following:
IsCacheCopyNeeded returned 'true' by {5777363A-FB22-4a42-ABB0-522DD42711DC}
Found the AppV package [{5BB2B69F-67B2-4DE1-BD48-1A33E41CEEBA}] uses ConfigMgr
content ID [Content_9aa07c57-d736-4f1a-a403-bf2e0d0b5dfe] version 1, and it is
configured as download and execute
The AppV package {5BB2B69F-67B2-4DE1-BD48-1A33E41CEEBA} is not fully loaded
into AppV cache, so we cannot delete the ConfigMgr cache copy(content ID
Content_9aa07c57-d736-4f1a-a403-bf2e0d0b5dfe Version 1)
The content Content_9aa07c57-d736-4f1a-a403-bf2e0d0b5dfe version 1 is needed
>From there, I opened the App-V client management console, went to
>applications, turned on the Package GUID column, and found the package with
>GUID 5BB2B69F-67B2-4DE1-BD48-1A33E41CEEBA.
The odd part about this issue is it only appeared to affect this piece of
software. It also displayed the same issue whether it was deployed as an
Application or as a Package/Program. During the time we had this App-V package
on our machines, several other software packages (App-V 4/5, Application,
Package/Program) of various sizes (up to ~4G) were deployed without issue. My
guess would be it has something to do with clearing space on the cache (caches
were originally configured at 20G, bumped to 30G without a change in behavior).
Special thanks to Claude Henchoz for pointing me in the right direction on this
one.
Jesse Schauer
Windows Server Administrator II
Endpoint Manangement Services
University of Idaho ITS
From: [email protected] [mailto:[email protected]] On
Behalf Of Phil Wilcock
Sent: Monday, January 19, 2015 12:51 AM
To: [email protected]
Subject: [mssms] RE: "IsCacheCopyNeeded returned 'true' by
{5777363A-FB22-4a42-ABB0-522DD42711DC}" during software deployment
Hi Jesse,
Looks to me like BITS is erroring somewhere in the DL - try this command on the
client to look at the BITS job perhaps?
Bitsadmin.exe /info {insert-bits-guid-from cas.log-here} /verbose
This should point you in the right direction
Thanks
Phil
Phil Wilcock
2Pint Software
http://2pintsoftware.com
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Schauer, Jesse
([email protected]<mailto:[email protected]>)
Sent: 16 January 2015 17:03
To: '[email protected]'
Subject: [mssms] "IsCacheCopyNeeded returned 'true' by
{5777363A-FB22-4a42-ABB0-522DD42711DC}" during software deployment
I am trying to deploy a rather huge piece of software (SAS 9.4, ~19G) and am
running into some issues with clients not being able to download the content.
The software is being deployed as an application. When I set up a required
deployment for a machine, the machine will see it, see it needs to download
content, and try to start downloading. Around this time, CAS.log will start to
go crazy spamming "IsCacheCopyNeeded returned 'true' by
{5777363A-FB22-4a42-ABB0-522DD42711DC}". It write about 3-5M of this per minute.
While googling around I found this thread:
https://social.technet.microsoft.com/Forums/en-US/ce763dc6-c184-47bf-85a8-463501206000/2012-client-stuck-problem?forum=configmanagergeneral.
There is not much detail but they do reference the "dodgy registry key
IsCacheCopyNeededCallBack" (which is actually a value under
HKLM\SOFTWARE\Microsoft\SMS\Mobile Client\ Software Distribution). Deleting
this value causes the callback to fail, after which the content immediately
starts downloading. It should be noted that machines that are not having these
issues also have this registry value.
Anyone else run into this before? We've pushed a ton of software out with this
site (though this is the largest) and have never run into this until now. I'm
not sure what deleting the registry value does and while it seems to alleviate
the issue, I don't want to cause unexpected issues down the road.
For reference, site and client version are ConfigMgr 2012 R2 CU1. The client
cache size is currently set at 30G.
Jesse Schauer
Windows Server Administrator II
Endpoint Manangement Services
University of Idaho ITS
