5
Vote

Indihiang crash

description

Hi
Where i try to parse Remote Web server or Log file i receive application crash

comments

balint256 wrote Jul 3, 2010 at 12:18 PM

Firstly, may I start by saying this is a very handy tool (when it works properly!).
Version 1.0 crashes for me know parsing logs that version 0.2.x could. I use a 'web accelerating' Squid proxy (in 'vhost' mode) in front of my IIS server, which adds the XForwardFor field to each incoming request's header. I have an IIS ISAPI extension that deals with that field so web apps and log entries can correctly identify the IP address of the remote host (as opposed to always logging the same IP of the proxy server). As the complete field is stored in the log, when multiple proxies have handled the request on the way from the end-user to my server, a string is built up e.g. '1.2.3.4,+5.6.7.8,+9.0.1.2', i.e. it is not just a single IP. I believe this is what may be causing Indihang to fail now, as debugging the crash shows a System.FormatException from Number.ParseInt32, which is called from Indihiang.Cores.IndihiangHelper.IPAddressToNumber.
Thank you!

wrote Jul 5, 2010 at 8:52 AM

sorcer1 wrote Jul 5, 2010 at 8:53 AM

Me too.
This is the message when i choose to debug :

An unhandled exception of type 'System.BadImageFormatException' occurred in Indihiang.exe

Additional information: Impossible de charger le fichier ou l'assembly 'System.Data.SQLite, Version=1.0.64.0, Culture=neutral, PublicKeyToken=db937bc2d44ff139' ou une de ses dépendances. Tentative de chargement d’un programme de format incorrect.

sukeshak wrote Sep 2, 2010 at 3:20 PM

Great app and good job!

Since it was crashing, I ran the app under windbg and found that SQLLite was throwing the BadImageFormatException error.
If you have x64 OS then install x64 version of the application which fixes this issue. Right side link for download by default installs x86 version.

wrote Jan 26, 2012 at 12:26 PM

wrote Dec 12, 2012 at 3:00 PM

wrote Feb 21, 2013 at 11:54 PM