Share via

Application Deployment Evaluation Cycle fails with an error code 80040e14

  • Article

Question

Thursday, March 17, 2016 11:21 AM

Hey guys,

I'm having trouble with one of my Configuration Manager clients. It's not evaluating application deployments at all. I have been struggling with this problem for the last few days now. During that time I have been searching the internet for similar problems. Usually I could find at least some similarities, but this one seems to be a rare one.

Running the task Application Deployment Evaluation Cycle it fails at some point and the error 0x80040e14 pops up multiple times. Monitoring the log files related to application deployment in merge mode outputs the following after the Application Deployment Evaluation Cycle is triggered.

CAgent::CreateJob - Creating new CI Agent Job for machine CIAgent 17-3-2016 12:04:27 24604 (0x601C)
CAgent::EvaluateCIs CIAgent 17-3-2016 12:04:27 12936 (0x3288)
CIAgentJob({E8B13476-8E7E-4593-BF47-B056E8D0E800}): CAgentJob::QueueEvent - Queueing event and incrementing semaphore Transition CIAgent 17-3-2016 12:04:27 12936 (0x3288)
CIAgentJob({E8B13476-8E7E-4593-BF47-B056E8D0E800}): CAgentJob::HandleEvent(Event=Transition, CurrentState=Init) CIAgent 17-3-2016 12:04:27 12936 (0x3288)
CIAgentJob({E8B13476-8E7E-4593-BF47-B056E8D0E800}): Client requesting CIAgentJob context info for key: StateMessagePriority CIAgent 17-3-2016 12:04:27 12936 (0x3288)
CIAgentJob({E8B13476-8E7E-4593-BF47-B056E8D0E800}): TransitionState(From=Init, To=WaitingForAssignedCI) for Event=Transition CIAgent 17-3-2016 12:04:27 12936 (0x3288)
CIAgentJob({E8B13476-8E7E-4593-BF47-B056E8D0E800}): CAgentJob::QueueEvent - Queueing event and incrementing semaphore Transition CIAgent 17-3-2016 12:04:27 12936 (0x3288)
CIAgentJob({E8B13476-8E7E-4593-BF47-B056E8D0E800}): QueueDebug - Executing Event. CIAgent 17-3-2016 12:04:27 12936 (0x3288)
DCMAgentJob({1D3BE0E7-39C6-4807-B77B-326A28FDE9EC}): CDCMAgentJob::HandleEvent(Event=Transition, CurrentState=Evaluating) DCMAgent 17-3-2016 12:04:27 12936 (0x3288)
CIAgentJob({E8B13476-8E7E-4593-BF47-B056E8D0E800}): CAgentJob::HandleEvent(Event=Transition, CurrentState=WaitingForAssignedCI) CIAgent 17-3-2016 12:04:27 5676 (0x162C)
CIAgentJob({E8B13476-8E7E-4593-BF47-B056E8D0E800}): CAgentJob::QueueEvent - Queueing event and incrementing semaphore DownloadCIs CIAgent 17-3-2016 12:04:27 5676 (0x162C)
CIAgentJob({E8B13476-8E7E-4593-BF47-B056E8D0E800}): QueueDebug - Executing Event. CIAgent 17-3-2016 12:04:27 5676 (0x162C)

... and a lot more in between ...

