Skip to main content
New Participant
August 6, 2019
Answered

Can only open 1 PDF at a time from DFS server

  • August 6, 2019
  • 16 replies
  • 30685 views

Hi all,

I recently moved files over to a server which is using DFS and can only open one PDF at a time unless I turn off Sandbox Protection. This is happening to everyone and I've narrowed it down to be an issue with Adobe Reader and DFS. That being said:

Is Sandbox Protection worth having on?

Has anyone else had this issue and were you able to resolve it?

Thanks

    This topic has been closed for replies.
    Correct answer GGbce

    Just upgraded to version: 2021.001.20135 and the issue seems to be resolved !

     

    Can you try?

     

    Maybe a regression bug caused it to re-appear?


    Like I told in august 2020, this issue was fiex since version 20.012.20041. I upgraded many time through 20.013.20074 than this latest version in 2021 and still working fine !

     

    Someone could edit the initial post to say "RESOLVED".

    16 replies

    Meenakshi Negi
    Community Manager
    Community Manager
    August 14, 2020

    Hi All,

     

    Thank you for confirming that the issue is resolved with the Acrobat and Reader August 2020 update version.

     

    To check the latest version for the application, please refer to the release notes here: https://helpx.adobe.com/acrobat/release-note/release-notes-acrobat-reader.html

    And to know about what new features added with this version, you may check them here: https://helpx.adobe.com/acrobat/using/whats-new.html

     

    Hope the information helps.

    Let us know if you have any questions.

     

    Thanks,

    Meenakshi

    New Participant
    October 26, 2020

    I can NOT confirm that this issue is fixed.
    Environment:
    Windows Server 2019 running as RDS host ("Terminal Server")
    Adobe Acrobat Pro 2020 Release (Classic) Version 2020.001.30005
    Adobe Acrobat Reader 2020 Release Version 2020.001.30005
    Both versions are "up to date" as of writing this post.
    DFS shares are mapped as network drives.
    Unless "Protected Mode" is disabled, users are not able to open more than one PDF at a time by double-clicking on it in Windows Explorer.
    Manually opening more than one file in the application itself works (and has always worked).

    New Participant
    February 10, 2021

    Issue is not resolved.

     

    We are running on Mapped Drive with DFS Shares.

    We can only open one file and Protected Mode is on (do not wish to disable it).

     

    Acrobat Reader DC 2020.009.20063

    Windows 10 x64 Client

    DFS and File Servers: Windows Server 2019

    New Participant
    August 13, 2020

    Today I noticed that Adobe updated the icon for Reader DC so I randomly gave it another try and it seems like this problem was fixed. I can open multiple PDFs on a DFS network share via double clicking (version 2020.012.20041).

     

    Environment:

    • Windows Server 2019 DFS share
    • Windows 10 Pro 2004 client

     

    Enabled security settings:

    • Enable Protected Mode at startup
    • Protected View: Files from potentially unsafe locations
    ls_rbls
    Community Expert
    August 13, 2020

    Amen to that!

    GGbce
    Participating Frequently
    July 16, 2020

    Hi,

     

    Just to keep this post up-to-date, I newer version of Adobe Acrobat and Adobe Reader DC was released on July 6th (20.009.20074) and June 2nd (20.009.20067) with some fixes related to the "sandbox" when protect mode is enabled. But nothing about this specific issue seem to be fixed.

     

    If I take a look to the "Known issues" list, nothing was added for this issue also... But a similar problem was added: Problem with "sandbox" and access denied  error when opening PDF from a symbolic link UNC path. May be Adobe work more on some things around "sandbox" issues in the last months.

     

    I tested, the newest version but unfortunately the problem still there.

     

    ls_rbls did you found a job in cybersecurity laywer ? (Joke)

     

     

    New Participant
    June 1, 2020

    Not OP, but i just moved our company shares from a 2012R2 DFS share to 2019 DFS share overnight and this issue popped up. Our clients are running windows 1909 and adobe latest 20.009.20065 and i can confirm the same issue is still occuring. It can be "bypassed" by turning off "Protected Mode at startup" but this is not something we are willing to disable.

    New Participant
    July 9, 2020

    Still no resolution to this?

     

    Can someone from Adobe please update us on what is happening with a solution to this. It seems crazy that Acrobat can't work with Server 2019 DFS shares - The current MS server operating system that has been out for almost two years!?

    ls_rbls
    Community Expert
    July 9, 2020

    There has been no fix to this phenomena since 2012, and there is no fix now.

     

    Good luck with your wishes.

     

    Amal.
    Community Manager
    Community Manager
    May 20, 2020

    Hi there

     

    A new version of Adobe Acrobat/Reader DC is now available v20.009.20063. Please update the application to the new version and see if that works. Go to Help > Check for Updates.

     

    Let us know how it goes

     

    Regards

    Amal

    New Participant
    May 21, 2020

    Confirmed that this is still broken with v20.009.20063.

    Barnett Waddingham
    New Participant
    May 11, 2020

    Clients with Windows 10 1809 or more (or Win2019) trying to access a PDF via a DFS that is stored on a Windows server 2019 server are not able to open more than 1 pdf.

    Bernd Alheit
    Community Expert
    May 11, 2020

    Try this:

    disable the protection mode in Acrobat Reader.

    Barnett Waddingham
    New Participant
    May 11, 2020

    That does help, but we don't want to disable protection mode as you then lose the security.

    https://helpx.adobe.com/reader/using/protected-mode-windows.html

    Is there any plans to get this fixed properly?

    Amal.
    Community Manager
    Community Manager
    April 16, 2020

    Hi All,

     

    We're sorry for the trouble and the experience you had with this ongoing issue,

     

    Please collect the process monitor logs for the affected machines on which you are not able to open the multiple PDF files by double click so that we can investigate further?

     

    Download the Process Monitor tool Process Monitor - Windows Sysinternals | Microsoft Docs

    Open and run it, reproduce the issue at your end, save the log files, and share it with us.

     

    Upload the log files in Document Cloud (https://documentcloud.adobe.com/link/home/), generate the link and share the link with us.

     

    Regards

    Amal

    New Participant
    May 7, 2020

    Hello Amal,
    thanks for the answer.

     

    Test conditions
    The PDFs 1st.pdf and 2nd.pdf are opened one after the other on a Windows file server from a client in Windows Explorer with a double click.
    the test client with which the PDFs are opened is a Windows 10 Enterprise Version 1809
    in the first test case on a Windows 2019 file server with DFS
    in the second test case on a Windows 2019 file server without DFS
    in the third test case on a Windows 2012 R2 file server with DFS


    capture file for first case
    2019dfs.PML
    Result 2nd PDF does not open

     

    capture file for second case
    2019nodfs.PML
    Result 2nd PDF opens

     

    capture file for third case
    2012dfs.PML
    Result 2nd PDF opens

     

    PML Files are packet in pdftests.zip
    Link for file:
    https://documentcloud.adobe.com/link/track?uri=urn%3Aaaid%3Ascds%3AUS%3A1a5c1391-7460-425a-b3cb-ce47b872dd2c

     

    Kind regards

    Amal.
    Community Manager
    Community Manager
    May 8, 2020

    Hi All

     

    Thank you for sharing the information. We have shared the logs with the engineering team for further investigation.

     

    We will share the update once we hear anything from them.

     

    Regards

    Amal

    April 14, 2020

    This problem occurs under following circumstances:

    Document is on Fileshare on a MS Server 2019 and is accessed through a DFS.

    Acrobat Reader DC can open one document. More documents can not be opened. By double click a next document, nothing happens.

    This problem don’t occur, when Fileshare is not accessed through a DFS.

    This problem don’t occur, when Fileshare is on a MS Server 2016.

    This problem don’t occur, when you open a previous opened documents (listed on the Start Tab).

    It is version independent. I tested it with DC 2015, 2019 and 2020: same behavior.

    I think, the problem is, hoe the path of the document is passed to Reader DC.

     

    Regards, Peter

    GGbce
    Participating Frequently
    April 15, 2020

    Hi,

     

    Like JPS-Wien tell, it's not exactly true.

     

    We observed this problem happen from a computer running Windows 10 (1809) or higner, Windows  10 LTSC 2019 (where it's the same build code like Windows 10 (1809)) and Windows server 2019 + Adobe Reader DC (seem to be all versions of DC).. This is where the action is started (where the user have a session).

     

    The other end (DFS server) can be any version of Windows Server. We have many DFS shares in our enterprise running under Windows Server 2008 R2, Windows Server 2012 R2, Windows Server 2016 and Windows Server 2019... where one "DFS cluster/farm"  always use the same Windows Server version (Ex.: If three DFS server in a specific context, those are with the same Windows Server version to ensure compatibility).

     

    Then, in all cases, when a PDF is located on a DFS share and the client side use Win10 (1809) or newer or WS2019, we are not able to open more than 1 PDF... when a double-click method is used in the Windows Explorer.

     

    But the drag & drop from Windows  Explorer to Adobe Reader  Dc window work... But not very userful method and hard to explain in many case to end-users to change a basic method onyl for one application... Where is not normal.

    February 5, 2020

    Nice to see there are still DFS issues after a decade of reports. Especially since so many organisations are upgrading to Win2019 with DFS serving Win10 clients now that Win2008r2 is out of support. Thank goodness Edge and Chrome have their own renderers. Time to look seriously at other products.

    New Participant
    April 6, 2020

    I cant believe this is STILL not being fixed. Maybe Adobe doesn't want their software used in companies anymore.

    Hopefully the browsers will "solve" this issue so we can get rid of this.

    ls_rbls
    Community Expert
    April 6, 2020

    Can anyone who has macOS and who participates in a Windows server DFS can check this guidance https://support.apple.com/guide/directory-utility/distributed-file-system-namespace-support-ior598b5f4f9/mac 

     

    And see if opening PDFs in Acrobat from a macOS client shows the same behavior?

     

    What I'm trying to figure out is that macOS supports 64bit version of Acrobat. Acrobat for Ms Windos doesn't. It is still a 32 bit application that has been tested to run in 64bit versions of MS Windows.

     

    Let's say that you have an Apple client in that network, with the exact same Preferences settings in Adobe Acrobat and Reader. This include starting in Protected Mode, sandbox protection enabled in Security Enhanced, and Trust Manager settings, etc.

     

     

    I suspect, that if a mac user can access PDFs in Active Directory domains without disabling these protections in Acrobat/Reader, then we're definitely looking at a compatibility issue on how Acrobat enforces the 32bit Protected View on 64bit operating systems.

     

    Would this make sense?

     

    Someone please share some feedback.

     

    ls_rbls
    Community Expert
    January 22, 2020

    Hi,

     

    I am going to post here the same info that I shared in a similar thread.

     

    After much reading, I thinks the following references might be useful.

     

    It seems like the DFS is preventing access to the  namespace when a client tries to hit a folder target with Acrobat in protected mode .

     

    Verify if when  you add the absolute path for a priviledged location ,   

    that the  namespace is not configured to issue referrals with the "insite" option.

     

    See here  for troubleshooting: https://support.microsoft.com/en-us/help/975440/how-to-troubleshoot-distributed-file-system-namespace-access-failures 

     

    Enable the cross domain troubleshooting log  in Reader / Acrobat and confirm if the messages that you get are not suggesting to "allow any" type of access which is the least restricted access policy, which would also defeat the purpose of using Enhanced Security and  Protected Mode .

     

    See here too: https://www.adobe.com/devnet-docs/acrobatetk/tools/AppSec/xdomain.html#policy-file-configuration  

     

    See here : https://helpx.adobe.com/acrobat/using/enhanced-security-setting-pdfs.html#bypass_enhanced_security_restrictions 

     

    Since this seems to be not entirely related to Adobe Reader/Acrobat, there are a few more things that need to  be observed:

     

     

     

    I hope these references help.

     

     

    GGbce
    Participating Frequently
    January 28, 2020

    Hi, I would like to inform people that we have the same problem in our enteprise since many months. For Adobe Support, we can easly reproduce the problem on your side following this procedure:

     

    1. Just have a shared folder on your local network in Microsoft DFS mode. To validate if you network share is in DFS mode, when you right-click on folder properties you can see "DFS" tab.

     

    2. Put 2 PDF files on this share.

    3. Try to open one PDF.

    4. Let Adobe Reader DC opened with your actual PDF file

    5. Double-click on the second PDF file to open it... 

    6. Normally, this second file should be opened in a new tab inside Adode Reader DC... But those files are located on a DFS share nothing happen !!!

     

    Other tests that you can do to confirm this issue happen only in this context:

     

    A. Reproduce the same steps, but copy 2 PDF files on local hard drive. Result: The second PDf file open in a new tab correctly.

    B. Reproduce the same steps, but copy 2 PDF files on a "regular" SMB/CIFS/Windows share. Result: The second PDF file open in a new tab correctly.

    C. Go to Edit -> Preferences... menu. Go to Protection (Enforced) category, uncheck "Enable protected mode at startup". Close Adobe Reader, then reproduce the same steps on a DFS share. Result: The second PDf file open in a new tab correctly.

     

    Then, it's easy to confirm this issue happen with Adobe Reader DC when"default security" is activated for sandbox mode. I tested to open multiples PDF file using a non-Adobe application and it work fine.

     

    I tested to add UNC share in the privileged locations, but no changes. This option not seem to have a link with sandbox... And also not support UNC with star like \\*.mydomain.com\ only URL like *.mydomain.com... (in other context it could be an improvement.)

     

    Tested on many computers:

    Microsoft Windows 10 (1809 or 1903)

    Adobe Reader DC (2019.010.20098, 2019.010.20064, 2019.012.20040, 2019.021.20061, ...)

    The issue happen on all these versions combined... 

     

     

    ls_rbls
    Community Expert
    January 29, 2020

    Hey this is awesome. Thanks for sharing this info.

     

    I am actually trying to help a Windows 10 Enterprise user with a different issue.

     

    He is trying to enforce disablement of Adobe Acrobat automatic updates using Group Policy in an Active Directory domain.

     

    Long story short, I found a very interesting detail that  is not well documented in the Adobe Acrobat Preferences Reference guide, unless you combine this reference with the Adobe Acrobat Customization Wizard Reference Guide, and the Enterprise Toolkit.

     

    My angle is, that a few things have changed in Windows Servers since the 2008R2 version.

     

    For starters, Microsoft support for 2008 Server reached its EOL a few days ago this month.

     

    So now we are left with 2012, 2012R2, 2016 and latest to experiment with. 

     

    A note on that however, some Windows Server 2012 users have expressed that they don't seem to have this issue with the 2012 Server versions and earlier.

     

    And I read somewhere that in 2016 version and later,  that the opening of a second file that resides in the same file share location triggers the enforcement of Windows Protected View a little tighter than prior versions. 

     

    So it seems like this issue could be related to how the files that are shared in Priviledged locations is handled with Protected View enforcement in windows explorer and Internet Explorer respectively; then it conflicts when Protected Mode and Security Ehnaced (sandboxing) settings are enforced in  the Acrobat/Reader applications.

     

    For network administrators:  the ability to edit or modify Protected View settings is, or could be, hidden by default from other administrative user accounts.

     

    So, in order  for those system admins that are concerned with disabling Protected Mode and don't want to disable it in Acrobat/Reader, it may be necessary to manually edit an administrative template using GPO with the primary Administrator Account in the Windows Server that is enforcing group policies.

     

    Furthermore, it seems like the way to go from here is to modify a registry preference that restrict users from browsing and discovering priviledged locations in a domain (unless authorized with GPO),  manually  editing, copy and pasting, or typing in a fully qualified domain path in the Acrobat/Reader Preferences when they're trying  edit Acrobat Preferences, Trsusted Manager settings, Internet Zones, to access a Priviledged file share location, for example.

     

    The key here is to disable Protected View in  that priviledged location for them while restricting their ability to browse and discover other absolute paths in a domain.

     

    This is documented  in the Enterprise Toolkit and the Adobe Acrobat Customization Wizard reference guide but vsry vaguely.

     

    There are a few other things involved.

     

    I will post back with the actual references that I've found.

     

    In the meanwhile, I want to believe we're almost getting there.