Answers

If I don't misunderstand, you noticed the following event Log on the problematic Windows Server 2008 operation system.

Log Name: System

Source: VDS Dynamic Provider

Date: Date

Time: Time

Event ID: 10

Description: The provider failed while storing notifications from the driver. The Virtual Disk Service should be restarted. hr=80042505

Please note: This event is logged every time that we shut down and then restart the operating system.

Cause:

This problem occurs if the Virtual Disk service is started. The Virtual Disk service is a "demand start" service that runs only if something has called it to be run. Therefore, the start type of the Virtual Disk service in Services.msc is "MANUAL."

This issue occurs because the Virtual Disk service stops the Virtual Disk providers when it shuts down. When this occurs, the Virtual Disk service unregisters for driver notifications. Then, the service stops the notification processing thread. Because the process occurs in this order, the notification processing thread may call back in to the driver after the provider has unregistered for notifications with the driver. In this case, an event is logged.

Resolution:

To resolve this issue if you have an application, an accessory, or a service that experiences a failed Virtual Disk start, restart the Virtual Disk service.

"When the service shuts down it stops the providers. When the dynamic provider unloads, it unregisters for driver notification, then stops the notification processing thread. Because of this order, it is possible that the notification processing thread could call back into the driver, after the provider has unregistered for notifications with the driver. In this case we log an event."

Sequence:

1.When VDS shuts down, it stops providers.

2.When provider unloads, it first unregisters driver notification and then stops the notification processing thread.

3.Because notification processing thread may still working when the driver notification has been unregistered, you may receive the event error when notification process thread needs to call back into a driver.

As a result, the notification processing thread is a thread from dynamic provider.

All replies

If I don't misunderstand, you noticed the following event Log on the problematic Windows Server 2008 operation system.

Log Name: System

Source: VDS Dynamic Provider

Date: Date

Time: Time

Event ID: 10

Description: The provider failed while storing notifications from the driver. The Virtual Disk Service should be restarted. hr=80042505

Please note: This event is logged every time that we shut down and then restart the operating system.

Cause:

This problem occurs if the Virtual Disk service is started. The Virtual Disk service is a "demand start" service that runs only if something has called it to be run. Therefore, the start type of the Virtual Disk service in Services.msc is "MANUAL."

This issue occurs because the Virtual Disk service stops the Virtual Disk providers when it shuts down. When this occurs, the Virtual Disk service unregisters for driver notifications. Then, the service stops the notification processing thread. Because the process occurs in this order, the notification processing thread may call back in to the driver after the provider has unregistered for notifications with the driver. In this case, an event is logged.

Resolution:

To resolve this issue if you have an application, an accessory, or a service that experiences a failed Virtual Disk start, restart the Virtual Disk service.

"When the service shuts down it stops the providers. When the dynamic provider unloads, it unregisters for driver notification, then stops the notification processing thread. Because of this order, it is possible that the notification processing thread could call back into the driver, after the provider has unregistered for notifications with the driver. In this case we log an event."

Sequence:

1.When VDS shuts down, it stops providers.

2.When provider unloads, it first unregisters driver notification and then stops the notification processing thread.

3.Because notification processing thread may still working when the driver notification has been unregistered, you may receive the event error when notification process thread needs to call back into a driver.

As a result, the notification processing thread is a thread from dynamic provider.

I am getting 'Unable to connect to Virtual Disk Service' and a popup that says: 'RPC service unavailable' and then the Virtual Disk Service stops

I have tried to restart it on the Core install ( net start "virtual disk" ) and through the MMC on a client mahine - not sure why it's not working , but I am also getting the error ID 10 from Virtual Disk Service.

Please help ?!?!?

MB

EDIT !! - Nevermind ! I disabled the firewall on the 'client' again, and it seems to be working !! - thanks y'all !