Event ID 1058
| Event ID | 1058 |
| Source | ClusSvc |
| Type | Error |
| Description | The Cluster Resource Monitor could not load the DLL "<dll file>" for resource type <resource type>. |
| Comments and links for event id 1058 from source ClusSvc | |
| Event ID | 1058 |
| Source | DhcpServer |
| Type | Error |
| Description | The DHCP service failed to initialize its configuration parameters. The following error occurred: <error>. |
| Comments and links for event id 1058 from source DhcpServer | |
| Event ID | 1058 |
| Source | Microsoft-Windows-GroupPolicy |
| Type | Error |
| Description | The processing of Group Policy failed. Windows attempted to read the file %9 from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: a) Name Resolution/Network Connectivity to the current domain controller. b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). c) The Distributed File System (DFS) client has been disabled. |
| Comments and links for event id 1058 from source Microsoft-Windows-GroupPolicy | |
| Event ID | 1058 |
| Source | MSExchangeDS |
| Type | Information |
| Description | Internal event: The directory replication agent (DRA) call completed successfully. |
| Comments and links for event id 1058 from source MSExchangeDS | |
| Event ID | 1058 |
| Source | Userenv |
| Type | Error |
| Description | Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=<domain name>,DC=com. The file must be present at the location <\\<domain name>\sysvol\<domain name>\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (<error description>.). Group Policy processing aborted. |
| Comments and links for event id 1058 from source Userenv | |
|
Contribute If you have details about an event with id 1058 that is not listed in our database, please, send it to us. The submitted event will be forwarded to our consultants for analysis. We recommend you to check the EventID.Net Processing Queue to see if the event was already been submitted by another contributor. | |