Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About dmg1969

  • Rank
    Occasional forum poster
  1. dmg1969

    MapError and Restore failure

    bump...still hoping for a reply or two. Thanks!
  2. OK...this is a two part question. We are using Retrospect Backup Single Server 7.6. After every backup, whether it's our file server or a client (workstation), the execution completes, but we get a "MapError: unknown Windows error -2,147,221,275". The last time I tried to restore a workstation and it failed, I called in to EMC Dantz. The tech I spoke with said not to worry about the MapError...that we were OK as long as it says that the execution completed successfully. Now, I just tried to restore another computer that I had to install a new hard drive in and it also failed (the restore). I got the following result: MapError: unknown Windows error -2,147,221,275 System configuration restored, please reboot the computer. Can't continue with client disaster recovery, error 1301 (unknown) Execution incomplete. Then, when I reboot the PC, I get that Windows could not start because of a computer disk hardware configuration problem. What is going on? Is it the MapError that we get during backup causing this? How do I correct it? Dave G.
  3. Let me start off by saying that I am not that knowledgable in SQL, which is why I contacted support with this question first. I called and asked one of the support techs this question and his answer was not at all helpful. We are currently running MSDE and it is being backed up by our Retrospect 7.0 SQL agent. This is on a Windows Server 2003 Ent. file server. The MSDE is installed as part of our accounting software (Juris). We will be upgrading the MSDE to SQL 2005 Express. I need to know if Retrospect 7.0 is going to be compatible (and be able to back up) the SQL 2005 Express. The support agent could only tell me that it has only been tested with Windows XP. He was trying to talk me into upgrading to Retrospect 7.5 but, even then, he would only parrot that it had only been tested with SQL 2005 Express on Windows XP. Dave G.