Installation succeeded but a patch failed

I have produced an application for "Microsoft Teams" 64 little bit client. When I install it from Software Center it runs and installs appropriately but reflects up as Failed. The AppEnpressure.log reflects the complying with (edited for clarity)

Post install actions is BasedOnExitCode Waiting for process 6352 to finish. Timeout = 120 minutes. Process 6352 terminated with exitcode: 0 Looking for exit code 0 in departure codes table... Matched departure code 0 to a Success entry in departure codes table.

You watching: Installation succeeded but a patch failed

Which, to me, reflects that the install completed with a code of 0, which is in the "Rerevolve Codes" tab for the program.

I've tfinished to usage packeras, having relocated from SCCM 2007, so might have done something stupid as soon as producing the application.

Thanks


7 comments
share
save
hide
report
67% Upvoted
This thread is archived
New comments cannot be posted and votes cannot be cast
Sort by
best


*

level 1
Admin - MSFT Enterpincrease Mobility MVP (damgoodadmin.com)
3 years ago
Detection rules. That snippet simply shows that the installer exited through code 0 which is success. However, look further/in other places in the logs to watch if the app was successfully detected.

If an installer succeeds yet the application isn't detected; that's a faientice.


6
Share
ReportSave
level 2
3 years ago

Take a look at AppDiscoexceptionally.log on the client to verify this.

See more: Standard Dual Chanel Pci Ide Controller Drivers Download, Driverupdate


3
Share
ReportSave
level 1
3 years ago

What's the actual error code in the Software Center? Its possible that the regime set up and also exited fine, however your detection method has something wrong through it.

Also, what is your detection method?


3
Share
ReportSave
level 2
3 years ago

Probably "detection method failed" :)


2
Share
ReportSave
level 1
3 years ago

Along via what everyone else has said about double checking your​ detection settings additionally double inspect that the installer is actually done. I've had actually a regime that we were utilizing a manuscript to install and also even though the script completed the installer was still doing stuff (or it was running the detection as well quick, I can't remember). I finished up adding a "ping 127.0.0.1 -n 60" to the finish of my install manuscript to provide everything time to type itself out. It was a little regimen in my case that took seconds to install.


1
Share
ReportSave
level 2
3 years ago

also the "failed" status in the software facility is a link that provides even more details. plug the hex code you acquire from that into cmtrace error lookup and also you have the right to get another clue regarding why it failed.


1
Share
ReportSave
level 1
Initial Poster3 years ago

Thanks everyone. It was a typo in my detection strategy, I was checking for DosplayVersion quite than DisplayVersion. I assumed that the detection was used before installation fairly than thereafter so never before also thshould look at that.

See more: Should I Delete My Linkedin Account, 7 Reasons Not To Delete Your Linkedin Profile


1
Share
ReportSave
View Entire Discussion (7 Comments)
More short articles from the SCCM community
Continue searching in r/SCCM


*

r/SCCM
All things System Center Configuration Manager...
50.4k
Members


431

Online


Created Nov 11, 2011
Join
*
*
*
*

*

Top posts june 8th 2017Top short articles of june, 2017Top articles 2017
helpclassiccomputers.info Appclassiccomputers.info coinsclassiccomputers.info premiumclassiccomputers.info gifts
aboutcareerspressadvertiseblogTermsContent policyPrivacy policyMod policy
Back to Top