Data Protector Express Single Server Edition error codes, explanations & solutions

[CA1496242]

Can you tell me, where I can find the detailed explanations of Data Protector Express Single Server Edition Error Codes (e.g. "Error 4: Invalid Handle" or "Error 4029: Drive is becoming ready" or etc.) and possible solutions of how to resolve the problems with this errors?

I had browsed a lot across this site, but found nothing; the same result I had while reading the manual & help. Please, give me a direct link to the page(s) with error's explanations & solutions (if the page(s) is/are exist).

Best regards, Sergey.

[D Lancaster]

Hello Sergy,

Unfortunately there is not a single complete list of all error codes and explanations. I continue to work with the developers to make that happen but we are not there yet.

Answers to several of the most common errors and problems are available on hp.com at http://h41206.www4.hp.com/webapps/IV3/node.iv;jsessionid=2E2EB5400D465029BABB456871C3B07D.ubbnpwb3?locale=en_us&prodSeriesId=501431&node=prodITRC%2FUK_HS_IPG_PSG_Ktree_Homepage_EN_01_E%2FN1%7C3%7C5%7C37&prodTypeId=12169&serverId=1#src

(sorry for the long link)

As for the specific errors you mentioned:

Error 4029 indicates that the system timed out waiting for the tape drive to get ready. There may be a problem with the drive or communication with the drive. If it is an HP tape drive, use Library and Tape Tools to check it out. L&TT is available free at http://h18006.www1.hp.com/products/storageworks/ltt/index.html.

Error 4 indicates either a problem with the service or with the catalog. First exit the GUI and try stopping and restarting the service. For Windows the service name is dpwinsvc. For Linus the service name is dplinsvc. If that doesn't work you can force a catalog repair. I have attached the instructions.

DL

[CA1496242]

Greetings, Dave. Thank you for your answer.

I've already been on the page you gave me link for - it's a pity, but there are no solutions on specific problems, like mine.
I'll explain my problem(s) here & if you, or some other forum users can help me to resolve them, it will be great.
---------------------
Identify Media Job. Ends with error 4029. Thanks for the solution, I'll check the connection once more. Though, if Data Protector Express correctly indicates my autoloader in device list, it may be not connection problem? May be the problem is in autoloader hardware?

Import Media Job. Ends with error 4. All my Media Jobs ends with this error. Thanks for instructions you attached to your post, I'll follow them today.

Backup Local Machine Job (backup all server). Ends with error 4024 (IO failure). Pressing the Continue button makes the job cycle began once more, but the result is the same. I found no solution. All my Backup Jobs ends with this error.

Also, Data Protector Express don't count correctly the number of files and used space - it's "lost" about 10-15 percent of data & space before backup process... For example, number of files on server is 150 000 and the uses 12.5 Gb of space (Windows calculation). But Data Protector Express counts 120 000 elements (files) that uses 11 Gb of space - why? How can it lost 1.5 Gb of data?

And in the "devices - hp 1x8 autoloader - storage slots - storage slot 1 ... 8" in status field of any cartridge is "Invalid - Media not identified". Identify Media Job ends with error 4, as I wrote earlier.

I'll be thankful if you can give me some advice of what to do to resolve the problems.

With best regards, Sergey.

[caprcisco]

Hello Sergey..

i suggest first to check if your equipment has a hardware problem.

if you use LTT ( library tape and tool ) you will figure out the source of the problem.

take a look under this link

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00791550/c00791550.pdf

install the application, and before you run LTT be aware that under windows you must disable all backup services, and removable storage.

also check this link for more information:

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&objectID=PSD_OT040301_CW01&jumpid=reg_R1002_USEN

so, complete section:

How do I run L&TT?
How do I check the health of my drive?
How do I generate a support ticket.?
How do I run the Drive Assessment test?
How do I send a support ticket by e-mail?
How do I send an L&TT event log?
How do I send the results of the assessment test to Support?

and attach the test result files to this thread in order to analyze, or you can call to 800-633-3600 op1, op2 create a case support and provide this info to the agent.

so checking first if your equipment doesn't have a hardware problem will a excellent point, after this you can go and check data protector express for support, also check when this problem happend if there is a error code in the from panel of the library or autoloader if this is your case, please provided equipment information, and os.

Best regards..

[CA1496242]

Hello, caprcisco.

Of course, I use LTT & have already done some diagnostic procedures. I've done Health and Test on Drive 1 of 1/8 Tape Autoloader, that I plan to use for backup jobs. Here are last log files of both operations (attached to the post, standard zip-file).

As I check info in logs, there are no hardware problems with autoloader - the problem is in DPE program, I think, cause I tried to perform a backup on the autoloader using Windows Backup tool - and it ends succesfully.

[D Lancaster]

Hi Sergey,

Have you run the catalog repair yet? I'd be interested to see if the results changed after the repair.

Also, you didn't mention which version of Data Protector Express you are running.

AFTER you have run the repair, make sure to go to http://hp.com/go/dataprotectorexpress and download the latest upgrade to Version 3.5

DL

[CA1496242]

Hi Dave

Yes, I've done DPE catalog repair. Though, I haven't found any logs of this procedure, no errors occures during this process. So I think it completed successfully.

But after that I ran HP LTT Tools and it couldn't detect my autoloader! I'm sure it began after catalog repair procedure, because before repairing I tried to backup some data on tapes using Windows Backup tool and it ends successfully.

Now LTT cannot detect autoloader and in Computer Management Console in Removable Storage section the autoloader is marked by red cross with status message "The interface is unknown". So I can't perform any backup operations - neither using DPE nor Windows Backup.

