VSS Hardware Provider

NTDEV
1

All,

I am trying to understand how the VSS hardware Provider API works using the
VSS Sample Hardware Provider that comes with the Win 7 SDK. I do the
following:

  1. Installed virtual storage driver using vstorcontrol
  2. Install the sample provider using install-sampleprovider
  3. Create a virtual disk using vstorcontrol
  4. Create a volume on the disk using Disk Manager.

I test the provider using the following:
vshadow -p -nw E:

When running vshadow I am also running vsstrace.

Everything seemed to work ok and the snap shot is created (verified by
running vshadow -v) but I never see any of the hardware provider entry
points being invoked.

I am running on Win7 and using the following command line for tracing:
vsstrace -f 0 +HWDIAG.

Does anyone have any ideas?

Also, is this the correct forum for a question like this?

TIA

2

Actually, after looking at the registeration process I see that there are
errors. The errors are below:
Any help anyone?
TIA

Creating a new COM+ application:

  • Creating the catalog object
  • Get the Applications collection
  • Populate…
  • Add new application object
  • Set app name = VssSampleProvider
  • Set app description = VSS HW Sample Provider
  • Set app access check = true
  • Set encrypted COM communication = true
  • Set secure references = true
  • Set impersonation = false
  • Save changes…
  • Create Windows service running as Local System
  • Add the DLL component
    ERROR:
  • Error code: -2146368511 [0x80110401]
  • Exit code: 113
  • Description:
  • Source:
  • Help file:
  • Help context: 0
  • COM+ Errors detected: (2)
    * (COM+ ERROR 0) on C:\SDK\Windows\v7.0\Bin\vsstools\VssSampleProvider.dll
    ErrorCode: -2146368486 [0x8011041A]
    MajorRef: C:\SDK\Windows\v7.0\Bin\vsstools\VssSampleProvider.dll
    MinorRef:
    * (COM+ ERROR 1) on SampleProvider
    ErrorCode: -2146368486 [0x8011041A]
    MajorRef: {423BBC78-9B20-4BBE-A967-B63EC43BC7F3}
    MinorRef:

    “Jiimmy James” wrote in message news:xxxxx@ntdev…
    > All,
    >
    > I am trying to understand how the VSS hardware Provider API works using
    > the VSS Sample Hardware Provider that comes with the Win 7 SDK. I do the
    > following:
    > 1. Installed virtual storage driver using vstorcontrol
    > 2. Install the sample provider using install-sampleprovider
    > 3. Create a virtual disk using vstorcontrol
    > 4. Create a volume on the disk using Disk Manager.
    >
    > I test the provider using the following:
    > vshadow -p -nw E:
    >
    > When running vshadow I am also running vsstrace.
    >
    > Everything seemed to work ok and the snap shot is created (verified by
    > running vshadow -v) but I never see any of the hardware provider entry
    > points being invoked.
    >
    > I am running on Win7 and using the following command line for tracing:
    > vsstrace -f 0 +HWDIAG.
    >
    > Does anyone have any ideas?
    >
    > Also, is this the correct forum for a question like this?
    >
    > TIA
    >
    >
    >
    >
    >
    >
    >
3

It looks like the registeration of the VSS provider encountered failure.

“0x8011041A” error code is COMADMIN_E_DLLREGISTERSERVER, which means “DllRegisterServer failed on component install.”

Just a thought. Is there by any chance you were using a 32-bit VSS provider in WOW64 environment, which is not supported. More details in http://msdn.microsoft.com/en-us/library/bb968832(VS.85).aspx

Good luck!

Tai-Hing

From: xxxxx@gmail.com
Subject: Re:[ntdev] VSS Hardware Provider
Date: Tue, 6 Jul 2010 22:14:13 -0600
To: xxxxx@lists.osr.com

Actually, after looking at the registeration process I see that there are
errors. The errors are below:
Any help anyone?
TIA