CCIDigestStore::CancelAndStartIdleTimer Canceling existing idle time-out task CIDownloader 17-3-2016 12:04:28 12936 (0x3288)
DCMAgentJob({EB68B6E0-AEE6-48A2-AC6C-0C1DF7496A03}): NotifyComplete DCMAgent 17-3-2016 12:04:28 12936 (0x3288)
DCMAgentJob({EB68B6E0-AEE6-48A2-AC6C-0C1DF7496A03}): TransitionState(From=Evaluating, To=Success) for Event=Transition DCMAgent 17-3-2016 12:04:28 12936 (0x3288)
DCMAgentJob({EB68B6E0-AEE6-48A2-AC6C-0C1DF7496A03}): CDCMAgentJob::QueueEvent - Queuing Event and incrementing semaphore Transition DCMAgent 17-3-2016 12:04:28 12936 (0x3288)
DCMAgentJob({EB68B6E0-AEE6-48A2-AC6C-0C1DF7496A03}): CDCMAgentJob::HandleEvent(Event=Transition, CurrentState=Success) DCMAgent 17-3-2016 12:04:28 17304 (0x4398)
Triger AppV Maintaining Task DCMAgent 17-3-2016 12:04:28 17304 (0x4398)
CDCMAgentJobMgr::DeleteJob - Request to delete DCM Agent job {EB68B6E0-AEE6-48A2-AC6C-0C1DF7496A03} DCMAgent 17-3-2016 12:04:28 17304 (0x4398)
CIAgentJob({9CF071D1-04D0-4DBB-92A2-59A6427E6FDE}): ReportMethodInvocation :: Obtained lantern reports CIAgent 17-3-2016 12:04:28 14492 (0x389C)
CIAgentJob({9CF071D1-04D0-4DBB-92A2-59A6427E6FDE}): ReportMethodInvocation failed (0x80040e14). CIAgent 17-3-2016 12:04:28 14492 (0x389C)
CCIStore::EnumConfigPointAccessorsForCIs failed with error 0x80040e14 CIStore 17-3-2016 12:04:28 14492 (0x389C)
CDCMReporting::FinalConstruct. DCMReporting 17-3-2016 12:04:28 14492 (0x389C)
CDCMReporting::BuildReport DCMReporting 17-3-2016 12:04:28 14492 (0x389C)
CDCMReporting::CreateCIReports DCMReporting 17-3-2016 12:04:28 14492 (0x389C)
CDCMReporting::DetermineTargettingInformation DCMReporting 17-3-2016 12:04:28 14492 (0x389C)
CDCMReporting::LoadLanternDocuments DCMReporting 17-3-2016 12:04:28 14492 (0x389C)
Discovered PolicyPlatform_RuleStatusDetailReport DCMReporting 17-3-2016 12:04:28 14492 (0x389C)
Discovered PolicyPlatform_InventoryReport DCMReporting 17-3-2016 12:04:28 14492 (0x389C)
Discovered PolicyPlatform_AuthoredConfigPointReport DCMReporting 17-3-2016 12:04:28 14492 (0x389C)
Discovered PolicyPlatform_InstanceConfigPointReport DCMReporting 17-3-2016 12:04:28 14492 (0x389C)
Discovered PolicyPlatform_RuleStatusReport DCMReporting 17-3-2016 12:04:28 14492 (0x389C)
Discovered PolicyPlatform_RuleToStateReport DCMReporting 17-3-2016 12:04:28 14492 (0x389C)
Discovered PolicyPlatform_StateReport DCMReporting 17-3-2016 12:04:28 14492 (0x389C)
Discovered PolicyPlatform_SynchronizationDetailReport DCMReporting 17-3-2016 12:04:28 14492 (0x389C)
Discovered PolicyPlatform_SynchronizationErrorReport DCMReporting 17-3-2016 12:04:28 14492 (0x389C)
Discovered PolicyPlatform_JobSummaryReport DCMReporting 17-3-2016 12:04:28 14492 (0x389C)
CDCMReporting::LoadDigestsForPoliciesReportedByLantern DCMReporting 17-3-2016 12:04:28 14492 (0x389C)
CDCMReporting::ProcessCIReports DCMReporting 17-3-2016 12:04:28 14492 (0x389C)
CDCMReporting::AddImplicitRules DCMReporting 17-3-2016 12:04:28 14492 (0x389C)
CDCMReporting::LoadConfigurationPointAccessorsMap DCMReporting 17-3-2016 12:04:28 14492 (0x389C)
CDCMReporting::LoadConfigurationPointAccessorsMap failed (0x80040e14). DCMReporting 17-3-2016 12:04:28 14492 (0x389C)
CDCMReporting::BuildReport failed (0x80040e14). DCMReporting 17-3-2016 12:04:28 14492 (0x389C)
CDCMReporting::FinalRelease DCMReporting 17-3-2016 12:04:28 14492 (0x389C)

I have tried the following:

Nothing seemed to have helped and I'm totally in the dark about this at the moment. At this point even thinking about just reinstalling the OS.

All replies (12)

Thursday, March 31, 2016 1:18 PM ✅Answered | 1 vote

Given that no one else is seeing this issue, there is no way this isn't something unique to your environment IMO. As noted, opening a support case is the best path as there's simply no way for a forum thread to provide guidance for in-depth troubleshooting -- not to mention that the use of SQLCE by the agent in completely undocumented (publicly at least).

Jason | http://blog.configmgrftw.com | @jasonsandys

Monday, May 2, 2016 9:20 AM ✅Answered

The issue has been resolved, although I was not able to find the exact cause which generated the 0x80040e14 error.

This is what I have done to solve the problem and make the client run a Application Deployment Evaluation Cycle*: *

  • Backup of content like Queries, Device Collections, Software, Scheduled Tasks etc. in Configuration Mananger 2012 R2.
  • Shutdown Primary Site Server and the Database server.
  • Removed both Database and Primary Site server from the Active Directory.
  • Removed System Management container from the Active Directory.
  • Reinstalled Windows Server 2012 R2 on the Primary Site server and Database server.
  • Joined domain with both Database and Primary Site server.
  • Added Primary Site server to local administrators group on the Database server.
  • Re-installed prerequisites and SQL Server 2012.
  • Re-installed prerequisites and Configuration Manager 2012 SP1.
  • Imported Configuration Manager 2012 R2 backup content.
  • Manually reinstalled Configuration Manager 2012 client form the Primary Site server.
  • Rerun a Application Deployment Evaluation Cycle.

