Authentication Issues
Invalid username, password, security token, or user locked out
Invalid username, password, security token, or user locked out
- Login fails with “INVALID_LOGIN” error
- “User locked out” message
- Verify credentials: Double-check username, password, and security token
- Password + Token: Ensure password and token are in separate fields (don’t concatenate)
- Reset token: Get a fresh security token from Salesforce Settings
- Check account status: Verify your Salesforce account isn’t locked or deactivated
- Try web login: Log in to Salesforce in a browser to verify credentials work
- Contact admin: If locked, contact your Salesforce administrator
Connection timeout or network error
Connection timeout or network error
- “Connection timeout” error
- “Network error” or “Failed to connect”
- Check internet: Verify you have a stable internet connection
- Firewall/VPN: Ensure firewall or VPN isn’t blocking
*.salesforce.com - Correct environment: Verify you selected the right environment (Production/Sandbox/Custom)
- Custom domain: For My Domain, ensure URL is correct and includes
https:// - Try browser: Access Salesforce in a browser to rule out connectivity issues
API not enabled for user
API not enabled for user
- “API_DISABLED_FOR_ORG” error
- “User does not have API access”
- Check profile permissions: Contact admin to enable “API Enabled” on your user profile
- Permission set: Admin may need to assign an API-enabled permission set
- Trial org: Some Salesforce trial orgs don’t have API access
Two-factor authentication (2FA) blocking login
Two-factor authentication (2FA) blocking login
- 2FA prompt appears but can’t be completed in FileFetch
- Trusted IP: Add your IP address to Salesforce Network Access (trusted IPs)
- Contact admin: Ask admin to whitelist your IP in Salesforce Setup
- OAuth (coming soon): OAuth 2.0 support will handle 2FA in future release
Query Issues
No results returned from query
No results returned from query
- Query executes successfully but returns 0 files
- Check filters: Remove or broaden filters (date range, file type, etc.)
- Verify data exists: Check in Salesforce that files matching your criteria exist
- Permissions: Ensure you have access to view the files (sharing rules, etc.)
- Export type: Verify you’re querying the correct type (Files vs Attachments)
- Related object: If filtering by object, check that files are actually linked to that object
SOQL syntax error
SOQL syntax error
- “Unexpected token” or “syntax error” in Power Mode
- Check spelling: Common typos like
SELCTinstead ofSELECT - Verify field names: Ensure field API names are correct (e.g.,
TitlenotNamefor Files) - Check operators: Use
=not==, proper quoting for strings - Required fields: Include
IdandContentDocumentId(for Files) - Copy from examples: Use queries from SOQL Examples
Query returns 2000 results but I need more
Query returns 2000 results but I need more
- Query hits Salesforce 2000-row limit
- Add filters: Use date ranges or other filters to narrow results
- Multiple queries: Run separate queries for different date ranges
- CSV Import: If you have a list of IDs, use CSV Import instead
- Batch approach: Export in batches (e.g., monthly) rather than all at once
Invalid field error in query
Invalid field error in query
- “No such column ‘FieldName’ on entity ‘ContentVersion’”
- Verify field exists: Check the field exists in Salesforce for that object
- API name: Use the API name, not the label (e.g.,
ContentSizenotFile Size) - Custom fields: Custom fields need
__csuffix (e.g.,Category__c) - Object type: Some fields only exist on ContentVersion, not Attachment (and vice versa)
- Check reference: See Salesforce Objects for field lists
CSV Import Issues
No valid IDs found in CSV
No valid IDs found in CSV
- “No valid IDs found in CSV” error
- ID format: Ensure IDs are 18-character Salesforce IDs
- Correct prefix: Files should start with
069, Attachments with00P - Column name: Include header row with
ContentDocumentIdorId - No extra spaces: Remove leading/trailing spaces from IDs
- Check sample: Test with a known-good ID first
CSV contains IDs but files not found
CSV contains IDs but files not found
- CSV loads but many files show “not found or no access”
- Check permissions: Verify you have access to those files in Salesforce
- Wrong org: Ensure IDs are from the org you’re currently logged into
- Deleted files: Files may have been deleted since the CSV was created
- ID type mismatch: Using ContentDocument IDs when in Attachments mode (or vice versa)
File too large / CSV won't upload
File too large / CSV won't upload
- CSV file upload fails or is rejected
- Size limit: CSV must be under 5MB
- Reduce rows: Split into multiple smaller CSVs
- Remove columns: Keep only the ID column to reduce file size
- Paste instead: Try pasting content directly instead of uploading
Export/Download Issues
Download timeout errors
Download timeout errors
- “Download timeout after 120 seconds”
- Some files fail with timeout
- Increase timeout: Go to Settings → Download Timeout and increase (e.g., 300 seconds)
- Large files: Very large files may need longer timeout
- Reduce concurrency: Lower concurrent downloads in Settings (e.g., from 10 to 5)
- Internet speed: Check your internet connection speed
- Retry failed: Use Export History to retry failed downloads
Files downloading as 0 bytes or corrupted
Files downloading as 0 bytes or corrupted
- Downloaded files are empty or won’t open
- Check source: Verify file is valid in Salesforce
- Disk space: Ensure you have enough free disk space
- Retry download: Delete the file and re-export
- Antivirus: Temporarily disable antivirus and retry
- Different folder: Try exporting to a different location
Export stops or hangs mid-download
Export stops or hangs mid-download
- Progress bar stops moving
- Export appears frozen
- Wait: Some files may be large and take time
- Check logs: Open Export History to see what’s happening
- Cancel and retry: Click Cancel, then retry the export
- Reduce batch size: Export fewer files at once
- Check connection: Ensure stable internet throughout export
Permission denied / Can't write to export folder
Permission denied / Can't write to export folder
- “Permission denied” when trying to save files
- Files fail to save to disk
- Check folder permissions: Ensure FileFetch can write to export directory
- Choose different folder: Change export location in Settings
- Run as admin: On Windows, try running FileFetch as administrator
- Disk full: Check if your disk is full
- Path length: On Windows, ensure export path isn’t too long (260 char limit)
Duplicate files not being handled correctly
Duplicate files not being handled correctly
- Files with same name overwriting each other
- Expected duplicates not appearing
- Check duplicate setting: Verify “Append ID” is enabled in Export Configuration
- Grouped exports: If grouping by record, duplicates only apply within each folder
- Review summary: Check
_Export_Summary.txtfor duplicate handling report - Re-export: Re-run export with correct duplicate handling setting
Application Issues
FileFetch won't launch or crashes on startup
FileFetch won't launch or crashes on startup
- App crashes immediately on launch
- Window appears then closes
- Check Gatekeeper: Right-click → Open to bypass security
- Reset preferences: Delete
~/Library/Application Support/app.filefetch.filefetch - Reinstall: Uninstall and download fresh copy
- Console logs: Check Console.app for crash reports
- Run as admin: Right-click → Run as administrator
- Reinstall: Uninstall and download fresh installer
- Event Viewer: Check Windows Event Viewer for errors
- Antivirus: Whitelist FileFetch in your antivirus
App freezes or becomes unresponsive
App freezes or becomes unresponsive
- UI stops responding during export
- Can’t click buttons or interact with app
- Wait: Large exports may temporarily freeze UI - give it time
- Force quit: Quit app and restart (exports are saved in history)
- Reduce load: Export fewer files at once
- Update app: Check for updates (may fix performance issues)
- Restart computer: Sometimes helps with resource issues
Auto-update fails or update won't install
Auto-update fails or update won't install
- Update download fails
- Update won’t apply after restart
- Manual download: Get latest version from filefetch.app/download
- Full uninstall: Remove app completely, then install new version
- Check permissions: Ensure FileFetch has permissions to update itself
- Clear cache: Delete old update files from temp folder
High memory or CPU usage
High memory or CPU usage
- Computer slows down during exports
- FileFetch uses lots of RAM/CPU
- Reduce concurrency: Lower concurrent downloads in Settings
- Close other apps: Free up system resources
- Smaller batches: Export fewer files per batch
- Restart app: Close and reopen FileFetch between large exports
macOS-Specific Issues
'FileFetch is damaged and can't be opened'
'FileFetch is damaged and can't be opened'
- Right-click → Open: Bypass Gatekeeper warning
- Terminal command:
- System Settings: Go to Privacy & Security → allow FileFetch
Keychain access prompts
Keychain access prompts
- Click Always Allow: Choose “Always Allow” instead of “Allow”
- Keychain First Aid: Run Keychain Access → Keychain First Aid
- Reset keychain: As last resort, reset login keychain (will lose other passwords)
Windows-Specific Issues
Windows Defender / SmartScreen warning
Windows Defender / SmartScreen warning
- Click More Info → Run Anyway: On SmartScreen warning
- Whitelist: Add FileFetch to Windows Defender exclusions
- Certificate: FileFetch is signed - warning is due to newness
VCRUNTIME140.dll not found
VCRUNTIME140.dll not found
- Install Visual C++ Redistributable: Download from Microsoft
- Reinstall FileFetch: After installing redistributable
Performance Issues
Downloads are very slow
Downloads are very slow
- Exports take much longer than expected
- Download speed is low
- Check internet speed: Run speed test to verify connection
- Increase concurrency: Raise concurrent downloads in Settings (up to 10)
- Network congestion: Avoid peak hours or shared networks
- VPN: Disconnect VPN if using one (may slow downloads)
- Salesforce limits: API may throttle requests during peak times
Query execution is slow
Query execution is slow
- Query takes long time to return results
- Add indexes: Query indexed fields (Id, CreatedDate, etc.)
- Reduce scope: Use smaller date ranges or LIMIT clause
- Avoid complex queries: Simplify WHERE conditions
- Check Salesforce: Query may be slow on Salesforce side
Getting More Help
If you’re still experiencing issues after trying these solutions:Contact Support
Check Export History
FAQ
GitHub Issues
Information to Include When Reporting Issues
When contacting support, please include:- FileFetch version: Found in app footer
- Operating system: macOS or Windows version
- Error message: Exact error text or screenshot
- Steps to reproduce: What you were doing when issue occurred
- Export Summary: Attach
_Export_Summary.txtif relevant - Salesforce org type: Production, Sandbox, or Custom
- Number of files: How many files you were trying to export