I already noticed many of them are facing the same issue,
But already all the solutions you provided,
This has detailed configuration of My System,
OS : Window 8.1
VS : 2012 Professional
Python : python 2.7.4

Error:

Detailed Verbose Error:

Please provide me some inputs on this and how to fix this now. This happens for me for almost all
Il fattore scarpetta pdf - free software and shareware. modules which needs node-gyp rebuild.

If you need me to provide more inputs i am happy to help :)

wondering if it is related to this issue in msbuild. microsoft/msbuild#53 ??

@dhusemann This doesn't look like an MSBuild max-path issue.

From the MSBuild part of the log:

Note the d:Microsoft.Cpp.Default.props part. That file would usually be referenced by

where VCTargetsPath is part of an MSBuild toolset. Here, it looks like it's unset, causing the import to be expanded to Microsoft.Cpp.Default.props, which Windows then opens using the current drive root.

This looks like this old StackOverflow problem.

@bboysathish, can you post the contents of your registry's HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSBuildToolsVersions (and the Wow64 version)? Then try a repair install of Visual Studio to see if that fixes the issue--I don't recommend manually editing the registry at this point.

I have once again cleanly installed python, visual studio and problem got solved. Thanks

Just in case, when reinstalling python and visual studio does not help, I got it working by setting the environment variable VCTargetsPath to the directory location where Microsoft.Cpp.Defaults.props is installed, C:Program Files (x86)MSBuildMicrosoft.Cppv4.0v140 in my case on Windows 7.

@RomanManz it's works !

or..
C:Program Files (x86)MSBuildMicrosoft.Cppv4.0V140Microsoft.CppCommon.targets(356,5): error MSB6006: 'CL.exe' exited with code -1073741515

..ideas?
followed thread instructions

I solved it with Roman's @RomanManz approach:
SET VCTargetsPath=C:Program Files (x86)MSBuildMicrosoft.Cppv4.0v140

I also removed Microsoft Visual Studio 2015 Community Edition and installed Microsoft Visual C++ Build Tools, version 14.0.25420.1.

Download link for the Standalone Build Tools

Reinstalling Visual C++ Build Tools worked for me. Thanks, @RomanManz and @lboening !

@nightwolfz thanks that worked for me

+1 on the tip from @RomanManz and @lboening - the 2015 Build Tools seemed to be enough for me, without needing VS2015 Express Edition or the more current Community versions.

I also needed to make sure that I had the Windows 8.1 SDK option selected in the Build Tools 2015 install. The Windows 10 SDK by itself was not enough.

I tried many variations and components of the Build Tools 2017 install and my node-gyp build would fail on my machine.

Here are the steps that worked for me, if you are trying to install node-java

1. Install windows .NET framework 4.5.1 (Restart your machine)
2. npm install --global --production windows-build-tools
3. Add VCTargetsPath enviornment variable with value 'C:Program Files (x86)MSBuildMicrosoft.Cppv4.0v140'
4. npm install java

I did a couple of things to fix it, probably ugly but it's working now :

• Installed Node v8.9.1
• I copied the missing files from my VS2017 installation (C:Program Files (x86)Microsoft Visual Studio2017BuildToolsVCToolsMSVC14.13.26128libx64) to Windows Kits installation (C:Program Files (x86)Windows Kits8.1Libwinv6.3umx64)
• Updating VS2017/2015 C++ Build tools from VS installer
• Added VCTargetsPath=C:Program Files (x86)MSBuildMicrosoft.Cppv4.0v140
• Added GYP_MSVS_VERSION=2015

Hope this help 👍