restoredb.wsf doesn't extract SYMANTECGHOST.DB on Windows Server 2008

[GoogleCodeExporter]

extract any backup cab on Windows 2008 and the above fails to extract due
to a silent and incompatible change in the command-line behaviour of
extract.exe

Original issue reported on code.google.com by nigel.bree@gmail.com on 5 Aug 2008 at 12:11

[GoogleCodeExporter]

Change to r4 contains a potential fix to this (along with some other in-process
cleanup work) which needs testing.

http://code.google.com/p/gss-scripts/source/detail?r=4

Original comment by nigel.bree@gmail.com on 5 Aug 2008 at 12:13

• Changed state: Fixed

[GoogleCodeExporter]

I tried your new set of DB restore tools here.  With same failure as before on 
my new
2008 server, "Failed to extract data file "db\Symantecghost.db" from input 
cabinet.
I'm coming from Windows 2003.  

Original comment by stettler...@gmail.com on 30 Jan 2009 at 4:54

[GoogleCodeExporter]

Thanks for the report; I won't be able to try creating a Server 2008 test bench 
for
this for a couple of days, and in any case I may not be able to reproduce the 
failure
you are seeing straight away, so something that would be really helpful would 
be if
you could take a Process Monitor trace covering the restore from start to the 
time it
fails - you can get it from 
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

The trace will be big but it will compress well with a zip utility; probably 
rather
than attaching it here it's better to e-mail it to me (my username is my 
gmail.com
address) to inspect.

Original comment by nigel.bree@gmail.com on 31 Jan 2009 at 12:06

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Restoring from an elevated restoredb.wsf worked fine using the Vista branch 
version
of the tools, so this appears to be more a usability issue. Lowered priority to 
medium.

There did turn out to be a small bug in the creation of the restore shortcut to
request elevation because I forgot to make the shortcut target the script 
interpreter
rather than the script (an odd quirk of Vista's shell means that elevation is
controlled by the "RunAs" registry key based on the extension of the shortcut
target), so that's fixed.

Additionally, since I had to go to all the work of setting up a test system, 
I've
taken the opportunity to add new code to make the backup and restore scripts 
request
elevation programmatically (and fixed a small bug in the handling of the 
automatic
shortcut creation in the backup script), which should completely fix the actual
usability problem.

In addition, the code to test for elevation on Vista is conditioned so that on
non-Vista systems there is now an error clearly stating only admins can run the
script, which on Vista systems when run as non-Admin the "runas" style of 
elevation
is to an admin, which works well.

Checked in with changelist 9, 
http://code.google.com/p/gss-scripts/source/detail?r=9

Original comment by nigel.bree@gmail.com on 2 Feb 2009 at 7:46

• Changed state: Fixed
• Added labels: Priority-Medium
• Removed labels: Priority-High