To resolve this issue, do the following in the specified order:
Ensure the registry data and permissions
Confirm the providers are registered
To perform these procedures, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
Ensure that the registry data is correct
Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.
To ensure that the registry data is correct:
Open Registry Editor. (Click Start, type regedit in the Start Search box, and then press ENTER.)
Verify that the registry key for the provider that failed exists at the following location:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers. Note: The failed provider is specified in the event log message. To find the message, search Event Viewer for WDSServer event 258.
If the registry key exists at the specified location, verify that the IsCritical subkey for the provider that failed exists and is set either to 1 (for a critical provider) or to 0 (for a noncritical provider).
If either the provider key (ProviderDll) or the file is missing, do one of the following:
If the provider is one of the default providers (WDSPXE, BINLSVC, WDSIMGSRV, WDSMC, and WDSTFTP), you will need to reinstall Windows Deployment Services by using Server Manager (see the following section).
If the provider is a custom or non-Microsoft provider, reinstall it. If that does not fix the problem, contact the vendor for troubleshooting information.
Reinstall Windows Deployment Services
To reinstall Windows Deployment Services:
Open Server Ma.(Click Start, point to Administrative Tools, and then click Server Manager.)
Under Roles Summary, click Remove Roles.
Select Windows Deployment Services, and then follow the instructions in the wizard.
After the role removal is completed, click Add Roles in Server Manager to reinstall Windows Deployment Services.
For more information about installing Windows Deployment Services, see http://go.microsoft.com/fwlink/?LinkId=89222.
Target | Microsoft.Windows.Server.6.2.WDSRole | ||
Category | EventCollection | ||
Enabled | True | ||
Event_ID | 258 | ||
Event Source | WDSPXE | ||
Alert Generate | True | ||
Alert Severity | Error | ||
Alert Priority | Normal | ||
Remotable | True | ||
Alert Message |
| ||
Event Log | Application |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Microsoft.Windows.EventProvider | Default |
Alert | WriteAction | System.Health.GenerateAlert | Default |
<Rule ID="Microsoft.Windows.Server.6.2.WDSRole.EventCollection.258" Enabled="onEssentialMonitoring" Target="Microsoft.Windows.Server.6.2.WDSRole" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>EventCollection</Category>
<DataSources>
<DataSource ID="DS" TypeID="Windows!Microsoft.Windows.EventProvider">
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>Application</LogName>
<Expression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">258</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="String">WDSPXE</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>2</Severity>
<AlertName/>
<AlertDescription/>
<AlertOwner/>
<AlertMessageId>$MPElement[Name="Microsoft.Windows.Server.6.2.WDSRole.EventCollection.258.AlertMessage"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>$Data/EventDescription$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue>$Data/LoggingComputer$</SuppressionValue>
</Suppression>
<Custom1/>
<Custom2/>
<Custom3/>
<Custom4/>
<Custom5/>
<Custom6/>
<Custom7/>
<Custom8/>
<Custom9/>
<Custom10/>
</WriteAction>
</WriteActions>
</Rule>