Share via

Distribution of packages incomplete

Duchemin, Dominique 2,006 Reputation points
2022-09-18T23:37:00.033+00:00

Hello,

The last package content which went through were on Wednesday, September 14th , 2022 early morning and it was only between the Primary Server ands the distribution point (No client is involved)
242286-2022-09-18-17-07-33-distribution-ok.png

Since Wednesday, September 14 th , 2022 7:00 pm pst the Distribution points are not proceeding the distributions of packages...
242278-2022-09-18-17-10-13-distribution-not-ok.png

There is no error just packages distribution in progress...
242277-google-distribution.png

Reviewing the logs:

PatchDownloader.log (as Patch were downloaded on Tuesday, September 13th, 2022)

DistrMgr.log

Successfully created/updated the package UCP002CD SMS_DISTRIBUTION_MANAGER 9/14/2022 9:59:53 AM 34080 (0x8520)
…
CDistributionManager::CleanupDPRegistry process starts SMS_DISTRIBUTION_MANAGER 9/14/2022 1:05:45 PM 10372 (0x2884)
CDistributionManager::CleanupDPRegistry process completed SMS_DISTRIBUTION_MANAGER 9/14/2022 1:05:45 PM 10372 (0x2884)
CDistributionManager::CleanupMDMContent process started SMS_DISTRIBUTION_MANAGER 9/14/2022 1:05:45 PM 10372 (0x2884)
CDistributionManager::CleanupMDMContent process completed SMS_DISTRIBUTION_MANAGER 9/14/2022 1:05:45 PM 10372 (0x2884)
CDistributionManager::CleanDistributionPoints process completed. SMS_DISTRIBUTION_MANAGER 9/14/2022 1:05:46 PM 10372 (0x2884)
set quoted_identifier on;set ansi_warnings on;set ansi_padding on;set ansi_nulls on;set concat_null_yields_null on;set arithabort on;set numeric_roundabort off;set DATEFORMAT mdy; SMS_DISTRIBUTION_MANAGER 9/14/2022 1:20:39 PM 8804 (0x2264) [08S01][10054][Microsoft][SQL Server Native Client 11.0]TCP Provider: An existing connection was forcibly closed by the remote host. SMS_DISTRIBUTION_MANAGER 9/14/2022 1:20:39 PM 8804 (0x2264)
set quoted_identifier on;set ansi_warnings on;set ansi_padding on;set ansi_nulls on;set concat_null_yields_null on;set arithabort on;set numeric_roundabort off;set DATEFORMAT mdy; SMS_DISTRIBUTION_MANAGER 9/14/2022 1:20:39 PM 8804 (0x2264) [08S01][10054][Microsoft][SQL Server Native Client 11.0]Communication link failure SMS_DISTRIBUTION_MANAGER 9/14/2022 1:20:39 PM 8804 (0x2264)
Failed to connect to the SQL Server. SMS_DISTRIBUTION_MANAGER 9/14/2022 1:20:40 PM 8804 (0x2264)
IsSafeToGetSCF: Failed to get SQL connection SMS_DISTRIBUTION_MANAGER 9/14/2022 1:20:40 PM 8804 (0x2264)
Info: Currently Site UCP is initializing Site Control Data. Can't get SCF from database at this time. Will try later. SMS_DISTRIBUTION_MANAGER 9/14/2022 1:20:40 PM 8804 (0x2264)
Failed to get SCF while configuring ports. SMS_DISTRIBUTION_MANAGER 9/14/2022 1:20:40 PM 8804 (0x2264) set quoted_identifier on;set ansi_warnings on;set ansi_padding on;set ansi_nulls on;set concat_null_yields_null on;set arithabort on;set numeric_roundabort off;set DATEFORMAT mdy; SMS_DISTRIBUTION_MANAGER 9/14/2022 1:20:40 PM 160 (0x00A0)
[08S01][10054][Microsoft][SQL Server Native Client 11.0]TCP Provider: An existing connection was forcibly closed by the remote host. SMS_DISTRIBUTION_MANAGER 9/14/2022 1:20:40 PM 160 (0x00A0) set quoted_identifier on;set ansi_warnings on;set ansi_padding on;set ansi_nulls on;set concat_null_yields_null on;set arithabort on;set numeric_roundabort off;set DATEFORMAT mdy; SMS_DISTRIBUTION_MANAGER 9/14/2022 1:20:40 PM 160 (0x00A0)
[08S01][10054][Microsoft][SQL Server Native Client 11.0]Communication link failure SMS_DISTRIBUTION_MANAGER 9/14/2022 1:20:40 PM 160 (0x00A0) Failed to connect to the SQL Server. SMS_DISTRIBUTION_MANAGER 9/14/2022 1:20:40 PM 160 (0x00A0)
DP upgrade processing thread: Failed to get sql connection, will retry in 2 mins SMS_DISTRIBUTION_MANAGER 9/14/2022 1:20:40 PM 160 (0x00A0)
CDistributionManager::CleanupDPRegistry process starts SMS_DISTRIBUTION_MANAGER 9/14/2022 1:20:51 PM 10372 (0x2884)
CDistributionManager::CleanupDPRegistry process completed SMS_DISTRIBUTION_MANAGER 9/14/2022 1:20:51 PM 10372 (0x2884)
CDistributionManager::CleanupMDMContent process started SMS_DISTRIBUTION_MANAGER 9/14/2022 1:20:51 PM 10372 (0x2884)
CDistributionManager::CleanupMDMContent process completed SMS_DISTRIBUTION_MANAGER 9/14/2022 1:20:51 PM 10372 (0x2884)
CDistributionManager::CleanDistributionPoints process completed. SMS_DISTRIBUTION_MANAGER 9/14/2022 1:20:51 PM 10372 (0x2884)
RunContentCleanUp() start. SMS_DISTRIBUTION_MANAGER 9/14/2022 1:23:19 PM 5404 (0x151C)
GetContentLibLocation - VRPSCCMPR01.ad SMS_DISTRIBUTION_MANAGER 9/14/2022 1:23:31 PM 5404 (0x151C)
Finished GetContentLibLocation - VRPSCCMPR01.ad SMS_DISTRIBUTION_MANAGER 9/14/2022 1:23:31 PM 5404 (0x151C)
GetDPUsableDrives - SMS_DISTRIBUTION_MANAGER 9/14/2022 1:23:31 PM 5404 (0x151C)
Finished GetDPUsableDrives - SMS_DISTRIBUTION_MANAGER 9/14/2022 1:23:31 PM 5404 (0x151C)
RunContentCleanUp() end. SMS_DISTRIBUTION_MANAGER 9/14/2022 1:25:58 PM 5404 (0x151C)

