I think I have found the issue and it is related to service name
S:\ Disk Usage
the characters
:\
; so I guess when the url is parsed, the system will process this as escape character which will break the service name. Because of this, there is no matching service name, and the system cannot take appropriate actions.
I guess, some JavaScript validation for service names should get around this problem.
Hmmm, Have you verified this with all of the services that were having problems?
I am thinking that what may be happening is that by changing the service description the system is just forcing the file to be written to a different location.
It might for some reason have been a file permissions problem.
I have exhausted all the possible options, it is not a permission issue. It definitely has something to do with the way the link is parsed even it is in quotes. It is very strange behavior.
Actually, we were able to reproduce it. It is a bug and we will be fixing it as soon as we can. I filed a bug report on our bug tracker. You can view it here.
Be sure to check out our Knowledgebase for helpful articles and solutions!