Had a similar problem with stuck "In Progress" distributions.  Opened a call 
with Microsoft and got no good answers as to why they were stuck and wouldn't 
finish.  A large group of packages were stuck trying to distribute to 4 
secondary sites, we found that redistributing to one of the four got the 
package to successfully finish on the other 3.

One interesting thing I found was that on a couple packages that were stuck 
they had been set to retired, which apparently if there is any in progress 
distributions once it gets set to retired, it will just stay that way 
perpetually.

From: [email protected] [mailto:[email protected]] On 
Behalf Of Brian Mason
Sent: Monday, June 23, 2014 9:53 AM
To: [email protected]
Subject: [mssms] RE: Apps/Packages Stuck in "In Progress" state

Any stale or orphaned files in the inboxes?  Like replmgr.box or something?  Is 
the log below from the primary site?

MMS MOA NOV

_________________
Brian Mason
MCTS, MS MVP ECM
http://www.mnscug.org/<https://urldefense.proofpoint.com/v1/url?u=http://www.mnscug.org/&k=DRaZFQufJSh%2Bz2CJu01vGA%3D%3D%0A&r=G7Rp%2FyVEkz9AB1xRQWzmh1E0dbzzZxlFIY6QTWSRqzc%3D%0A&m=OjkQqzCYVULwck08u%2Ff9AXYS7a4JPyTChu8q9SR39hU%3D%0A&s=910d4692bf8ef23953837b2cf3fe9e155d7639328ba314f9436899986f10bfa8>

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of 
[email protected]<mailto:[email protected]>
Sent: Friday, June 20, 2014 1:14 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] Apps/Packages Stuck in "In Progress" state

Does anyone know how to reset an App or a package that's stuck in "In progress" 
state trying to distribute to the DPs?  I've tried changing removing the DPs 
and adding them back, then also tried changing the source location, and no 
dice.  We're on CM12 R2 with CU1.  Two tier; CAS, Primaries and DPs .  I do see 
this in the despooler.log.  Over and over for this particular app...

Received package CAS008DB version 6. Compressed file -  
D:\SMSPKG\CAS008DB.PCK.6 as D:\SMS\inboxes\despoolr.box\receive\PKGfooh3.TRY
Instruction D:\SMS\inboxes\despoolr.box\receive\ds_2ivq1.sni won't be processed 
till 6/20/2014 1:42:00 PM Central Daylight Time
Instruction D:\SMS\inboxes\despoolr.box\receive\ds_ijdl4.sni won't be processed 
till 6/20/2014 1:13:50 PM Central Daylight Time
Instruction D:\SMS\inboxes\despoolr.box\receive\ds_oko21.sni won't be processed 
till 6/20/2014 1:31:10 PM Central Daylight Time
Instruction D:\SMS\inboxes\despoolr.box\receive\ds_vy0p3.sni won't be processed 
till 6/20/2014 1:36:40 PM Central Daylight Time
Instruction D:\SMS\inboxes\despoolr.box\receive\ds_xzqrp.sni won't be processed 
till 6/20/2014 2:08:40 PM Central Daylight Time
Waiting for ready instruction file....
Old package storedUNC path is .
This package[CAS008DB]'s information hasn't arrived yet for this version [6]. 
Retry later ...
Created retry instruction for job 00005921
Despooler failed to execute the instruction, error code = 12







JEFF CARREON


[email protected]<mailto:[email protected]>





________________________________

CONFIDENTIALITY NOTICE: This email contains information from the sender that 
may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected 
from disclosure. This email is intended for use only by the person or entity to 
whom it is addressed. If you are not the intended recipient, any use, 
disclosure, copying, distribution, printing, or any action taken in reliance on 
the contents of this email, is strictly prohibited. If you received this email 
in error, please contact the sending party by reply email, delete the email 
from your computer system and shred any paper copies.

Note to Patients: There are a number of risks you should consider before using 
e-mail to communicate with us. See our Privacy & Security page on 
www.henryford.com for more detailed information as well as information 
concerning MyChart, our new patient portal. If you do not believe that our 
policy gives you the privacy and security protection you need, do not send 
e-mail or Internet communications to us.



Reply via email to