Failed to schedule Software Protection service for re-start

I have been running Windows 8 for a while now, upgraded from 7.

I've been seeing the following error in my Event Viewer for a while and decided to look into it:

Failed to schedule Software Protection service for re-start at 2113-02-08T11:19:03Z. Error Code: 0x80070002.

After much searching I found this thread on Technet that covers deleting and reinstalling the offending scheduled task.

http://social.technet.microsoft.com/Forums/en/winservergen/thread/6f986797-0db9-454d-9979-dbc625f09b82

So, with thanks to Yan Li I was able to stop the error occurring, but I did encounter a different error when attempting to import the task from my backup:

(24,9): Priority

The error message isn't very helpful, but comparing the XML with that of SvcRestartTaskLogon, I noticed that the following section in SvcRestartTask

<RestartOnFailure>
      <Priority>3</Priority>
      <Priority>PT1M</Priority>
</RestartOnFailure>

in SvcRestartTaskLogon is

<RestartOnFailure>

      <Interval>PT1M</Interval>

      <Count>3</Count>

</RestartOnFailure>

I changed the offending lines in SvcRestartTask and it now imports correctly.

Microlite BackupEdge again...

Info: Restore Failed With Exit Code 64

Helpful error message when attempting an Expert restore today - pulling back an inadvertently deleted file from last nights backup created with Microlite BackupEdge

What it actually meant to say was :

Info: Restore Failed - unable to create directory in restore location.

If you try to restore without selecting Flat Restore AND if a file with the same name as the folder you're attempting to restore exists in the Restore To: path, you'll get this error.

http://forums.devshed.com/showpost.php?p=2072796&postcount=17

Delete Files Older Than Date Using Batch Files


This problem has nagged at me for years. Here is a batch command to delete files on a Windows 2003 machine.

forfiles -p z:\backup -s -m *.* -d -3 -c "cmd /c del /q @path"
This will delete all files in my backup directory older than 3 days. To test it first, use this:

forfiles -p z:\backup -s -m *.* -d -3 -c "cmd /C Echo 0x22@Path\@File0x22"
This will print out each file that you will be deleting

This came in handy for deleting my old Macrium Reflect backups which were created using it's Duplicate facility, I didn't want to use their suggestion of robocopy, as my initial backup is over the network and I didn't want to drag it all back again!  Thanks erijas!

A nice exciting new error in Microlite BackupEdge today.

af token exists before mount

Got this error in edgemenu when we attempted to access a usb disk which was setup as an attached file system af0, using a file system partition fsp0.

Turned out that once again there were left over files in the mount point:

/usr/lib/edge/system/mnt/af0

Moved the .edge_af file to /tmp and it's all working again now!

I wish the firm would make the change to using the smartdrive method, it's certainly less problematic in my experience.

To uninstall microlite backupedge / edgemenu


Simply execute the following command from root ::


/usr/lib/edge/bin/edge.remove

Attempted to add a cow-worker to a MSN (Windows Live) Messenger Group today.


When sending from within messenger, the invite went from my screen but never arrived.
Tried again from the group website and it said I couldn't invite him:


"This person doesn't allow invitations"


Turned out that his account needed setting to a Limited Profile, rather and Private.
Changed that, and was then able to invite him to the group successfully.

AF Unmount Command Failed / AF Token File Missing

Using Microlite BackupEDGE getting the following error:

Command was: "umount /usr/lib/edge/system/mnt/af0"
Reason is AF Unmount Command Failed          

Setup all looks OK in edgemenu - default resource is:
 fsp!fsp0 (/fsp0) (Directory Resource) 

Using USB HDD as backup media, which can be mounted and unmounted without problems.

Found that the backup was actually going into the directory mentioned in the unmount command. There shouldn't be anything in that folder. Removed the contents and ran the scheduled backup.
New error :

Generic System Error
Reason is AF Token File Missing

Initialised the media - didn't help.
Make sure af0 is empty still.

Rebooted - errors gone, backup ran through OK.
Strange!

-update-
seems that removing the following file will negate the need to reboot and is likely the whole cause of the problem - this file is used to track the mount status. It gets 'mounted' even though the device isn't mounted, then it never attempts to mount and creates the backup in the folder, rather than the USB drive.

/usr/lib/edge/system/locks/af0.lck

You DO still need to initialise the media.