ApexSQL Recover displays the “Database log.ldf cannot be found” error when SQL Server is running on Windows 8.1 or Windows Server 2012 R2

Applies to
ApexSQL Recover 2011.02.1058 and earlier

Summary
This article describes how to resolve the “Database log.ldf cannot be found” problem in ApexSQL Recover when running on Windows 8.1 or Windows Server 2012 R2

Symptoms
When trying to recover the data from any edition and version of SQL Server running on Windows 8.1, ApexSQL Recover shows the “Database log.ldf cannot be found” error for all recovery options, and recovery process don’t start

Cause
The internal structure for acquiring read access to a file has been changed in Windows 8.1, so ApexSQL Recover cannot access the online transaction log (LDF) file

Resolution
The issue is fixed in ApexSQL Recover 2011.03.1061

  1. Uninstall ApexSQL Recover client and Server-side components
  2. Download the latest versions of ApexSQL Recover
  3. Install the downloaded version of ApexSQL Recover

Related posts:

  1. The old ApexSQL Recover version isn’t removed after the update
  2. ApexSQL Log and ApexSQL Log API show no transactions on Windows 8.1 or Windows Server 2012 R2
  3. The “You need to be a member of the sysadmin role to complete the installation” error is encountered when installing server-side components in ApexSQL Recover 2014”
  4. The ‘Sqlcmd: Error: Syntax error at line XYZ near command ‘X’ in file ‘file_name.sql’.’ error is encountered when running SQL script via sqlcmd utility
  5. ApexSQL Recover doesn’t recover all lost data