System not able to create restore points

[Qu0ll]

I just opened up System Restore for the first time on my Vista Ultimate x64
system only to find that NO restore points had ever been created. So I
immediately tried to create a manual restore point only to get this error:

The restore point could not be created for the following reason:

The shadow copy provider had an unexpected error while trying to process the
specified operation. (0x8004230F)

Please try again.

Does anyone know what this means or how to resolve it? There is plenty of
disk space available on the system partition.

--
And loving it,

-Q
_________________________________________________
(e-mail address removed)
(Replace the "SixFour" with numbers to email me)

 

[Chad Harris]

Hi QuOIl--

Sometimes but not always, restarting the pc makes this error disappear. I
don't know a percent of times that has efficacy.

This error has been a frequent topic of numerous groups and forums, and I
haven't seen a clearcut explanation.

MSFT is well aware this has been happening, probably a byproduct of the many
shortcuts made in a frantic effort to get Vista to RTM instead of taking 6
more months as many of us repeatedly urged them to do. We were completely
ignored as were many bug reports.

Jill Zoeller [MSFT] who communicates to newsgroups for the Windows Core File
Services team and also works closely with members of the System Restore
teams and other related teams' responses to this error in the past have
requested that people email her the contents of these two logs:

Windows\Logs\WindowsBackup and
\Windows\Logs\CompletePC.

A search of Jill's Blog shows no discussion of a solution or solutions for
this error and a new interface for the blog:

The Filing Cabinet An IT Pro blog about file services and storage features
in Windows Server, Windows XP, and Windows Vista
http://blogs.technet.com/filecab/



I don't know the current status of this error with MSFT and the error may
repesent more than one type of problem. I don't know what Jill and the
people who work with her have been seeing in the logs they have examined.
You might search her blog but I don't see an answer there:

I don't see this problem addressed on a Beta Chat with the SR team either:
http://blogs.technet.com/filecab/pages/447166.aspx

Jill has also requested when she has responded on this error:

Please contact me via email (remove "online") and include the following:

1. The problem description you put below.
2. A screenshot of your Disk Management screen showing disks and volumes.
3. Zip up the contents of %windir%\logs\windowsbackup\
4. Generate a log file using the instructions below and email it to me:

Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Asr,
create a new key called LogFileSetting

Under LogFileSetting, create a new DWORD value called EnableLogging.
Right-click that value, click Modify, and then enter 00000001 (hexadecimal)
or 1 (decimal)

Under LogFileSetting, create a new String value called LogPathName.
Right-click that value, click Modify, and then enter C:\asr.log.

Next, reproduce the error. You should have a file called asr.log under c:\.

You might want to try searching Jill's Blog for this error. I didn't find
any info. I did find discussions of what happens when there is not
sufficient space to create a restore point.

Good luck,

CH

 

[Qu0ll]

Hi QuOIl--

Sometimes but not always, restarting the pc makes this error disappear. I
don't know a percent of times that has efficacy.

This error has been a frequent topic of numerous groups and forums, and I
haven't seen a clearcut explanation.

MSFT is well aware this has been happening, probably a byproduct of the
many shortcuts made in a frantic effort to get Vista to RTM instead of
taking 6 more months as many of us repeatedly urged them to do. We were
completely ignored as were many bug reports.

Jill Zoeller [MSFT] who communicates to newsgroups for the Windows Core
File Services team and also works closely with members of the System
Restore teams and other related teams' responses to this error in the past
have
requested that people email her the contents of these two logs:

Windows\Logs\WindowsBackup and
\Windows\Logs\CompletePC.

A search of Jill's Blog shows no discussion of a solution or solutions for
this error and a new interface for the blog:

The Filing Cabinet An IT Pro blog about file services and storage features
in Windows Server, Windows XP, and Windows Vista
http://blogs.technet.com/filecab/



I don't know the current status of this error with MSFT and the error may
repesent more than one type of problem. I don't know what Jill and the
people who work with her have been seeing in the logs they have examined.
You might search her blog but I don't see an answer there:

I don't see this problem addressed on a Beta Chat with the SR team either:
http://blogs.technet.com/filecab/pages/447166.aspx

Jill has also requested when she has responded on this error:

Please contact me via email (remove "online") and include the following:

1. The problem description you put below.
2. A screenshot of your Disk Management screen showing disks and volumes.
3. Zip up the contents of %windir%\logs\windowsbackup\
4. Generate a log file using the instructions below and email it to me:

Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Asr,
create a new key called LogFileSetting

Under LogFileSetting, create a new DWORD value called EnableLogging.
Right-click that value, click Modify, and then enter 00000001
(hexadecimal)
or 1 (decimal)

Under LogFileSetting, create a new String value called LogPathName.
Right-click that value, click Modify, and then enter C:\asr.log.

Next, reproduce the error. You should have a file called asr.log under
c:\.

You might want to try searching Jill's Blog for this error. I didn't find
any info. I did find discussions of what happens when there is not
sufficient space to create a restore point.

Good luck,

CH

OK thanks Chad for the effort to give such a detailed reply. It's not a
complete disaster for me as I take an image of the disk every night using
Acronis True Image so if I need to go back to a previous point I simply
restore from a saved image. However, it may point to a more serious problem
and I would really like to find a solution.

--
And loving it,

-Q
_________________________________________________
(e-mail address removed)
(Replace the "SixFour" with numbers to email me)