[DXLog.net - Support] WG: Great crash

9A5K 9a5k at 9a5k.com
Wed Oct 2 20:01:28 CEST 2013


Hi Ricardo and others.

Thanks for config file.
It was useful to detect where the problem is.
Actually, this was really unhandled exception from TCP socket  and this
happens when DXLog.net tries to start a server on specific
interface defined in network parameters. In your example, you have server
enabled on interface with IP 192.168.0.100.
I suppose that you had that IP address before on some of your network
interfaces, but you've changed in meantime.
So, DXLog.net was trying to open a socket, but there isn't interface with
such IP on your PC, and here comes socket exception.
Now, I've added exception handler around this initialization part and
instead of such message from windows, there will be nice
Message box with explanation what happened.

73,
Chris - 9A5K




On Wed, Oct 2, 2013 at 7:05 PM, Ricardo Navarrete <ricardoea4zk at gmail.com>wrote:

> Here you are chris.......
>
> It is renamed as DXLog.config.......
>
>
>
>
> 2013/9/27 9A5K <9a5k at 9a5k.com>
>
>> Hi Ricardo and others.
>>
>> As Braco, OE1EMS/E77DX wrote, this could be a problem with something
>> written in the config file.
>> It could be something around network config, or cluster connection.
>> If you didn't delete DXLog.net directory in ApplicationData folder, it
>> will
>> be useful if you can send the content
>> of DXLog.net.config file which is located in %APPDATA%\DXLog.net folder so
>> I can investigate this more.
>> Of course, you can just try to rename this file, and restart DXLog after
>> that.
>>
>> Thanks in advance.
>>
>> 73,
>> Chris - 9A5K
>>
>>
>>
>> On Fri, Sep 27, 2013 at 1:51 AM, Bob Wilson, N6TV <n6tv at arrl.net> wrote:
>>
>> > Translating according to this
>> > post<
>> >
>> http://blogs.msdn.com/b/oanapl/archive/2009/01/30/windows-error-reporting-wer-and-clr-integration.aspx
>> > >,
>> > the error info is:
>> >
>> > Problem Event Name: CLR20r3
>> > AppName: dxlog.net.exe
>> > AppVer: 2.0.15.0
>> > AppStamp: 52430b6c
>> > AsmAndModName: System
>> > AsmVer: 4.0.0.0
>> > ModStamp: 4ba1dff4
>> > MethodDef : 2500
>> > Offset: 40
>> > ExceptionType: System.Net.Sockets.SocketException
>> > OS Version: 6.1.7601.2.1.0.256.1
>> > Locale ID: 3082
>> >
>> > From Google searches, it seems that many .NET applications have failed
>> with
>> > this exception, for many different reasons.  All I can guess is that
>> there
>> > was some type of network error or error making a System call.
>> >
>> > Did you lose your Internet connection?  Were you connecting to a
>> cluster?
>> >  Were you running networked DXLog computers?  Did you install DXLog.net
>> in
>> > something other than the default directory?  Were there two copies of
>> > DXLog.net running at the same time?
>> >
>> > 73,
>> > Bob, N6TV
>> > _______________________________________________
>> > Support mailing list
>> > Support at dxlog.net
>> > http://www.dxlog.net/mailman/listinfo/support
>> >
>> _______________________________________________
>> Support mailing list
>> Support at dxlog.net
>> http://www.dxlog.net/mailman/listinfo/support
>>
>
>
>
> --
> EA4ZK Ricardo Navarrete
> ricardoea4zk at gmail.com
> *
> *
> *CWops : 1070*
> *POR FAVOR, SI VAS A REENVIAR ESTE CORREO, TEN EN CUENTA LOS SIGUIENTES
> PUNTOS:
> 1.- Borra la dirección e-mail del remitente así como cualquier otra
> dirección e-mail que aparezca en el cuerpo del mensaje.
> 2.- Protege frente a terceros a todos los destinatarios de tus mensajes
> colocando sus direcciones en la línea de CCO (Con Copia Oculta).
> *
> *Combatir el spam es tarea de todos.*
> *Gracias por tu colaboración.*
>
>


More information about the Support mailing list