The user might not have access rights to service data on the target server, or service data files might not contain valid data. I haven't found anything that might have caused it. Thanks. Reply Subscribe RELATED TOPICS: Online - Cannot get event data All servers showing "Online - Cannot Get The Enable-ServerManagerStandardUserRemoting cmdlet does not provide standard users access to BPA result data. Server Manager cannot get event data from the target server. Source
Client is in a domain, and the target server is in a workgroup (using the IP address of the server): User has specified explicit credentials for the target server, and added You cannot manage this computer by using Server Manager. Join the community of 500,000 technology professionals and ask your questions. I think it's safe to say that recreating the file is the best approach towards fixing the problem. https://community.spiceworks.com/topic/290802-adam-events-xml-could-not-be-enumerated
unbob says: December 14, 2012 at 2:25 PM Hi, There's an official workaround available: http://support.microsoft.com/kb/2721972 Reply Dan Begallie says: December 14, 2012 at 11:07 PM I'm going to check it out Note that computers in the TrustedHosts list might not be authenticated. Use winrm.cmd to configure TrustedHosts.
Since searching online didn't provide any useful hint except your post… Thank you again! ;-) Reply Dan Begallie says: March 10, 2013 at 10:54 PM Glad you sorted it out. Error Error
Note that computers in the TrustedHosts list might not be authenticated. -For more information about WinRM configuration, run the following command: winrm help config. File Server.events.xml Could Not Be Enumerated Verify that the computer exists on the network and that the name provided is spelled correctly. Error Error
Client computer is in a domain and the target server is in a workgroup (using the NetBIOS name of the server): User has specified explicit credentials for the target server, and Online - Cannot Get Event Data (activated) However, a subnet timeout error occurs if the user has not changed the default subnet restrictions for computers in workgroups. The target server was added to Server Manager by using its IP address. The operation failed because of an HTTP error.
Join Now For immediate help use Live now! Read the Possible Causes and Suggested Resolutions column in the matching row to find resolution steps that might help, or causes that are easy to eliminate (such as typographical errors in Events From 'application' Could Not Be Enumerated Magazine; Forums; Blogs ... Fileserver.events.xml Could Not Be Enumerated For information about how to add remote servers to a workgroup client that is running Server Manager, see Add Servers to Server Manager.
Both the client and target server are in workgroups (using the IP address of the server): User has added the server to the trusted host list of the client, and removed Seems to be a more permanent fix. h Error Online - Server Manager WMI providers not loading on the target server Server Manager WMI provider cannot load error Error
asked 3 years ago viewed 2040 times active 1 month ago Related -1Server 2012 Roaming Profile from server 20084Windows Server 2012 IPAM feature - “Unblock IPAM Access” error/recomended action2Windows Server Manager However, a subnet timeout error occurs if the user has not changed the default subnet restrictions for computers in workgroups. Is it possible to have 3 real numbers that have both their sum and product equal to 1? Troubleshoot manageability status errors The following table can help you interpret the brief manageability status messages, and resolve problems that are preventing you from managing remote servers by using Server Manager.
Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and no user name are specified. -Kerberos accepts domain user names, but not Active Directory Lightweight Directory Services Wizard See “To add remote workgroup servers to Server Manager” in Add Servers to Server Manager to resolve this issue. Dan Begallie (a.k.a.
Back to a nice happy green management console again. For me, the xml file in question was not the same as the one in the MS KB article, so I updated the post to describe what worked for me (which Note that computers in the TrustedHosts list might not be authenticated. Server Manager Target Computer Not Accessible Promoted by Acronis An exclusive Black Friday offer just for Expert Exchange audience!
An authentication error occurs because the target server has not been added to the trusted host list of the client computer, which permits Negotiate authentication. Error Error
Reply Felix Kay says: February 12, 2014 at 1:05 AM Sorry this is a tad off topic but you (or someone), has misspelled the word architect in you personal description (i.e. Error The metadata failed to be retrieved from the server, due to the following error: WS-Management cannot process the request. The user might not have access rights to the target server event log, or event log files might not contain valid data. Client computer is in a workgroup, and the target server is also in a workgroup (using the IP address of the server): An authentication error occurs because the target server has
Both the client and the target server are in workgroups (using the NetBIOS name of the server): The user’s network can resolve the name of the server, the user has added Client is in a workgroup and the target server is in a workgroup (using the IP address of the server): The user has added the server to the trusted hosts list Thanks for the tip. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig".
A user might have enabled WinRM 2.0, but not DCOM, on a target server that is running an older Windows Server operating system, and not yet installed the Windows Management Framework However, a subnet timeout error occurs if the user has not changed the default subnet restrictions for computers in workgroups. For information about how to add a domain server to Server Manager when the client is in a workgroup, see Add Servers to Server Manager. Configuring the installed role services does not resolve the error.
Follow instructions in Managing Downlevel Windows-based Servers from Server Manager in Windows Server 2012 to resolve this error. Covered by US Patent. Use winrm.cmd to configure TrustedHosts. The error is resolved after post-installation configuration is complete.
Client is in a domain and the target server is in the same domain, but the domain name provided for the target server is incorrect or misspelled. Your blog post allowed me to get past this. The biggest error that I seem to be getting is Online - Cannot get event data. However, I'm not really sure where to launch the wizard from so I can't verify that.
Spot checked the file against the same on a different server and also copied over the one from the other server. Explicit credentials must be used to manage the target server. Events from ‘Virtualization.Events.xml’ could not be enumerated. (This error is cleared after required post-installation configuration for Hyper-V is completed.) Events from ‘PrintServices.Events.xml’ could not be enumerated. (This error is cleared after