StoreEver Tape Storage
cancel
Showing results for 
Search instead for 
Did you mean: 

Error: 4462, HP DPE SSE 4.00-sp1 (build: 43064)

 
Highlighted

Error: 4462, HP DPE SSE 4.00-sp1 (build: 43064)

Hello,

Server: ProLiant ML350G5
S/N: -removed-
P/N: 470064-928

Problem description:
Using HP Data Protector Express Single Server Edition 4.00-sp1 (build: 43064) to do a full backup with OBDR (One Button Disaster Recovery) functionality.

Get an Error 4462 (see below). Added the dptrace.txt too. Both services "Volume Shadow Copy" and the "Volume Shadow Copy Provider" are started (set to automatic). HBA and Ultrium data see below. Both are OBDR ready. Latest firmware has been installed.

thanks in advance
Siegfried Greisinger

==== Error message ===========
Fehler 4462: Der Datenträger wurde nicht zum Booten mit OBDR (One-Button Disaster Recovery) von HP vorbereitet.

SVP04L\Geräte\HP Ultrium 2-SCSI (Serial Number HU109119LJ)
Datenträger

Die Bootspur wurde aufgrund eines Fehlers (Unhandled Error) nicht auf den Datenträger geschrieben. Weitere Informationen erhalten Sie im Auftragsprotokoll.
==============================

==== dptrace.txt =============
2009-05-11 09:40:36 Sup: Data Protector Express v4.00 (build 43064) sp1

Copyright (c) 2008 Hewlett Packard Development Company, L.P.

OS Type : 2
OS Sub Type : 0
OS Version : 5.2
Node Name : SVP04L
Command Line : C:\Programme\HP\Data Protector Express\win\x86\dpwinsdr.exe
2009-05-11 09:50:32 Drm: Failed to enum keys 1
2009-05-11 09:50:32 Drm: Failed to enum keys 1
2009-05-11 09:50:32 Reg: Failed to unload hive DRSYSTEM (87)
2009-05-11 09:50:36 Wrg: Unable to open key setupdd (2)
2009-05-11 09:50:36 Wrg: Unable to delete value NetcardDlls (2)
2009-05-11 09:50:36 Wrg: Unable to delete value LowerFilters (2)
2009-05-11 09:50:36 Wrg: Unable to delete value LowerFilters (2)
2009-05-11 09:50:36 Wrg: Unable to delete value UpperFilters (2)
2009-05-11 09:50:36 Wrg: Unable to delete value LowerFilters (2)
2009-05-11 09:50:36 Wrg: Unable to delete value UpperFilters (2)
2009-05-11 09:50:36 Wrg: Unable to open key DRSYSTEM\ControlSet001\Control\Keyboard Layouts\00000c07 (2)
=============================

HP ULTRIUM448 DRV - Device 4:
=============================
Status: OK
Model: HP ULTRIUM448 DRV
Firmware Revision: T61D
Serial Number: -removed-
SAS Address: 500110A00122CAC8

Ultrium Drive attached to HBA:
==============================
HP SC44Ge Host Bus Adapter in Slot 6 (3)
Model: HP SC44Ge Host Bus Adapter
Status: OK
Bios Version: 6.18.5.0
Serial Number: -removed-
Firmware Version: 1.23.40.0
3 REPLIES 3
Highlighted
Frequent Advisor

Re: Error: 4462, HP DPE SSE 4.00-sp1 (build: 43064)

Dear Siegfried,
I had a similar problem and after going through the manuals, licenses, etc. I figured the OBDR requires a "boot image" on disk, the creation of which is not part of the basic DPX SSE.
With my new drive however there was an offer for a 30day evaluation license of the full package, which I activated. Now everything did work. I now also could create a recovery boot CD, which before was not possible.
When the 30 days were over I had to remove the expired evaluation license but found out that the OBDR keeps working. So apparently it's the missing boot image that was causing the trouble at the start. Maybe also in your case.
I'm using DAT72 though.
Highlighted

Re: Error: 4462, HP DPE SSE 4.00-sp1 (build: 43064)

Hi,

Trying to write a bootable media to a *.iso (drboot.iso) doesn't work too.

I'm using: Windows Server 2003 Standard Edition 32-bit (german).

I tried it now at home with a Vista 64-bit machine, there the creation of the boot media suceeds.

But this doesn't help me. Tried it with a fresh Win2k3 installation too - same failure.

Any ideas?

cu
Siegfried
Highlighted

Re: Error: 4462, HP DPE SSE 4.00-sp1 (build: 43064)

Good night,

I guess i found a solution now. It looks like HP Data Protector can't handle incorrect registry values. A lot of PreLoad settings inside the registry refer to a keyboard layout 00000c07, that doesn't exist. I manually edited about 20-30 keys in my registry (test machine) and changed the value to an existing keyboard layout (00000407 - german).

Now i was able to create a boot image in my test environment. I will test it tomorrow on the production machine. Maybe this will solve the OBDR issues too.

cu
Siegfried