locked
Installation of a distribution point fails, Error 1722 DPConnection::ConnectWMI() - Failed to connect RRS feed

  • Question

  • Hi!

    I have tried to install a DP on a newly installed 2012 server. The SCCM DP role will not complete installation. Site server and the new DP server are in the same domain and the firewall openings are in place

    Technical information:

    DISTMGR.log:

    CWmi::Connect() failed to connect to \\ADMCMDP001.domain\root\CIMv2. Error = 0x800706BA $$<sms_distribution_manager><10-17-2013 15:20:57.176-120><thread=7932 (0x1efc)="">STATMSG: ID=2391 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Admcmsite001.domain SITE=VSM PID=4980 TID=7932 GMTDATE=to okt 17 13:20:57.178 2013 ISTR0="["Display=\\ADMCMDP001.domain\"]MSWNET:["SMS_SITE=VSM"]\\ADMCMDP001.domain\" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\ADMCMDP001.domain\"]MSWNET:["SMS_SITE=VSM"]\\ADMCMDP001.domain\" $$<sms_distribution_manager><10-17-2013 15:20:57.178-120><thread=7932 (0x1efc)="">DPConnection::ConnectWMI() - Failed to connect to ADMCMDP001.domain. $$<sms_distribution_manager><10-17-2013 15:20:57.178-120><thread=7932 (0x1efc)="">~Failed to install DP files on the remote DP. Error code = 1722 $$<sms_distribution_manager><10-17-2013 15:20:57.179-120></sms_distribution_manager></thread=7932></sms_distribution_manager></thread=7932></sms_distribution_manager></thread=7932></sms_distribution_manager>

    .........

    Start adding package to server ["Display=\\ADMCMDP001.domain\"]MSWNET:["SMS_SITE=VSM"]\\ADMCMDP001.domain\...  $$<SMS_DISTRIBUTION_MANAGER><10-17-2013 16:17:44.719-120><thread=7484 (0x1D3C)>
    ~The last source update time for pkg VSM001AA is 17.10.2013 15:22:37 W. Europe Daylight Time  $$<SMS_DISTRIBUTION_MANAGER><10-17-2013 16:17:44.719-120><thread=11244 (0x2BEC)>
    ~The next start time for pkg VSM001AA is 18.10.2013 15:19:00 W. Europe Daylight Time  $$<SMS_DISTRIBUTION_MANAGER><10-17-2013 16:17:44.719-120><thread=11244 (0x2BEC)>
    ~Sleep 262 seconds...  $$<SMS_DISTRIBUTION_MANAGER><10-17-2013 16:17:44.720-120><thread=11244 (0x2BEC)>
    Will wait for 1 threads to end.  $$<SMS_DISTRIBUTION_MANAGER><10-17-2013 16:17:44.721-120><thread=7484 (0x1D3C)>
    Thread Handle = 0000000000003488  $$<SMS_DISTRIBUTION_MANAGER><10-17-2013 16:17:44.721-120><thread=7484 (0x1D3C)>
    Attempting to add or update a package on a distribution point.  $$<SMS_DISTRIBUTION_MANAGER><10-17-2013 16:17:44.722-120><thread=6400 (0x1900)>
    The distribution point ["Display=\\ADMCMDP001.domain\"]MSWNET:["SMS_SITE=VSM"]\\ADMCMDP001.domain\ is not installed or upgraded yet.  $$<SMS_DISTRIBUTION_MANAGER><10-17-2013 16:17:44.728-120><thread=6400 (0x1900)><sms_distribution_manager><thread=7932 (0x1efc)=""><sms_distribution_manager><thread=7932 (0x1efc)=""><sms_distribution_manager><thread=7932 (0x1efc)=""><sms_distribution_manager></sms_distribution_manager></thread=7932></sms_distribution_manager></thread=7932></sms_distribution_manager></thread=7932></sms_distribution_manager>

    <sms_distribution_manager><thread=7932 (0x1efc)=""><sms_distribution_manager><thread=7932 (0x1efc)=""><sms_distribution_manager><thread=7932 (0x1efc)=""><sms_distribution_manager><thread=7932 (0x1efc)="">

    The server appears in the SCCM console as a site system server, and as a distribution point, but IIS will not install, I chose to install IIS in the wizard for DP site system role installation, and the folders that are supposed to appear in the D drive automatically are not created. According to Technet, port TCP 135 and 445 must be open from the site server to the DP, which I have verified, and the Admin$ share on the distribution point should be accessible from the site server, which it is.

    How should I proceed?

    Thursday, October 17, 2013 2:26 PM

Answers

  • Last night the DP role installed successfully after I left the Office, I am guessing there was a local firewall issue. Thx for the suggestions anyway...


    Freddy

    • Marked as answer by CesarTabares Friday, October 18, 2013 3:04 PM
    Friday, October 18, 2013 3:04 PM

All replies

  • Are the features .NET 3.5, BITS and Remote Differential Compression installed on the DP?  I would also try disabling the firewall and put the computer account of the primary server in the local admin group on the DP.  This gets around any permissions issues.

    Mike Leach | http://blogs.catapultsystems.com/mleach/default.aspx


    Thursday, October 17, 2013 2:49 PM
  • 0x800706BA = The RPC server is unavailable.

    This would normally suggest a network connectivity issue of some sort (eg firewall settings).

    the firewall openings are in place

    What does this mean? Are you referring to a hardware firewall? Did you turn off the Windows firewall on the servers as a test?



    Gerry Hampson | Blog: www.gerryhampsoncm.blogspot.ie | LinkedIn: Gerry Hampson | Twitter: @gerryhampson


    Thursday, October 17, 2013 5:34 PM
  • Last night the DP role installed successfully after I left the Office, I am guessing there was a local firewall issue. Thx for the suggestions anyway...


    Freddy

    • Marked as answer by CesarTabares Friday, October 18, 2013 3:04 PM
    Friday, October 18, 2013 3:04 PM
  • I'm having this same error, except the primary site server and the new distribution point server are on the same subnet and the Windows Firewall is disabled on both of them. If I run WBEMTEST from the primary site server and connect to the new DP, Enum Classes connects just fine.

    I don't know what else to check.. it can't be a firewall issue because there is no firewall between nodes on the same subnet.  (They're even plugged into the same switch!)

    What else can I check?

    Friday, July 25, 2014 5:36 PM
  • Another common mistake is not having an admin context to install the remote DP. By default, that would be the site server's computer account, although you can specify a different account when you configure the DP as a site system. I'd check that first if the firewall is not an issue.

    Wally Mead

    Friday, July 25, 2014 5:47 PM
  • The primary site server's computer account is a member of Domain Admins and also a member of the Local Administrators group on the new server.  I know that's redundant, but I just want to be sure.  I've even completely formatted the drive and reinstalled windows server 2012 from scratch on the new server.
    Friday, July 25, 2014 5:50 PM
  • I even had a working DP on this same server before.  I removed it and tried to re-add it to change the name because we closed one of our offices and brought the server back to the HQ.
    Friday, July 25, 2014 5:51 PM
  • I'd check the prerequisites here, and then if you've confirmed them all, including admin rights, then I'd contact CSS:

    http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SiteSystemRolePrereqs


    Wally Mead

    Friday, July 25, 2014 6:05 PM
  • Interesting.  I deleted the site server and recreated it to use a service account instead of the primary site server's computer account and it worked.  But.. both accounts have the exact same permissions on the new server.  Is that a bug that was introduced in CU3?  Can't use computer accounts anymore?
    Friday, July 25, 2014 6:25 PM
  • Haven't tried it in CU3, as I am on R2, and it only has CU2. But I seriously doubt it is a bug in CU3. If you think it is, open a case with CSS and they'll tell you. I know it works with computer accounts in R2.

    Wally Mead

    Friday, July 25, 2014 6:46 PM
  • I have the license for SCCM 2012 R2, but I'm a little gunshy about upgrading to it.  I've got everything working and I'm afraid an in-place upgrade will break something.

    I know this is a total-threadjack, but if I were to install it on the primary site server, how do all the DPs get upgraded?

    Friday, July 25, 2014 7:05 PM
  • They get upgraded automatically by the site server after its upgrade. I can't help you feel more secure in it, but I'd upgrade immediately if it were me.

    Wally Mead

    Friday, July 25, 2014 7:52 PM
  • I had this same issue with installing additional DP's under Secondary Sites. I discovered that both the Primary Site server account AND and Secondary Site server account have to be local admins of the DP.
    Thursday, August 21, 2014 5:23 PM
  • I had this same issue with installing additional DP's under Secondary Sites. I discovered that both the Primary Site server account AND and Secondary Site server account have to be local admins of the DP.

    Are you 100% sure? I can't think of any reason why the primary site server would contact a DP that belongs to a secondary site. But I might be wrong.

    Torsten Meringer | http://www.mssccmfaq.de

    Thursday, August 21, 2014 5:52 PM
  • You are probably correct. My initial configuration was to have the Primary as local admin. Things worked on all my servers except one which is when I realized that it was missing the Secondary Site server account and somehow all the other working DP's had their Sec Site server accounts as admin.  I added that and it worked. I must have configured the others ones in the past and forgot.  I assumed both were required.

    • Edited by JoelDB Thursday, August 21, 2014 10:26 PM
    Thursday, August 21, 2014 10:24 PM
  • I would agree with Torsten, can't think of any reason why the primary site server's computer account would need any access to a DP installed at a secondary site.

    Wally Mead

    Monday, August 25, 2014 9:38 PM