Share via

Application not installing

Duchemin, Dominique 2,006 Reputation points
2022-02-04T01:26:39.183+00:00

Hello,

I have an application which appears properly in SOftware Center as available but when trying to install it it failed...
Where to look for clues?

AppDiscovery.log

Did not detect app deployment type IBM Tivoli Storage Manager Client - Windows Installer (.msi file)(ScopeId_67BB9074-421B-4166-A053-A8090F9523EF/DeploymentType_c370df46-23b3-4557-a221-5004ee52e471, revision 1) for system. AppDiscovery 2/3/2022 4:42:07 PM 10668 (0x29AC)
ActionType - Install will use Content Id: Content_f8efe660-fc15-48fd-9198-c3f6aff7dd87 + Content Version: 1 for AppDT "IBM Tivoli Storage Manager Client - Windows Installer (.msi file)" [ScopeId_67BB9074-421B-4166-A053-A8090F9523EF/DeploymentType_c370df46-23b3-4557-a221-5004ee52e471], Revision - 1 AppDiscovery 2/3/2022 4:42:07 PM 10668 (0x29AC)
Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_67BB9074-421B-4166-A053-A8090F9523EF/DeploymentType_c370df46-23b3-4557-a221-5004ee52e471" AND Revision = 1)" AppDiscovery 2/3/2022 4:50:34 PM 3628 (0x0E2C)
Performing detection of app deployment type IBM Tivoli Storage Manager Client - Windows Installer (.msi file)(ScopeId_67BB9074-421B-4166-A053-A8090F9523EF/DeploymentType_c370df46-23b3-4557-a221-5004ee52e471, revision 1) for system. AppDiscovery 2/3/2022 4:50:34 PM 3628 (0x0E2C)
+++ MSI application not discovered [MSI Product Code: {6AFCC9C0-419D-48C1-B0A5-6C316C116C9D}, MSI Product version: ] AppDiscovery 2/3/2022 4:50:34 PM 3628 (0x0E2C)
+++ Did not detect app deployment type IBM Tivoli Storage Manager Client - Windows Installer (.msi file)(ScopeId_67BB9074-421B-4166-A053-A8090F9523EF/DeploymentType_c370df46-23b3-4557-a221-5004ee52e471, revision 1) for system. AppDiscovery 2/3/2022 4:50:34 PM 3628 (0x0E2C)
ActionType - Install will use Content Id: Content_f8efe660-fc15-48fd-9198-c3f6aff7dd87 + Content Version: 1 for AppDT "IBM Tivoli Storage Manager Client - Windows Installer (*.msi file)" [ScopeId_67BB9074-421B-4166-A053-A8090F9523EF/DeploymentType_c370df46-23b3-4557-a221-5004ee52e471], Revision - 1 AppDiscovery 2/3/2022 4:50:35 PM 3628 (0x0E2C)
Entering ExecQueryAsync for query "select * from CCM_AppDeliveryType where (AppDeliveryTypeId = "ScopeId_67BB9074-421B-4166-A053-A8090F9523EF/DeploymentType_c370df46-23b3-4557-a221-5004ee52e471" AND Revision = 1)" AppDiscovery 2/3/2022 4:58:31 PM 30468 (0x7704)
Performing detection of app deployment type IBM Tivoli Storage Manager Client - Windows Installer (.msi file)(ScopeId_67BB9074-421B-4166-A053-A8090F9523EF/DeploymentType_c370df46-23b3-4557-a221-5004ee52e471, revision 1) for system. AppDiscovery 2/3/2022 4:58:31 PM 30468 (0x7704)
+++ MSI application not discovered [MSI Product Code: {6AFCC9C0-419D-48C1-B0A5-6C316C116C9D}, MSI Product version: ] AppDiscovery 2/3/2022 4:58:31 PM 30468 (0x7704)
+++ Did not detect app deployment type IBM Tivoli Storage Manager Client - Windows Installer (.msi file)(ScopeId_67BB9074-421B-4166-A053-A8090F9523EF/DeploymentType_c370df46-23b3-4557-a221-5004ee52e471, revision 1) for system. AppDiscovery 2/3/2022 4:58:31 PM 30468 (0x7704)
ActionType - Install will use Content Id: Content_f8efe660-fc15-48fd-9198-c3f6aff7dd87 + Content Version: 1 for AppDT "IBM Tivoli Storage Manager Client - Windows Installer (*.msi file)" [ScopeId_67BB9074-421B-4166-A053-A8090F9523EF/DeploymentType_c370df46-23b3-4557-a221-5004ee52e471], Revision - 1 AppDiscovery 2/3/2022 4:58:32 PM 30468 (0x7704)

mtrmgr.log

