Cannot save to a network shared drive

[nis]

We have been using PDF X-changer now for about 2 years now. We started getting this error:

Error saving document to "\\server\folder\folder\name.pdf": Error [IO subsystem]: Invalid access mode.

We have a Windows 2003 SBS server and this happens using Windows XP Pro, Vista Business, and Windows 7 Pro client workstations.

We cannot save edited PDFs or use SAVE AS to the network drive. We can use SAVE AS COPY though. If we do want to save, either we use SAVE AS COPY or Save to local drive, then cut/paste onto network drive.

We have Sunbelt Vipre Enterprise as our AV solution. We do not have any local workstation firewalls enabled. We also tried upgrading PDF X-Change to latest version (version 2.5 build 195.0) as well with no luck.

Any suggestions?
Thanks so much!

[nis]

oh... follow up... I noticed that this problem happened before but I cannot seem to find a solution in the forum.

[Paul - PDF-XChange]

Hi nis,

well this is a tough one. I can verify that the Viewer has no problems saving to a Windows share - I do it all day every day. Have you mapped the share to a drive letter? That's how we do it here and I never see this issue.

It could be that there are access issues to the share or it could be the AV you mentioned. For us to investigate we would need to be able to reproduce the issue. Do you find that this is consistent and can you provide details on how we can reproduce it here? I can save without issue to both mapped and unmapped shares.

Does mapping the share make a difference?

[david hutton-squire]

I have just tested this on my Win 7 Home Premium system. It works fine when I save to my ReadyNAS box.

May I mention a precaution I always take when accessing my NAS after it has had time to go to sleep? Using Windows Explorer, I make sure the NAS is fully awake by browsing the contents before I try to save anything to it. Whether I am using Office, some image tool, photo utilities, whatever, I always make sure the NAS is awake before using the Save As dialogue to point to a NAS share.
This may not be strictly necessary, but I have found it just avoids odd hiccups in the Save As dialogue.

[John - Tracker Supp]

Excellent tip - thanks David

[TBA_Dave]

Hi

One of my users is having the same issue the pdf she is attemptting to save was created under adobe pro (thank god we are phasing that out) had a paged removed and a new one added in with PDF XChange and when she tries to save it to back to the share where the file is hosted. Saving locally how ever the file is fine.


so 2 questions

1) Is this strictly permissions related? The share is mapped and the user in question has modify permissions to all folders and files in that share.
2) Would the length of file path be an issue? does PDF Xchange have an issue with files paths over 128 characters?

Any help or advice on this issue would be welcome.

[Stefan - PDF-XChange]

Hello Dave,

I lean towards permissions and sleeping drives rather than the length of path names, but will discuss it with other guys in the team to check whether they have any further comments.

Best,
Stefan

[TBA_Dave]

Thanks Stefan.

[Paul - PDF-XChange]

Modify right should be enough. Is it possible to grant the user Full Control of the file/folder for a test?

[TBA_Dave]

I can do, but she's just gone home for the weekend

I'll try it on monday and let you know.

Have a nice weekend.

[Paul - PDF-XChange]

Great - post here the results and we'll follow through.

You enjoy your week end also.

regards

[heidl]

We're having a similar error, where a user cannot save a file with PDF-Xchange Pro on a network drive.
I'm suspecting the pathlength because our user is able to save to the root directory on the server without any problems.

Was there any resolution on this topic?

[Stefan - PDF-XChange]

Hello heidl,

Yes - file paths longer than 256 characters might be a bit problematic. We are already investigating a similar issue:
#2935: Editor 312.1: Files with paths longer than 256 characters fail to load from explorer.

And while the problem in the above ticket is with opening files, they are most likely related.
Can you please let us know what is the OS version on the machine on which the file is being manipulated? And how long is the path?
Are there any error messages shown or does it just fail silently to save the file?

Regards,
Stefan