ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

P2P download fails with HTTP error 404 when the package path is very long.

book

Article ID: 171888

calendar_today

Updated On:

Products

Management Platform (Formerly known as Notification Server)

Issue/Introduction

P2P download fails with HTTP error 404 when the package path is very long.

Example Symantec Management Agent log entry:
Operation 'Direct: Get Block 0-12288' failed.
Protocol: HTTP
Host: 192.168.2.105:56118
Path:
/Altiris/AS/Pkg/8ef28bc606f8304a7d0a774165b71ddaf3ab0778/cache/0123456789/LetsMakeThis%20A%20VeryLongPackagePath0123456789/SomeDriversandFiles/Applications/AC/W10/HDAudioOEDrv/Firmware/dsp_fw_release_7CAD0808-AB10-CD23-EF45-12AB34CD56EF.bin

Connection Id: 19.5016
Communication profile Id: {21722741-9783-4E72-9AF7-E396856035A3}
Error type: HTTP error
Error code: HTTP status 404: The requested URL does not exist on the server or
the server is down (0x8FA10194)
Error note: 404 Not Found

Cause

Known Issue

Environment

Symantec Management Platform 8.1 RU5, RU6

Resolution

Symantec engineering is working on addressing the issue tentatively in Symantec Management Platform 8.5.
WORKAROUND: Shorten the package root path on the Symantec Management Platform server. Alternatively package server to client downloads will also work.