ApexSQL Log and ApexSQL Log API show no transactions on Windows 8.1 or Windows Server 2012 R2

Applies to
ApexSQL Log 2011.03.1088 and earlier
ApexSQL Log API 2011.03.1062 and earlier

Summary
This article describes how to resolve the problem when ApexSQL Log and ApexSQL Log API show no transactions when running on Windows 8.1 or Windows Server 2012 R2

Symptoms in ApexSQL Log
When trying to show the transactions from a SQL Server transaction log using the Open results in a Grid view option, no transactions are displayed in the main grid. There is no error message displayed, just an empty main grid

Symptoms in ApexSQL Log API
After building and executing the project in Visual Studio, the “Parameters not valid” error is displayed

Cause
The Windows 8.1 internal structure needed by ApexSQL Log and ApexSQL Log API to access the online transaction log is changed and ApexSQL Log and ApexSQL Log API cannot access and read the transactions

Resolution
The issue is fixed in ApexSQL Log 2013.01.1098 and ApexSQL Log API 2013.01.1098

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

Related posts:

  1. Top ApexSQL Log issues and resolutions – an index to often used TS articles
  2. What should I do if ApexSQL Log returns fewer transactions than I expected?
  3. The “System.OutOfMemory” error
  4. ApexSQL Audit central repository database is becoming too large
  5. Loading a project file saved by ApexSQL Diff 2012 or previous version in ApexSQL Diff 2013 resets and blocks the Object filter and Schema mapping features