Start a conversation

Adobe Photoshop (2024/2025) Fails to Save to Xinet AFP (AppleShare) Shares on macOS Sequoia

Contents

Overview

On macOS Sequoia, Adobe applications (reported with Photoshop 2024/2025 and an InDesign export-to-PDF workflow) may fail to save files to a Xinet AFP (AppleShare) share, even though saving to the same storage over SMB works. Common errors include "Unable to save as <file_name>.psd due to disk error." and "The operation cannot be performed because an item named <<>> already exists."

This behavior was confirmed as a product defect a fix is available in Xinet 2025.12.19.

Solution

Issue Details (Symptoms & Environment)

  • Client OS: macOS Sequoia
  • Applications: Adobe Photoshop 2024 & 2025 (reported versions included 2024.1.0 and 2025.5.16)
  • Protocol behavior: AFP fails, SMB succeeds (workaround)
  • Impact scope: affected all users in the reported environment
  • Typical repro: open a file from an AFP-mounted Xinet share → modify → save → error
  • Related workflow observed: InDesign exporting a PDF to the same AFP target also showed similar failure behavior

Common Error Messages (translated)

  • Unable to save as <file_name>.psd due to disk error.
  • The operation cannot be performed because an item named <<>> already exists.

Additional Observed Behavior

  • Adobe temporary files (for example, entries resembling Adobe Photoshop 2024…) may remain/persist on the AFP share during or after failed save attempts.

Resolution

Fix is available in: Xinet 2025.12.19.

Implementation Steps

  1. Upgrade the Xinet server
    • Upgrade your Xinet environment to version 2025.12.19 (or later), following your standard upgrade procedure.
    • Review the Xinet 2025.12.19 release notes for any prerequisites or post-upgrade steps relevant to your environment.
  2. Retest AFP save behavior
    • From a macOS Sequoia client, mount the Xinet share via AFP.
    • Open an existing file in Photoshop.
    • Make a change and save back to the AFP share.
  3. (Optional) Validate related workflows
    • If applicable, retest InDesign exporting a PDF to the AFP share, including re-exporting to the same target.

Workaround (If Upgrade Is Not Immediately Possible)

Use SMB where feasible as a workaround, since saving to the same Xinet storage over SMB was successful in the reported scenario.

Validation / Success Criteria

  • Saving no longer triggers:
    • Unable to save as <file_name>.psd due to disk error.
    • The operation cannot be performed because an item named <<>> already exists.
  • Temporary files created during save are cleaned up normally (no unexpected persistent Adobe Photoshop … temp files on the AFP share).
  • Multiple users can reproduce successful saves (not just a single test account).

If the Issue Persists After Upgrading

  1. Enable AppleShare/KSD debug logging (single user first)
    • Enable KSD (AppleShare) debug mode for a single test user and reproduce the issue.
    • If necessary and operationally acceptable, enable KSD debug mode globally (this is more invasive and may require a process restart).
  2. Capture complete evidence for the full reproduction window
    • Collect a screen recording showing the entire sequence from file open through the failed save.
    • Collect server logs that cover the entire time window of the reproduction (logs captured outside the failure window may show no AFP errors even when the problem occurs).
  3. Record versions in use
    • macOS version (Sequoia build if available)
    • Adobe application and version (e.g., Photoshop 2024.1.0 / 2025.5.16)
    • Xinet server version

Frequently Asked Questions

1. How do I know I’m hitting this same issue?
You’re likely affected if saving from Adobe apps to a Xinet AFP share on macOS Sequoia fails with either "Unable to save as <file_name>.psd due to disk error." or "The operation cannot be performed because an item named <<>> already exists.", while saving to the same Xinet storage via SMB works.
2. What versions were involved, and where is it fixed?
The issue was reported with macOS Sequoia and Adobe Photoshop 2024/2025 (including reported versions 2024.1.0 and 2025.5.16). The defect is fixed in Xinet 2025.12.19.
3. What is the recommended remediation?
Upgrade the Xinet server to 2025.12.19 (or later) and then retest saving to the AFP share from the affected Adobe applications.
4. Why were debug logs and a screen recording requested?
This issue requires logs that cover the entire reproduction window. Short log snippets or logs captured outside the failure time can show no errors even when the save fails. Enabling KSD (AppleShare) debug logging increases the diagnostic detail needed to confirm behavior and support escalation for defect analysis when required.
5. What should I verify after upgrading?
Confirm you can open-modify-save files to the AFP share without the disk error, and that no unexpected persistent Adobe temporary files remain on the share after saving.
6. What if upgrading isn’t immediately possible?
Use SMB where feasible as a workaround. If SMB is not viable in your environment, enable KSD debug logging (single-user) and capture a full reproduction recording plus complete logs covering the time window so the behavior can be analyzed while planning the upgrade.
Choose files or drag and drop files
Was this article helpful?
Yes
No
  1. Priyanka Bhotika

  2. Posted
  3. Updated

Comments