alphavss Issue Tracker Rss Feed

Created Issue: Cannot expose as mounted folder [19698]

mcgyver60 — Fri, 10 May 2013 20:56:59 GMT

Hello,

I think that the AlphaVSS library doesn't allow to expose as a __mounted folder__.
I can successfully expose a shadow as a network share, or as a drive letter.
However, impossible to expose, for example, as "C:\shadow".

Problem observed with VB.NET.

Shoud be possible to expose as a mounted folder:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa381608(v=vs.85).aspx

Can you confirm this issue? Or any workaround?

Thank you

Commented Issue: Sample application namespace names don't exist [19603]

musicisair — Tue, 16 Apr 2013 17:55:48 GMT

When building VssBackup.cs I get the following errors:

* The type or namespace name 'Snapshot' could not be found (are you missing a using directive or an assembly reference?)
* The type or namespace name 'IVssAsync' could not be found (are you missing a using directive or an assembly reference?)
* The type or namespace name 'Snapshot' could not be found (are you missing a using directive or an assembly reference?)
* The type or namespace name 'VssWMFileDescription' could not be found (are you missing a using directive or an assembly reference?)
* The type or namespace name 'IVssAsync' could not be found (are you missing a using directive or an assembly reference?)
* The type or namespace name 'IVssAsync' could not be found (are you missing a using directive or an assembly reference?)
* The type or namespace name 'VssWMFileDescription' could not be found (are you missing a using directive or an assembly reference?)
Comments: ** Comment from web user: musicisair **

Nevermind, I'm an idiot.

When I read the following line from the README.txt I assumed that each class was intended to be used on its own:

> This directory contains two classes that might be useful to anyone looking to use the AlphaVSS libraries to manage shadow copies.

:-)

Created Issue: Sample application namespace names don't exist [19603]

musicisair — Tue, 16 Apr 2013 17:50:31 GMT

Commented Issue: .CHM files doesn't work [19602]

musicisair — Tue, 16 Apr 2013 17:30:59 GMT

I can view the Table of Contents of the CHM but the actual contents will not appear on Windows 7 Professional.
Comments: ** Comment from web user: musicisair **

Found a fix:

1. Right click on the CHM
2. Select "Properties"
3. At the bottom of the Properties dialog there will be an "Unblock" button. Click it.
4. Close the Properties dialog.
5. Open the .CHM

Created Issue: .CHM files doesn't work [19602]

musicisair — Tue, 16 Apr 2013 17:27:45 GMT

I can view the Table of Contents of the CHM but the actual contents will not appear on Windows 7 Professional.

Closed Issue: AlphaVSS hangs on GatherWriterMetadata() [18861]

decaf — Tue, 13 Nov 2012 18:48:17 GMT

Hi,

I noticed a weird issue a couple of days ago where the GatherWriterMetadata() will hang indefinitely. I am assuming it is caused by a bad VSS service as I have noticed it happens on one of my colleagues machine but I failed to reproduce the case on mine. He runs a Win7 x86 Pro.

This is the code I am using to create the snapshot set:

IVssImplementation _VssImpl = Alphaleonis.Win32.Vss.VssUtils.LoadImplementation();
IVssBackupComponents _VssBComp = _VssImpl.CreateVssBackupComponents();
_VssBComp.InitializeForBackup(null);
_VssBComp.SetBackupState(false, true, Alphaleonis.Win32.Vss.VssBackupType.Full, false);
using (Alphaleonis.Win32.Vss.IVssAsync async = _VssBComp.GatherWriterMetadata())
{
async.Wait(); //---------> hangs
}

I am looking for a way to abort the operation or set a timeout for it, thinking if my program is still waiting after 5 mins or so.

Can I set a time out to IVssAsync ??
Comments:

Not enough imformation to reproduce this issue. The answer to the question can be found in the discussion board.

Commented Issue: Handle leak in AlphaVSS? [18899]

decaf — Fri, 09 Nov 2012 21:50:39 GMT

I am running the alphashadow sample in a loop to create 1000 snapshots. I have added a while loop around the code that creates snapshot. I am seeing that the thread count, handle count and memory (private working set) keep increasing.

At the end of 70 loops:

Memory =296 MB

Handles = 2100

Threads = 90

The process finally dies.

I am trying to understand which code is leaking so much handles / memory. Will appreciate any help...
Comments: Associated with changeset 95993: Merge Main => 1.2,
Fixed memory/handle leak in Error.cpp. (Incorrect use of CComPtr)

Commented Issue: Handle leak in AlphaVSS? [18899]

decaf — Fri, 09 Nov 2012 21:50:08 GMT

I am running the alphashadow sample in a loop to create 1000 snapshots. I have added a while loop around the code that creates snapshot. I am seeing that the thread count, handle count and memory (private working set) keep increasing.

At the end of 70 loops:

Memory =296 MB

Handles = 2100

Threads = 90

The process finally dies.

I am trying to understand which code is leaking so much handles / memory. Will appreciate any help...
Comments: Associated with changeset 95992: Merge Main => 1.1,
Fixed memory/handle leak in Error.cpp. (Incorrect use of CComPtr)

Commented Issue: Handle leak in AlphaVSS? [18899]

decaf — Fri, 09 Nov 2012 21:49:24 GMT

I am running the alphashadow sample in a loop to create 1000 snapshots. I have added a while loop around the code that creates snapshot. I am seeing that the thread count, handle count and memory (private working set) keep increasing.

At the end of 70 loops:

Memory =296 MB