... then today I have ...

SMS_EXECUTIVE started SMS_DISTRIBUTION_MANAGER as thread ID 5692 (0x163C). SMS_DISTRIBUTION_MANAGER 9/18/2022 5:46:27 PM 3388 (0x0D3C)
Inbox source is local on VRPSCCMPR01.AD SMS_DISTRIBUTION_MANAGER 9/18/2022 5:46:29 PM 5692 (0x163C)
Package Thread Limit: 5 SMS_DISTRIBUTION_MANAGER 9/18/2022 5:46:32 PM 5692 (0x163C)
Per package Thread Limit: 10 SMS_DISTRIBUTION_MANAGER 9/18/2022 5:46:32 PM 5692 (0x163C)
Retry interval: 30 SMS_DISTRIBUTION_MANAGER 9/18/2022 5:46:32 PM 5692 (0x163C)
DP upgrade thread Limit: 50 SMS_DISTRIBUTION_MANAGER 9/18/2022 5:46:32 PM 5692 (0x163C)
DP upgrade retry interval: 20 SMS_DISTRIBUTION_MANAGER 9/18/2022 5:46:32 PM 5692 (0x163C)
Shared DP reassignment thread limit: 50 SMS_DISTRIBUTION_MANAGER 9/18/2022 5:46:32 PM 5692 (0x163C)
DP Config change Thread Limit: 50 SMS_DISTRIBUTION_MANAGER 9/18/2022 5:46:32 PM 5692 (0x163C)
GetDPUsableDrives - SMS_DISTRIBUTION_MANAGER 9/18/2022 5:46:33 PM 5692 (0x163C)
Finished GetDPUsableDrives - SMS_DISTRIBUTION_MANAGER 9/18/2022 5:46:33 PM 5692 (0x163C)
GetContentLibLocation - VRPSCCMPR01.ad SMS_DISTRIBUTION_MANAGER 9/18/2022 5:46:33 PM 5692 (0x163C)
GetContentLibraryLocationFromDB() no records from ContentLibrary table. select Location from ContentLibrary where SiteCode='UCP' SMS_DISTRIBUTION_MANAGER 9/18/2022 5:46:33 PM 5692 (0x163C)
Finished GetContentLibLocation - VRPSCCMPR01.ad.medctr.ucla.edu SMS_DISTRIBUTION_MANAGER 9/18/2022 5:46:33 PM 5692 (0x163C)
SetContentLibLocationInReg - (null) SMS_DISTRIBUTION_MANAGER 9/18/2022 5:46:33 PM 5692 (0x163C)
Finished SetContentLibLocationInReg - (null) SMS_DISTRIBUTION_MANAGER 9/18/2022 5:46:33 PM 5692 (0x163C)
SetContentLibLocationInReg - (null) SMS_DISTRIBUTION_MANAGER 9/18/2022 5:46:33 PM 5692 (0x163C)
Finished SetContentLibLocationInReg - (null) SMS_DISTRIBUTION_MANAGER 9/18/2022 5:46:33 PM 5692 (0x163C)
Compiling E:\SCCM\bin\x64\smsdpprov.mof SMS_DISTRIBUTION_MANAGER 9/18/2022 5:46:33 PM 5692 (0x163C)
E:\SCCM\bin\x64\smsdpprov.mof is compiled successfully SMS_DISTRIBUTION_MANAGER 9/18/2022 5:46:40 PM 5692 (0x163C)
GetDPUsableDrives - SMS_DISTRIBUTION_MANAGER 9/18/2022 5:46:40 PM 5692 (0x163C)
Finished GetDPUsableDrives - SMS_DISTRIBUTION_MANAGER 9/18/2022 5:46:40 PM 5692 (0x163C)
successfully created directory F:\SMS_DP$\sms\logs SMS_DISTRIBUTION_MANAGER 9/18/2022 5:46:40 PM 5692 (0x163C)

