locked
SCCM CB 1710 - DP Issue RRS feed

  • Question

  • Hi All,

    I have SCCM CB 1710 and i am trying to install distribution point. The installation is successfull but the package transfer is getting failed 

    Tried turning off antivirus, restarted the machine, rebuild the distribution point role, Rebuild WMI repository etc... but still the situation is same. Please help in how can we proceed further

    Package Transfer Log:

    \XXXX.com\~  $$<SMS_PACKAGE_TRANSFER_MANAGER><04-14-2018 07:59:13.972-180><thread=7080 (0x1BA8)>
    STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=XXXX.com SITE=XXX PID=2096 TID=7080 GMTDATE=Sat Apr 14 04:59:13.990 2018 ISTR0="XXX00003" ISTR1="["Display=\\XXXX.com\"]MSWNET:["SMS_SITE=XXX"]\\XXXX.com\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="XXX00003" AID1=410 AVAL1="4" AID2=404 AVAL2="["Display=\\XXXX.com\"]MSWNET:["SMS_SITE=XXX"]\\XXXX.com\"  $$<SMS_PACKAGE_TRANSFER_MANAGER><04-14-2018 07:59:13.990-180><thread=7080 (0x1BA8)>
    Sent status to the distribution manager for pkg XXX00003, version 4, status 0 and distribution point ["Display=\\XXXX.com\"]MSWNET:["SMS_SITE=XXX"]\\XXXX.com\~  $$<SMS_PACKAGE_TRANSFER_MANAGER><04-14-2018 07:59:15.042-180><thread=7080 (0x1BA8)>
    ~There is no existing connection, Win32 error = 67  $$<SMS_PACKAGE_TRANSFER_MANAGER><04-14-2018 07:59:15.098-180><thread=7080 (0x1BA8)>
    ~There is no existing connection, Win32 error = 67  $$<SMS_PACKAGE_TRANSFER_MANAGER><04-14-2018 07:59:15.115-180><thread=7080 (0x1BA8)>
    Error during connection to \\XXXX.com\SMS_DP$ (67).~  $$<SMS_PACKAGE_TRANSFER_MANAGER><04-14-2018 07:59:15.116-180><thread=7080 (0x1BA8)>
    Error is considered fatal.~  $$<SMS_PACKAGE_TRANSFER_MANAGER><04-14-2018 07:59:15.116-180><thread=7080 (0x1BA8)>
    ~Cannot connect to server XXXX.com at remote site XXXX.com, won't try send requests going to site XXXX.com for an hour or until there are no active send requests.  $$<SMS_PACKAGE_TRANSFER_MANAGER><04-14-2018 07:59:15.117-180><thread=7080 (0x1BA8)>
    Could not establish connection.~  $$<SMS_PACKAGE_TRANSFER_MANAGER><04-14-2018 07:59:15.117-180><thread=7080 (0x1BA8)>
    ~Attempt to connect failed.   $$<SMS_PACKAGE_TRANSFER_MANAGER><04-14-2018 07:59:15.118-180><thread=7080 (0x1BA8)>
    ~Restart time = 4/14/2018 8:10:15 AM Arab Standard Time  $$<SMS_PACKAGE_TRANSFER_MANAGER><04-14-2018 07:59:15.118-180><thread=7080 (0x1BA8)>
    ~ Attempted max retry count. The job would be marked for deletion now.  $$<SMS_PACKAGE_TRANSFER_MANAGER><04-14-2018 07:59:15.119-180><thread=7080 (0x1BA8)>
    STATMSG: ID=8207 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=XXXX.com SITE=XXX PID=2096 TID=7080 GMTDATE=Sat Apr 14 04:59:15.119 2018 ISTR0="XXX00003" ISTR1="XXXX.com" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="XXX00003" AID1=410 AVAL1="4" AID2=404 AVAL2="XXXX.com"  $$<SMS_PACKAGE_TRANSFER_MANAGER><04-14-2018 07:59:15.119-180><thread=7080 (0x1BA8)>
    Sent status to the distribution manager for pkg XXX00003, version 4, status 5 and distribution point ["Display=\\XXXX.com\"]MSWNET:["SMS_SITE=XXX"]\\XXXX.com\~  $$<SMS_PACKAGE_TRANSFER_MANAGER><04-14-2018 07:59:16.164-180><thread=7080 (0x1BA8)>
    Sending thread complete~  $$<SMS_PACKAGE_TRANSFER_MANAGER><04-14-2018 07:59:16.169-180><thread=7080 (0x1BA8)>

    Error Snap:


    Regards, Pratap

    Wednesday, April 18, 2018 5:35 AM

Answers

  • Why would you rebuild WMI? Rebuilding WMI is never a good idea and has nothing to do with this issue whatsoever.

    Error code 67 = "The network name cannot be found."

    Thus you've got a name resolution type issue. Have you validated that you can ping the DP by name and IP and that the name resolution returns the correct IP?

    Have you manually tried to connect to the path shown using the computer account of the site server?


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

    • Marked as answer by Sanak pratap Wednesday, April 25, 2018 4:58 AM
    Wednesday, April 18, 2018 2:55 PM
  • check your firewalls to ensure that the ports are open.

    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed

    • Marked as answer by Sanak pratap Wednesday, April 25, 2018 4:58 AM
    Monday, April 23, 2018 10:29 AM
  • Your logs say the network can't be found. 

    Even though you have pingged and telnet. 

    It doesn't mean that everything is right. Is the IP address correct for that server? Is the DNS entry right, aka have the right IP address?  Can you open wbemtest on the site server and connect to the DP? Is a firewall getting it the way? 

    Does this work from the site server to DP? https://www.youtube.com/edit?o=U&video_id=2nPxjzhZbVM


    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed

    • Marked as answer by Sanak pratap Wednesday, April 25, 2018 4:58 AM
    Monday, April 23, 2018 1:53 PM

All replies

  • Why would you rebuild WMI? Rebuilding WMI is never a good idea and has nothing to do with this issue whatsoever.

    Error code 67 = "The network name cannot be found."

    Thus you've got a name resolution type issue. Have you validated that you can ping the DP by name and IP and that the name resolution returns the correct IP?

    Have you manually tried to connect to the path shown using the computer account of the site server?


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

    • Marked as answer by Sanak pratap Wednesday, April 25, 2018 4:58 AM
    Wednesday, April 18, 2018 2:55 PM
  • Hi

    I can access DP path from primary server, DNS resolution is fine on both the primary server and DP server.

    Both are pinging. IP is correct

    I added new disk as well still same issue. Any other checks i have to do


    Regards, Pratap

    Monday, April 23, 2018 5:55 AM
  • check your firewalls to ensure that the ports are open.

    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed

    • Marked as answer by Sanak pratap Wednesday, April 25, 2018 4:58 AM
    Monday, April 23, 2018 10:29 AM
  • i am able to telnet from primary server to DP. both 445/135

    There is no firewall in between as per the customer. They have implemented "L3 – MPLS Network and mesh network connectivity". There is no WAN accelerator also. Not sure what is causing this issue. Is there a way we can use to find which is blocking


    Regards, Pratap

    Monday, April 23, 2018 12:52 PM
  • and how are you testing the RPC ports? 

    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed

    Monday, April 23, 2018 1:17 PM
  • I did telnet to 135 - telnet DPname 135 from primary site server which is working fine. Do you suspect dynamic port blocked???

    Regards, Pratap

    Monday, April 23, 2018 1:26 PM
  • Your logs say the network can't be found. 

    Even though you have pingged and telnet. 

    It doesn't mean that everything is right. Is the IP address correct for that server? Is the DNS entry right, aka have the right IP address?  Can you open wbemtest on the site server and connect to the DP? Is a firewall getting it the way? 

    Does this work from the site server to DP? https://www.youtube.com/edit?o=U&video_id=2nPxjzhZbVM


    Garth Jones

    Blog: https://www.enhansoft.com/blog Old Blog: https://sccmug.ca/

    Twitter: @GarthMJ Book: System Center Configuration Manager Reporting Unleashed

    • Marked as answer by Sanak pratap Wednesday, April 25, 2018 4:58 AM
    Monday, April 23, 2018 1:53 PM
  • Are you using the Primary Server Account to connect to the DP, if so, did you add the Primary Server account to the local admin group on the DP?
    Tuesday, April 24, 2018 4:15 AM
  • Seems its a issue with network device which is filtering the content transferred from SCCM primary server to DP.

    I found it using network flow and captured the transferred package (100 MB size package transferred but it has allowed only 15MB). 

    Thanks all for your suggestion for finding the root cause


    Regards, Pratap

    Wednesday, April 25, 2018 4:48 AM
  • Is this causing the issue. Can anyone confirm please

    "I found it using network flow and captured the transferred package (100 MB size package transferred but it has allowed only 15MB)."

    Or will the data gets compressed by default and its normal


    Regards, Pratap

    Wednesday, April 25, 2018 7:17 AM