Wotnumbers bug on Windows 10 - DateTime error [FIXED]
I've been trying to get this thing to work for some time now and can't. Every time I try to make a new DB or use an o...

I've been trying to get this thing to work for some time now and can't. Every time I try to make a new DB or use an old one I get these errors. I am using 64-bit windows 10 pro . I had Wotnumbers setup on win 7 pro and it worked like a charm.

pic1


  • BadButton - 03.08.2015

    Hmm, I did teste Wot Numbers on a Win 10 technical preview for a while a go without any problems. I'll try to get hand of a Win 10 and test once more. 

    When is the error occuring? On startup or after you change to tank/battle view?

  • BadButton - 03.08.2015

    Could you turn on "Debug mode" from menu: Settings + Application Settings.

    Then delete the Log.txt file (from menu: Settings + Show Log File)

    Then restart or make the error occur in any way, and then copy the content of the logfile in a comment below.

  • Pottulaari - 03.08.2015

    You made my older topic as duplicate for this, but what ever.

    I caused the error by playing CW-match. (new map) It works for me with other than CW matches.

    Here is my log (Wot Number actually crashed when I first had those errors twice):

    ------------------------cut----------------------

    **************************************************
    Start logging: 3.8.2015 21.32.07
    **************************************************

    3.8.2015 21.32.11    '********* Application startup - Wot Numbers 0.9.3 (33423) *********'

    3.8.2015 21.36.15     > > IronPython exception thrown converted battle DAT-file to JSON file: C:\Users\USER\AppData\Roaming\Wot Numbers\BattleResult\13806530293904284.dat

    {
    3.8.2015 21.36.15 ### EXCEPTION ###
       Source:          Microsoft.Dynamic
       TargetSite:      System.Object CheckAndThrow(System.Object)
       Data:            System.Collections.ListDictionaryInternal
       Message:         No module named battle_results_shared_16
       Details:
       ConvertBattleUsingPython exception running: C:\Program Files (x86)\Wot Numbers\dossier2json\wotbr2j.py with args: C:\Users\USER\AppData\Roaming\Wot Numbers\BattleResult\13806530293904284.dat -f
    }

    [Edit: removed stack trace / repeated errors]

    ###### WoTDC2J 0.9.9.0 DOSSIER FILE CONVERT TO JSON
    Time: 2015-08-03 21:36:16.315000
    Encoding: ascii - mbcs
    Processing C:\Users\USER\AppData\Roaming\Wot Numbers\dossier.dat
    Dossier version 22
    Wrong number of frags for Bat.-Chatillon 25 t, 92: 140 = 117 + 0 + 0 + 7 + 15 + 0
    Wrong number of frags for E 100, 92: 100 = 59 + 0 + 0 + 22 + 17 + 0
    ###### Done!

    3.8.2015 21.36.17     > > Renamed copied dossierfile as previous file

    {
    3.8.2015 21.36.17 ### EXCEPTION ###
       Source:          mscorlib
       TargetSite:      System.DateTime ParseExactMultiple(System.String, System.String[], System.Globalization.DateTimeFormatInfo, System.Globalization.DateTimeStyles)
       Data:            System.Collections.ListDictionaryInternal
       Message:         String was not recognized as a valid DateTime.
       Stack Trace:
       at System.DateTimeParse.ParseExactMultiple(String s, String[] formats, DateTimeFormatInfo dtfi, DateTimeStyles style)
       at System.Data.SQLite.SQLiteConvert.ToDateTime(String dateText, SQLiteDateFormats format, DateTimeKind kind, String formatString)
       at System.Data.SQLite.SQLite3.GetDateTime(SQLiteStatement stmt, Int32 index)
       at System.Data.SQLite.SQLite3.GetValue(SQLiteStatement stmt, SQLiteConnectionFlags flags, Int32 index, SQLiteType typ)
       at System.Data.SQLite.SQLiteDataReader.GetValue(Int32 i)
       at System.Data.SQLite.SQLiteDataReader.GetValues(Object[] values)
       at System.Data.ProviderBase.SchemaMapping.LoadDataRow()
       at System.Data.Common.DataAdapter.FillLoadDataRow(SchemaMapping mapping)
       at System.Data.Common.DataAdapter.FillFromReader(DataSet dataset, DataTable datatable, String srcTable, DataReaderContainer dataReader, Int32 startRecord, Int32 maxRecords, DataColumn parentChapterColumn, Object parentChapterValue)
       at System.Data.Common.DataAdapter.Fill(DataTable[] dataTables, IDataReader dataReader, Int32 startRecord, Int32 maxRecords)
       at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
       at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
       at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
       at WinApp.Code.DB.FetchData(String sql, Boolean ShowError)
       Details:
       SELECT * FROM playerTank WHERE playerId=1 AND tankId=2865;
    }

    [Edit: removed stack trace / repeated errors]
    ------------------------cut----------------------

  • Gekko1 - 03.08.2015

    I get the error on startup.  Here is the log you asked for.

    **************************************************
    Start logging: 3.8.2015 23.32.03
    **************************************************


    3.8.2015 23.32.03    '********* Application startup - Wot Numbers 0.9.3 (33423) *********'

    ###### WoTDC2J 0.9.9.0 DOSSIER FILE CONVERT TO JSON
    Time: 2015-08-03 23:32:07.796000
    Encoding: ascii - mbcs
    Processing C:\Users\USER\AppData\Roaming\Wot Numbers\dossier.dat
    Dossier version 22
    ###### Done!

    3.8.2015 23.32.09     > > Renamed copied dossierfile as previous file

    {
    3.8.2015 23.32.09 ### EXCEPTION ###
       Source:          mscorlib
       TargetSite:      System.DateTime ParseExactMultiple(System.String, System.String[], System.Globalization.DateTimeFormatInfo, System.Globalization.DateTimeStyles)
       Data:            System.Collections.ListDictionaryInternal
       Message:         String was not recognized as a valid DateTime.

       Details:
       SELECT * FROM playerTank WHERE playerId=1 AND tankId=2113;
    }

    [Edit: removed stack trace / repeated errors]


  • BadButton - 04.08.2015

    OK, I can see you got the same error - could you send me a copy of your database? You will locate the databasefile normally named: WotNumbers.db here: %appdata%\Wot Numbers\Database.

    Please send it to webmaster@wotnumbers.com

  • Pottulaari - 05.08.2015

    I sent mine this morning.

  • Gekko1 - 06.08.2015

    I send mine 2 days ago.

  • BadButton - 06.08.2015

    Thanx for db, I got them both. Will take some days before I am able to look at it. 

  • BadButton - 08.08.2015

    I have now got hold of a Windows 10 OS, and has been able to reproduce the problem. Hopefully a fix will be available during the weekend.

  • Pottulaari - 08.08.2015

    As a dev I think it's half solved if you are able to reproduce it yourself. I won't be able to test it until late next week so no need to hurry for me ;)

  • BadButton - 08.08.2015

    I totally agree Pottulaari! I found that Windows 10 language / datetime settings affected how datetime is handled by .NET. I have made a fix for this in version 0.9.4 - now released.

    The the version solved the problem on my my test rig - please post a comment below if it worked or not tongue-out

  • Pottulaari - 09.08.2015

    Well as this was last time to try until next late next week I did test.

    Unfortunately it doesn't seem to help. I tried to put myself to offline mode and run "Force Update All Data", but no change.

    If it has any help, I use Finnish date time formatting, but have English Windows 10.

    Here is log for "Force Update All Data":

    -----cut-----

    **************************************************
    Start logging: 9.8.2015 0.58.47
    **************************************************


    9.8.2015 0.58.47    '********* Application startup - Wot Numbers 0.9.4 (38919) *********'

    9.8.2015 0.58.47    // Automatically fetch new battles stopped
    9.8.2015 0.59.02    // Running battle check with force update...
    9.8.2015 0.59.02    // Manual run, looking for new dossier file
    9.8.2015 0.59.02     > Start analyze dossier file
    9.8.2015 0.59.02     > > Dossier file handling started
    9.8.2015 0.59.02     > > Start converting Dossier DAT-file to json
    9.8.2015 0.59.05     > > Finish converted Dossier DAT-file to json
    9.8.2015 0.59.05     > > IronPython output:

    ###### WoTDC2J 0.9.9.0 DOSSIER FILE CONVERT TO JSON
    Time: 2015-08-09 00:59:04.007000
    Encoding: ascii - mbcs
    Processing C:\Users\USER\AppData\Roaming\Wot Numbers\dossier.dat
    Dossier version 22
    Wrong number of frags for Object 907, 92: 80 = 20 + 0 + 0 + 14 + 44 + 0
    Wrong number of frags for T110E5, 92: 55 = 36 + 0 + 0 + 10 + 5 + 0
    Wrong number of frags for IS-7, 92: 157 = 129 + 0 + 0 + 18 + 5 + 0
    Wrong number of frags for Bat.-Chatillon 25 t, 92: 140 = 117 + 0 + 0 + 7 + 15 + 0
    Wrong number of frags for IS-4, 92: 182 = 180 + 0 + 0 + 0 + 1 + 0
    Wrong number of frags for E 100, 92: 100 = 59 + 0 + 0 + 22 + 17 + 0
    ###### Done!

    9.8.2015 0.59.05     > > Renamed copied dossierfile as previous file

    {
    9.8.2015 0.59.05 ### EXCEPTION ###
       Source:          mscorlib
       TargetSite:      System.DateTime ParseExactMultiple(System.String, System.String[], System.Globalization.DateTimeFormatInfo, System.Globalization.DateTimeStyles)
       Data:            System.Collections.ListDictionaryInternal
       Message:         String was not recognized as a valid DateTime.
       Stack Trace:
       at System.DateTimeParse.ParseExactMultiple(String s, String[] formats, DateTimeFormatInfo dtfi, DateTimeStyles style)
       at System.Data.SQLite.SQLiteConvert.ToDateTime(String dateText, SQLiteDateFormats format, DateTimeKind kind, String formatString)
       at System.Data.SQLite.SQLite3.GetDateTime(SQLiteStatement stmt, Int32 index)
       at System.Data.SQLite.SQLite3.GetValue(SQLiteStatement stmt, SQLiteConnectionFlags flags, Int32 index, SQLiteType typ)
       at System.Data.SQLite.SQLiteDataReader.GetValue(Int32 i)
       at System.Data.SQLite.SQLiteDataReader.GetValues(Object[] values)
       at System.Data.ProviderBase.SchemaMapping.LoadDataRow()
       at System.Data.Common.DataAdapter.FillLoadDataRow(SchemaMapping mapping)
       at System.Data.Common.DataAdapter.FillFromReader(DataSet dataset, DataTable datatable, String srcTable, DataReaderContainer dataReader, Int32 startRecord, Int32 maxRecords, DataColumn parentChapterColumn, Object parentChapterValue)
       at System.Data.Common.DataAdapter.Fill(DataTable[] dataTables, IDataReader dataReader, Int32 startRecord, Int32 maxRecords)
       at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
       at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
       at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
       at WinApp.Code.DB.FetchData(String sql, Boolean ShowError)
       Details:
       SELECT * FROM playerTank WHERE playerId=1 AND tankId=2865;
    }



    {
    9.8.2015 0.59.41 ### EXCEPTION ###
       Source:          mscorlib
       TargetSite:      System.DateTime ParseExactMultiple(System.String, System.String[], System.Globalization.DateTimeFormatInfo, System.Globalization.DateTimeStyles)
       Data:            System.Collections.ListDictionaryInternal
       Message:         String was not recognized as a valid DateTime.
       Stack Trace:
       at System.DateTimeParse.ParseExactMultiple(String s, String[] formats, DateTimeFormatInfo dtfi, DateTimeStyles style)
       at System.Data.SQLite.SQLiteConvert.ToDateTime(String dateText, SQLiteDateFormats format, DateTimeKind kind, String formatString)
       at System.Data.SQLite.SQLite3.GetDateTime(SQLiteStatement stmt, Int32 index)
       at System.Data.SQLite.SQLite3.GetValue(SQLiteStatement stmt, SQLiteConnectionFlags flags, Int32 index, SQLiteType typ)
       at System.Data.SQLite.SQLiteDataReader.GetValue(Int32 i)
       at System.Data.SQLite.SQLiteDataReader.GetValues(Object[] values)
       at System.Data.ProviderBase.SchemaMapping.LoadDataRow()
       at System.Data.Common.DataAdapter.FillLoadDataRow(SchemaMapping mapping)
       at System.Data.Common.DataAdapter.FillFromReader(DataSet dataset, DataTable datatable, String srcTable, DataReaderContainer dataReader, Int32 startRecord, Int32 maxRecords, DataColumn parentChapterColumn, Object parentChapterValue)
       at System.Data.Common.DataAdapter.Fill(DataTable[] dataTables, IDataReader dataReader, Int32 startRecord, Int32 maxRecords)
       at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
       at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
       at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
       at WinApp.Code.DB.FetchData(String sql, Boolean ShowError)
       Details:
       SELECT * FROM playerTank WHERE playerId=1 AND tankId=2865;
    }


    9.8.2015 1.01.01    // Application Exit

    -----cut-----

  • BadButton - 09.08.2015

    Could you try to create a new database, your current database has invalid data - probably because of this datetime-problem.

    Use Settings menu + Application Settings, or just delete the current config file (config.json) located here: %appdata%\Wot Numbers

  • Gekko1 - 09.08.2015

    I got Wotnumbers working now cool I can't use my old databases but I guess that is not a big loss.

  • BadButton - 09.08.2015

    It will probably be possible to repair the SQLite database, using a database management tool for SQLite. If it's OK to start with a new DB then go for it - and you save some work foot-in-mouth

  • Pottulaari - 09.08.2015

    Well THIS was last time I had until late next week (starting to sound liar)...

    Anyway, creating new database solved the issue. Couldn't care less to fix db by hand.

    Thanks for your hard work!

Sign in for replying to topic Close