PkgXferMgr.log

UCP002CD Found send request with ID: 140867, Package: UCP002CD, Version:147, Priority: 2, Destination: VSPSCCMDP01.AD, DPPriority: 200
UCP00D8E not found
UCP00D8F not found

ContentTranferManager.log

CTMJob({83E0CA31-3DA2-4110-8E6C-3EA73A2B1257}): CCTMJob::UpdateLocations - Received empty location update ContentTransferManager 9/18/2022 4:52:11 PM 17920 (0x4600)
CTMJob({83E0CA31-3DA2-4110-8E6C-3EA73A2B1257}): job suspended. ContentTransferManager 9/18/2022 4:52:11 PM 17920 (0x4600)
CTMJob({488A1A53-2076-48C4-9378-E27DBF479912}): CCTMJob::UpdateLocations - Received empty location update ContentTransferManager 9/18/2022 4:52:11 PM 5864 (0x16E8)
CTMJob({488A1A53-2076-48C4-9378-E27DBF479912}): job suspended. ContentTransferManager 9/18/2022 4:52:11 PM 5864 (0x16E8)

Thanks,
Dom

Microsoft Configuration Manager
0 comments
Accepted answer
  1. AllenLiu-MSFT 44,111 Reputation points Microsoft Vendor
    2022-09-22T06:58:11.74+00:00

    Hi, @Duchemin, Dominique

    Thanks very much for your feedback. We're glad that the problem is solved now. Here's a short summary for the problem, we believe this will help other users to search for useful information more quickly.

    Problem/Symptom:
    All distributed package stuck in "in progress" for all distribution point.
    The error message "Failed to connect to the SQL Server." show in distmgr.log.
    But the SQL connection seems good.

    Solution/Workaround:
    The issue was with one class "Win32_Serverfeature" which was not processed, when run wmi query in wbemtest "select * from Win32_ServerFeature where ID = 324", it does not show anything.

    So the solution is:
    Step 1: open cmd with admin rights
    Step 2: in command prompt, run below command:
    mofcomp.exe c:\windows\system32\wbem\ServerManager.DeploymentProvider.mof
    Step 3: use wbemtest to test wmi query “select * from Win32_ServerFeature where ID = 324”

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.
    0 comments

3 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. AllenLiu-MSFT 44,111 Reputation points Microsoft Vendor
    2022-09-19T07:36:12.573+00:00

    Hi, @Duchemin, Dominique

    Thank you for posting in Microsoft Q&A forum.

    It seems the error is related to SQL Server, we may try to:

    Verify that SQL Server services are running.
    Verify that the site can access the site database.
    Verify that the site database, transaction log, and tempdb are not full.

    And we might need to get a SQL admin to help us to solve this problem.

    If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    1 person found this answer helpful.
    0 comments
  2. Duchemin, Dominique 2,006 Reputation points
    2022-09-19T14:52:59.857+00:00

    Hello,

    All SQL Server services are running.
    242510-2022-09-19-7-50-13-sql-services.png

    The site can access the site database as I was able top deploy System Center Endpoint Protection to 300+ servers.

    The site database, transaction log, and tempdb are not full.

    Site Database
    242611-2022-09-19-7-48-59-database-data.png

    transaction log
    242488-2022-09-19-7-55-15-tempdb-data.png

    tempdb data
    242544-2022-09-19-7-48-22-database-log.png

    tempdb log
    242538-2022-09-19-7-56-09-tempdb-log.png

    Thanks,
    Dom

    0 comments
  3. Duchemin, Dominique 2,006 Reputation points
    2022-09-21T21:04:31.27+00:00

    Hello,

    Thank you to Sherry & Ziqi for their hard work and diligence.

    The issue was with one class "Win32_Serverfeature" which was not processed... (even Clicking "Add Roles and features" does not work)
    243672-2022-09-21-14-02-27-vrpsccmpr01-add-roles-and-feat.png

    or
    wbemtest to test wmi query “select * from Win32_ServerFeature where ID = 324”
    run locally or remotely does not show anything...

    So then:
    Step 1: open cmd with admin rights
    Step 2: in command prompt, run below command:
    mofcomp.exe c:\windows\system32\wbem\ServerManager.DeploymentProvider.mof
    Step 3: use wbemtest to test wmi query “select * from Win32_ServerFeature where ID = 324”

    Now the distribution point are getting all informations expected

    Thanks,
    Dom

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.