Menu

#3 Corrupted Registry not reported

v1.1.4
closed-postponed
1
2003-04-04
2002-06-06
No

When taking a base image of a Windows
NT/W2K/XP system, The Rembo Wizard attempts to
read the SID-value of the system from the stored
archive image on the server. The value is stored
on the server in a file.

We have had a problem where the image is taken
without a problem but when The Rembo Wizard
attempts to read the SID-value, the call fails and the
execution of The Rembo Wizard's base image
backup programs stops without completion.

Unless the user has opened a console screen, the
problem passes unnoticed to the user. With the
console there is a message

VM Error: No such device

that appears on the console. The problem is that

1) The image, or at least the registry in it is
probably corrupted.

2) The description of the backup is never stored.

3) The SID value of the installation is never stored.

Discussion

  • Petri Makijarvi

    Petri Makijarvi - 2002-06-06

    Logged In: YES
    user_id=187097

    The error has appeared only on a particular hardware
    (Dell Dimension series XPS R333). I have reported about
    the problems with NTDetect() and other disk access
    problems to Rembo (the toolkit we have is 1.1.022).

    In the next version of The Rembo Wizard I plan for the
    following actions:

    Run NTDetect() before taking the base image, and not
    after. This way we can stop the process if the detection
    fails.

    Also, in the function that extracts the SID from the
    archive, I am planning to catch the exceptions so that I
    could at least report if there was severe problems when
    reading the registry values from the archive.

    The above modifications should be ready for the next
    release >1.1.4. Meanwhile, if you have problem, keep
    the console open and look for the VM Error message.

    Petri

     
  • Petri Makijarvi

    Petri Makijarvi - 2002-11-20

    Logged In: YES
    user_id=187097

    I have fixed the problem (of missing problem report - not
    the possibility that it will occur again) in 2.0 release.

     
  • Petri Makijarvi

    Petri Makijarvi - 2002-11-20
    • milestone: 210883 --> v1.1.4
    • status: open --> closed-postponed
     
  • Petri Makijarvi

    Petri Makijarvi - 2003-04-04
    • priority: 7 --> 1
     

Log in to post a comment.

Auth0 Logo