Yarpserver results in Access Denied

[dariosortino]

Hello!
After having enabled the ICUB_HEAD module of the superbuild I encountered a weird behavior when I launch yarpserver (I'm on Windows)

Talking with @traversaro it seems that is an OS-related problem, so he suggested me to trace the events that are happening in the OS. I used the Process Monitor to see that in fact the Access Denied is from yarpserver.

Any hints on what it could be?

[traversaro]

It seems that yarpserver does not even start, cmd.exe returns the error even before starting yarpserver.exe . Can you try to delete the file and install again the superbuild (no need to recompiled everything by deleting the build, just reinstalling on the existing build is probably enough).

[dariosortino]

Unfortunately, removing yarpserver.exe and installing again didn't solve the problem.

[traversaro]

Interesting. What is the output of:

type C:\Users\dsortino\Desktop\GithubProj\robotology-superbuild\build\install\bin\yarpserver.exe

?

Note that if yarpserver does not work, you can try to use yarp server, with a space between yarp and server.

[dariosortino]

This is the output

Surprisingly enough, with yarp server everything seems running fine

[traversaro]

This is the output

Surprisingly enough, with yarp server everything seems running fine

Great, so at least you are able to test what you needed to do by running yarpserver? I have a theory that the problem is related to the length of the path. Can you try to copy C:\Users\dsortino\Desktop\GithubProj\robotology-superbuild\build\install to C:\robsubinstall and try to use that (i.e. changing the setup.bat that you invoke to the one in C:\robsubinstall\share\robotology-superbuild\setup.bat)?

[pattacini]

Any update about that @dariosortino?

[dariosortino]

yarpserver started working fine out of nowhere

[PeterBowman]

Since the "access denied" event originated in the file system during a "CreateFile" operation (see attached screenshots above), I was wondering whether YARP, due to --write, was trying to create a configuration file (yarp.conf) and failed in the process, perhaps due to a lack of permissions in the default location.