Here is HP LTT log after autoloader detecting efforts:

|__ Scanning Devices (using NT Miniport)
||__ 'atapi IDE Adapter' at address '0/0.0.0', driver: atapi
| ||__ Not scanned for devices
||__ 'atapi IDE Adapter' at address '1/0.0.0', driver: atapi
| ||__ Not scanned for devices
||__ 'ql2300 SCSI Adapter' at address '2/0.128.0', driver: ql2300
| ||__ Found 'COMPAQ MSA1000' at address 2/0.0.0
| | ||__ Device is not claimed by NT
| ||__ Found 'COMPAQ MSA1000 VOLUME' at address 2/0.0.1
| | ||__ Device is claimed by NT: class driver is \\.\PhysicalDrive0
| ||__ Found 'COMPAQ MSA1000 VOLUME' at address 2/0.0.2
| | ||__ Device is claimed by NT: class driver is \\.\PhysicalDrive1
| ||__ Found 'COMPAQ MSA1000' at address 2/0.1.0
| | ||__ Device is not claimed by NT
| ||__ Found 'COMPAQ MSA1000 VOLUME' at address 2/0.1.1
| | ||__ Device is not claimed by NT
| | ||__ This device has been hot-swapped: the old driver may not work for the new device
| ||__ Found 'COMPAQ MSA1000' at address 2/0.1.1
| | ||__ Device is not claimed by NT
| ||__ Found 'COMPAQ MSA1000 VOLUME' at address 2/0.1.2
| | ||__ Device is not claimed by NT
| | ||__ This device has been hot-swapped: the old driver may not work for the new device
| ||__ Found 'COMPAQ MSA1000' at address 2/0.1.2
| ||__ Device is not claimed by NT
||__ 'HpCISSs2 SCSI Adapter' at address '3/0.255.0', driver: HpCISSs2
| ||__ Found 'COMPAQ SCSI COMMUNICATE' at address 3/0.0.0
| | ||__ Device is not claimed by NT
| ||__ Found 'HP LOGICAL VOLUME' at address 3/0.4.0
| ||__ Device is claimed by NT: class driver is \\.\PhysicalDrive2
||__ 'HpCISSs2 SCSI Adapter' at address '3/1.255.0', driver: HpCISSs2
||__ 'HpCISSs2 SCSI Adapter' at address '3/2.255.0', driver: HpCISSs2
||__ 'HpCISSs2 SCSI Adapter' at address '3/3.255.0', driver: HpCISSs2
||__ 'HpCISSs2 SCSI Adapter' at address '3/4.255.0', driver: HpCISSs2
||__ 'HpCISSs2 SCSI Adapter' at address '3/5.255.0', driver: HpCISSs2
||__ 'HpCISSs2 SCSI Adapter' at address '3/6.255.0', driver: HpCISSs2
||__ 'HpCISSs2 SCSI Adapter' at address '3/7.255.0', driver: HpCISSs2
||__ 'symmpi SCSI Adapter' at address '4/0.7.0', driver: symmpi
||__ Found 'HP Ultrium 3-SCSI' at address 4/0.5.0
| ||__ Device not accessible - cannot determine class driver, or opened exclusively
||__ Found 'HP 1x8 autoloader' at address 4/0.5.1
||__ Device is not claimed by NT
|__ Checking for redundant devices.
||__ Redunant device listing. Device PB9840TX3TY0B9 listed with paths 2/0.0.1 and 2/0.0.2.
||__ Removing redundant device at path 2/0.0.1.
|__ Searching for drives of Library 'HP 1x8 autoloader' at address '4/0.5.1'
||__ 1st Method: drives on primary bus
| ||__ Drive at address x.5.255 could not be found on primary bus.
| ||__ Found 0 of 1 drives, must use 2nd or 3rd method.
||__ 2nd Method: finding drives by address
| ||__ Found 0 of 1 drives, must use 3rd method.
||__ 3rd Method: finding drives by serial number
||__ Drive with serial number 'HP' could not be found
||__ Found only 0 of 1 drives.
1 drives of library at address 4/0.5.1 could not be found

Though in Windows Device Manager the autoloader still persists and isn't marked as unusable or corrupted - "device is working properly".

What can happen?

Best regards, Sergey.

[CA1496242]

Any ideas? Or I am at myself?

[D Lancaster]

Sergey,

The catalog repair would not have effected the general MSWindows access to the autoloader. We'll call in some addition help.

DL

[Wes H]

I'm also getting a similar error when I try to do anything. Error: 4024: IO failure. DPX can see the tape device but can't seem to communicate with it when I run any jobs. The tape device works fine on another server using Veritas and/or DPX. I'm using the latest version of DPX and a HP 1/8 autoloader, and a brand new HP AiO 1200 Storage System server. Could this be a SCSI id problem perhaps?

[Curtis Ballard]

Sergey,

I would normally say that your problem is caused by an application however it sounds like you understand the applications and will have checked that.

The connection to the library and the drive is over an identical path and the communication to the library appears fine which suggests that there is a software problem somewhere on the server causing you to not be able to connect to the drive.

Usually that can be traced to some application such as Windows Removable Storage Manager or a backup application. If you can't find anything using the device you can go to device manager and disable the tape drive. After disabling the tape drive try L&TT again and it should work fine. If L&TT works with the tape device disabled then some drive or application is causing the connection problem. If L&TT can't work with the disabled drive then we need to dig a bit deeper.

[CLin_1]

Wich OS you have?

if you are running on windows, make sure there's no "unknown medium changer" under device manager.

Regards,

Chun

[CLin_1]

And also make sure you have a HBA not a smart array controller.