Our full technical support staff does not monitor this forum. If you need assistance from a member of our staff, please submit your question from the Ask a Question page.


Log in or register to post/reply in the forum.

Loggernet installation problems


ftiedem Jan 7, 2020 01:18 AM

Dear all,

I've got a new computer (Win 10 Pro) and installed Loggernet (4.5) there. Installation went fine, no errors. After starting LoggerNet.exe, the Control Box shows up, BUT:

If I try to start an application (e.g. Setup, but all the others are affected too), I get an error message (0xc0000142).

Even uninstalling and reinstalling did not fix that issue.

I've tried several fixes I've found on web, but none of them helped.

Is this a known error or does somebody has an idea of how to get rid of it?

Thanks in advance,

Frank


JDavis Jan 9, 2020 02:57 PM

The clients like Setup and Connect us IP port 6789 to communicate with the server portion of Loggernet. Make sure your Windows firewall, and any firewalls your security software use allow port 6789 for Loggernet Server.

This is the default install path on English language computers:

C:\Program Files (x86)\Campbellsci\Loggernet\LoggerNetService.exe


gpluca Feb 19, 2020 07:57 AM

I'm having the same issues on my new laptop.

I tried opening the port 6789 but nothing changed.

I also tried cleaning my dll registry and other things from the web. Someone suggested that Microsoft Office could be a problem.

Is that possible or does anyone have any other sollutions?

Luca


ftiedem Feb 20, 2020 03:59 AM

still not solved my problems.

opening the port and even deactivating firewall did not help

Btw: I haven't installed MS Office, so at least in my case, thats not the issue


kc Mar 30, 2020 09:49 AM

Had the same problem, it was fixed with changing the language settings of the PC, first step as described here: https://www.youtube.com/watch?v=QpSDikJLZj8

Chris


ftiedem Mar 31, 2020 12:23 AM

That worked,

Thanks a lot Chris,

Problem is solved


GaryTRoberts Apr 1, 2020 10:58 AM

The issue is resolved in LoggerNet 4.6.2. Patches are available from the downloads section of our website.

Log in or register to post/reply in the forum.