locked
Client does not get installed RRS feed

  • Question

  • Hello,

    I have checked:

    - Network firewall ports are opened tested with telnet

    - Windows firewall: off

    - DNS entries are correct

    - account "svcconfigmgrsrv" is local admin on the client side

    ======>Begin Processing request: "2097154528", machine name: "VIPSANTOOLS01" 
    Execute query exec [sp_IsMPAvailable] N'UCP' 
    ---> Trying each entry in the SMS Client Remote Installation account list 
    ---> Attempting to connect to administrative share '\\VIPSANTOOLS01.ad\admin$' using account 'AD\svcconfigmgrsrv' 
    Submitted request successfully 
    Getting a new request from queue "Incoming" after 100 millisecond delay. 
    Waiting for change in directory "E:\SCCM\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). 
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account AD\svcconfigmgrsrv (00000040) 
    ---> Attempting to connect to administrative share '\\VIPSANTOOLS01.ad\admin$' using account 'AD\svc_ConfigMgr_WKSAdm' 
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account AD\svc_ConfigMgr_WKSAdm (00000040)
    ---> Attempting to connect to administrative share '\\VIPSANTOOLS01.ad\admin$' using account 'AD\svc_ConfigMgr_SRVAdm'
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account AD\svc_ConfigMgr_SRVAdm (00000040)
    ---> Attempting to connect to administrative share '\\VIPSANTOOLS01.ad\admin$' using account 'AD\svcDGITsccm' 
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account AD\svcDGITsccm (00000040)
    ---> Attempting to connect to administrative share '\\VIPSANTOOLS01.ad\admin$' using account 'AD\svcconfigmgrdts'
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account AD\svcconfigmgrdts (00000040)
    ---> Attempting to connect to administrative share '\\VIPSANTOOLS01.ad\admin$' using machine account. 
    ---> Failed to connect to \\VIPSANTOOLS01.ad\admin$ using machine account (64)
    ---> ERROR: Failed to connect to the \\VIPSANTOOLS01.ad\admin$ share using account 'Machine Account'
    ---> Trying each entry in the SMS Client Remote Installation account list 
    ---> Attempting to connect to administrative share '\\VIPSANTOOLS01\admin$' using account 'AD\svcconfigmgrsrv'
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account AD\svcconfigmgrsrv (00000040)
    ---> Attempting to connect to administrative share '\\VIPSANTOOLS01\admin$' using account 'AD\svc_ConfigMgr_WKSAdm'
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account AD\svc_ConfigMgr_WKSAdm (00000040)
    ---> Attempting to connect to administrative share '\\VIPSANTOOLS01\admin$' using account 'AD\svc_ConfigMgr_SRVAdm'
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account AD\svc_ConfigMgr_SRVAdm (00000040)
    ---> Attempting to connect to administrative share '\\VIPSANTOOLS01\admin$' using account 'AD\svcDGITsccm'
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account AD\svcDGITsccm (00000040)

    ---> Attempting to connect to administrative share '\\VIPSANTOOLS01\admin$' using account 'AD\svcconfigmgrdts'
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account AD\svcconfigmgrdts (00000040)
    ---> Attempting to connect to administrative share '\\VIPSANTOOLS01\admin$' using machine account.
    ---> Failed to connect to \\VIPSANTOOLS01\admin$ using machine account (64)
    ---> ERROR: Failed to connect to the \\VIPSANTOOLS01\admin$ share using account 'Machine Account'
    ---> ERROR: Unable to access target machine for request: "2097154528", machine name: "VIPSANTOOLS01",  access denied or invalid network path.
    Execute query exec [sp_CP_SetLastErrorCode] 2097154528, 64 
    Stored request "2097154528", machine name "VIPSANTOOLS01", in queue "Retry". 
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097154528, 2 
    Execute query exec [sp_CP_SetLatest] 2097154528, N'10/25/2017 19:50:45', 239
    <======End request: "2097154528", machine name: "VIPSANTOOLS01". 

    What could be the issue?

    Both servers the client and the SCCM primary server are Windows Server 2016.

    Thanks,

    dom


    Security / System Center Operations Manager 2012 / System Center Configuration Manager 2012 / SQL System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager



    • Edited by Felyjos Wednesday, October 25, 2017 8:22 PM
    Wednesday, October 25, 2017 8:04 PM

