This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
notlogan
Level 6
‎Jul 11, 2013 10:16 AM

error 6307 and 1007

Never mind.....moved solution to a shorter directory path....

Error 65 -6307: Unable to extract one or more files to 'C:\Users\John\Documents\Visual Studio 2012\Projects\Setup\Setup\Setup\Express\Interm\MergeModules\policy_9_0_Microsoft_VC90_OpenMP_x86.24876AE8_F1D7_393B_8A72_D65B918D2BFB'. The file path is longer than the limit set by the operating system. Change the build location of the current release to a shorter path to resolve this issue.

Error 67 -1007: Unable to copy file from 'C:\Users\John\Documents\Visual Studio 2012\Projects\Setup\Setup\Setup\Express\Interm\MergeModules\policy_9_0_Microsoft_VC90_OpenMP_x86.24876AE8_F1D7_393B_8A72_D65B918D2BFB\ul_policy.21022.08.policy_9_0_Microsoft_VC90_OpenMP_x86.RTM.24876AE8_F1D7_393B_8A72_D65B918D2BFB' to 'C:\Users\John\Documents\Visual Studio 2012\Projects\Setup\Setup\Setup\Express\DVD-5\DiskImages\DISK1\Windows\winsxs\ulpOpenMPx86\9.0.21022.8.policy'. The file path is longer than the limit set by the operating system. Change the build location of the current release to a shorter path to resolve this issue.
0 Kudos
(2) Replies
john_dubois
Level 2
‎Jan 10, 2014 07:08 AM

InstallShield uses paths with these huge string of subdirectories that it adds, so adding even a moderate root path produces composite paths that exceed the OS path name limit. Our root paths are defined by our configuration management system, and are not easily changed. As a consequence, ALL of my projects can no longer build install kits after "upgrading" to In InstallShield.

I think this is a fairly major flaw in the InstallShield product.

Is there a work around that doesn't require reconfiguring all of my workspaces?
0 Kudos
alphonseg
Level 4
‎Jan 10, 2014 07:25 PM

A similar problem exist with Microsoft Visual Studio. The simplest solution seems to be creating environment variables to replace some of the long paths. It worked for me. Here is the thread
http://social.msdn.microsoft.com/Forums/vstudio/en-US/0902665a-fefe-47f0-9bfe-904a57fdd0c6/visual-studio-2012-and-2010-both-fail-with-exception-has-been-thrown-by-the-target-of-an?forum=vssetup
0 Kudos