SCUP 2011 Import: Exception: An error occurred while updating the entries. See the inner exception for details. Updates Publisher xx/xx/xxxx x:xx:xx AM 13 (0x000D)

I was getting error message while updating Dell updates using SCUP 2011


    Import: Skipped import due to no change in creation date for update 56c63df6-5267-44ca-b7d9-78c22b2e9843, title: Intel Unite Protected Guest Access  Plugin Application,3.2.82.42,A00 Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Processing XML for package 0dc345fb-52fe-4380-8565-11758a02e64d, length 7397 characters. Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Skipped import due to no change in creation date for update 0dc345fb-52fe-4380-8565-11758a02e64d, title: Intel Unite Hub Application Installer,3.1.45.26,A00 Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Processing XML for package 56e205cf-16dc-4b63-81d1-a3b748a89c86, length 7364 characters. Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Skipped import due to no change in creation date for update 56e205cf-16dc-4b63-81d1-a3b748a89c86, title: Intel Unite Client Application Installer,3.1.45.26,A00 Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Processing XML for package 4eaf38b8-b3d8-4596-a6ed-3dd3be80a8d4, length 7525 characters. Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Importing new update 4eaf38b8-b3d8-4596-a6ed-3dd3be80a8d4, title: Intel Unite Add-In for Microsoft Outlook,3.2.82.42,A00 Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Exception: An error occurred while updating the entries. See the inner exception for details. Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Processing XML for package 388a5fae-a141-46d1-8968-6c15501a6a7d, length 7671 characters. Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Importing new update 388a5fae-a141-46d1-8968-6c15501a6a7d, title: Intel Unite Plugin for Telemetry for Business Installer,3.2.82.42,A00 Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Exception: An error occurred while updating the entries. See the inner exception for details. Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Processing XML for package 08cc667b-043d-4afc-89a5-1700560bbbbf, length 4434 characters. Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)
    Import: Skipped import due to no change in creation date for update 08cc667b-043d-4afc-89a5-1700560bbbbf, title: Dell OptiPlex 7050 System BIOS,1.6.5 Updates Publisher 12/26/2017 9:49:19 AM 13 (0x000D)

I had 27 of Import: Exception: An error occurred while updating the entries errors and I was scratching my head on this for a few days.
I found a similar problem on https://community.spiceworks.com/topic/1751827-service-pack-3-for-sql-server-2012-breaks-scup-2011-any-suggestions
and
https://social.technet.microsoft.com/Forums/en-US/e8267fe0-9c39-4fdc-8bdc-6b4b471b2e96/scup-fails-importing-of-updates?forum=ConfigMgrCompliance

But I use SQL 2008 so it was not the case.

To fix this problem, there are two options:

1, Get list of all failed updates and delete them individually from the Dell updates, and reimport.

If you miss any failed updates, you will still get the same error!. Delete them all and close SCUP 2011 and open again, and reimport the catalog.

2. Delete the "Dell" folder on the "Updates" and import Dell catalog again.
Warning: You will lose your all of your local information such as "Date Published", "Expired" and "Date Modified" information, if you expired or published and updates.

To delete the "Dell" folder on Updates:
Make a backup of your SCUP DB first (simply do copy and paste of the DB),  SCUP -> Updates -> Overview -> All Software Updates -> Dell. Highlight the "Dell", right click, and delete.


UPDATE: SCUP 2017 production version is now available! and it works much better! http://exchcluster.blogspot.com/2018/04/system-center-updates-publisher-scup.html

That damn event ID 129

I was getting this event id 129 on several server 2012 R2 systems

Log Name:      System

Source:        LSI_SAS

Date:          

Event ID:      129

Task Category: None

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      

Description:

Reset to device, \Device\RaidPort0, was issued.

and I found this

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2063346

Changed LSI_SAS to PVSCSI and got:

Log Name:      System

Source:        pvscsi

Date:          

Event ID:      129

Task Category: None

Level:         Warning

Keywords:      Classic

User:          N/A

Computer:      

Description:

Reset to device, \Device\RaidPort0, was issued.

Contacted VMware and they blamed on M$, and told me to upgrade the SAS driver.

Went to broadcom.com site and look for newer driver for "Lsi SAS 3801E", that is what the real name of the "LSI Adaptoer, SAS 3000 series, 8-port with 1068"

https://www.broadcom.com/support/download-search/?pg=&pf=&pn=LSI+SAS+3801E&po=&pa=&dk=

and failed to find any newer drivers for windows 2012 R2, ended up downloading driver for 2008 R2 and replaced it, but still got the event id 129.

Vmware recommended to do https://blogs.technet.microsoft.com/kevinholman/2013/06/21/event-id-129-storachi-reset-to-device-deviceraidport0-was-issued/

but still getting the 129.

Called M$ and they blamed VMware, ended up doing 3way call with VMware and M$, it was fun to hear them blaming each others, and finally they agreed(!) that it was disk system's problem.

Called SAN manufacture and they said there is no error recorded.

Finally I found that event id 129 recorded only when vsphere replication is active.

Called vmware, still was blaming SAN system, and two days later I got this reply:

"I want you to try one more troubleshooting step, which helps to identify and regulate if vSphere Replication is replicating huge data though there are no changes happening on the VM.

This issue is could also be caused by a GuestOS sent unmap command. 

To disable Unmap in the Guest OS:

Using a Windows CMD window on the Host, run the command:

fsutil behavior set DisableDeleteNotify 1

To re-enable the feature, use the following command:

fsutil behavior set DisableDeleteNotify 0

To verify the current setting, use the following command:

fsutil behavior query DisableDeleteNotify

DisableDeleteNotify=0 - indicates the 'Trim and Unmap' feature is on (enabled)

DisableDeleteNotify=1 - indicates the 'Trim and Unmap' feature is off (disabled)

Kindly try the above steps and update the status to us, Awaiting your response."

Tried the solution and the event id 129 is gone, however, if you disable the unmap, you are effectively disabling reclaim function from vSphere, read more about this from: 

https://www.vladan.fr/what-is-vmware-unmap-dead-space-reclamation/

I asked if VMware can make changes so when replication happens the replication process ignore the unmap command. Their answer was "We will surely consider  the inputs suggested by your side which helps us to enhance the product"

Hope this help someone and save their time.

SCCM UEFI OS deployment error 0x80004005

I tried to push Windows 10 through UEFI on SCCM 2016 and got error like this

<![LOG[!sBootDevicePath.empty(), HRESULT=80004005 (e:\qfe\nts\sms\framework\tscore\bootvolume.cpp,34)]LOG]!>

<![LOG[System partition not set]LOG]!>

<![LOG[Unable to find the partition that contains the OS boot loaders. Please ensure the hard disks have been properly partitioned

Unspecified error (Error: 80004005; Source: Windows)]LOG]!>

<![LOG[BootVolume::GetCurrent(pBootVolume), HRESULT=80004005 (e:\qfe\nts\sms\framework\tscore\bootimage.cpp,542)]LOG]!>

The problem was, on "Partition Disk 0 - UEFI" step, I forgot to check "Make this the book disk"