VerQueryValue failed for FileDescription, file C:\Windows\FireEye\xagtnotif.exe, error 1813 mtrmgr 2/3/2022 5:22:47 PM 3520 (0x0DC0)
VerQueryValue failed for FileDescription, file C:\Windows\FireEye\xagtnotif.exe, error 1813 mtrmgr 2/3/2022 5:22:47 PM 3520 (0x0DC0)
VerQueryValue failed for FileDescription, file C:\Windows\FireEye\xagtnotif.exe, error 1813 mtrmgr 2/3/2022 5:22:47 PM 3520 (0x0DC0)
VerQueryValue failed for FileDescription, file C:\Windows\FireEye\xagtnotif.exe, error 1813 mtrmgr 2/3/2022 5:22:47 PM 3520 (0x0DC0)
VerQueryValue failed for FileDescription, file C:\Windows\FireEye\xagtnotif.exe, error 1813 mtrmgr 2/3/2022 5:22:47 PM 3520 (0x0DC0)
VerQueryValue failed for FileDescription, file C:\Windows\FireEye\xagtnotif.exe, error 1813 mtrmgr 2/3/2022 5:22:47 PM 3520 (0x0DC0)
Termination event received for process 30072 mtrmgr 2/3/2022 5:23:12 PM 9536 (0x2540)
Termination event received for process 24700 mtrmgr 2/3/2022 5:24:14 PM 9536 (0x2540)
Termination event received for process 456 mtrmgr 2/3/2022 5:24:14 PM 9536 (0x2540)

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. CcmSqlCE 2/3/2022 4:50:36 PM 29008 (0x7150)
[C:\Windows\CCM\CcmStore.sdf] Max active concurrent sessions has been reached for the session pool. Waiting for one of them to finish. CcmSqlCE 2/3/2022 4:50:36 PM 29008 (0x7150)
[C:\Windows\CCM\CcmStore.sdf] Max active concurrent sessions has been reached for the session pool. Waiting for one of them to finish. CcmSqlCE 2/3/2022 4:50:36 PM 29008 (0x7150)
[C:\Windows\CCM\CcmStore.sdf] Max active concurrent sessions has been reached for the session pool. Waiting for one of them to finish. CcmSqlCE 2/3/2022 4:50:36 PM 29008 (0x7150)
[C:\Windows\CCM\CcmStore.sdf] Max active concurrent sessions has been reached for the session pool. Waiting for one of them to finish. CcmSqlCE 2/3/2022 4:50:36 PM 29008 (0x7150)
Closed database 'C:\Windows\CCM\StateMessageStore.sdf'. CcmSqlCE 2/3/2022 4:51:27 PM 14456 (0x3878)
[C:\Windows\CCM\StateMessageStore.sdf] Initialized database session manager, session pool is NOT enabled. CcmSqlCE 2/3/2022 4:52:04 PM 21784 (0x5518)
Closed database 'C:\Windows\CCM\StateMessageStore.sdf'. CcmSqlCE 2/3/2022 4:53:04 PM 21784 (0x5518)
[C:\Windows\CCM\StateMessageStore.sdf] Initialized database session manager, session pool is NOT enabled. CcmSqlCE 2/3/2022 4:58:32 PM 21820 (0x553C)
Closed database 'C:\Windows\CCM\StateMessageStore.sdf'. CcmSqlCE 2/3/2022 4:59:18 PM 21820 (0x553C)
[C:\Windows\CCM\StateMessageStore.sdf] Initialized database session manager, session pool is NOT enabled. CcmSqlCE 2/3/2022 5:07:04 PM 12768 (0x31E0)
Closed database 'C:\Windows\CCM\StateMessageStore.sdf'. CcmSqlCE 2/3/2022 5:08:16 PM 12768 (0x31E0)
Database 'CcmStore.sdf' has been idled for 676 seconds. Closing it. CcmSqlCE 2/3/2022 5:21:21 PM 3520 (0x0DC0)
Closed database 'C:\Windows\CCM\CcmStore.sdf'. CcmSqlCE 2/3/2022 5:21:21 PM 3520 (0x0DC0)
[C:\Windows\CCM\StateMessageStore.sdf] Initialized database session manager, session pool is NOT enabled. CcmSqlCE 2/3/2022 5:22:04 PM 25268 (0x62B4)
Closed database 'C:\Windows\CCM\StateMessageStore.sdf'. CcmSqlCE 2/3/2022 5:23:16 PM 25268 (0x62B4)

StateMessageProvider

Could not load logging configuration for component CcmSqlCE. Using default values. StateMessageProvider 2/3/2022 4:52:03 PM 21784 (0x5518)
[01C5CA50] Received shutdown request from WMI StateMessageProvider 2/3/2022 4:53:04 PM 21784 (0x5518)
Could not load logging configuration for component CcmSqlCE. Using default values. StateMessageProvider 2/3/2022 4:58:32 PM 21820 (0x553C)
[01C2CA50] Received shutdown request from WMI StateMessageProvider 2/3/2022 4:59:18 PM 21820 (0x553C)
Could not load logging configuration for component CcmSqlCE. Using default values. StateMessageProvider 2/3/2022 5:07:03 PM 12768 (0x31E0)
[01BBCA50] Received shutdown request from WMI StateMessageProvider 2/3/2022 5:08:16 PM 12768 (0x31E0)
Could not load logging configuration for component CcmSqlCE. Using default values. StateMessageProvider 2/3/2022 5:22:04 PM 25268 (0x62B4)
[01B7CA50] Received shutdown request from WMI StateMessageProvider 2/3/2022 5:23:16 PM 25268 (0x62B4)

Any idea?
Thanks,
Dom

Microsoft Configuration Manager
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Rahul Jindal [MVP] 9,391 Reputation points MVP
    2022-02-04T08:20:09.45+00:00

    Did you check in appenforce log? If its an msi then try enabling verbose logging by adding /l*v <path to the log file> in the command line. Look for 'value 3' in the log to reveal the description of the error. Test it manually before making any changes in ConfigMgr.

    1 person found this answer helpful.
    0 comments
  2. Pavel yannara Mirochnitchenko 12,371 Reputation points MVP
    2022-02-05T19:02:08.757+00:00

    It is appenforce.log and eventviewer for msiinstaller you need to look.

    1 person found this answer helpful.
    0 comments
  3. Duchemin, Dominique 2,006 Reputation points
    2022-02-10T04:43:31.487+00:00

    Let me recheck these logs

    Thanks,
    Dom