Error 105: Troubleshooting Media Database Corruption

Adobe Error 105 breaks down the local media file tracking network, halting asset generation and database updates during app initialization or file imports. This breakdown locks up video timelines, stalls media rendering, and risks losing active links to project files if ignored. The failure occurs because the localized shared database directory becomes corrupted, meaning the storage ledger cannot log new assets or clear outdated scratch references.

Fast-Fix: The 45-Second Solution

To resolve a corrupted media database, close all running Adobe programs, locate the hidden common media cache folder on your drive, and delete the MediaDB.db and database journal files entirely. This forces the system to compile a clean asset ledger upon the next software launch.

Quick Status Snapshot

• Severity Tier: High
• Project Risk: Timeline Unlinking / Immediate Performance Degradation
• Root Cause: Corrupted SQLite records or broken file index pointers in the central media catalog folder.
• Rare Cause: Intermittent hardware power loss during asset compilation, resulting in truncated database headers.

Low-Friction vs. High-Friction Scenarios

• Low-Friction Scenario: The error triggers immediately after importing a corrupted .mp4 or .mov clip. The application stalls because it encounters an unreadable file header while trying to log the clip into its registry. Deleting the single faulty file and clearing the app cache fixes the glitch instantly.
• High-Friction Scenario: The error surfaces across all projects and resists standard app restarts. This points to broken directory access parameters within your operating system user account, preventing the backend media service from modifying files on the disk drive.

Service-Level Mechanism

The Adobe Media Encoder Core and the shared Media Cache service use a central file ledger to monitor raw storage data. This database acts exactly like a library catalog system. When a book is pulled from the shelf or a new volume is added, the librarian writes the change down in a master ledger.

If someone rips pages out of that master ledger, the librarian can no longer track where books belong or where to file incoming shipments. When this ledger gets corrupted, the backend file engine triggers a protective freeze, labeled as Error 105, to keep the system from accidentally scattering data over wrong storage locations.

Probability Breakdown

• 60% Probability: Abrupt app shutdowns or system crashes that interrupt live writing operations to the media cache.
• 30% Probability: Multi-drive project setups where external storage links are disconnected before the background cache writer finishes syncing.
• 10% Probability: Internal drive sectors failing where the database ledger resides.

Escalation Variables

Working across different operating systems with shared external project drives accelerates database corruption. If one workstation formats drives via exFAT and another uses NTFS, the shifting file properties can scramble the master index. Similarly, background security scanners can lock the database file mid-read, causing the software to assume a hardware disconnect has occurred.

The Cost of Delay: Immediate → Next Session

Ignoring Error 105 leads to cumulative file linking failures. While your current project timeline might stay open temporarily, the database cannot write any new records to the storage drive. By the next editing session, the software will drop its connection to your scratch disk, forcing a slow file re-indexing process that can trigger a total system freeze during timeline playback.

Diagnostic Contrast (Differential Diagnosis)

Check your background log directories to distinguish Error 105 from adjacent setup failures:

• Error 105: Indicates structural corruption inside the media asset logging catalog, preventing raw asset imports.
• Error 101: Displays when the central setup manifest file cannot be located during the initial decompression phase. To reconstruct that deployment map manually, see Error 101: Manifest File Missing – Manual Reconstruction Steps.
• Error 103: Signifies that the installation app is trapped in a closed loop because it cannot overwrite system files. To clear out locked installation loops, see Error 103: Creative Cloud Update Loop – Bypassing the Manifest.
• Error 106: Surfaces when the installer engine fails to align raw platform definitions. To realign installation metadata paths, see Error 106: Why Adobe Installer Can’t Find the Product Metadata.

What To Do Right Now

• Kill the Software: Fully close Premiere Pro, After Effects, and Media Encoder.
• Disconnect Network Storage: Temporarily unplug active NAS or SAN storage lines to isolate local drive issues.
• Clear Storage Locks: Run a disk permissions verification check on your primary boot partition.

Hard-Stop Failure Signals

Watch out for these critical failure indicators:

1. The media tracking status bar gets permanently stuck at 0% during file imports.
2. The application directory outputs zero-byte .db-journal files that cannot be modified or moved.
3. The software crashes back to the desktop the moment you attempt to change your scratch disk target directory.

The Professional Recovery Sequence

Step 1: Force Terminate Shared Audio-Visual Processes

Background cache links will block any manual removal steps until they are fully deactivated.

• Windows: Open Command Prompt with administrative privileges and run:DOS taskkill /F /IM "Adobe Premiere Pro.exe" /T taskkill /F /IM "AdobeMediaEncoder.exe" /T taskkill /F /IM "dynamiclinkmanager.exe" /T
• macOS: Open Terminal and execute:Bash sudo killall "Premiere Pro" "AdobeMediaEncoder" "dynamiclinkmanager"

Step 2: Purge the Centralized Media Database Folder

Manually stripping out the damaged index files forces the storage ledger to rebuild itself cleanly on the next startup.

1. Use your file browser to go to the following hidden locations:
   • Windows: %APPDATA%\Adobe\Common\Media Cache Files\ and %APPDATA%\Adobe\Common\Media Cache\
   • macOS: /Users/[YourUsername]/Library/Application Support/Adobe/Common/Media Cache Files/ and /Users/[YourUsername]/Library/Application Support/Adobe/Common/Media Cache/
2. Locate and delete the files named exactly MediaDB.db and MediaDB.db-journal.
3. Empty your system recycling bin to clear the locked file descriptors from the drive.

Step 3: Reassign Storage Permissions for the Media Cache Path

Ensure the operating system explicitly allows the software engine to read and write database changes to the drive:

• Windows: Right-click the Common folder, select Properties, uncheck the Read-only attribute box, and click Apply.
• macOS: Open Terminal and reset the folder access permissions:Bash sudo chmod -R 777 /Users/Shared/Adobe/

Step 4: Re-route the Scratch Disk Target Destination

Launch your video app, navigate immediately to Preferences > Media Cache, and click the Browse button. Move the media cache directory to a new folder location on a fast local SSD. This step ensures that any hidden sector glitches on the old drive location will not corrupt the fresh database files.

Required Resource Allocation

• Drive Access Speed: A local NVMe or SATA SSD is required. Running a media database across an external mechanical drive or network storage can trigger timing mismatches.
• Storage Allocation: Keep at least 30 GB of clean, unallocated disk space to handle the temporary video indexing files.
• Administrative Rights: Local administrator privilege is required to clean out hidden application folders.

Combined Symptom Escalators

If your media database corrupts while the software frequently displays “Media Missing” offline screens, stop working immediately. This combination indicates your storage connection line or thunderbolt cable is loose, which drops input/output signals mid-edit and corrupts the file ledger.

Final Render

Error 105 is an index file conflict, not a loss of your source video assets. By shutting down background syncing tools, stripping out the broken MediaDB.db file, and moving the cache folder to an active local SSD partition, you can force the software to safely index your assets from scratch. This fixes the playback issues and lets you return to editing without losing project timeline data.