[WriteLog] UDP listener (Wayne, W5XD)

[I2SVA - Alessandro]

I have a similar issue here:
- WL 12.35C
- WL UDP Listener
- WSJT 2.0.0-rc5
- O/S Windows 10

Running UDP listener (normal or as administrator does not make any difference):
- Listening on UDP Port 2333 this machine only

When I log the QSO in WSJT the UDP listener answers:
- NG Writelog not running <ADIF data...>

Nothing happens in WL.

Thanks, 73
Alessandro I2SVA

  
    ------------------------------
    
    Message: 3
    Date: Tue, 4 Dec 2018 15:44:52 -0500
    From: Mike Seguin <n1jez at burlingtontelecom.net>
    To: "writelog at contesting.com" <writelog at contesting.com>
    Subject: [WriteLog] UDP listener
    Message-ID:
    	<b9224522-b889-c48a-3e9e-69e93e97a479 at burlingtontelecom.net>
    Content-Type: text/plain; charset=utf-8; format=flowed
    
    I'm testing the new UDP listener. I log a contact in WSJT-X which is 
    being sent to UDP listener. I see it in the status window. But it says:
    
    NG WriteLog not running (followed by the ADIF info) and it does not show 
    up in WriteLog
    
    I have to be missing something...
    
    -- 
    
    73,
    Mike, N1JEZ
    "A closed mouth gathers no feet"
    
    
    ------------------------------
    
    Message: 4
    Date: Tue, 4 Dec 2018 15:56:36 -0500
    From: Mike Seguin <n1jez at burlingtontelecom.net>
    To: "writelog at contesting.com" <writelog at contesting.com>
    Subject: Re: [WriteLog] UDP listener
    Message-ID:
    	<6b0b46c2-e1bf-5e17-9de0-1eacb4e1dbf3 at burlingtontelecom.net>
    Content-Type: text/plain; charset=utf-8; format=flowed
    
    I found the problem. UDP Listener needs to "Run as Administrator". 
    Working now.
    
    On 12/4/2018 3:44 PM, Mike Seguin wrote:
    > I'm testing the new UDP listener. I log a contact in WSJT-X which is 
    > being sent to UDP listener. I see it in the status window. But it says:
    > 
    > NG WriteLog not running (followed by the ADIF info) and it does not show 
    > up in WriteLog
    > 
    > I have to be missing something...
    > 
    
    -- 
    
    73,
    Mike, N1JEZ
    "A closed mouth gathers no feet"
    
    
    
    I don't have a diagnosis, but something is wrong (i.e. not working as
    designed) if the fix is an explicit "Run as Administrator".? There are
    very few WriteLog actions that require admin privilege, and ALL of those
    are designed to auto-magically pop up the built-in Windows system login
    as admin. You should never have to force that issue.
    
    Can you share anything about your installation that you think might be
    unique? (Please respond off-list my email reply address)
    
    Wayne
    
    
    ------------------------------