Could anyone please suggest any workaround for 1320 error: the specified path is too long. The application is installing some files to a substitute drive.

Does it happen when we try to install some files to a substituted drive ? If we map that drive and install, then it is perfect. But can anyone help me to understand the reason for that.

I googled, but not able to figure out the reason.

Thanks in advance.

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Presumably you mean a drive created using SUBST? That won't work because DOS still has to resolve the path at some point and it's at that point that the path is too long (> 254 characters). There is no one-stop solution. I recall working around the issue with one product (was it BEA WebServer?) with a scripted install which copied the folders to a point roughly half-way down the intended path and then moved them to the actual target when that completed. Hideous...
Answered 07/02/2009 by: VBScab
Red Belt

Please log in to comment
Thanks for the information VBScab :)
Answered 07/03/2009 by: ramesh111k
Purple Belt

Please log in to comment

Thanks for the information. Also try Long Path Tool. It helped me with Error 1320 on Win 7. :)

Answered 03/22/2013 by: GarryBrown
White Belt

Please log in to comment