All,
I seem to be stuck here. I can't uninstall, repair or modify my installation of NetAdvantage. I was trying to modify my existing 11.2 version because a team-mate realized we had different DLL versions based on the same install. I can do anything. I even tried installing the latest version of the tools but I get the same message.
If I try to uninstall via the Windows control panel I get the same message. I am in a corporate environment and my "My Documents" folder is mapped to a network drive. Any advice?
Kevin
Hello Kevin,
Can you paste/attach a log file that shows the actual exception?
Also can you attach the log file of the installer itself?
This will allow us to see what the actual reason for such behavior may be.
Thank you.
Alex,
Thanks. I have attached the log file. Let me know if you need anything else.
I believe you are experiencing the same kind of issue that is described in this Microsoft forum thread http://social.technet.microsoft.com/Forums/windows/en-US/7ef1e664-7dfa-4ac9-ac48-9ff41717f8f4/error-1324-the-folder-path-my-pictures-contains-an-invalid-character. In their case, it was the "My Pictures" folder that was mapped to a network drive and giving the same "Error 1324" that your log shows. They list a couple of workarounds for this kind of issue.
1) Map a drive to your "My Documents" folder and change the registry key to use that mapped drive. The key is at HKEY_CURRENT_USER \ Software \ Microsoft \ Windows \ CurrentVersion \ Explorer \ User Shell Folders. Your "My Documents" folder should be listed in the "Personal" registry value. After that is done, the installer should be able to resolve the path. If you go this route, be sure to back up your registry so you can roll back as needed.
2) For some, the "invalid character" error was thrown because it couldn't read the directory and was actually a permission issue. Users had full access to "\\servername\home\username\" but did not have access to "\\servername\home". Once they received Read permissions on that folder, the error stopped for them. At the end of the forum thread, it is mentioned that all users needed was the ability to "Read Attributes" on the home folder. That was enough to stop the error in their case, but still not give everyone permission to list the directory or search or run files from that home directory.
I hope this helps resolve your issue.