Database Selection for Production Environments

Question: I am getting “file already in use” errors when using Microsoft Access databases with WinSyslog, EventReporter, or MonitorWare Agent. What should I do?

The Problem

Microsoft Access databases (JET databases) are not designed for production server environments and are prone to file locking issues, especially when accessed through web interfaces or multiple connections. Common errors include:

Microsoft OLE DB Provider for ODBC Drivers error 80004005
[Microsoft][ODBC Microsoft Access Driver] Could not use (unknown); file already in use.

Recommended Solution: Use Enterprise Database

For production environments, we strongly recommend migrating to an enterprise-grade database:

• MySQL: Free, open-source, high-performance database with excellent Windows support
• Microsoft SQL Server: Native Windows integration, powerful features, excellent performance
• PostgreSQL: Robust open-source alternative with enterprise features

Migrating to these databases will:

• Eliminate file locking issues
• Provide significantly better performance
• Enable proper multi-user access
• Allow web viewer functionality without conflicts
• Improve overall system reliability

Microsoft Access Database Best Practices (If You Must Use It)

Warning: MS Access should only be used for testing, small deployments, or non-production environments.

If you must continue using MS Access, ensure proper permissions:

1. Right-click the folder containing the MS Access database and select “Properties”
2. Ensure the “Read-only” property is unchecked
3. Navigate to the “Security” tab
4. Click “Add” to open the “Select Users or Groups” window
5. Add the IIS application pool identity (typically IUSR or IIS_IUSRS)
6. Grant “Modify” or “Full Control” permissions to this account

Modern Windows Systems: Note that newer Windows Server versions may have different permission requirements. In Windows Server 2016+, ensure the service account has appropriate database folder permissions.

Migration Considerations

If you are currently using MS Access and experiencing issues:

• Data Migration: WinSyslog, EventReporter, and MonitorWare Agent support exporting configuration and can work with multiple database types
• Downtime: Plan for minimal maintenance window during migration
• Testing: Test the migration in a non-production environment first
• Support: Contact support for assistance with database migration if needed

Additional Notes

• Microsoft Access databases have file size limitations (2GB)
• Concurrent access is limited, causing performance bottlenecks
• Web-based access is problematic due to file locking
• No built-in backup/recovery mechanisms
• Poor performance with large datasets

For questions or support with database migration, please contact support@adiscon.com.