Jump to content

mkmike

Members
  • Content count

    18
  • Joined

  • Last visited

Community Reputation

0 Neutral

About mkmike

  • Rank
    Occasional Forum Poster
  1. mkmike

    Error -1017, (Insufficient Permissions)

    Having re-installed Vista, I have found the culprit on VSS problems. The culprit, for me anyway, is Macrovision InstallShield 2008. On my new installation, everything with Retrospect, Open File backup and VSS was fine until I installed Macrovision InstallShield 2008 Professional. As soon as I did that, the VSS problems returned and Open File backup ceased to work. In addition, Vista's own backup program would not work and even worse that that, creating restore points would not work. I then un-installed InstallShield, re-booted my PC and everything relating to VSS works again as it should. This is clearly not a Retrospect problem and I have reported the matter to Macrovision.
  2. mkmike

    Error -1017, (Insufficient Permissions)

    Quote: >>Why any of this should have been neccesary I do not understand. None of it should be necessary. Retrospect uses VSS in it's default state. That said, problems with VSS will cause problems in Retrospect. What caused those problems is unknown to me. Are you running x64 Vista? No just 32 bit Vista Ultimate. I suspect that I do have a problem with VSS because the bulit-in Vista backup also failed with an error. Note that the change of maximum ShadowStorage size has nothing to do with the VSS error. I have changed it back to 90GB and everything still works. I changed it back because when I backed up in Retrospect at maximum 30GB, there were lots of comparison errors. When I backup up at 90GB there were no comparison errors. By the way, the built-in Vista backup also now works.
  3. mkmike

    Error -1017, (Insufficient Permissions)

    I have got it working now (3 times it has worked) and am not sure which of the changes I made did it. The changes I made (remember this is Vista in my case) are: 1) I changed the ownership of 'volsnap.sys' (Windows\System32\Drivers) to 'Administrators' from 'TrustedInstaller' and gave 'Administrators' 'Full Control'; 2) Used vssadmin.exe (Windows\System32) from the Command Line (run as Administrator) to reduce the maximum size of Shadow Storage on my C: drive from 90GB to 30GB (this seems unlikely to have done it); and 3) Edited the registry key: \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl adding several additional REG_DWORD entries in the form 'Name'='User' 'Value'=1'. The 'Users' I added were: SYSTEM, Administrator and myself. This is supposed to permit Shadow Writers to use these specific accounts (see: http://technet2.microsoft.com/windowsserver/en/library/d8288c6d-2064-4a54-b516-98acc315dd481033.mspx ). I have a feeling it may just be the 'SYSTEM' one that did it. Why any of this should have been neccesary I do not understand. Anyway, this may help someone else.
  4. mkmike

    Error -1017, (Insufficient Permissions)

    It only worked once and now I am back to failure. Actually, Retrospect does start the Volume Shadow Service but it does not help. The VSS error is always much the same as above.
  5. mkmike

    Error -1017, (Insufficient Permissions)

    I have found the answer to my first question and the Volume Shadow Copy service should by default be set to manual and should by default be in stopped mode. The service is dependent on RPC and that service is set to automatic and running as it should be. The 'vssadmin.exe' commands line tool suggests that everything is fine with the Volume Shadow Copy service. It follows that programs requiring it, like Retrospect, should be able to start it. If I can start it manually, why is Retrospect not starting it?
  6. mkmike

    Error -1017, (Insufficient Permissions)

    Further to my last post I have cured the problem, although this will not help the OP (bobsch). In my case, I noticed that the Volume Shadow Copy Service VSS was not running and was set to 'manual'. I started the service and Open File Backup worked without error. I will change the service to start automatically. Is it usual for this service to be set to 'manual'? If so, Retrospect would need to start it and clearly this is not happening. Any view on that?
  7. mkmike

    Error -1017, (Insufficient Permissions)

    I have looked in the Event logs and have found the following relating to VSS before the Retrospect error: Log Name: Application Source: VSS Date: 04/07/2007 19:35:58 Event ID: 12293 Task Category: None Level: Error Keywords: Classic User: N/A Computer: Desktop.mshome.net Description: Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details PreFinalCommitSnapshots({e48ca755-0668-44e0-89f2-c616840de743}, 2) [hr = 0x8000ffff]. Operation: Executing Asynchronous Operation Context: Current State: DoSnapshotSet I have searched Microsoft for various aspects of this and have not found anything useful.
  8. mkmike

    Error -1017, (Insufficient Permissions)

    I am getting exactly the same problem but do not have any ideas. In my case, the OS is Vista. At least it is encouraging to know that it nothing to do with Vista security.
  9. mkmike

    7.5.370 with Vista - Backup size ballooning

    I found a similar problem and decided it was because the Retrospect 'Selectors' do not work in Vista as they did in XP. I suppose they were written for XP and may have to be re-written for Vista. I am now doing a very selective, item by item, backup. It is the only way that I can get what I want without a lot of rubbish.
  10. It is now only 2 weeks to the general release of Windows Vista to the worldwide public. The RTM version has been around in developer circles for several months. In spite of this there is a complete absence of any mention of it on the EMC Retrospect site. It would be nice to get some indication of when we can expect a version of Retrospect that is supported on Vista or instructions on how to get the current version (7.5) to run thereon .
  11. mkmike

    7.5 and Windows Vista

    You could well be right. However, surely EMC must be thinking about it. If they wait until final release before starting development, it will be many months after final Vista release before they will have a saleable product for that OS.
  12. mkmike

    7.5 and Windows Vista

    Does anyone know if Retrospect Professional can be installed and work on MS Windows Vista or will we have to wait for a new version? If the answer is the latter, how long will we have to wait. Vista is currently at RC2 and the final version is due to be released to professional users in November. I should be getting my Vista in November but can only install it if I have a version of Retrospect Professional that will work thereon.
  13. mkmike

    Assert error

    Sorry but that was another red herring. I used the program several times on the day that I thought I had cured it, just to be sure, and it worked perfectly. However, as soon as I tried it on the following day I was back to the assert error every time. What I have noticed is that it only seems to happen when backing up my main system disk 'C:'. It does not happen if I backup my secondary disk 'D:'. Anyway, I am now back on version 5.6, which works, and I will not be trying 6 again in a hurry.
  14. mkmike

    Assert error

    It is me again with another thought. Why should should this have so affected version 6, when it had no similar effect on version 5.6?
  15. mkmike

    Assert error

    I have now fixed it. It was because I had installed an MS package 'CE Tools', on the day the problem started. This package defaults to a directory c:\Windows CE Tools. I wanted to exclude this directory from my backup and added the folder to the exclusion list in my script. Clearly however, the 'Windows' in the folder name was causing some confusion. I have now changed the script entry to '*CE Tools' and the problem has gone away.
×