Computer Monitoring Error - DeviceProviderReporting!DomainJoinStatusInfo
-
Tuesday, January 15, 2013 11:09 PM
I'm having the following error come up on one of my desktops running Windows 7 multiple times a day. The "Learn More About" link takes me to an empty page (http://technet.microsoft.com/library/f1e6b377-4a24-4d28-9b25-05910914826b) and I'm hoping someone on here may know how to solve.
Exact text is: "Computer monitoring error. Can only partially assess the health of this cmptuer. The failing components are: DeviceProviderReporting!DomainJoinStatusInfo"
The warning comes and goes throughout the day.
SCREENCAP:
KevenD.
- Moved by Cicely FengMicrosoft Contingent Staff Thursday, January 17, 2013 7:04 AM Windows 7 related issue
All Replies
-
Wednesday, January 16, 2013 1:21 PMIs it Win7 Pro? Domain Joined?
Robert Pearman SBS MVP | www.titlerequired.com | www.itauthority.co.uk
-
Wednesday, January 16, 2013 10:43 PM
-
Friday, January 18, 2013 9:25 AMModerator
Hi,
Normally if you get "Computer Monitoring Error", it indicates the infrastructure error. There are some causes, like.
1. Alert service is temporary down, the server can't get alerts.
2. The feature definition or the alert parsing component is missing, server don't know what the alert is.
3. Timeout issue, waiting for an alert evaluation is taking too much time.
Except for 2, the issues will fixed by server itself and the alert will disappear.
There’s a similar thread you can refer:
Furthermore, I suggest to contact Server Forum for further help:
http://social.technet.microsoft.com/Forums/en-US/winservergen/threads
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Leo Huang
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
Leo Huang
TechNet Community Support
-
Monday, January 21, 2013 7:08 PM
I was posted in the other forum and then I got notification that someone moved my posting as per below. The computer monitoring error only exists on the one machine regardless if connected to the wireless or wired networks. Other machines using either connection have no issues at all - I do not see how this is an infrastructure error. It comes and goes all throughout the day and has been doing so for WEEKS.
Wed 1/16/2013 11:04 PM
A forums thread you have subscribed to has been moved by Cicely Feng!
Thread Title: Computer Monitoring Error - DeviceProviderReporting!DomainJoinStatusInfo
Started by: kevend
The Microsoft Developer NetworkKevenD.
-
Wednesday, January 23, 2013 9:04 PM
I'm getting the exact same error, however my client machine is Windows 8 Pro x64. Error comes and goes throughout the day - very annoying.
I've dug into the SharedServiceHost-ClientAlertServiceConfig log file which was referenced in the similar errors with SBS2011. I pasted an exception block at the very bottom which I think *might* be related. Some history is that I had 2012 essentials installed and had connected this machine and then upgraded the hardware of the server, requiring a reinstall. Thus, I removed the client machine from the old domain and added to the new domain (albeit the domains had the same name).
Elsewhere in the log I get these messages which I'm guessing are related to the removal from the old domain and adding to the new domain:
----
[556] 130123.134108.2788: AlertFramework: Subcomponent: ClearCurrentCommand > Clearing alert that does not exist: Key=S-1-5-21-2185799238-237342817-1757492711-1123$MicrosoftBase$InstallFailed
[556] 130123.134108.2788: AlertFramework: Subcomponent: AlertAgentProviderService > ClearAlert: error=Clearing alert that does not exist: Key=S-1-5-21-2185799238-237342817-1757492711-1123$MicrosoftBase$InstallFailed
[9364] 130123.134108.2788: AlertFramework: Subcomponent: ClearCurrentCommand > Clearing alert that does not exist: Key=S-1-5-21-2185799238-237342817-1757492711-1123$MicrosoftBase$UpgradeFailed
[9364] 130123.134108.2788: AlertFramework: Subcomponent: AlertAgentProviderService > ClearAlert: error=Clearing alert that does not exist: Key=S-1-5-21-2185799238-237342817-1757492711-1123$MicrosoftBase$UpgradeFailed
[9468] 130123.134108.2788: AlertFramework: Subcomponent: ClearCurrentCommand > Clearing alert that does not exist: Key=S-1-5-21-2185799238-237342817-1757492711-1123$MicrosoftBase$UninstallFailed
[9468] 130123.134108.2798: AlertFramework: Subcomponent: AlertAgentProviderService > ClearAlert: error=Clearing alert that does not exist: Key=S-1-5-21-2185799238-237342817-1757492711-1123$MicrosoftBase$UninstallFailed
[9240] 130123.134108.2798: AlertFramework: Subcomponent: ClearCurrentCommand > Clearing alert that does not exist: Key=S-1-5-21-2185799238-237342817-1757492711-1123$MicrosoftBase$AddinRebootInstall
[9240] 130123.134108.2798: AlertFramework: Subcomponent: AlertAgentProviderService > ClearAlert: error=Clearing alert that does not exist: Key=S-1-5-21-2185799238-237342817-1757492711-1123$MicrosoftBase$AddinRebootInstall
[11148] 130123.134108.2798: AlertFramework: Subcomponent: ClearCurrentCommand > Clearing alert that does not exist: Key=S-1-5-21-2185799238-237342817-1757492711-1123$MicrosoftBase$AddinRebootUninstall
[11148] 130123.134108.2798: AlertFramework: Subcomponent: AlertAgentProviderService > ClearAlert: error=Clearing alert that does not exist: Key=S-1-5-21-2185799238-237342817-1757492711-1123$MicrosoftBase$AddinRebootUninstall----
anyone have any idea how to fix this? I'm really close to reinstalling this machine b/c the alert is so annoying.
Thanks,
-John
--------
EXCEPTION BLOCK
---------5488] 130123.134917.9425: NetworkHealthEngine: Exception happened in Microsoft.WindowsServerSolutions.NetworkHealth.Engine.BinaryActionDefinition: System.Security.Authentication.AuthenticationException: The user name or password is incorrect.
---> System.Runtime.InteropServices.COMException: The user name or password is incorrect.at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.get_AdsObject()
at System.DirectoryServices.PropertyValueCollection.PopulateList()
at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName)
at System.DirectoryServices.PropertyCollection.get_Item(String propertyName)
at System.DirectoryServices.ActiveDirectory.PropertyManager.GetPropertyValue(DirectoryContext context, DirectoryEntry directoryEntry, String propertyName)
--- End of inner exception stack trace ---
at System.DirectoryServices.ActiveDirectory.PropertyManager.GetPropertyValue(DirectoryContext context, DirectoryEntry directoryEntry, String propertyName)
at System.DirectoryServices.ActiveDirectory.Domain.GetDomain(DirectoryContext context)
at System.DirectoryServices.ActiveDirectory.Domain.GetComputerDomain()
at Microsoft.WindowsServerSolutions.Reporting.DomainOSHelpers.GetCurrentComputerDomainName()
at Microsoft.WindowsServerSolutions.Reporting.DeviceProviderDomainJoinReporter.Run(IActionContext context)
at Microsoft.WindowsServerSolutions.NetworkHealth.Engine.BinaryActionProcessor.RunBinary[T](IActionDefinition definition, IActionContext context)
at Microsoft.WindowsServerSolutions.NetworkHealth.Engine.BinaryActionProcessor.RunBinary[T](IActionDefinition definition, IActionContext context)
at Microsoft.WindowsServerSolutions.NetworkHealth.Engine.ActionProcessingUnit.DoRun[T](IActionDefinition definition, IActionContext context)
[5488] 130123.134917.9425: AlertFramework: Subcomponent: HealthEvaluator > Condition Evaluation for HealthDefinitionName=DomainJoinStatusInfo FeatureName=DeviceProviderReporting threw an exception: Microsoft.WindowsServerSolutions.NetworkHealth.Engine.ActionRuntimeException: The user name or password is incorrect.
---> System.Security.Authentication.AuthenticationException: The user name or password is incorrect.
---> System.Runtime.InteropServices.COMException: The user name or password is incorrect.at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)
at System.DirectoryServices.DirectoryEntry.Bind()
at System.DirectoryServices.DirectoryEntry.get_AdsObject()
at System.DirectoryServices.PropertyValueCollection.PopulateList()
at System.DirectoryServices.PropertyValueCollection..ctor(DirectoryEntry entry, String propertyName)
at System.DirectoryServices.PropertyCollection.get_Item(String propertyName)
at System.DirectoryServices.ActiveDirectory.PropertyManager.GetPropertyValue(DirectoryContext context, DirectoryEntry directoryEntry, String propertyName)
--- End of inner exception stack trace ---
at System.DirectoryServices.ActiveDirectory.PropertyManager.GetPropertyValue(DirectoryContext context, DirectoryEntry directoryEntry, String propertyName)
at System.DirectoryServices.ActiveDirectory.Domain.GetDomain(DirectoryContext context)
at System.DirectoryServices.ActiveDirectory.Domain.GetComputerDomain()
at Microsoft.WindowsServerSolutions.Reporting.DomainOSHelpers.GetCurrentComputerDomainName()
at Microsoft.WindowsServerSolutions.Reporting.DeviceProviderDomainJoinReporter.Run(IActionContext context)
at Microsoft.WindowsServerSolutions.NetworkHealth.Engine.BinaryActionProcessor.RunBinary[T](IActionDefinition definition, IActionContext context)
at Microsoft.WindowsServerSolutions.NetworkHealth.Engine.BinaryActionProcessor.RunBinary[T](IActionDefinition definition, IActionContext context)
at Microsoft.WindowsServerSolutions.NetworkHealth.Engine.ActionProcessingUnit.DoRun[T](IActionDefinition definition, IActionContext context)
--- End of inner exception stack trace ---Server stack trace:
at Microsoft.WindowsServerSolutions.NetworkHealth.Engine.ActionProcessingUnit.DoRun[T](IActionDefinition definition, IActionContext context)
at Microsoft.WindowsServerSolutions.NetworkHealth.Engine.ActionProcessingUnit.Run[T](IActionDefinition definition, IActionContext context)
at Microsoft.WindowsServerSolutions.NetworkHealth.Engine.HealthDefinition.RunCondition()
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)
at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed, MessageData& msgData)
at System.Func`1.EndInvoke(IAsyncResult result)
at Microsoft.WindowsServerSolutions.NetworkHealth.AlertFramework.Internal.HealthEvaluator.RunConditionCallback(IAsyncResult asyncResult) -
Thursday, January 24, 2013 9:19 AMModerator
Hi,
Try to logon with Safe Mode with networking or create another administrator account and login to see if the same occurs.
I suspect the issue should relate with server configuration. Some similar threads you can refer:
Leo Huang
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
Leo Huang
TechNet Community Support -
Thursday, January 24, 2013 4:23 PM
Both those articles are about SBS 2011 Rollup 2. This is 2012 Essentials - hopefully the same issue hasn't been reintroduced.
I don't believe it's a server issue as it only happens on 1 of my 4 clients.
I've tried signing in as a different administrator account and the issue still occurs. Tonight I'll try starting in Safe Mode and see what happens.
-
Tuesday, January 29, 2013 2:07 AMModerator
Hi,
How’s everything going? Please feel free to give me any update.
Thank you for your cooperation.
Leo Huang
If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.
Leo Huang
TechNet Community Support -
Tuesday, January 29, 2013 3:21 AM
Sorry - had some sick kids over the weekend so forgot to post the results. In Safe Mode the Alert service can't run - going up the dependency stack the Net.TCP Port Sharing Service won't run.
Any other ideas?
-
Tuesday, January 29, 2013 4:24 AMDitto on my side.. that one machine only still keeps kicking error messages throughout the day.
KevenD.
-
Wednesday, January 30, 2013 2:02 PM
The error is reporting for DomainJoinStatusInfo, can attempt to disjoin and then rejoin the machine to see what will happen.
If the error remains, post a full screenshot.
Regards,
Diana
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
-
Monday, February 18, 2013 9:30 PM
I've just run into the same issue. I've disconnected and reconnected a few times but still get the same errors.
Warning Alert: !Warning is raised at DAD-DESKTOP. <Title> Computer monitoring error. <Description> Can only partially assess the health of this computer. The failing components are: DeviceProviderReporting!DomainJoinStatusInfo. <AdditionalInfo> Logon failure: unknown user name or bad password.
.And
Active Directory Certificate Services denied request 13 because The permissions on the certificate template do not allow the current user to enroll for this type of certificate. 0x80094012 (-2146877422). The request was for CN=DAD-DESKTOP. Additional information: Denied by Policy Module
This workstation was previously attached to WHS v1 and WHS 2011 and I ran into certificate errors there as well. I think there is a certificate on my machine that is leftover from WHS 2011 that is not getting replaced by Win Essential 2012 that is causing this problem.
My username and password allow me to log onto my workstation and the server, so the unknown username or bad password don't make sense. The certificate error is the most likely explanation, but I don't remember what I did last time to fix this sort of issue.
Gary J
-
Monday, February 18, 2013 9:34 PMSorry - I forgot to update my results. I tried removing the machine from the domain and reading it - and ran into some issue. Can't remember what but at that point I gave up and reimaged my machine, which I wanted to do anyways to have it installed in UEFI mode. Now it works perfectly and I don't get that annoying warning.
.png)