Handles = 2100

Threads = 90

The process finally dies.

I am trying to understand which code is leaking so much handles / memory. Will appreciate any help...
Comments: Associated with changeset 95991: Merge Dev => Main
Fixed memory/handle leak in Error.cpp. (Incorrect use of CComPtr)

Closed Issue: Handle leak in AlphaVSS? [18899]

decaf — Fri, 09 Nov 2012 21:48:34 GMT

I am running the alphashadow sample in a loop to create 1000 snapshots. I have added a while loop around the code that creates snapshot. I am seeing that the thread count, handle count and memory (private working set) keep increasing.

At the end of 70 loops:

Memory =296 MB

Handles = 2100

Threads = 90

The process finally dies.

I am trying to understand which code is leaking so much handles / memory. Will appreciate any help...
Comments: Resolved with changeset 95990: Fixed memory/handle leak in Error.cpp. (Incorrect use of CComPtr)

Created Issue: Handle leak in AlphaVSS? [18899]

decaf — Fri, 09 Nov 2012 17:09:09 GMT

Created Issue: AlphaVSS hangs on GatherWriterMetadata() [18861]

redserpent7 — Tue, 06 Nov 2012 08:27:06 GMT

Commented Issue: DisableWriterClasses or DisableWriterInstances exception [18004]

decaf — Thu, 02 Aug 2012 18:00:22 GMT

I am getting a System.NotImplementedException when running Alphaleonis.Win32.Vss.VssBackupComponents.DisableWriterClasses(Guid[]). Tried it before and after Initialize backup. It may be just something I am doing wrong... Below is my code:

Guid[] ArrayOfDisabledWriters; //contains a list of disabled writers due to error
List<Guid> ListOfDisabledWriters = new List<Guid>();
IVssImplementation iv = VssUtils.LoadImplementation();
IVssBackupComponents ibc = iv.CreateVssBackupComponents();

ibc.InitializeForBackup(null);
ibc.GatherWriterMetadata();
ibc.GatherWriterStatus();

IList<VssWriterStatusInfo> wsi = ibc.WriterStatus;

foreach (VssWriterStatusInfo value in wsi)
{

if (value.Failure != VssError.Success) //checks for problem writer
{
ListOfDisabledWriters.Add(value.ClassId);
}

}

ArrayOfDisabledWriters = ListOfDisabledWriters.ToArray();
try
{
ibc.DisableWriterClasses(ArrayOfDisabledWriters);
}
catch (Exception e)
{
Console.WriteLine(e);

}

ibc.FreeWriterStatus();
ibc.AbortBackup();

....................................

I get:

System.NotImplemetedException: The requested operation is not supported on the current operating system or by the current profider

Running Windows XP with SP3. Using Visual Studio 2008 with .Net 2.0 version of AlphaVSS.
Comments: ** Comment from web user: decaf **

That is a bit strange indeed. It seems that the call to the DisableWriterClasses method on the raw IVssBackupComponents interface (i.e. the one in the Win32-api, not the AlphaVSS one) returns E_NOTIMPL which in turn causes the exception to be thrown.

The documentation states that this method should be supported on Windows XP so I genuinely have no idea on why this happens. Can you confirm that this method really does work on Windows XP 32-bit if used from a pure unmanaged program?

Commented Issue: DisableWriterClasses or DisableWriterInstances exception [18004]

nickgarvey — Thu, 02 Aug 2012 01:31:32 GMT

I don't believe this is a duplicate of http://alphavss.codeplex.com/workitem/18251 . I am experiencing this problem on Windows XP 32-bit SP3 when using 1.1.4000.3. It doesn't appear to be related to the other bug.

Commented Issue: GetWriterStatus fails on Windows Server 2008 [18251]

mcgyver60 — Tue, 26 Jun 2012 10:17:50 GMT

Hello,

I wrote a small backup application that uses the AlphaVSS 1.1 and it works great on almost any operating system, including Windows Server 2008 R2. Only on Windows Server 2008 x64 (not R2) I always get the Exception:

Alphaleonis.Win32.Vss.UnsupportedOperatingSystemException: The requested operation is not supported on the current operating system.
bei Alphaleonis.Win32.Vss.VssBackupComponents.RequireIVssBackupComponentsEx3()
bei Alphaleonis.Win32.Vss.VssBackupComponents.WriterStatusList.get_Item(Int32 index)

This happens with any writer I try to use. Everything else (initializing backup, setting up backup status, setting up writers, etc.) works perfectly. Has anyone an idea why that happens?

Thanks,

Paul
Comments: ** Comment from web user: mcgyver60 **

Hi Decaf,

Thank you a lot for having solved it in the 4000.3 releases !

Commented Issue: GetWriterStatus fails on Windows Server 2008 [18251]

mcgyver60 — Tue, 26 Jun 2012 10:10:17 GMT

Hi Decaf,

Thank you a lot for having solved it in the 4000.3 releases !

Closed Issue: GetWriterStatus fails on Windows Server 2008 [18251]

decaf — Fri, 22 Jun 2012 17:58:26 GMT

Commented Issue: GetWriterStatus fails on Windows Server 2008 [18251]

decaf — Fri, 22 Jun 2012 17:54:44 GMT

Commented Issue: GetWriterStatus fails on Windows Server 2008 [18251]

decaf — Fri, 22 Jun 2012 17:54:00 GMT

Commented Issue: GetWriterStatus fails on Windows Server 2008 [18251]

decaf — Fri, 22 Jun 2012 17:51:28 GMT