Applications not deploying to computers; Dts failed with error code 0x80070002

Question

Applications not deploying to computers; Dts failed with error code 0x80070002

Maralok 26

Ever since we upgraded to ConfigMgr 2002, we have an issue that some newly built PCs do not receive any applications deployed to computers. Not all computers are affected, there is about a 50% chance that newly built PC is.

The task sequences themselves all finish successfully according to the "Status Messages" and the smsts.log. It's only after the task sequence, that the computers don't get any additional apps deployed to collections they are a member of. Weirdly enough, applications deployed to a user work just fine on the same computer. The computer accounts in the console all show as ok (with green checkmark), and they are really a member of the collection. The accounts aren't duplicated either.

The log files AppEnforce.log and AppDiscovery.log show absolutely no trace of the missing applications, it's like they don't exist.

The log file CIDownload.log however has these errors:

CCIDownloader::ParseDtsMessage - Dts failed with error code: 0x80070002. CI Downloader will retry.
CIDownloaderJob({CCE54587-6729-49B3-963A-633EA7318816}): Received Dts failure message during CI download.

And DataTransferService.log has these:

DTS job {BE1F799A-20BF-4E57-BC02-6768ABFEE16F} BITS job {5A3AA1B0-1B30-4F27-8DD3-9B67917AC24C} failed to download source file http://managementpoint.domain.com:80/SMS_MP/.sms_dcm?Id&DocumentId=GLOBAL/Platform_Settings/PROPERTIES&Hash=291F906FCBF1693519DA4F015D1265E11C5FAF1223B5B48D1410F20608C3A7EC&Compression=zlib to destination C:\WINDOWS\CCM\CIDownloader\Staging{278187BA-61B7-480B-BDCA-F38B61D4702F}_2.zip with error 0x80190194

It seems like the client isn't able to correctly talk to the management point for some reason, but I cannot figure out why. We use HTTP, so certificates can't be an issue. If I uninstall the client ("ccmsetup /uninstall") and reinstall it, the PCs work correctly by the way.

I have looked at a few similar posts, however those mentioning the same error codes are generally just about a single application failing to install because of a faulty requirement in the deployment type. However, for us, all applications fail to install, even those that don't have any requirements set.

Accepted answer

2 additional answers

Your answer

Answer 1

AllenLiu-MSFT 49,316 Microsoft External Staff

@Maralok
Thank you for posting in Microsoft Q&A forum.
I found someone has encountered the similar issue with yours, to resolve the issue, he created a new revision of every application, a easy way is to make a small change to the application properties and then save it. You may update some properties you are not using. This will cause a new revision to be created automatically. After that check if clients can download the packages correctly?

If the response is helpful, please click "Accept Answer" and upvote it.
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.

Maralok 26 Reputation points

2020-09-22T14:53:32.173+00:00

Thank you, this seems to have resolved the issue.

For reference, what I did to create a new revision of every application was use the following Powershell to try and remove a nonexistant support contact, that incremented the revision number on every application without changing anything:

Get-CMApplication | % { $.LocalizedDisplayName; Set-CMApplication $ -RemoveSupportContact foo }
Mike Niles 1 Reputation point

2021-12-30T18:28:05.373+00:00

Nice work on this! It worked well for me after the changes below. I'm on 2111 and still running across the same issue occasionally.

I had to modify this slightly as I was running into a hard stop when the command ran across the first Retired Application. Also notable is the web page seems to have eliminated the underscore after your dollar sign. That lead me to removing the reference to the LocalizedDisplayName altogether.

I also found that it took a while to run and gave no feedback on progress, so I added -Verbose to the last bit.

Here's my changed version:

Get-CMApplication | Where-Object -Property IsExpired -EQ 0 | SetCMApplication -RemoveSupportContact foo -Verbose

Cheers!
Giles Frankling 1 Reputation point

2022-02-14T11:57:44.18+00:00

Thanks we had this issue as well after going up to version 2111.
pilgi3 21 Reputation points

2022-02-23T10:19:44.757+00:00

I don't know why this works, because I tried but without success.
Still the same error after creating new revision numbers of the affected applications.
If I understand it right, you have created new revisions of all your applications?
That's not practical for 400+ applications and IMO it is not a application error in the database.
Because If I reinstall the memcm client with unistall on the affected client all works again properly.
As well I can see in the logs, the applications version are fine, but I don't know how I could clean up the policy completely and download all again from scratch without uninstall the memcm client.
Any ideas maybe?
Maralok 26 Reputation points

2022-02-24T11:24:26.513+00:00

Your symptoms sound exactly like the ones I had. Some computers do not receive applications, and if you reinstall the SCCM client, the issue is fixed for that one computer.

And in my case, the issue was completely fixed site wide by the proposed solution of creating a new revision for all applications. As I noted above, I did it with that Powershell script because I also didn't feel like manually clicking on hundreds of applications.

