Hi all,

I'm struggling to deploy virtual application via Application Catalog in lab environment, it fails with error Application installation not started, There was a problem starting the application installation on your computer ,  not sure for reason of failure but I can see some errors in ConfigMgrSoftwareCatalog.log... logs as below..

--------

[1][01/28/2013 18:09:23] :RTMWindowsClient.EvaluateScriptAndLog:Script function 'PollCDRSDKMethod' returned '1,16'
[1][01/28/2013 18:09:23] :ApplicationDetailViewModel.PollCDRSDKMethod:Polling method returned 1,16
[1][01/28/2013 18:09:23] :ApplicationDetailViewModel.InstallAppProgression-Error:The call to poll CDR SDK method failed with status of 16
[1][01/28/2013 18:09:23] :ApplicationDetailViewModel.UpdatePageView:PageViewMode changed to:FastInstallError
[1][01/28/2013 18:09:24] :FastInstallPageView:Create Page View FastInstallError
[1][01/28/2013 18:14:44] :PortalContext.NotifyShortcutReceived:Keyboard shortcut Shift
[1][01/28/2013 18:14:44] :PortalContext.HandleEventOnDemand:begin handling ShortcutReceived

---------

Please advise

• Edited by samtiger Monday, January 28, 2013 2:05 PM

I noticed the line "Error:The call to poll CDR SDK method failed with status of 16".  Any errors in log file Ccmsdkprovider.log?

We have seen this when there are applications that have dependancies that are not on the DP.  Can you verify this is not the case?

Were you able to resolve it?

we experienced a similar issue...turns out that BITS was disabled.

Once we enabled bits, the install worked.

cosimo

Good Morning\Afternoon,

We are experiencing a similar issue trying to invoke an installation from the application catalog. When trying to install an application with dependencies, the install fails with the above error after trying to evaluate requirements. All content has been checked and is available, BITS is on. I can install other applications from the catalog

My question is, is there a log file that might lead me to some answers, I have not found any relative information yet.

Any help would be greatly appreciated.

AppEnforce.log / AppDiscovery.log

Thanks,

I am aware of these two logs for determining installation status, but there are no entries getting written to either of these log files. I don't believe that I have even got to the app enforcement stage of this install. When I click on install from the application catalog, the window pops up saying preparing installation, then when it goes to evaluating requirements the installation fails pretty much straight away. I understand that at this stage SCCM is determining the dependencies and relationships of the install, so there is something broken there. So i guess my question, to be more specific, Is there a log file that captures this application preparation\evaluate requirements information that is happening prior to the commencement of the install.

Thanks.

Have you verified that you can deploy an application via the Admin Console successfully?

Is there a log file that captures this application preparation\evaluate requirements information that is happening prior to the commencement of the install.

Anyone find an answer on this one? Had the same issue/question today with one of our apps in software center.

If you have defined a custom script detection mode, please make sure the vbscript or powershell script are correct!

If you have defined a custom script detection mode, please make sure the vbscript or powershell script are correct!

• Proposed as answer by Rich Mawdsley 23 hours 23 minutes ago

If you have defined a custom script detection mode, please make sure the vbscript or powershell script are correct!

• Proposed as answer by Rich Mawdsley Friday, June 26, 2015 8:22 AM

The OP was referencing the App Catalog,  so my question for him/her remains.  As Torsten stated above, you should start by reviewing the AppEnforce.log and AppDiscovery.log for additional information.

In cases like this, where the install process fails before it gets to the SCCM client, I've found you generally won't find much help in the regular SCCM log files. At this point in the sequence it is likely the Silverlight component, not the SCCM client itself, which is experiencing the failure. You must check the Silverlight logs for troubleshooting details.

C:\Users\User.Name\AppData\LocalLow\Microsoft\Silverlight\is\*\*\1\s\*\f\ConfigMgrLogs
--* is a randomly-generated directory name, but there should only be one directory in the folder

This folder will contain a file named ConfigMgrSoftwareCatalog.log which may help troubleshoot where the install is failing.

If you have defined a custom script detection mode, please make sure the vbscript or powershell script are correct!

This was the issue for me.  The custom script on the Requirements was a WQL Query.  Although the WQL Query was correct, it was set with the "Begins With" value.  Once I changed this to "Contains" then it works fine.

• Proposed as answer by Rich Mawdsley 23 hours 22 minutes ago

If you have defined a custom script detection mode, please make sure the vbscript or powershell script are correct!

This was the issue for me.  The custom script on the Requirements was a WQL Query.  Although the WQL Query was correct, it was set with the "Begins With" value.  Once I changed this to "Contains" then it works fine.

• Proposed as answer by Rich Mawdsley Friday, June 26, 2015 8:23 AM