Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!
When an application reports it failed to install but you can see it installed; that's usually the result of:
The detection method defined for the application is incorrect.
The install was wrapped inside of something that returned an exit code marked as failure for some reason not related to the application install itself.
For #1, check the detection method in the application on SCCM vs. what's on the client after installation. For #2, you have to troubleshoot what failed in the wrapper, however if the detection method is solid it'll clear up on its own after the next time the client runs a discovery cycle.
The result of the install (detection too) is in appenforce upon installation but after that the status is a reflection of appdetect.
In your case the answer lies within appenforce.log