In fact this was a total re-installation of Configuration Manager 2012 in the entire network... Things I also tried but were unsuccessful:

  • Site Recovery from installation media.
  • Re-installing the SQL Server 2012 instance.
  • Re-installing the SQL Server 2012 instance under a different name.
  • Re-installing the Configuration Manager 2012 R2 Primary Site server, with cleaning the Active Directory.
  • Removing Configuration Manager 2012 R2, with cleaning the Active Directory and installing Configuration Manager 2012 SP1.
  • Lots and lots of permission checks.

In my opinion, the thing that really did the trick was a complete re-installation of the Database server including the operating system.

Thursday, March 17, 2016 3:41 PM

The error code you've noted is normally associated with issues accessing a SQL DB. ConfigMgr 2012 clients do use a local SQL CE database for storing various things (because its faster than WMI). The main client DB is in a file called ccmstore.sdf (on the client of course).

The error indicates an issue with the OLE DB provider used to connect to the DB. I don't know exactly how to troubleshoot it, but I would start by checking the event viewer and the ODBC connections. A web search on troubleshooting OLE DB may provide some additional help also.

Jason | http://blog.configmgrftw.com | @jasonsandys

Thursday, March 17, 2016 4:00 PM

Thanks for your reply Jason. Indeed, I did found SQL database related problems but I didn't expected the client was using a local SQL CE database.

Will look into it a.s.a.p. and report my findings here.

Thursday, March 17, 2016 6:45 PM

Another thing you could try is uninstalling/reinstalling the Microsoft Policy Platform (MPP). You can grab the MSI from the ConfigMgr client folder (choose x64 or i386 depending on the architecture) Copy it to a local folder on the system like C:\Temp then from an elevated command prompt run

cd C:\Temp

msiexec.exe /x microsoftpolicyplatformsetup.msi /qn

Verify uninstall by making sure that the C:\Program Files\Microsoft Policy Platform folder is no longer present

Reinstall with

C:\Temp\microsoftpolicyplatformsetup.msi /qn REBOOT=Suppress ALLUSERS=1

(This matches the parameters used by ccmsetup)

This should prevent having to uninstall and reinstall the ConfigMgr client. However, the "cleaner" way may be to uninstall the ConfigMgr client first, then uninstall the MPP, then install the ConfigMgr client which will automatically reinstall MPP.

I've seen this fix issues with CI related errors, but I don't know if it will fix this specific issue.

Thursday, March 24, 2016 11:14 AM

Local Database Troubleshooting

It seems quite hard to get any information from the configuration manager client while its storing/retrieving data from the SQL CE database. I can see the file ccmstore.sdf is used by the process CcmExec.exe and could probably even check the files contents using something like SQL Management Studio but I doubt this would give me any valuable information. It would be more of help when I could actually see the queries being executed at the moment this error pops up.

Removing CCM and MMP

So I have removed the configuration manager client again by using the command:

ccmsetup.exe /uninstall

After that I used the Get-WmiObject cmdlet to see the list of installed products, searching for configuration manager client related products. Uninstalled the following:

  • Uninstalled Microsoft SQL Server Compact 4.0 x64 EN
  • ConfigMgr Client Setup Bootstrap
  • Microsoft Policy Platform

The uninstallation was done via PowerShell/WMI as well. All three uninstallations returned exit code 0. Verified the directory Microsoft Policy Platform no longer exists. Rebooted the server. And reinstalled configuration manager client.

Conclusion

After the actions described above the error still occurs. And like I mentioned earlier in this reply I think monitoring the queries executed to the SQL CE database would be very helpful. The big question would now be, is that even possible?

Wednesday, March 30, 2016 8:53 AM

It seems all clients on this site now have this issue.

Wednesday, March 30, 2016 12:56 PM

That sounds like something environmental now like anti-virus, anti-malware, an actual virus or malware, or something else common in that environment.

You'll probably want to open a ticket with Microsoft to help figure out what's happening as this is beyond what we in a forum can help with.

Jason | http://blog.configmgrftw.com | @jasonsandys

Thursday, March 31, 2016 9:32 AM

I doubt it has something to do with our environment. One important thing to note here is that we rolled out an client updated a while ago. The clients were updating in the default time period of 7 days.

Monday, May 2, 2016 9:44 AM

Have you also tried running a site reset?

Torsten Meringer | http://www.mssccmfaq.de

Monday, May 2, 2016 12:54 PM

Hi Torsten,

Before starting to re-install software, I did try Site Recovery from the installation media. This did not resolve the problem. I have edited my previous answer.

Monday, May 2, 2016 1:33 PM

Site recovery != site reset.

Torsten Meringer | http://www.mssccmfaq.de