none
Offline servicing cancels/fails itself on the last index? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi All, wondering if anyone can help me with offline servicing of our OS image failing, it seemingly is cancelling for no reason by itself and I am left scratching my head. It will apply updates successfully to 5 out of 6 index's and then just cancel itself towards the end with no specific error message.

    Running SCCM 1906 with hotfix rollup with ADK/WinPE 1809/ stock 1809 Windows 10 WIM

    Tried updating to ADK 1903 -  no change

    also ran DISM restore health command - no change

    OfflineServicingMgr log Excerpt:

    Total number of updates that have been successfully applied on the mounted image is 15	SMS_OFFLINE_SERVICING_MANAGER	11/21/2019 11:01:09 AM	3324 (0x0CFC)
UnMounting Image (Commit Changes = 1) ...	SMS_OFFLINE_SERVICING_MANAGER	11/21/2019 11:01:09 AM	3324 (0x0CFC)
Successfully run 'dism /cleanup-wim'	SMS_OFFLINE_SERVICING_MANAGER	11/21/2019 11:06:04 AM	3324 (0x0CFC)
Successfully run 'dism /cleanup-mountpoints'	SMS_OFFLINE_SERVICING_MANAGER	11/21/2019 11:06:05 AM	3324 (0x0CFC)
Processing image at index 6	SMS_OFFLINE_SERVICING_MANAGER	11/21/2019 11:06:05 AM	3324 (0x0CFC)
Mounting image at index 6. Image file='C:\ConfigMgr_OfflineImageServicing\P0100102\install.wim', MountDirectory='C:\ConfigMgr_OfflineImageServicing\P0100102\ImageMountDir', ImageFileType='WIM', Mode='ReadWrite'	SMS_OFFLINE_SERVICING_MANAGER	11/21/2019 11:06:05 AM	3324 (0x0CFC)
Schedule processing cancelled ...	SMS_OFFLINE_SERVICING_MANAGER	11/21/2019 11:08:41 AM	3324 (0x0CFC)
UnMounting Image (Commit Changes = 0) ...	SMS_OFFLINE_SERVICING_MANAGER	11/21/2019 11:08:41 AM	3324 (0x0CFC)
WARNING : Timed-out waiting for the processing thread to complete.	SMS_OFFLINE_SERVICING_MANAGER	11/21/2019 11:10:04 AM	9108 (0x2394)
Offline Servicing Manager thread is exiting.	SMS_OFFLINE_SERVICING_MANAGER	11/21/2019 11:10:04 AM	9108 (0x2394)
Successfully run 'dism /cleanup-wim'	SMS_OFFLINE_SERVICING_MANAGER	11/21/2019 11:10:50 AM	3324 (0x0CFC)
Successfully run 'dism /cleanup-mountpoints'	SMS_OFFLINE_SERVICING_MANAGER	11/21/2019 11:10:51 AM	3324 (0x0CFC)
Completed processing image package P0100102. Status = Failed	SMS_OFFLINE_SERVICING_MANAGER	11/21/2019 11:10:51 AM	3324 (0x0CFC)
Not copying back  the image to source location	SMS_OFFLINE_SERVICING_MANAGER	11/21/2019 11:10:51 AM	3324 (0x0CFC)
Successfully deleted entry from database for schedule ID=16777265 Name="" assigned to ImageID=P0100102	SMS_OFFLINE_SERVICING_MANAGER	11/21/2019 11:10:51 AM	3324 (0x0CFC)
Successfully deleted entry from database for schedule ID=16777261 Name="" assigned to ImageID=P0100102	SMS_OFFLINE_SERVICING_MANAGER	11/21/2019 11:10:51 AM	3324 (0x0CFC)
Updated history for image package P0100102 in the database	SMS_OFFLINE_SERVICING_MANAGER	11/21/2019 11:10:51 AM	3324 (0x0CFC)
Schedule processing failed	SMS_OFFLINE_SERVICING_MANAGER	11/21/2019 11:10:51 AM	3324 (0x0CFC)
Processing completed for Schedule with ID 16777271	SMS_OFFLINE_SERVICING_MANAGER	11/21/2019 11:10:51 AM	3324 (0x0CFC)
STATMSG: ID=7910 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=myserver.mydomain.COM SITE=P01 PID=1648 TID=3324 GMTDATE=Thu Nov 21 16:10:51.204 2019 ISTR0="16777271" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_OFFLINE_SERVICING_MANAGER	11/21/2019 11:10:51 AM	3324 (0x0CFC)
SMS_EXECUTIVE started SMS_OFFLINE_SERVICING_MANAGER as thread ID 7016 (0x1B68).	SMS_OFFLINE_SERVICING_MANAGER	11/21/2019 11:14:32 AM	11688 (0x2DA8)
Inbox source is local on myserver.mydomain.com	SMS_OFFLINE_SERVICING_MANAGER	11/21/2019 11:14:32 AM	7016 (0x1B68)
Offline Servicing staging drive is assigned to be C:	SMS_OFFLINE_SERVICING_MANAGER	11/21/2019 11:14:32 AM	7016 (0x1B68)

    Thursday, November 21, 2019 4:37 PM
    |

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    After troubleshooting further I found the culprit was our new enterprise antivirus that got installed the same month the problems began, it was killing the job. (SentinelOne). Hopefully this helps some other poor soul in the future
    • Marked as answer by Msurge Thursday, November 21, 2019 9:25 PM
    Thursday, November 21, 2019 9:24 PM
    |

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    my co-worker just suggested that I re-create the WIM file with only the 1 index (3) that I need... I think I will try this route and see if I have any success- probably not a bad idea to recreate the WIM anyway in case it got corrupted
    Thursday, November 21, 2019 5:01 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Same result with a brand new base WIM :( I found this line in DISM log right before the shutdown is signaled -wondering if it is directly related

    2019-11-21 15:08:18, Info                  DISM   API: PID=1376 TID=13060 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath


    • Edited by Msurge Thursday, November 21, 2019 8:29 PM
    Thursday, November 21, 2019 8:29 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    After troubleshooting further I found the culprit was our new enterprise antivirus that got installed the same month the problems began, it was killing the job. (SentinelOne). Hopefully this helps some other poor soul in the future
    • Marked as answer by Msurge Thursday, November 21, 2019 9:25 PM
    Thursday, November 21, 2019 9:24 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    Thank you very much for posting in TechNet and sharing the solution. Here's a short summary for the problem.

    Problem/Symptom:
    ===================
    Offline servicing cancels/fails itself on the last index with no specific error message.

    Solution:
    ===================
    The culprit was the new enterprise antivirus that got installed the same month the problems began, it was killing the job.

    Thanks for your time again. 

    Best regards,
    Simon

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, November 22, 2019 3:06 AM
    |