iversonk56044 / gss-scripts

Automatically exported from code.google.com/p/gss-scripts
0 stars 0 forks source link

backupdb.wsf stops with error 800A000D at line 246 #17

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.simply execute the backupdb.wsf script from an elevated prompt
2.
3.

What is the expected output? What do you see instead?
see the attached file for the script error

What version of the product are you using? On what operating system?
GSS 11.5.1 2266 / Windows XP SP3

Please provide any additional information below.
I can't be more specific

Original issue reported on code.google.com by cuic...@gmail.com on 1 Jul 2012 at 12:16

Attachments:

GoogleCodeExporter commented 8 years ago
I can't reproduce this situation here on a normal install of GSS, but it would 
appear that the most likely cause is that the product's registry settings are 
not correct: the CDbl() function will give this error if given an empty string, 
and if the target file does not exist the call to get the file version will 
return an empty string.

The product install location comes from 
HKLM\Software\Symantec\InstalledApps\Ghost and it would be good to verify that 
this registry value is correct: the normal value it would have is "C:\Program 
Files\Symantec\Ghost" so that on line 246 the code can inspect the version 
string of the file "C:\Program Files\Symantec\Ghost\ngserver.exe"

For this to fail, then the registry key could be not set or set incorrect, or 
something else could be interfering with things. If you you check the value of 
this registry key and whether it's correctly pointing at the directory 
containing the GSS server executables that would help a lot in determining how 
I should handle the situation in code, since if the registry setting for this 
is wrong then it will have other effects on code later in the script.

Original comment by nigel.bree@gmail.com on 1 Jul 2012 at 3:37

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
I have found the registry and its has the correct value.

As expected there's is also ngserver.exe in C:\Program
Files\Symantec\Ghost, so ServerExe should be properly set.

---------

On a side note, i have a sandbox running GSS 2.5.1 on a windows 7 32
bits and there's no HKLM\Software\Symantec.

On the same machine, regedit find no strings refering to either
"C:\Program Files\Symantec\Ghost" or "C:\Program
Files\Symantec\Ghost\ngserver.exe"

Original comment by cuic...@gmail.com on 1 Jul 2012 at 8:09