Path too long - Upgrade/Backup
The 'Path Too long' problem might occur due to an earlier patch/upgrade that is applied.
While upgrading (applying PPM,) the files that are to be overwritten in the PPM will be backed up inside a folder named Patch.
The files inside this follow the same directory structure as the original and results in this error.
eg. ManageEngine/reports/webapps/ROOT/WEB-INF/web.xml will be moved to ManageEngine/reports/Patch/ZOHO_DB-3.1.00-SP-0.0.0/SERVER/ROOT.war/WEB-INF/web.xml
As the number of sub-folders increases, the path elongates and exceeds windows limit of 260 characters.
This will not affect the product in anyway, but will not let the files with lengthy path to be deleted or copied.
In this case, the you can ignore the un-copied files.
New to ADSelfService Plus?
Related Articles
Upgrade to AnalyticsPlus 5400 Fails for Users with Missing zsoid Values
Issue Upgrading from builds between 5301 and 5360 to build 5400 fails because the zsoid field for some users is null. Error Trace java.sql.SQLException: This column [ZSOID] has some null values, hence it cannot be modified as not-null. Cause The ...Failed to upgrade to build 5300/5301
Issue: Upgrade fails while attempting to upgrade to the build 5300/5301. Cause: Upgrade fails due to a necessary system property required for logging slow queries is missing. This issue will arise while attempting to upgrade to the ...Upgrade Key steps
Key steps that must be followed without which the upgrade may fail. All Analytics Plus Services must be stopped. AnalyticsPlus folder must be given "Everyone" folder permission with "Full Control" before upgrade (Can be revoked after upgrade) ...Analytics Plus upgrade from build 4270 to 4280 failed.
Error trace: Jul 28, 2019 9:41:06 AM [com.adventnet.tools.update.installer.Backup] [SEVERE] : ERR:The Jar File to be updated is not presentlib\hadoop-0.13.0-core.jar Text instructions: 1. Stop the Analytics Plus services. 2. Delete the folders ...Upgrade issue in build 3200
Upgrade issue in build 3200 The below cases were identified in local system and couple of customer's system during 3200 upgrade. Issue 1: PGSQL migration fails: Since this upgrade will upgrade pgsql version, pgsql has its own upgrade prior to ...