Creating a new COM+ application:

  • Creating the catalog object
  • Get the Applications collection
  • Populate…
  • Add new application object
  • Set app name = VssSampleProvider
  • Set app description = VSS HW Sample Provider
  • Set app access check = true
  • Set encrypted COM communication = true
  • Set secure references = true
  • Set impersonation = false
  • Save changes…
  • Create Windows service running as Local System
  • Add the DLL component
    ERROR:
  • Error code: -2146368511 [0x80110401]
  • Exit code: 113
  • Description:
  • Source:
  • Help file:
  • Help context: 0
  • COM+ Errors detected: (2)
    * (COM+ ERROR 0) on C:\SDK\Windows\v7.0\Bin\vsstools\VssSampleProvider.dll
    ErrorCode: -2146368486 [0x8011041A]
    MajorRef: C:\SDK\Windows\v7.0\Bin\vsstools\VssSampleProvider.dll
    MinorRef:
    > * (COM+ ERROR 1) on SampleProvider
    > ErrorCode: -2146368486 [0x8011041A]
    > MajorRef: {423BBC78-9B20-4BBE-A967-B63EC43BC7F3}
    > MinorRef:
    >
    >
    >
    > “Jiimmy James” wrote in message news:xxxxx@ntdev…
    > > All,
    > >
    > > I am trying to understand how the VSS hardware Provider API works using
    > > the VSS Sample Hardware Provider that comes with the Win 7 SDK. I do the
    > > following:
    > > 1. Installed virtual storage driver using vstorcontrol
    > > 2. Install the sample provider using install-sampleprovider
    > > 3. Create a virtual disk using vstorcontrol
    > > 4. Create a volume on the disk using Disk Manager.
    > >
    > > I test the provider using the following:
    > > vshadow -p -nw E:
    > >
    > > When running vshadow I am also running vsstrace.
    > >
    > > Everything seemed to work ok and the snap shot is created (verified by
    > > running vshadow -v) but I never see any of the hardware provider entry
    > > points being invoked.
    > >
    > > I am running on Win7 and using the following command line for tracing:
    > > vsstrace -f 0 +HWDIAG.
    > >
    > > Does anyone have any ideas?
    > >
    > > Also, is this the correct forum for a question like this?
    > >
    > > TIA
    > >
    > >
    > >
    > >
    > >
    > >
    > >
    >
    >
    >
    > —
    > NTDEV is sponsored by OSR
    >
    > For our schedule of WDF, WDM, debugging and other seminars visit:
    > http://www.osr.com/seminars
    >
    > To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

    _________________________________________________________________
    Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox.
    http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1
4

Thanks for the reply.

The provider is definitely compiled for 32-bit and is running on a 32-bit
Win7 platform.

“Tai-Hing Tse” wrote in message news:xxxxx@ntdev…

It looks like the registeration of the VSS provider encountered failure.

“0x8011041A” error code is COMADMIN_E_DLLREGISTERSERVER, which means
“DllRegisterServer failed on component install.”

Just a thought. Is there by any chance you were using a 32-bit VSS provider
in WOW64 environment, which is not supported. More details in
http://msdn.microsoft.com/en-us/library/bb968832(VS.85).aspx

Good luck!

Tai-Hing

> From: xxxxx@gmail.com
> Subject: Re:[ntdev] VSS Hardware Provider
> Date: Tue, 6 Jul 2010 22:14:13 -0600
> To: xxxxx@lists.osr.com
>
> Actually, after looking at the registeration process I see that there are
> errors. The errors are below:
> Any help anyone?
> TIA
>
> Creating a new COM+ application:
> - Creating the catalog object
> - Get the Applications collection
> - Populate…
> - Add new application object
> - Set app name = VssSampleProvider
> - Set app description = VSS HW Sample Provider
> - Set app access check = true
> - Set encrypted COM communication = true
> - Set secure references = true
> - Set impersonation = false
> - Save changes…
> - Create Windows service running as Local System
> - Add the DLL component
> ERROR:
> - Error code: -2146368511 [0x80110401]
> - Exit code: 113
> - Description:
> - Source:
> - Help file:
> - Help context: 0
> - COM+ Errors detected: (2)
> * (COM+ ERROR 0) on C:\SDK\Windows\v7.0\Bin\vsstools\VssSampleProvider.dll
> ErrorCode: -2146368486 [0x8011041A]
> MajorRef: C:\SDK\Windows\v7.0\Bin\vsstools\VssSampleProvider.dll
> MinorRef:
> * (COM+ ERROR 1) on SampleProvider
> ErrorCode: -2146368486 [0x8011041A]
> MajorRef: {423BBC78-9B20-4BBE-A967-B63EC43BC7F3}
> MinorRef:
>
>
>
> “Jiimmy James” wrote in message news:xxxxx@ntdev…
> > All,
> >
> > I am trying to understand how the VSS hardware Provider API works using
> > the VSS Sample Hardware Provider that comes with the Win 7 SDK. I do the
> > following:
> > 1. Installed virtual storage driver using vstorcontrol
> > 2. Install the sample provider using install-sampleprovider
> > 3. Create a virtual disk using vstorcontrol
> > 4. Create a volume on the disk using Disk Manager.
> >
> > I test the provider using the following:
> > vshadow -p -nw E:
> >
> > When running vshadow I am also running vsstrace.
> >
> > Everything seemed to work ok and the snap shot is created (verified by
> > running vshadow -v) but I never see any of the hardware provider entry
> > points being invoked.
> >
> > I am running on Win7 and using the following command line for tracing:
> > vsstrace -f 0 +HWDIAG.
> >
> > Does anyone have any ideas?
> >
> > Also, is this the correct forum for a question like this?
> >
> > TIA
> >
> >
> >
> >
> >
> >
> >
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer

_________________________________________________________________
Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_1