Power Log Client: Run-time error '-2147417848' Automation Error

Home
»
Product Forums
»
Powerlog Category
»
Powerlog
»
Power Log Client: Run-time error '-2147417848' Automation Error

Power Log Client: Run-time error '-2147417848' Automation Error

Author	Message
HullUniRadio	HullUniRadio Posted 10 Years Ago #7775
Forum Sage Group: Forum Members Posts: 3, Visits: 34	Good afternoon Our station has just started using powerlog (despite having it on licence for years). We installed the latest subversion of V3 of both the server and client. The server seems to run fine but we can not get the client to work. When opening the client we receive the following error while the splash screen is still visible: Run-time error '-2147417848 (80010108)': Automation error The object invoked has disconnected from its clients. The program then closes. We have tried running as normal user and administrator but the same error occurs. The server and client are both running on windows 7 Ultimate but on separate machines. The log files are stored on a shared network drive. Microsoft VB5 Runtime has been installed on both machines. Any advise would be greatly received. Tags Automation error powerlog client Edited 10 Years Ago by HullUniRadio 383
	Reply
David Boulton	David Boulton Posted 10 Years Ago #7778
Brand Manager - Broadcast Radio Group: Broadcast Radio Posts: 562, Visits: 74K	Hmmm Ok can you tell us more about the PC, 32bit or 64bit? Windows 7 or Win2008R2 Server OS? Not sure if it was in that early version, but if you put /debug on the shortcut - does it create a folder on your C:\ called "Debug" or "Debugfiles" - and then we can take a look at the files. Regards David Boulton Brand Manager Broadcast Radio Ltd 323
	Reply
HullUniRadio	HullUniRadio Posted 10 Years Ago #7790
Forum Sage Group: Forum Members Posts: 3, Visits: 34	Sorry for the late reply we have currently in exam season at the moment at uni so it's only when we have a spare moment we are dealing with radio work. The client is on windows 7 Ultimate 64bit The server is on windows 7 Ultimate 64bit Here is the debug file output: 17:34:10 OpenLogLocation: Z:\powerlog\default.dir 17:34:10 singleLog=False 17:34:10 Configure DST 17:34:10 sysGetStreams: Open Directory 17:34:10 sysGetStreams: New Log 1: Z:\powerlog\MainStudioLive 17:34:10 VerifyLicense: ExpiryDate=16/05/2024, bSilent=True 17:34:10 sysGetStreams: Close Directory 17:34:10 OpenLogLocation: Find index of last log 17:34:10 OpenLogLocation: Set Client Control path: Z:\powerlog\MainStudioLive 17:34:10 Start PLClient1_LogsAvailable 17:34:10 Calling SeekAbsolute to the latest position Thank you 320
	Reply
philedmonds	philedmonds Posted 10 Years Ago #7793
Forum Sage Group: Forum Members Posts: 127, Visits: 620	My finger of suspicion will be that you are missing some ofthe visual basic runtime files, as I've had the similar issues with Vista/7 and Powerlog v3 client. I haven't got my notes to hand to the exact files you need, but I'd search theMS website for the Visual Basic 5 run-time re-distributable files and install them, then Powerlog client should play nice. Another thing to be aware with Powerlog 3 being built for XP you may run into UAC Virtualization "niggles" on newer versions of Windows ifyou have multiple windows users on a machine as what was designed as 'per machine' Powerlog Client settings get virtualised away into 'per user' settings. -- Myriad user since 1998, now custodian of dozens of Myriad,Autotrack, Powerlog and Scoop boxes of many different flavours. http://www.philedmonds.com Edited 10 Years Ago by philedmonds 322
	Reply
HullUniRadio	HullUniRadio Posted 10 Years Ago #7795
Forum Sage Group: Forum Members Posts: 3, Visits: 34	We installed the Microsoft VB5 Runtime Libraries after we realised you needed them for powerlog server. We did manage to get the client to work twice several weeks ago using run as administrator but that's not working either now. It's looking like we may just have to accept we need the new version. Thanks for the help though appreciate it 309
	Reply