-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Desktops
- Desktop Operating Systems and Recovery
- HPDM 5 SP10: “Error 34603008” While imaging ThinPro 8.1

Create an account on the HP Community to personalize your profile and ask a question
03-17-2025 01:00 PM
Hi,
Problem:
When trying to capture an image from a ThinClient with ThinPro 8.1.0 the “_Capture image” task fails with error 34603008. The error does not occur when running the same task on a ThinPro 7.2 client.
Running HPDM version 5.0.3610.40681 on Windows Server 2019
Think client hardware is T540
2025-03-14 10:09:19 | Successfully sent task to the HPDM Gateway |
2025-03-14 10:09:23 | Task has been retrieved by the Agent. |
2025-03-14 10:12:25 | Task has been retrieved by the Agent. |
2025-03-14 10:12:31 | [Error code: 34603008] [Module: Agent] [Category: 0] |
2025-03-14 10:12:31 | [Error Details]: Capture image to the Master Repository. Failed to upload testCap001.dd.gz to /Repository/Images/testCap001. Failed to execute CaptureImage task. ErrorCode: 34603008, Error Info: ../../Task/common/MachiningTask.h@40: Failed to handle post image. ../../Task/linux/ImageTask_Thinpro.cpp@1584: Imaging operating failed. ../../Task/common/ImageTask.cpp@259: Error Code: 127 |
2025-03-14 10:12:31 | Request to delete failed packages about imaging from Master Repository |
2025-03-14 10:12:31 | Failed to execute common task. |
2025-03-14 10:12:31 | ErrorCode: 34603008 |
I see the same type of error documented here: https://h30434.www3.hp.com/t5/Business-PCs-Workstations-and-Point-of-Sale-Systems/HPDM-ErrorCode-346...
It links to a fix using a a 8.0 patch that has worked for some. Is there something similar for version 8.1?
Thanks!
04-03-2025 02:27 PM
Here's a bit of an update. We have a DEV HPDM server setup the same as the PROD one that has the error. The same issues occurs when on the DEV server. I updated the DEV server from 5.0.3610.40681 to 5.0.3610.41643. It made no difference.