Closed GoogleCodeExporter closed 8 years ago
Please check the error.log file (can bring it up with the Error button in the
About
window) and get the error log that corresponds to this and copy it here. As a
workaround, close tabs until the error goes away (it should be caused by one of
the
plugins), and don't open that tab while a parse is running.
Original comment by Kinemati...@gmail.com
on 18 Dec 2009 at 6:27
WaywardGamers.KParser.ParserCore, Version=1.4.7.0, Culture=neutral,
PublicKeyToken=null
Error severity level: Error
System.Data.StrongTypingException
System.Data.StrongTypingException: The value for column 'EnemyID' in table
'Battles'
is DBNull. ---> System.InvalidCastException: Specified cast is not valid.
at WaywardGamers.KParser.KPDatabaseDataSet.BattlesRow.get_EnemyID()
--- End of inner exception stack trace ---
at WaywardGamers.KParser.KPDatabaseDataSet.BattlesRow.get_EnemyID()
at
WaywardGamers.KParser.Plugin.EnfeeblePlugin.<>c__DisplayClass37.<ProcessData>b__
1d(InteractionsRow
i)
at System.Linq.Enumerable.WhereArrayIterator`1.MoveNext()
at System.Linq.Enumerable.Count[TSource](IEnumerable`1 source)
at WaywardGamers.KParser.Plugin.EnfeeblePlugin.<ProcessParalyze>b__44(EnfeebleGroup a)
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Linq.Enumerable.Sum(IEnumerable`1 source)
at System.Linq.Enumerable.Sum[TSource](IEnumerable`1 source, Func`2 selector)
at
WaywardGamers.KParser.Plugin.EnfeeblePlugin.ProcessParalyze(EnumerableRowCollect
ion`1
paralyzeSet, StringBuilder& sb, List`1& strModList)
at WaywardGamers.KParser.Plugin.EnfeeblePlugin.ProcessData(KPDatabaseDataSet dataSet)
at WaywardGamers.KParser.Plugin.BasePluginControl.HandleDataset(KPDatabaseDataSet
databaseChanges)
Contained Exception:
System.InvalidCastException: Specified cast is not valid.
at WaywardGamers.KParser.KPDatabaseDataSet.BattlesRow.get_EnemyID()
Original comment by proxitel...@gmail.com
on 18 Dec 2009 at 7:51
I don't open the Enfeebling tab and I don't see the error anymore :)
Original comment by proxitel...@gmail.com
on 18 Dec 2009 at 7:54
Ok, a fix has been checked in. Next release won't be til after Christmas,
though.
Original comment by Kinemati...@gmail.com
on 18 Dec 2009 at 8:51
Was wrong. New version released that includes this fix.
Original comment by Kinemati...@gmail.com
on 19 Dec 2009 at 7:48
Original issue reported on code.google.com by
proxitel...@gmail.com
on 17 Dec 2009 at 11:08Attachments: