Error [IO Subsystem]: Invalid Access Mode

[toadmiller]

Greetings... We have some users who are not able to save modified files to our network share drive. We have been through the permissions on the share, not the issue. They can save fine to local drives. The error being issued is:

Error saving documents to: (path\filename)
Error [IO Subsystem]: Invalid Access Mode

Any ideas?

[Patrick-Tracker Supp]

Hello toadmiller,

Welcome to our forum!

This sounds like an issue we were having in a previous version, could you make sure that your users are running the latest build 5.5.309.0)? You will find the installers here: https://www.pdf-xchange.com/product/downloads

I hope this helps!

[ts.net]

Dear Support,

we have a similar issue.

Until last week it was possible to change pdf files in the outlook inbox (on exchange server) and save it directly. Then we installed windows updates and citrix update.

No we get the attached error.

We are using PDF XChange Viewer Version 2.5 (Build 214.2). Last updated in January 2015 (i´m quite sure about the date).

Any ideas for resolve the issue?

Thanks in advance,
Julius

[Will - Tracker Supp]

Hi Julius,

Thanks for the post - 214.2 is quite old, so please try using build 312.1, available here:
https://www.pdf-xchange.com/PDFXVwer.zip

If that doesn't help, then please try the Editor, as the Editor has replaced the Viewer and the Viewer is no longer supported:
https://www.pdf-xchange.com/PDFXVE5.zip

HTH!

[ts.net]

Thx!

When I start the update function of PDF X-Change:

...Setup has detected a previous installation of this product using an older style serial number - no longer valid for
this version....

It´s still possible to renew licence / renew maintenance for keys from 2009?

[Stefan - PDF-XChange]

Hello ts.net,

Yes you should be able to upgrade your Viewer license key to an Editor one with a discount. Just log in with your account on our website:
https://www.pdf-xchange.com/login
And click the "Upgrade Options" button.

Regards,
Stefan

[ts.net]

hello,

we now installed the version PDF-XChange Editor Version 5.5 (Build 321.1).

Still errors! See attachment.

Do you have an idea for resolve this issue?

Thanks,
Julius

[Will - Tracker Supp]

Hi Julius,

Thanks for getting back to us - could you run us through the exact steps taken that results in this error?

Cheers,

[ts.net]

Hello,

Working on a PDF file with more than 2 pages (scanned or by PDF Printer) in a e-mail in Outlook 2010 hosted by Exchange 2010 on a Server 2008 R2 Std.
-> the customers working on a Terminalserver with Server 2008 R2 Standard or Server 2012 R2 Standard (on both OS the issue exist)

Then on page is necessary to delete
-> to delete on page is ok

If you now want to save the changed PDF file appears the error (screenshot above)

[Will - Tracker Supp]

Hi Julius,

So you open the email attachment (PDF) directly (no Right Click --> Save), then edit the file and use the "Save" function?

If so, then I believe that this is happening because we are not provided direct access to the email attachment, but instead are provided a temporary copy, by Outlook, to view, edit, etc, so cannot make changes back to the file directly. I would need to confirm this with the Dev. Team, but this is my current suspicion.

I'll confirm this with the Dev. Team when they're in and will get back to you.

Cheers,

[ts.net]

Yes! We open the attachment directly. Without saving!
Till about 1 1/2 weeks ago works fine like this!

We are for an information after you spook with the Dev. Team.

Thanks!

[Will - Tracker Supp]

Hi Julius,

I've spoken with the Dev. Team on this and, as I had suspected, this isn't our issue, but seems to simply be a change in Outlook's behaviour. When a file is opened from an email attachment, in the Editor, we are simply sent the information on the file to work with and do not work with the actual attachment itself. Because of this, it is up to the email client to watch for any changes to the document and suck them back in to the attachment. It seems that they are not doing this and, instead, flag the PDF document as a Read Only, which is why you're receiving this error.

Cheers,