Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 697
  • Last Modified:

UNC Paths with "#" Character Fail - Outlook 2010 on XP

Shows adding the file and then trying to test opening it on the same machine. File is show on the desktopInteresting Problem.

This only occurs on systems running Outlook 2010 and Windows XP. This occurs on users receiving an email containing a local UNC path / shortcut in the email and that file on the UNC path contains a "#" symbol.  

example:

Actual file name:

\\server\share\folder\folder2\xyzfilename # 2013.doc

The email is created using any version of outlook on another computer, they drag the file into the email with the 2nd mouse button using the 'create hyperlink here' feature. It creates the UNC shortcut, but strips the "#" from the visual text, and replace it with a "-" symbol.  However, when you mouse over the UNC path it does show the proper path name containing the #.  (Yes, testing the path with CTRL + Click after creation causes the same problem)

You send it on to the recipient (who is using XP and Outlook 2010), who also sees the file name missing the # symbol.  The recipient can also mouse over the UNC link and see the # in the file name, and the file name looks correct.  However, when you attempt to click on it you receive the following error.

"Cannot find file \\server\share\folder\folder2\xyzfilename"

It strips off anything past the # symbol, in the example above the "# 2013.doc" part.

This behavior is easy to replicate providing you are on Windows XP and Outlook 2010.

I have confirmed this doesn't occur with Windows XP on Outlook 2007 or Windows 7 with Outlook 2010.  Only Windows XP with Outlook 2010.

Ideas short of upgrading users? I can remove the "#' symbol from all files.

Screen Shot Info:  Showing the file itself on desktop, the short cut it created, and the mouse over info.  Image 2 shows the error that pops up if you try to then test the link created using CTRL and click.  It would also fail to the receiver providing they too are using Outlook 2010 and XP.  If the recipient is on Windows 7 and Office 2010, the received link WILL work.
0
MountainTechGuy
Asked:
MountainTechGuy
1 Solution
 
diogo_fmCommented:
Hi mountainTechGuy,
There's a MS hotfix that may solve your problem if the # is not the last character of the UNC path.

http://support.microsoft.com/kb/2596485

Hope this helps!
Cheers
0
 
MountainTechGuyAuthor Commented:
Perfect!  this is the solution. There is a 64bit and 32bit version of the hotfix. The hotfix is for Outlook 2010 specifically.  All solved! thnaks wise one!
0

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

Tackle projects and never again get stuck behind a technical roadblock.
Join Now