Troubleshooting Adobe Acrobat Shared Review: Server Errors, Crashes, and What They Mean
Adobe Acrobat’s older shared review workflow depends on an internal server, a SharePoint library, a WebDAV server, or a network folder, that your organization sets up and hosts. Most of the errors below trace back to that server connection rather than to Acrobat itself. This guide covers the most common ones and what to check first.
1. “Cannot connect to the review server”
This error occurs when Adobe Acrobat is unable to establish a initial or ongoing network handshake with the designated hosting location, whether that is a SharePoint library, a WebDAV directory, or a shared network folder. Instead of opening the document in collaborative mode, Acrobat halts the session and displays an alert dialog stating it cannot connect to the review server path. This typically points to an underlying server outage, an interrupted network connection, an out-of-date UNC/URL path, or security software blocking Acrobat's outbound traffic.
How to Fix This?
- Test baseline reachability: Try accessing the host location directly outside of Acrobat (via your web browser or Windows File Explorer / macOS Finder).
- Check network & VPN state: If the server is unreachable globally, confirm whether remote reviewers are connected to your organization’s VPN.
- Audit firewall & server paths: If the server is reachable via browser but not Acrobat, check if an internal firewall rule is blocking Acrobat’s outgoing network requests or if the UNC/WebDAV path changed.
2. Shared review crashes repeatedly
In this scenario, Acrobat launches normally but abruptly freezes, becomes non-responsive, or closes completely mid-session. These crashes typically trigger when Acrobat attempts to background-sync reviewer comments, initialize the review tracking pane, or poll the host server for changes over a fluctuating connection. When the connection drops unexpectedly or encounters a latency timeout, the application fails to handle the interrupted data stream, resulting in repeated desktop crashes for one or more participants.
How to Fix This?
- Update Acrobat: Verify you are running the latest release build (helo > check for updates). Many crash patterns are build-specific bugs with existing hotfixes.
- Inspect connection stability: Intermittent network drops over unstable network drives or weak VPN tunnels frequently trigger crash loops during live sync attempts.
- Isolate the server build: If crashes occur consistently for multiple users on the same server, treat the server configuration or network storage driver as the root cause.
3. SharePoint shared review isn't working
When utilizing Microsoft SharePoint as the review host, participants may click the shared review link only to encounter immediate "Access Denied" dialogs, prompt failures, or an inability to publish their markup back to the document library. This issue stems from the fact that an Acrobat shared review file relies entirely on SharePoint's underlying Access Control Lists (ACLs). If the parent library, folder permissions, or site structure do not align with the reviewer's credentials, Acrobat cannot read or write feedback to the server.
How to Fix This?
- Verify library-level access: Confirm that every participant has direct Read/Write permissions to the exact SharePoint document library hosting the review. An Acrobat shared review link does not override underlying SharePoint ACLs.
- Validate URL stability: Ensure the SharePoint library URL or folder structure was not renamed or moved after the review was initiated.
- Account for sync latency: Allow time for SharePoint file indexing. Apparent "broken" reviews are often just minor sync delays between client machines and SharePoint Online/On-Premises.
4. Setting up a shared review on WebDAV
WebDAV server setups often work smoothly for internal employees on the corporate network, but fail when attempting to include external collaborators, contractors, or remote stakeholders. External users typically encounter login loops, permission error codes, or an complete inability to locate the WebDAV path. Because Acrobat requires continuous two-way HTTP/HTTPS read/write communication over WebDAV, any missing external network routing, closed server ports, or strict authentication policies will block external participation.
How to Fix This?
- Configure Read/Write privileges: Ensure the WebDAV directory grants full Read, Write, and Modify permissions to all designated reviewer accounts.
- Address external network paths: Internal WebDAV paths (e.g.,
http://intranet-server/reviews/) are unreachable outside your intranet. You must configure an externally resolvable domain, reverse proxy, or SSL-secured WebDAV endpoint for non-internal participants. - Check authentication protocols: Ensure basic or digest authentication policies on the WebDAV server align with Acrobat's supported network authentication methods.
5. Could not save the shared review-enabled PDF file
This failure mode surfaces when a reviewer attempts to save their local progress, publish new comments, or export an updated copy of the review document. Instead of completing the operation, Acrobat displays a critical dialog stating it could not save the shared review-enabled PDF file. Because shared review PDFs maintain an active background connection to the remote repository, any loss of write access mid-session, due to restricted folder rights, full disk quotas, or a temporary network disconnect, prevents Acrobat from updating the file.
How to Fix This?
- Check write permissions mid-review: Confirm your user session hasn't lost write authorization to the destination folder due to a session timeout or policy reset.
- Inspect storage quotas: Verify that the destination network drive or SharePoint library has not reached its disk capacity limit.
- Rule out network drops: Because shared review PDFs maintain active background links to server locations, any brief network outage during a save action will surface as a critical file-save failure.
6. New reviewer comments aren't showing up
In this situation, reviewers successfully add and publish their annotations on their local machines, but other team members or the review initiator see a blank comment list or an outdated document state. This happens because Acrobat relies on a background polling process to fetch new markup from the host server at set intervals. If this background sync operation encounters a silent network timeout, a minor server disconnect, or a cached file conflict, Acrobat fails to refresh the comment stream without warning the user.
How to Fix This?
- Force manual connection check: Acrobat periodically polls the server for updates. If this check fails silently, new feedback won't render.
- Reopen the file: Save local work, close the document completely, and reopen it from the network location to trigger a clean server sync.
- Confirm live server state: Verify that the reviewer who posted the comments had an active network connection at the exact moment they published their feedback.
Still Having Server Issues?
If this keeps happening: these errors share a common cause, the review depends on a server your team has to host and keep running. If you're troubleshooting this on a recurring basis rather than as a one-off, it may be worth looking at what replacing that setup entirely looks like: a shared-review alternative that doesn't require hosting a server