Symlink script returned with an error

[comejv]

Symlink script returned with an error

[comejv]

Thank you ! Please tell me if you need any more info about my system or if you want me to run some tests.

[arnobpl]

Hi Côme, First of all, thank you for using Symlink Creator and reaching out to me about this issue. Could you tell me what is your file system of your destination path (`D:\`)? I suspect, your destination file system is not supported for symlink. If that is not the case, then I suspect, it is blocked by your computer's policy. You can check that by running the following command (needs admin rights): ``` fsutil behavior set symlinkevaluation /? ``` The output of the command shows if symlink creation permission is enabled for different cases (local-to-local, local-to-remote, remote-to-local, remote-to-remote). Let me know if it helps. Happy symlinking! :)

[comejv]

Hey ! Sorry didn't get the notification... Thank you for your answer. The D: Drive is an NTFS drive, just like the main C: drive. The fsutil command tells me that local to local and to remote symlinks are enabled by default.

[arnobpl]

I have reopened the issue. I will take a look to understand what might get wrong.

[arnobpl]

Welcome. One thing I would like to know about the exit code coming from the script. To do so:

1. In the application, tick "Retain script file after execution".
2. Add a source file and set a destination path. It could be anything. I just want to test why it never worked.
3. Click "Create symlinks" button and grant admin permission.
4. So it will fail in your system. Now go to the Symlink Creator application's path and find the script file, say SymlinkCreator_1234567890.cmd.
5. Copy SymlinkCreator_1234567890.cmd file to Downloads folder.
6. Right-click Start Button on Taskbar and click "Terminal (Admin)".
7. Now copy-paste the following command (and replace SymlinkCreator_1234567890.cmd with the actual script filename) in terminal, and click "Paste anyway" button in the warning dialog and press Enter:

cd .\Downloads
.\SymlinkCreator_1234567890.cmd
echo $LASTEXITCODE

8. Terminal will print a number at the end. Let me know what is the number. Is it just 1 or something else? Also, do you see any other error messages in the terminal?

Hope that will find something in your system. Then we can proceed further to solve the problem.

[comejv]

Ok that's weird, using the generated script worked...

But the app still doesn't. Any idea why ?

[arnobpl]

Thank you for helping me to resolve the Symlink Creator issue. Since the generated script executed successfully, my guess is now: Symlink Creator could not run the script by itself due to file path length limit while executing the script by a wrapper script (reference).

The solution to the problem is to disable file path length limit by following this Mircrosoft article: https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#enable-long-paths-in-windows-10-version-1607-and-later

Could you follow the command (to disable file path length limit) mentioned in the Mircrosoft article and then try creating symlinks with Symlink Creator again?

Let me know the result.

Happy Symlinking!

[arnobpl]

I have published Symlink Creator v1.2.6 that adds more error messages from caught exception. It might help to find the root cause of the issue you are facing with Symlink Creator.

Feel free to try the new version and check if more detailed error message is published from Symlink Creator, instead of the generic error message.

Happy Symlinking!

[comejv]

Tried, it, same non descriptive error ! But the generated script will be enough for my usage. Thank you for your answers.

[arnobpl]

Glad to know that the generated script is working fine. But I don't know why it does not work directly with Symlink Creator itself, even no descriptive error message even after update. So the error occurred somewhere else. Anyway, I am closing this issue since there is no action item for me now.

Happy Symlinking!

[maomaochong199]

遇到了同样的报错，非常奇怪，当我在压缩包里直接运行程序则不会报错，解压后运行反而会报错。版本1.2.5 1.2.6 1.2.7 都存在相同问题 @comejv @arnobpl