Thank you, czofnas001.
Long path names are common problems with PAL, but the paths you provided seems small enough. The problem looks to be a corrupted counter log. Relog.exe (part of the operating system) is unable to convert the counter log from binary to text, so PAL can parse it. This can happen if you are using Windows XP or earlier operating system or the counter log is corrupted. It looks like there is only 15 minutes of data in the log, so likely there is just not enough data to work with. Try using a counter log that has captured more data.
Does the sample counter log work? Its the one provided with PAL as a known good log test.
Long path names are common problems with PAL, but the paths you provided seems small enough. The problem looks to be a corrupted counter log. Relog.exe (part of the operating system) is unable to convert the counter log from binary to text, so PAL can parse it. This can happen if you are using Windows XP or earlier operating system or the counter log is corrupted. It looks like there is only 15 minutes of data in the log, so likely there is just not enough data to work with. Try using a counter log that has captured more data.
Does the sample counter log work? Its the one provided with PAL as a known good log test.