Answer 2

Jason Sandys 31,411 Microsoft Employee Moderator

0x80190194 = Not Found (404)

Thus, the clients are talking to the MP fine, but the requested files aren't found on the MP.

Do you have multiple MPs in the environment?

Are the clients going through a proxy or any other type of network filtering to get to the MP(s)?

Maralok 26 Reputation points

2020-09-18T12:06:33.12+00:00

We used to have a second MP but it was removed. It was properly uninstalled by right clicking it in "Servers and Site System Roles" and doing a "Remove Role".

If I look in ADSI Edit in the "System Management" container, the correct MP is listed and the old MP is gone. If I check affected clients in the ClientLocation.log then they show communication to the correct MP.

There is no proxy or similar device or any network partitioning, the internal network is completely open. The MP also has its firewall turned off.
Jason Sandys 31,411 Reputation points Microsoft Employee Moderator

2020-09-18T18:17:21.227+00:00

And I'm assuming that the MP listed in the log is correct, expected one?

Does this happen on all applications?
Maralok 26 Reputation points

2020-09-18T19:50:46.047+00:00

Yes, the MP is the correct one. Also, some things on the affected computers work. I can distribute applications that install as the user. I can run packages. Hardware inventory runs, and correctly reports in "Resource Explorers", and task sequences deployed to that computer show up correctly.

Only applications that install as system fail to do anything.

Yes, this happens for all applications deployed to the computer. Those that install during the task sequence as part of an "Install Applications" step work fine (and they show up in all the appropriate logs like AppEnforce.log), only the ones that are deployed to collections do not do anything.
Jason Sandys 31,411 Reputation points Microsoft Employee Moderator

2020-09-18T20:12:37.117+00:00

Have you tried the URL that fails on one system from another system that is able to receive apps? For the log snippet above, that's http://managementpoint.domain.com:80/SMS_MP/.sms_dcm?Id&DocumentId=GLOBAL/Platform_Settings/PROPERTIES&Hash=291F906FCBF1693519DA4F015D1265E11C5FAF1223B5B48D1410F20608C3A7EC&Compression=zlib to destination C:\WINDOWS\CCM\CIDownloader\Staging{278187BA-61B7-480B-BDCA-F38B61D4702F}_2.zip.

Answer 3

AlexG 1

Hi everyone! I see that it's old discuss but I want to know how you solved this problem.
Now I have MECM 2203, and applications doesn\t visible in Software Center.
Changing revision helping only for current PCs, if new pc appear in SCCM applications doesn't visible

Anonymous

2022-06-17T10:50:20.847+00:00

We're on MECM 2111, having exactly the same issues. The same as AlexG-2537 changing the application revision number only works for existing clients, any newly imaged devices fail to see applications which have worked for years. How do we fix this?
Jiri Lastovka 1 Reputation point

2022-06-17T11:20:24.24+00:00

Hello,
Similar problem here after installing SCCM update 2203 and 2203 hotfix. Before installation everything worked.

After new computer installation in CCM there are only packages and updates but no applications is available in the client. The logs AppDiscovery.log AppEnforce.log in %WINDIR%/CCM/Logs are completely missing.

Tried to disable defender and firewall, multiple restarts but still only in the packages are shown.
If we try to reinstall the client multiple times sometimes it gets to work again. On clients installed before update, everything seems to work.

Some info from logs...

CIDownloader.log
CCIDownloader::ParseDtsMessage - Dts failed with error code: 0x80070002. CI Downloader will retry.
CIDownloaderJob({D196BBB5-47A9-4616-BFBC-74028DB4B250}): Received Dts failure message during CI download.

CcmSqlCE.log
[C:\WINDOWS\CCM\CcmStore.sdf] Max active concurrent sessions has been reached for the session pool. Waiting for one of them to finish.

SystemTempLockdown.log
Failed to re-direct system temp folder to a more secure location. Error 0x80070005

wedmtrace.log
No CCM Identification blob
InventoryVersionNumber for '{00000000-0000-0000-0000-000000000002}' not found.
Jiri Lastovka 1 Reputation point

2022-06-17T12:20:08.427+00:00

As suggested by Maralok-8255 and MikeNiles

Set-Location 'C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin'
Import-Module .\ConfigurationManager.psd1

New-PSDrive -Name "SCCMDrive" -PSProvider CMSite -Root "sccm.domain.local" -Description "Primary site"
Set-Location SCCMDrive:

Get-CMApplication | Where-Object -Property IsExpired -EQ 0 | Set-CMApplication -RemoveSupportContact foo -Verbose

after this apps start showing in the client
AlexG 1 Reputation point

2022-06-17T13:21:16.23+00:00

It's just workround that help to show applications on current PCs.
After you deploy new PC this is applications will be not visible again

Share via

Applications not deploying to computers; Dts failed with error code 0x80070002

2 additional answers

Your answer