P Squared Community Forum / Product Forums / Powerlog Category / Powerlog FAQs

Client v4 throws Path/Access errors and a Jet Database error on startup

Richard Payne — Thu, 11 Jan 2007 14:28:15 GMT

This combination of errors usually occurs because you are trying to run PowerLog Client for the first time from a restricted windows user.

When the Client is first installed it stores it's contacts/users directory files in the installation folder. This folder is not writable for restricted users and read/write access is required for Jet Databases to operate.

The solution is to log in to Windows as an administrator, run PowerLog and then re-point the Directory to a location that is accessible to all. This option is in the Settings menu > Directory Settings.

You should be doing this anyway in a multi-user environment since the whole point of the Directory is to be a shared information store. A share on the PowerLog Capture machine would seem like the ideal place.

v4: Object Variable or With Block not Set

Richard Payne — Thu, 21 Jul 2005 11:20:43 GMT

Just encountered a rather bizarre problem on one of our test boxes here. The Log Processor was exploding with an \"Object Variable or With Block not Set\" error when it start trying to actually convert audio files. The problem only affected logs trying to convert to WMA files.The cause of the problem was a corrupted XML installation. WMA audio formats are chosen from a list of profiles. This profile list is stored in a prx file which is effectively just an XML formatted file.The solution is to visit http://msdn.microsoft.com/XML/XMLDownloads/default.aspx and download and install both v3 and v4 XML installations. You just need the msxml.msi installers, not the SDKs.As of v4.0.5 of PowerLog Capture a more informative error message will be presented! :D

Problems with ccrpsld.ocx

Richard Payne — Mon, 27 Jun 2005 15:45:49 GMT

Some people have experienced problems with installing PowerLog v3 on Windows Server 2003. The errors relate to ccrpsld.ocx.This file relies on another dll called msvbvm50.dll. We did not include it in our installers since prior to Windows Server 2003 it had always been supplied with Windows. For some inexplicable reason they have now removed it.You can resolve the issue by downloading and installing msvbvm50 from Microsoft's website: http://support.microsoft.com/kb/180071/EN-US/

Does Powerlog 'listen' to the audio looking for silences

Liam Burke — Fri, 06 Feb 2004 11:56:22 GMT

Does Powerlog 'listen' to the incoming audio looking for silencesYes, Powerlog Server checks all incoming audio and detects and records all silences over a configurable length. All silences are displayed on the Powerlog Client when the log is played back, as a coloured mark however, longer silences can also trigger an alarm by switching a hardware output on the Powerlog Server itself.Search key words: Silence detection, hardware output, listen.