Hi,
I got such a message when added a slave site:
# Unable to create the symbolic link [administrator] ->
# Unable to create the symbolic link [components] ->
# Unable to create the symbolic link [includes] ->
# Unable to create the symbolic link [language] ->
# Unable to create the symbolic link [libraries] ->
# Unable to create the symbolic link [media] ->
# Unable to create the symbolic link [modules] ->
# Unable to create the symbolic link [plugins] ->
# Unable to create the symbolic link [xmlrpc] ->
# Unable to create the symbolic link [.htaccess] ->
# Unable to create the symbolic link [robots.txt] ->

Could you help me with this problem, please? Multisites on my master site indicates that the symbolic link is allowed on my server.

thanks in advance, Krzysztof

First question, can you specific with JMS version are you using.
Is it a JMS .1.2.0 RC4 ?
If not, perhaps you could retry with JMS 1.2.0 RC4.
See FAQ www.jms2win.com/faq#sec-122
for the procedure on how to get the latest version.

Otherwise, you have to check the permission of the directory where you want to create the symbolic link.
Something strange in your post, is that all the symbolic link does not have anything after the ->
Is is normal ? or have you remove the real link.

IF YOU OWN YOUR OWN SERVER, BE IT A VPS, OR DEDICATED, AND HAVE ACCESS TO THE ROOT, DO NOT FOLLOW THE TUTORIAL OR YOU WILL RECEIVE THE ERROR "UNABLE TO CREATE A SYMBOLIC LINK"

SOLUTION: ENTER YOUR WEBSITE HTTP://WWW.YOURSITE.COM/

NEXT GO DOWN AND PLACE THE SLAVE NAME IN LINE

YOURSITE

CHECK DEPLOY BOX

HIT SAVE AND VOILA! IT WORKS!!!

You just re-explained with other words many of the answers that I have posted to the permission issues.

When you are working as root this is normal that you have such kind of problem because you have used a user like "root" that does not allow a normal user to like "apaches" to access the files.

This just mean that you have not correctly configured your server like the hosting company are doing for you.

Normally you have to create users that are in the same group than apaches and have the permission on the file.

If you are working as root this just mean that you DO NOT autorise anybody to update your file and in particular "apaches".

The problem is just you have NOT correctly installed your joomla environment due to this "privileged" user (root).

You have just reported the most common error that an admniistrator of its own server is doing.
They are generally using root login to perform task and after they have may problem because they have not correctly instaleld their environment.

In summary, you have to create like the hosting company are doing a "normal" user that is compatible with apaches and that you are using to install the joomla environment and websites.
If you are using a "root" user, this is the kind of problems that you can encounter and also may have problem to install the patches.

Don't be surprised to receive error when apaches tries to access or modify files that you have protected with a root user.