LockDown Browser Error -105 on Mac (Server Configuration Fix)

Error -105 in LockDown Browser belongs to the same "general configuration" family as -101 - almost always a Respondus Dashboard configuration issue on your university's server. Mac-side cache-clear + reinstall resolves the small fraction that are actually client-side; the rest need instructor escalation.

What error -105 means

Error -105 indicates the server returned a Dashboard configuration that LDB could not apply because of a specific configuration value (often a feature flag mismatch, e.g. Respondus Monitor enabled on the Dashboard but the LDB version installed doesn't support the requested Monitor version).

Mac-specific causes

Fix 1 - Update LDB to the current version

If your LDB has been installed for >3 months, update to the current release. Launch your existing LDB; it auto-checks for updates on launch. Alternatively, uninstall (see uninstall cluster) and download fresh from your LMS - this guarantees the latest build.

The current production build at the time of writing is 2.1.5.01. Older builds (2.0.x, 2.1.4) are partially compatible with newer Dashboard configs and produce -105 in the mismatch cases.

Fix 2 - Clear cache + reinstall

rm -rf ~/Library/Application\ Support/LockDown\ Browser/
rm -rf ~/Library/Caches/com.respondus.lockdownbrowser/

Then reinstall from your LMS. If -105 still appears, the issue is server-side - escalate to your instructor.

Fix 3 - Contact instructor with full diagnostic

Provide LDB version, macOS version, time of failed launch, and whether classmates have the same issue. Your instructor or university IT opens a Respondus support ticket.

If none of these work

The remaining cases trace to your specific course's Respondus Dashboard configuration - your university IT or instructor needs to look at the server side. Contact them with: the exact error code, the LDB version (right-click LDB.app → Get Info), the macOS version (About This Mac), and the time of your launch attempt.

Frequently asked questions

Why does -105 fire on macOS Tahoe but not Sonoma?

Tahoe-introduced TCC changes occasionally cause LDB to fail certain Dashboard configurations that worked on Sonoma. Update LDB to the current release that supports Tahoe - earlier builds will produce -105 on the new OS.

I'm on the latest LDB and still see -105. What now?

Server-side Dashboard issue. Email instructor immediately with diagnostic data; do not retry repeatedly (the launch attempts log on Respondus servers and create review burden).