locked
No error after App-V 5.0 deployment fails from SCCM 2012 SP1 RRS feed

  • Question

  • Where’s the logs?!

    SCCM 2012 SP1 on Server 2008 R2 Standard

    App-V 5.0

    I have sequenced a couple simple apps (Adobe Reader and Softphone) on a clean vm’s

    I have packaged an Application with the .appv

    I have distributed it to all my DP’s and gone in the directory structure there to affirm the packages are there

    I can deploy regular Applications and Packages with no difficulty

    When I deploy and App-V package the test target computer eventually disappears from the Deployment Status tabs and the Summarization globe turns red.

    There are no AppEnforce.log or VirtualApp.log files on the target computer.

    There are, however, event logs showing successful functioning of the App-V client on the target computer but nothing about the deployments attempted.

    I have installed Windows Management Framework 3.0, KB2533623 and Appv_setup.exe successfully on several target machines and it appears to be installed correctly.

    After a failed attempt to deploy app-v package I have no error messages in the Monitoring Console in SCCM. The clients execmgr.log are not being touched. There is nothing in the eventvwr for app-v about the deployments. Is there a log on the SCCM server that would reveal what is failing? I know that it is getting to the distribution points. I am looking for configurations specifically to allow App-V delivery but all the documents I have read say that unlike 2007, 2012 is ready out of the box. Thanks for your consideration.

    Friday, July 5, 2013 11:45 PM

Answers

  • RESOLVED ~ I had not updated the client after updating SCCM 2012 to SP1

    I had the Server at SCCM 2012 SP1, App-V at 5.0 SP1

    BUT the SCCM Client agent was not updated to SP1

    SCCM 2012 Client version is 5.00.7711.0000

    SCCM 2012 SP1 Client version is 5.00.7804.1000

    • Proposed as answer by znack Sunday, July 28, 2013 10:12 AM
    • Marked as answer by Simifa Monday, July 29, 2013 7:02 PM
    Thursday, July 11, 2013 5:21 PM

