I am working on Windows 10 and trying to install Hadoop
I downloaded it from here.
When trying to extract Hadoop for files (libhdfs.so and libhadoop.so) I am getting the error.
Cannot create symbolic link : Access is denied
How do I fix this?
asked May 13, 2016 at 12:34
-
Are you running as an Administrator?– DavidPostill ♦Commented May 13, 2016 at 12:39
-
Note to install hadoop on Windows you need to download the source and build it yourself. Build and Install Hadoop 2.x or newer on Windows– DavidPostill ♦Commented May 13, 2016 at 12:44
-
@DavidPostill admin did it - had to run 7Zip as app. Thanks– Matas VaitkeviciusCommented May 13, 2016 at 12:49
-
Great! Added as answer.– DavidPostill ♦Commented May 13, 2016 at 12:51
Add a comment
|
2 Answers
How do I fix this?
I am getting the error: "Cannot create symbolic link : Access is denied"
You need to run 7-Zip File Manager in administrator mode.
Right-click the icon of 7-Zip File Manager, and then click "Run as administrator".
answered May 13, 2016 at 12:51
-
1Worked, but why do you need admin to create symlinks on Windows?– TimmmmCommented Sep 27, 2016 at 11:54
-
3@Timmmm You don't necessarily need admin but you do need a special privilege: See How do I create a link in Windows 7 home premium as a regular user?– DavidPostill ♦Commented Sep 27, 2016 at 11:58
-
@DavidPostill is this answer applicable to Windows 7? Commented Oct 5, 2016 at 14:32
-
The accepted answer is not really correct, although possibly may work in some scenarios, is not the reason "why", and privilege doesn't really apply here.
The problem is going to arise in most scenarios when unpacking a .tar.gz or other similar non-Windows file-system format. The problem is due to the order in which the files are being unpacked. In Linux for example, "dangling sym-links" are permitted, therefore no error occurs, and everything works fine, but on Windows, that is not the case. It is unpacking and trying to create a symbolic link to a file that does not yet exists, which is not permitted.
Forcing it may unpack the files in some situations, or may unpack them but they will be of 0 size. Extracting multiple times MAY fix the issue in other situations, depending on how they were packed, or manual extraction in the correct order.
For 100% success, unpack them on a system that permits symbolic links to non-existent files (i.e. Linux, or the system the file was intended for.
This is not a "permission" issue, but an OS one. You are not going to see this error on files that were packaged on the file-system you are using, only on files intended for "foreign" operating system, like .tar.gz, .dmg, etc.
-
1Do you think there's any way that 7ZIP could work around that issue if a bug report was made? Commented Dec 31, 2019 at 3:42
-
1@Pikamander2 It would probably be possible, likely involve some sort of sorting and resolving of symlinks before packing, though attempting to do so may introduce another new set of problems altogether, as this is going beyond the scope of a compression program. Symlinks between the systems work vastly differently, as well as the file systems. There are also certain things that are possible to do in one system, and not in others (even just between Windows versions). It is likely this will break more than it will fix, and best to just leave it to the user to ensure correctness. Commented Jan 1, 2020 at 0:07