It is actually "Faled to get a write lock" Me and other people. There are about 15 reasons for this error.
On Tue, Feb 3, 2015 at 7:15 AM, Marcum, John <[email protected]> wrote: > How many of these DP bug fixes in CU4 were ones that you reported Todd? > I'm guessing at least half of them. > > > > *Software distribution and application management* > > · 3007095 <http://support.microsoft.com/kb/3007095> > > (http://support.microsoft.com/kb/3007095/ ) > > Applications may not be downloaded in System Center 2012 R2 Configuration > Manager > > > · Removing a user who's assigned to a primary device triggers > the removal of all policies that are assigned to that device, even when > there are other users assigned. > > > · Deleting packages in environments that have many (thousands) > of distribution points may take longer than expected and may block other > package distribution operations. > > > · Pull distribution points may download an earlier version > instead of the most recent version of frequently updated packages. > > > > · When you pre-stage many packages on Pull distribution points > and you use a distribution point as the source, the operation may fail. In > this situation, errors that resemble the following are recorded in the > Ccmexec.log file on the Pull distribution point: > > Failed to get a WriteLock > > > > · Enabling the *Limit to specific maximum transfer rate by hour* > distribution point property limits package distribution to one every 20 > minutes. > > > > > > > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Todd Hemsell > *Sent:* Tuesday, February 03, 2015 5:51 AM > *To:* [email protected] > *Subject:* Re: [mssms] SCCM 2012R2 Content distribution warnings mismatch > between Content Status and Distribution Point Configuration Status > > > > I have. When I say "bug" I mean filed verified bug. > > If I find a bug I let it sit until we resolve it or verify it with MS. > > > > Try to do my part to improve the product. > > > > On Fri, Jan 30, 2015 at 10:04 PM, Nash Pherson <[email protected]> wrote: > > If possible, open a support case when you encounter this (or feedback on > Connect at a minimum). The couple times I’ve run into these types of > errors, I fixed the symptom before getting the info to the product team so > they could solve the issue. > > > > Nash > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Todd Hemsell > *Sent:* Friday, January 30, 2015 14:06 PM > *To:* [email protected] > *Subject:* Re: [mssms] SCCM 2012R2 Content distribution warnings mismatch > between Content Status and Distribution Point Configuration Status > > > > there are a lot of bugs in that content validation thing. > > Try to look at the content using the content browser from the SDK or > toolkit > > On my DP's with the validation bug, the content browser crashes. > > > > On Thu, Jan 29, 2015 at 12:54 PM, George Salmaniw < > [email protected]> wrote: > > Using SCCM 2012R2 CU3 and am seeing the following behaviour when monitor > content distribution on a specific distribution point: > > > > Under Monitoring / Distribution Status / Content Status / <Application> > status shows Content was distributed to distribution point > > > > Under Monitoring / Distribution Status / Distribution Point Configuration > Status / Distribution Point Name / Details the same Application [same > Package ID] shows error with message Failed to validate package on > distribution point … > > > > The only difference I am noticing is on the timestamps for each. Under > Content Status its last update was January 28, 2015. Under Distribution > Point Configuration Status its last update for the particular package was > January 24, 2015. > > > > Is the reason for the content mismatch warnings due to the Distribution > Point Configuration Status not being updated to the current status? Is > there a way of manually updating Distribution Point Configuration Status > for a particular DP? > > > > Assistance is appreciated, > > > > G > > > > > > > > > > > > > ------------------------------ > > > Confidentiality Notice: This e-mail is from a law firm and may be > protected by the attorney-client or work product privileges. If you have > received this message in error, please notify the sender by replying to > this e-mail and then delete it from your computer. > >