All replies

  • Hello,

    Without the appenforce.log - I would say that this client has never received any software using the Application Model.

    Is the SCCM client up and running? Have you determined if the computer fulfills your requirements?

    You can verify log-files for the SCCM-logs - read this article to better understand what SCCM-log file might be applicable.

    http://technet.microsoft.com/en-us/library/hh427342.aspx


    Nicke Källén | The Knack| Twitter: @Znackattack

    Sunday, July 7, 2013 5:53 PM
  • Thank you, I did not realize that the appenforce.log was created when deploying any "Application". I am using clean machines.

    As soon as I deployed a non-App-V "Application" an Appenforce.log was created and the "Application" was successfully installed and fully logged in the appenforce.log .

    Niether the appenforce or execmgr logs are touched when I deploy the App-V packages.

    The ConfigMgr client is working great with normal Application and Package deployments

    I can see that the client is not picking up the policy for App-V deployments. I have verified the data has reached the distribution point.

    My prerequisites for the App-V client install are there and I have a working service called 'Microsoft App-V client'

    Is there a way I can test the App-V client other than deploying a App-V package?

    Is there a way I can test my sequenced application other that deploying it as a package?

    Monday, July 8, 2013 4:02 PM
  • Hello,

    See howto test a package using the standalone distribution model;

    http://blogs.technet.com/b/virtualvibes/archive/2013/03/12/app-v-5-0-standalone-mode-adding-and-publishing-a-package.aspx

    I am very surprised that you claim that you have deployed applications, yet there is no appenforce.log?

    I really think you need to investigate the logs more to understand what happens with the SCCM 2012 client.


    Nicke Källén | The Knack| Twitter: @Znackattack

    Monday, July 8, 2013 6:21 PM
  • I am sorry, you may have misunderstood me. I DO have the AppEnforce.log as soon as I send an Application to it. Becuase I was using clean machines they had never had an regular application deployed to it yet. The AppEnforce log doesn't appear until one has been deployed.

    I have not been able to get and App-V package to update the AppEnforce log yet.

    I did test my sequenced application as is done in the link above and it installs successfully. (Thanks for the link!)

    I have discovered that the 'DeploymentID' of the App-v deployment exists in the PolicyAgent.log, the PolicyEvaluator.log and the StatusAgent.logs on the Client but it never gets to the AppIntentEval.log or the AppEnforce.log

    I am reviewing the logs with CMtrace and I am not recieving any errors.

    It just seems to stop there. I can see regular 'Application Model' deployments in all of the above logs.

    Since my normal Application deployments work fine, it must be a specific App-V configuration.

    Monday, July 8, 2013 9:00 PM
  • I finally found an Error! Seems totally benign but it is litterally the only errors I have found.

    They are in the PolicyEvaluator.log and are in amongst the DeploymentID I am testing which is{1212D908-714A-49AA-9792-1E316F02C6E3}

    I am not getting any hits on these errors:

    Failed to load CCM_CIAssociations object from XML. Instance is ignored.              PolicyAgent_PolicyEvaluator                7/9/2013 10:17:16 AM    2980 (0x0BA4)

    Raising event:

    instance of CCM_PolicyAgent_PolicyRuleApplied

    {

                    ClientID = "GUID:D356AF70-2188-4FDF-9960-C22E76BFD907";

                    DateTime = "20130709171716.752000+000";

                    PolicyID = "ScopeId_C87C8C34-55FD-4735-B675-4DA04A72F5C0/Application_82c8e8e3-aca0-4d3d-8b72-4f9487c90536/CA";

                    PolicyNamespace = "\\\\ULAB-1\\ROOT\\ccm\\Policy\\Machine\\RequestedConfig";

                    PolicySource = "SMS:EVC";

                    PolicyVersion = "6.00";

                    ProcessID = 3640;

                    RuleCondition = "";

                    RuleID = "{Rule_ScopeId_C87C8C34-55FD-4735-B675-4DA04A72F5C0/Application_82c8e8e3-aca0-4d3d-8b72-4f9487c90536/CA}";

                    ThreadID = 2980;

    };

                    PolicyAgent_PolicyEvaluator       7/9/2013 10:17:16 AM    2980 (0x0BA4)

    Applied policy CCM_Policy_Policy4.PolicyID="ScopeId_C87C8C34-55FD-4735-B675-4DA04A72F5C0/Application_82c8e8e3-aca0-4d3d-8b72-4f9487c90536/CA",PolicySource="SMS:EVC",PolicyVersion="6.00"            PolicyAgent_PolicyEvaluator       7/9/2013 10:17:16 AM       2980 (0x0BA4)

    Raising event:

    instance of CCM_PolicyAgent_PolicyEvaluationComplete

    {

                    ClientID = "GUID:D356AF70-2188-4FDF-9960-C22E76BFD907";

                    DateTime = "20130709171716.760000+000";

                    PolicyNamespace = "\\\\ULAB-1\\ROOT\\ccm\\Policy\\Machine\\RequestedConfig";

                    PolicyPath = "CCM_Policy_Policy4.PolicyID=\"ScopeId_C87C8C34-55FD-4735-B675-4DA04A72F5C0/Application_82c8e8e3-aca0-4d3d-8b72-4f9487c90536/CA\",PolicySource=\"SMS:EVC\",PolicyVersion=\"6.00\"";

                    ProcessID = 3640;

                    ThreadID = 2980;

    };

                    PolicyAgent_PolicyEvaluator       7/9/2013 10:17:16 AM    2980 (0x0BA4)

    Policy state for [CCM_Policy_Policy4.PolicyID="ScopeId_C87C8C34-55FD-4735-B675-4DA04A72F5C0/Application_82c8e8e3-aca0-4d3d-8b72-4f9487c90536/CA",PolicyVersion="6.00",PolicySource="SMS:EVC"] is currently [Active]  PolicyAgent_PolicyEvaluator                7/9/2013 10:17:16 AM    3896 (0x0F38)

    Updating policy CCM_Policy_Policy4.PolicyID="{1A9318B8-EE31-48C0-BA72-B63AD11BE58A}",PolicySource="SMS:EVC",PolicyVersion="1.00"              PolicyAgent_PolicyEvaluator       7/9/2013 10:17:16 AM       2980 (0x0BA4)

    Applying policy {1A9318B8-EE31-48C0-BA72-B63AD11BE58A}       PolicyAgent_PolicyEvaluator       7/9/2013 10:17:16 AM                2980 (0x0BA4)

    Failed to find property 'Order' in 'CCM_Scheduler_ScheduledMessage' class defintion. Error 0x80041002. Default value will be used for this property          PolicyAgent_PolicyEvaluator       7/9/2013 10:17:19 AM    2980 (0x0BA4)

    Failed to find property 'Order' in 'CCM_Scheduler_ScheduledMessage' class defintion. Error 0x80041002. Default value will be used for this property          PolicyAgent_PolicyEvaluator       7/9/2013 10:17:19 AM    2980 (0x0BA4)

    Failed to find property 'SettingTypes' in 'CCM_ApplicationCIAssignment' class defintion. Error 0x80041002. Default value will be used for this property          PolicyAgent_PolicyEvaluator       7/9/2013 10:17:19 AM    2980 (0x0BA4)

    Failed to find property 'PersistOnWriteFilterDevices' in 'CCM_ApplicationCIAssignment' class defintion. Error 0x80041002. Default value will be used for this property                PolicyAgent_PolicyEvaluator       7/9/2013 10:17:19 AM                2980 (0x0BA4)

    Tuesday, July 9, 2013 6:01 PM
  • RESOLVED ~ I had not updated the client after updating SCCM 2012 to SP1

    I had the Server at SCCM 2012 SP1, App-V at 5.0 SP1

    BUT the SCCM Client agent was not updated to SP1

    SCCM 2012 Client version is 5.00.7711.0000

    SCCM 2012 SP1 Client version is 5.00.7804.1000

    • Proposed as answer by znack Sunday, July 28, 2013 10:12 AM
    • Marked as answer by Simifa Monday, July 29, 2013 7:02 PM
    Thursday, July 11, 2013 5:21 PM