No responses... (no surprise).
Just went through a couple Windows tech sites and did not find a match for the error.
Definately an Adobe glitch.
I am still at it. Uninstalled everything Adobe, manually cleared the registry of all traces of adobe and acrobat. Reinstalled Reader (8.1.1) and still no joy.
Do you have Content Advisor turned on?
No content advisor.
I think it is aa Adobe permissions issue. Still working.
Making some headway. I have noticed that when I double click on the file it tries to open from
"c:\documents and settings\xxxx\https:\yyyy.com\webdav..."
now I could just figure out why....
That could be a malware problem with your computer. Looks like somthing might have tried hijack your documents link?
Try run ad-aware a anti-malware tool by lavasoft
I experience the same problem here. I can open WebDAV documents via the file open dialogue, though.
I could confirm the error that Adobe Reader tries to open
%USERPROFILE%<path_to_document> instead of <path_to_document>.
I have reported the bug, keep your fingers crossed.
No malware, no virus, all clean.
Markus, it sounds like the same thing. I can go through File/Open as well with success, just not by double clicking.
but it doesn't do that for everyone. Something isn't right about your system. Just don't know what it is yet.
And it only does it on one computer. But it does only happen with just *.pdf files. Everything else works as it should.
I still do not know what it is either.
I am facing the same problem"There was an error opening this document. The filename, directory name, or volume label syntax",have tried to uninstalled adobe reader(8.1.1) and reintalled(7.1).unfortunatly still appearing the same error message. I can't even open it via "File-open'.
can experts kindly provide a solution.
Unfortunately, version 8.1.2 does
fix the problem :-(
I'm still stuck with the same error. Adobe screwed with some permissons in Windows - that I was able to get out of Adobe tech support, any more costs money.
Hello, everyone! I am a new user here, but by no means a new user to the problem we're discussing. I work at a University here in the Midwest.
Has anyone looked into the possibility that a patch that Microsoft released on Patch Tuesday in November '07 might've caused this? In particular, I'm referring to KB943460 which refers to a security vulnerability in Shell32.dll.
I've done quite a bit of testing on this issue, using the SysInternals program Process Monitor. Adobe Acrobat Reader is doing exactly what eveyrone is talking about - tacking the logged-on user's default "home directory" onto the front of the requested WebDAV URL.
I consider it quite likely that 943460, perhaps in concert with whatever Adobe has done, might have caused, though I don't have any facts to back the statement up.
I've tried uninstalling 943460 which didn't get me anywhere.
However, I also have started fresh with a "fresh" XP install and Acrobat Reader 8.1.2. I patched the machine up to November '07 - I could still read PDF files via WebDAV. However, after I patched with 943460, I STILL could read PDF files via WebDAV, so that broke my theory about 943460.
Has anyone else done extensive testing, with different results?
No joy as of yet. I deal with this fluke when I have time, Adobe is of no help. I searched technet but did not find anything relevant. I thought someone would have posted an answer by now. Adobe says thay have the answer, but it'll cost ya.
I am not sure Adobe has the answer. We put up a credit card and spent 2 hours on the phone with Adobe on this very issue. After mindless Adobe config setting changes nothing new and no intelligent answers. Adobe conclusion, must be a Microsoft problem, but no charge.
Does anyone have an update on this issue?
Good morning, everyone!
I've done quite a bit of additional testing and I think I've narrowed this down to Microsoft update KB907306, which is the May 18,2007 WebDAV update. This update supersedes KB892211 from 2005, which was also a WebDAV patch.
On my test machine, I installed a clean Windows XP Pro (SP2), followed by roughly 87 Windows updates, including IE7. Prior to installing the patches, including IE7, I installed Acrobat Reader 8.0.0, logged on to my WebDAV site, tried opening a file, and was able to. Then, I installed the 87 patches, including IE7, rebooted, and tested again. This time, when I attempted to open my WebDAV site in IE7, as I had in IE6, the My Computer window opened. This, as you know, is a standard behavior in IE7 - it doesn't handle WebDAV URLs correctly. So, the fix is to install Microsoft's WebDAV patch. Prior to May 2007, you'd get 892211, but since then, 907306 has replaced 892211.
My test was to install 892211, which I had a copy of, and test as I had done before. I could open my WebDAV URL correctly in IE7 and open Acrobat files with no issue. However, when I installed the KB907306 patch, this is when the trouble began. Following installation of KB907306, which is associated with Office 2007 (and possibly O 2003), the behavior we're talking about appears.
Much testing has been done to try to uninstall 907306 and re-install 892211 on affected machines, but no reliable method has been demonstrated to this point.
The 907306 uninstaller does NOT remove the updated WebDAV files correctly, nor does it make the correct modifications to the Registry.
Has anyone done anything similar? Found out anything different?
All I know is that it must be something odd. I have a couple computers and only one of them is acting up. I have been through technet and have not seen anything related.
I am still stumped and dealing with it.
The error is received on several computers nearby that are running Windows XP. Problem does not occur on Windows Vista machines.
What I do to get the error on my side is open a PDF document that is located in SharePoint 2007 or either open a PDF document that is located in a web folder (WebDAV). It works just fine opening the PDF else way (excluding file > open).
I'm stumped and have ran out of solutions. George Blessing I appreciate your research. If you have any further information keep us updated.
Good morning, everyone!
I haven't had time to devote any more research to this issue, as I am at a stalemate for the time-being. I know what patch causes this issue, but haven't been able to come up with a reliable, reproducible fix. And, to my knowledge, I haven't see anything further from either Microsoft or Adobe.
I can confirm mgg99's observation regarding Vista. The problem does NOT occur on Vista and never has - only Windows XP. As a side note, though, Vista does require a patch to make WebDAV work correctly, though this doesn't appear to have any connection to our Adobe issue.
I'm watching this month's Patch Tuesday information closely because the "overview" indicated that ALL of the patches would be Office-related. Perhaps there's a WebDAV patch update that will fix this issue!
It seems like there are more knowledgeable people here than myself. So (out of curiosity) would not it make sence to figure out where webdav, windows, or adobe is pulling the path of
"c:\documents and settings\xxxx\https:\yyyy.com\webdav..."
(where xxxx is the user name)
and edit out the first part?
I had the same problem this morning and I can tell you how I solved it or what I think is the problem:
Here we had a pdf document with a german "Ö", it means a special german letter and tried to open it on an english installation of XP with english Adobe Reader (chinese language pack). Then I received this Error Message. After renaming it and replaced the german 'ö' to a normal english 'oe' in the filename it worked out well!
So give it a try: Rename the document to whatever you like (test.pdf) and try it again!
Hope this will help!
Thanks for the suggestion, but this is not an issue of filename and language conflicts, at least in my environment. I highly doubt that's the root cause of this issue.
The PDF files in my tests have all had very simple names, such as 123.pdf and test.pdf, as well as more complicated names with spaces in them. Nothing about the files contains anything outside of the English language, including the content and filenames.
From everything I've been able to determine, this is a WebDAV-related security issue that affects programs like Acrobat Reader. I know for a fact that MS's KB892211 WebDAV patch doesn't create the issue, however MS's update to that 892211 patch DOES create the issue. As I've outlined earlier in this thread, my extensive testing has proven this more than once.
At this point, I haven't been able to accurately uninstall the update to 892211 after the update has been installed. And, as far as I can tell, the update to 892211 comes down from MS as a Office and/or Windows Update component. So, everyone has it, the uninstaller doesn't work, and there's no documentation detailing what registry entries are being changed when the update to 892211 is installed.
My ultimate goal is to bring a test machine to the point just before the update to 892211 goes on, fire up the Registry, Process, and File monitors on my test box, and install the 892211 update. This should give me an accurate picture of what I need to restore in order to rid the machine of the update to 892211.
Until Microsoft officially fixes the issue, I am not totally sure how this will be resolved. I've ceased my work on the issue for now since copying the PDF file from the WebDAV share to the user's desktop gets the user what they wanted in the first place - the ability to open the PDF file!
Maybe, once some other projects slow down a bit, I might get back to creating a solution, but it's going to be a "hack" no matter which way you slice it. I'd much rather MS spend their time creating the solution. If I have to do it, my fee to MS will be quite HIGH! :*)
I'm still struggling, and the temporary work around is getting to be a bother. For the time being I am trying to use my backup computer when I am dealing with WebDav.
George, come up with the fix and send MS the invoice, I am sure they can afford it.
My Possible Solution:
My boss was having trouble opening 2 of a group of 5 or so adobe files with reader 8.x with this exact message. They had chinese characters in the file, as well as in the name.
I could open the files from my computer however, so i simply went to "save as copy" for each of them adding a number 2 at the end of file (ie, productline2.pdf).
Both appear to open up fine now from his computer.
Well thanks for the input, but I know my files are simply named (file.pdf) and I created them so they should not have anything funny inside.
I think someone else here tried that already as well.
I suspect it is the invalid characters (second colon, german or chinese characters) in the file path, not the filename. At least that seems to be my problem. I don't have a solution (other then renaming paths).
"c:\documents and settings\xxxx\https:\yyyy.com\webdav\index.php\\zzz\file.pdf"
Where xxxx is the Windows user name and
yyyy is the website name and
zzz is the username
No special charatecters in there.
It seems as though it is picking up the first half (up to the https) and does not need to be doing so.
I'm still stumped.
I agree SLawson.
Today I found a third-party application that works. It opens PDFs with no problem.
It uses a network drive rather than what we're using...a web folder.
It's even better than using WebFolders (WebDAV) because it allows to create TXT files, word docs by simply right-clicking in the empty white space where as us web folders only allows folder creation thru the right-click prompt.
The problem is: It is not suitable solution because $800 is pretty steep. The trial works excellent > http://www.webdrive.com/products/webdrive/index.html
So you may want to use that route.
So then I became to think more ---- instead of using web folders let's use a network drive. In my case, it doesn't work because my site is secure and in XP I am unable to map a network drive to a secure web site that is using SharePoint.
I still am investigating to map a network drive to a secure site that requires authentication so PDFs can be opened in an explorer view.
Microsoft has released a hot fix KB943337 that resolves my problems (consistent with what has been reported here) with webdav and PDFs. You must request this fix it is not readily downloadable. Although this article talks to Office 2007 it has cleared up my problems with XP and Office 2003.
I hope this helps some of you, as this has been a very frustrating and time consuming resolution.
Winner winner - chicken dinner...
I installed the patch and then realized I needed something else installed (per MS's site). I never did do the previous install or even look to see if it was installed, but I did get this patch and it is working.
Wow, J O'Connell! You definitely receive the GOLD STAR for this find!
I, too, have tested the installation of the patch on machines that have the 907306 WebDAV patch and the PDF functionality has been restored!
I am hoping that Microsoft will make this patch generally-available rather than keeping it as a "non-public" patch. From everything I've read and the past research I did, I can't see where having these two patches distributed via Microsoft Update would cause any negative side effects. If you use Acrobat Reader with WebDAV, you're good to go. If you don't, no big deal!
Thanks to all for the knowledge sharing! Good work!
Awesome find J. O'Connell. Our company (Daptiv), which is a SaaS provider, had implemented WebDav, but we couldn't figure out why some users could download PDF files within their browser and why others were receiving the infamous error that many people reported above since about June 2007. The issue seemed to be isolated to users who had Windows XP and Office 2007 installed. I requested the patch you referenced and now everyone is happy and I am a hero.
The only problem that some of our users are experiencing is that they are unable to download and open PDF files that are larger than about 25k. The browser window opens and they can see the download status in the lower left hand corner of the browser, but it stalls at various times during the download. It is only happening for a couple customers that we know of, that are each behind their company's firewalls. The users try to download the files at home and have no issues. They are not having problems with any other file type, just PDFs. From troubleshooting with them, I have determined that it is not determined by either browser version (IE6 & IE7) or Adobe Reader Version (v7 & v8). Does anyone have an idea what network, browser or other setting could be causing this issue?
I had similar problem. Here is how I solved it.
I deleted all the temporary files in the folder (C:\Documents and Settings\[user profile]\Local Settings\Temp). The number of files was 65000+, but was occupied only 4mb. Then the acrobat opened properly.
For more solutions:
Hope this helps.
I came across the problem when opening a particular PDF file this morning--I did a google search and then I am here.
Just found out the cause of my problem. I was opening a file that has a filename containing Chinese characters (I am Chinese :-)). Now the problem is gone with the file renamed.
I guess this problem might happen on files with a filename in other non-English languages as well.
here 's the easiest way and it worked pretty well with me
if u have an gmail account u just compose a message containing the file that u cant open to ur self (ur g-mail account) then open the message and click on view and voila
i wish it work with u guys
We are running windows Vista for us saving the file and renaming it worked.
Thanks for the advice
I discovered another source for this problem is a mixed MAC / PC environment where the MAC users have placed a non-standard character in a directory name.
As Windows/Adobe traverses the path it fails on the invalid directory name.
Using Windows Explorer I could see the Boxes representing unprintable characters, I simply renamed the problem directory and all worked perfectly.