none
KB2828185 failing with Error 0x80004005: Failed to create/modify file share: Err: 123

    Question

  • Hi All,

    We are trying to install KB2828185 on our production server and while running the setup its failing with below error.

    CreateSmb:  Error 0x80004005: Failed to create/modify file share: Err: 123
    MSI (s) (50!20) [11:20:02:872]: Closing MSIHANDLE (104) of type 790531 for thread 6688
    MSI (s) (50!20) [11:20:02:872]: Creating MSIHANDLE (105) of type 790531 for thread 6688
    CreateSmb:  Error 0x80004005: failed to create to share: 'WsusContent'
    MSI (s) (50!20) [11:20:05:290]: Product: Windows Server Update Services 3.0 SP2 -- Error 26301. Failed to create network share.  (-2147467259   WsusContent      )
    MSI (s) (50!20) [11:20:05:290]: Closing MSIHANDLE (105) of type 790531 for thread 6688
    MSI (c) (38:34) [11:20:02:872]: Font created.  Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
    Error 26301. Failed to create network share.  (-2147467259   WsusContent      )
    MSI (s) (50:64) [11:20:05:290]: Closing MSIHANDLE (99) of type 790536 for thread 7220
    CustomAction CreateSmb returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    MSI (s) (50:34) [11:20:05:665]: User policy value 'DisableRollback' is 0
    MSI (s) (50:34) [11:20:05:665]: Machine policy value 'DisableRollback' is 0
    Action ended 11:20:05: InstallFinalize. Return value 3.

    The WSUS content is on a network share and all the required permissions are set correctly.


    Server is running Window Server 2008 R2 and WSUS 3.0 SP2


    Regards, Rajul Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Friday, September 27, 2013 7:13 PM

Answers

  • Thanks Lawrence.

    I was able to get past the installation by moving the content location to the local server and then back to the remote server using wsusutil movecontent -skipcopy


    Regards, Rajul Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Saturday, September 28, 2013 2:58 AM

All replies

  • The WSUS content is on a network share

    The WSUS content is not supported on a network share, which is almost certainly why the installation is failing with this error:

    CreateSmb: Error 0x80004005: Failed to create/modify file share: Err: 123

    and all the required permissions are set correctly.

    They cannot be. As discussed extensively elsewhere, significant modifications to ACLs are required in order to make this work correctly. (Which is why it's not supported.)


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Friday, September 27, 2013 8:29 PM
  • Thanks Lawrence.

    It will be great if you could guide me to get the required ACL modifications. The content folder is of 420Gb and we don't have much space to accommodate it on the WSUS server now. So as a breakfix we need to do a temporary workaround and then plan for some disk drive expansion.


    Regards, Rajul Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Friday, September 27, 2013 8:42 PM
  • It will be great if you could guide me to get the required ACL modifications.

    The required (NOT SUPPORTED) modifications are discussed elsewhere in this forum.

    The content folder is of 420Gb and we don't have much space to accommodate it on the WSUS server now.

    Perhaps more appropriate remediation would be to get rid of the 400+GB of files you don't actually need! Then, with the more normal 10-12GB of files, you may actually be able to keep them ON the WSUS Server's local storage (which is a documented requirement for a WSUS server).

    Too Many Updates

    Remove Unneeded Update Approvals


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Friday, September 27, 2013 10:13 PM
  • Thanks Lawrence.

    I was able to get past the installation by moving the content location to the local server and then back to the remote server using wsusutil movecontent -skipcopy


    Regards, Rajul Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

    Saturday, September 28, 2013 2:58 AM