MS Word (Office 2008 - Mac) docs save, but won't re-open
Microsoft Word 2008 (Mac) "The document name or path is not valid. Try one or more of the following: *Check the path to make sure it was typed correctly.
I On the File menu, click Open. Serch for the file using this dialog box. (FileName2009_Client.doc)"
We've saved some revised documents to our server, and now we can't open them using expandrive at all.
I On the File menu, click Open. Serch for the file using this dialog box. (FileName2009_Client.doc)"
We've saved some revised documents to our server, and now we can't open them using expandrive at all.
3
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The best solution from the company
-
Lennart -
We've got a beta of ExpanDrive 2.0 currently in private testing that has a confirmed fix of this issue [but at the same time, it might have some other latent issues of its own that have yet to be uncovered].
Please email us at support@expandrive.com if you'd like to have access to the beta, and I think it'll solve your problem.
-Jeff
The company says
this solves the problem
-
Inappropriate?Also, this issue is consistent with 2 different Macs, and both are running the latest version of ExpanDrive.
-
Inappropriate?As of today, we can no longer save word docs with expanDrive without them becoming corrupted.
Still looking for the source of the issue. -
Inappropriate?I also got the "The document name or path is not valid", and in my case the copy on the server is not corrupted, but completely gone. Since I closed the document in Word with the intention of renaming and/or reopening it from the server, I have now completely lost it.
This might be the second time this has happened, unfortunately. I don’t recall seeing this error message from Word last time, but the document also vanished from the server.
Very bad.
-
Inappropriate?BBEdit is able to access the exact same documents when Word fails to even open them with the message below. I don’t know if it is an MS Word specific problem.
It’s also strange that I was able to open the document once, but then saving failed, as noted above, and now I can’t even open them anymore, even after reconnecting the drive.
Weird...
-
Inappropriate?I'm checking into this one, thanks for the report guys
-Jeff -
Inappropriate?We've recreated our "Normal" file for word on all our machines, checked all our word settings, made sure we have the latest versions of everything, removed some stray temporary (.hidden) files from the server. Saving locally and retrieving locally works fine.
We've lost a half-dozen documents to this and had to abandon use of the product (and our shared drive) until we can find a fix.
We're still looking for some pattern to help you (help us) track this down so we can squash it.
We've been enjoying expanDrive for months and now that we're hooked on it, its really painful no to be able to trust hitting the "save" button on documents.
My guess is that MS Office has changed the way the do some tiny little thing and that folks who don't update software monthly, haven't discovered it yet.
Thanks for looking into things Jeff. -
Inappropriate?I agree with PDXMan, this used to work.
I got really used to opening files directly from the server with Word, and regularly saving back with Cmd-S. This was never reliabe enough with other SSH file system solutions and ExpanDrive made this possible for the first time.
I don’t know if Word or ExpanDrive changed... -
Inappropriate?Can you help me trouble shoot this issue?
With MS Word for Mac (office 2008) I can't even save a new word document with ExpanDrive.
When I test with a .txt document, all is well (can save, open, make changes, re-save), so I'm guessing there is some strange issue with the way MS Office likes to save things.
Are there some settings I can check or something?
When ExpanDrive does "save" a document, they are forever corrupted afterwords. We've lost and had to recover about a dozen docs and spreadsheets before we put out a memo to staff to stop using ExpanDrive.
We would LOVE to get to the bottom of this and return to being able to relay on ExpanDrive again.
Can you help me resolve this? -
Inappropriate?We're looking into it - but it seems to be workign fine with our ExpanDrive 2.0 layer which goes into beta sometime in the next 5 days. Email us if you want to test it out earlier, we might be able to arrange this.
-
Inappropriate?Yes, yes! Please send me a beta, I'm happy to test it. You want me to email you, or can you look up my email here in the board?
-
Inappropriate?Hi Jeff! What happens next? Is there any progress? We have huge problems and we need a solution.
-
Inappropriate?Lennart -
We've got a beta of ExpanDrive 2.0 currently in private testing that has a confirmed fix of this issue [but at the same time, it might have some other latent issues of its own that have yet to be uncovered].
Please email us at support@expandrive.com if you'd like to have access to the beta, and I think it'll solve your problem.
-Jeff
The company says
this solves the problem
Loading Profile...




EMPLOYEE