Answers

  • Hello,

     2147944122 = The RPC Server is unavailable. So as said, it's more like a network related issue.


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

    • Marked as answer by Felyjos Monday, October 30, 2017 6:13 PM
    Saturday, October 28, 2017 2:23 AM
  • 51525 is not a defined port, it is a random high RPC port. File and print sharing in Windows requires the RPC ports to be open.

    Jason | https://home.configmgrftw.com | @jasonsandys

    • Marked as answer by Felyjos Monday, October 30, 2017 6:13 PM
    Monday, October 30, 2017 5:26 PM

All replies

  • >---> Attempting to connect to administrative share '\\VIPSANTOOLS01\admin$' using account 'AD\svcconfigmgrsrv'
    > ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account AD\svcconfigmgrsrv (00000040)

    Are you sure the password is correct? 


    Nash Pherson, Senior Systems Consultant
    Microsoft MVP in Enterprise Mobility (ConfigMgr/Intune)
    Now Micro - MyITForum Blog Posts - Now Micro Blog Posts
    If you found a bug or want the product to work differently, share your feedback.
    <-- If this post was helpful, please click the up arrow or propose as answer.

    Wednesday, October 25, 2017 8:12 PM
  • Hello,

    It is the only machine out of 900+ which is failing !!! so I consider the password correct...

    And as noticed in the log all "Client Push Accounts" are failing with the same error 40!!!

    Could it be a pre-req in Windows server 2016 Role & Features missing or disabled vs it was enabled in early OS?

    ERROR_NETNAME_DELETED
    64 (0x40)

    The specified network name is no longer available

    I am able to ping the name, the IP, I got the PTR and A Record verified...

    Is it case sensitive?

    Thanks,

    Dom


    Security / System Center Operations Manager 2012 / System Center Configuration Manager 2012 / SQL System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager



    • Edited by Felyjos Wednesday, October 25, 2017 9:15 PM
    Wednesday, October 25, 2017 8:23 PM
  • Just because you get a ping reply does not mean you can properly make a connection to the target system. PTR records are irrelevant. No DNS is not case sensitive.

    Have you tried manually connecting to the admin$ share of the system in question from the site server?


    Jason | https://home.configmgrftw.com | @jasonsandys

    Thursday, October 26, 2017 12:29 AM
  • Hello,

    Yes I tried manually and it is failing as well.

    Now I have 5 machines on the same subnet with the same error 64...

    I have also several machines on this particular subnet which have been installed successfully

    Thanks,.

    Dom


    Security / System Center Operations Manager 2012 / System Center Configuration Manager 2012 / SQL System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

    Thursday, October 26, 2017 2:00 AM
  • Exactly. Thus this has nothing to do with ConfigMgr. Firewall or some sort network traffic filtering are possibilities here as is malware or your actual anti-virus product. You may need to actually log onto these systems to troubleshoot them.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Thursday, October 26, 2017 3:08 AM
  • Hello,

    In progress the error 64 is gone for almost all servers... now I have 2147944122...

    Primay-MS any TCP Client 135 TCP
    Primay-MS any TCP Client 445 TCP
    Primay-MS any UDP Client 135 UDP
    MS03 any TCP Client 135 TCP
    MS03 any TCP Client 445 TCP
    MS03 any UDP Client 135 UDP
    Client any TCP RS01 80 TCP
    Client any TCP RS01 443 TCP
    Client any TCP RS01 135 TCP
    Client any TCP RS01 445 TCP
    Client any TCP DP01 80 TCP
    Client any TCP DP01 443 TCP
    Client any TCP Primay-MS 80 TCP
    Client any TCP Primay-MS 443 TCP
    Client any TCP DP01-Site5 80 TCP
    Client any TCP DP01-Site5 443 TCP
    Client any TCP DP01-Site2 80 TCP
    Client any TCP DP01-Site2 443 TCP
    Client any TCP DP02-Site2 80 TCP
    Client any TCP DP02-Site2 443 TCP
    Client any TCP DP01-Site3 80 TCP
    Client any TCP DP01-Site3 443 TCP
    Client any TCP DP02-Site3 80 TCP
    Client any TCP DP02-Site3 443 TCP
    Client any TCP DP01-Site4 80 TCP
    Client any TCP DP01-Site4 443 TCP
    Client any TCP DP02-Site4 80 TCP
    Client any TCP DP02-Site4 443 TCP
    Client any UDP DP01 67 UDP
    Client any UDP DP01 68 UDP
    Client any UDP DP01 69 UDP
    Client any UDP DP01 4011 UDP
    Client any UDP Primay-MS 67 UDP
    Client any UDP Primay-MS 68 UDP
    Client any UDP Primay-MS 69 UDP
    Client any UDP Primay-MS 4011 UDP
    Client any UDP DP01-Site5 67 UDP
    Client any UDP DP01-Site5 68 UDP
    Client any UDP DP01-Site5 69 UDP
    Client any UDP DP01-Site5 4011 UDP
    Client any UDP DP02-Site2 67 UDP
    Client any UDP DP02-Site2 68 UDP
    Client any UDP 10.1.26.146 69 UDP
    Client any UDP DP02-Site2 4011 UDP
    Client any UDP DP01-Site3 67 UDP
    Client any UDP DP01-Site3 68 UDP
    Client any UDP DP01-Site3 69 UDP
    Client any UDP DP01-Site3 4011 UDP
    Client any UDP DP02-Site3 67 UDP
    Client any UDP DP02-Site3 68 UDP
    Client any UDP DP02-Site3 69 UDP
    Client any UDP DP02-Site3 4011 UDP
    Client any UDP DP01-Site4 67 UDP
    Client any UDP DP01-Site4 68 UDP
    Client any UDP DP01-Site4 69 UDP
    Client any UDP DP01-Site4 4011 UDP
    Client any UDP DP02-Site4 67 UDP
    Client any UDP DP02-Site4 68 UDP
    Client any UDP DP02-Site4 69 UDP
    Client any UDP DP02-Site4 4011 UDP
    Client any UDP DP01-Site2 67 UDP
    Client any UDP DP01-Site2 68 UDP
    Client any UDP DP01-Site2 69 UDP
    Client any UDP DP01-Site2 4011 UDP
               
    Client any TCP MS03 10123 TCP
    Client any TCP Primay-MS 10123 TCP
    Client any TCP DP01-Site5 10123 TCP
    Client any TCP DP01-Site2 10123 TCP
    Client any TCP DP02-Site2 10123 TCP
    Client any TCP DP01-Site3 10123 TCP
    Client any TCP DP02-Site3 10123 TCP
    Client any TCP DP01-Site4 10123 TCP
    Client any TCP DP02-Site4 10123 TCP
    SU          
    Client any TCP SU01 8530 TCP
    Client any TCP SU01 8531 TCP

    Thanks,

    Dom


    Security / System Center Operations Manager 2012 / System Center Configuration Manager 2012 / SQL System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager


    • Edited by Felyjos Friday, October 27, 2017 5:20 PM
    Friday, October 27, 2017 4:59 PM
  • Hello,

     2147944122 = The RPC Server is unavailable. So as said, it's more like a network related issue.


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

    • Marked as answer by Felyjos Monday, October 30, 2017 6:13 PM
    Saturday, October 28, 2017 2:23 AM
  • Hello,

    the port 51525 was denied, opening it allowed the client to be installed... but where is the requirement referring to this port? is it a random port from a range?

    thanks,

    Dom


    Security / System Center Operations Manager 2012 / System Center Configuration Manager 2012 / SQL System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

    Monday, October 30, 2017 5:16 PM
  • 51525 is not a defined port, it is a random high RPC port. File and print sharing in Windows requires the RPC ports to be open.

    Jason | https://home.configmgrftw.com | @jasonsandys

    • Marked as answer by Felyjos Monday, October 30, 2017 6:13 PM
    Monday, October 30, 2017 5:26 PM