Jan 17, 2009 11:18 AM|TheAgus|LINK
Thanks a lot for your replies.
It's a Windows 2003 server, 32 bits.
I have added those keys but the problem persists.
DWORD AllowRestrictedChars with a hex value of 1, located on the root of
DWORD VerificationCompatibility with a hex value of 1, located on the root of
Indeed, this issue doesn't affect the Cassini server.
I could replace the ampersand with the word and, but then I would have to check if a file exists with either the
ampersand or the and word. If both exists... conflict.
Anyway, I can come up with a way to rewrite the troublesome filenames, with an MD5 hash perhaps.
But do you know what characters, other than the ampersand, would trigger the error ?
Thanks for your support.