Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Saturday, June 14, 2014 2:53 PM
Hi there
Trying to patch a new Windows 7 SP1 image within SCCM 2012 SP1, but it's failing.
I've searched for information on the failure messages I am seeing, but although there is a LOT of information online concerning Offline Servicing failures, I can't find anything on the errors I am seeing.
I've tried injecting a single update, five updates and ten updates, no difference, same messages.
We have McAfee Access Protection disabled, as we know Offline Servicing simply won't work if this is running.
In the console, in Schedule Update Status for the image I am trying to update, the following message is shown:
"Failed to find or access the update binaries to be applied on the image."
That sounds as if the process can't find the actual .cab file for any update I've tried to inject, but I don't know why it wouldn't be able to do that, we have Software Updates configured and the .cab files are on the same server.
When I looked at the OfflineServicingMgr.log file, I see the following entries:
Processing image at index 1 SMS_OFFLINE_SERVICING_MANAGER 14/06/2014 14:52:49 8272 (0x2050)
Mounting image at index 1. Image file='D:\ConfigMgr_OfflineImageServicing\PackageID\W7_Image.wim', MountDirectory='D:\ConfigMgr_OfflineImageServicing\PackageID\ImageMountDir', ImageFileType='WIM', Mode='ReadWrite' SMS_OFFLINE_SERVICING_MANAGER 14/06/2014 14:52:49 8272 (0x2050)
Image OS information : MajorVersionMS = 6, MinorVersionMS = 1, MajorVersionLS = 7601, MinorVersionLS = 17514 SMS_OFFLINE_SERVICING_MANAGER 14/06/2014 14:53:31 8272 (0x2050)
Failed to find properties of file 4 SMS_OFFLINE_SERVICING_MANAGER 14/06/2014 14:53:31 8272 (0x2050)
UnMounting Image (Commit Changes = 0) ... SMS_OFFLINE_SERVICING_MANAGER 14/06/2014 14:53:31 8272 (0x2050)
Completed processing image package PackageID. Status = Failed SMS_OFFLINE_SERVICING_MANAGER 14/06/2014 14:54:04 8272 (0x2050)
Updated history for image package PackageID in the database SMS_OFFLINE_SERVICING_MANAGER 14/06/2014 14:54:04 8272 (0x2050)
Schedule processing failed SMS_OFFLINE_SERVICING_MANAGER 14/06/2014 14:54:04 8272 (0x2050)
Processing completed for Schedule with ID 16777237 SMS_OFFLINE_SERVICING_MANAGER 14/06/2014 14:54:04 8272 (0x2050)
STATMSG: ID=7910 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=SCCMServer.domain SITE=Site_Code PID=8560 TID=8272 GMTDATE=Sat Jun 14 13:54:04.964 2014 ISTR0="16777237" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_OFFLINE_SERVICING_MANAGER 14/06/2014 14:54:04 8272 (0x2050)
Schedule processing thread stopped SMS_OFFLINE_SERVICING_MANAGER 14/06/2014 14:54:05 8272 (0x2050)
I'm not sure what file "Failed to find properties of file 4" is referring to, whether dism.exe, an update or the image itself, but immediately after this message appears the image is unmounted. After that this message shows:
"Completed processing image package PackageID. Status = Failed"
As I say, there's a lot of information available re Offline Servicing but I haven't found anything with these particular messages.
If anyone has encountered this before, I'd appreciate any information you have.
Regards,
John.
All replies (4)
Monday, June 16, 2014 7:57 AM ✅Answered
Hi,
I think file named 'NO_SMS_ON_DRIVE.SMS’ might be causing this issue. If this file is present in logical drives, then please give it a shot one more time after deleting this file from the logical drives.
Due to this file, it might be preventing 'smsexec' service to skip the drive when looking for content. So worth a try!
After deleting this file, you also need to restart 'smsexec' service to reflect the changes. You can also verify from below registry value & ensure that all of your logical drives (specially where SCCMContentLib directory resides) should be listed over there
'HKLM\Software\Microsoft\SMS\DP\ContentLibUsableDrives'
Hope this will help!
Cheers | Navdeep Sidhu
Saturday, June 14, 2014 7:42 PM
Is it a custom image and could it be a problem with the image itself?
Just to make sure that it's (not) a problem with the image itself, I would try with a different image (the default install.wim for example).
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude
Sunday, June 15, 2014 10:40 AM
Hi there
Yes it is a custom image, created via a capture ts, though there's not much to it other some features are disabled, it's quite simple.
This is the same ts we used to create the existing OS image, which was updated with patches earlier this year (I am creating a new image so will not be testing with the existing live image).
Just to be safe I created another image this morning, tested injecting updates, same error:
"Failed to find properties of the file 2"
What is particularly frustrating is I cannot find that error message anywhere online, though I doubt very much I am the first person to encounter it.
I'll keep on looking, thank you for taking the time to reply.
Regards,
John.
Tuesday, June 24, 2014 10:52 AM
Hi Navdeep
Thank you for your post, that worked.
Thanks again!
John