windows 10 Timeslips 2016 - error message tsystemexceptionc (EaccessViolation) on startup

Hi there, I had to update to windows 10, and we also upgraded Timeslips from 2014 to 2016.  after the upgrades (a few days later) we started to receive the following error message after you place the date (immediately after starting timeslips), all functionality is frozen within the program...any thoughts?

  

  • 0
    Is that the entire message? Are there any other details or information under a MORE button?
  • 0 in reply to Nancy Duhon
    Okay, I didn't start this thread but I have the same violation when importing time from a csv file. The full error message is

    Sage Timeslips has encountered an error
    Address violation error. This error is sometimes serious and the program may need to be exited. Often it indicates that some data is corrupt in memory. If the program was reading from a file, data in that file may be damaged.
    Area: System Error
    Error Code: 2
    Class: tSystemExceptionC (EAccessViolation)
    Version: 25.5.5.132

    I have double checked the "selected fields/source data" and there doesn't seem to be a conflict there.
    Each time I try to run an import, I am asked to match Time.Nickname 1 with the timekeeper (I am the only one) and the "Clie.Nickname 1"
    The first of four timeslips are imported and the other three are ignored
    Journal says
    "5/19/2016 13:18:06 C:\Credenza\timeslips\credenza.tpl
    Get Data From: C:\Credenza\timeslips\PostedEntriesFor5.19.2016-110 PM33.TXT
    Put Data Into: Slip
    Import finished. Records Imported: 1 Skipped: 0 Failed: 0"
  • 0 in reply to richjenkins
    Given that the area of the program where you are working is completely different, the issue may or may not be the same.
    First I would exit Timeslips and clear temp files from your computer
    Then open TSImport from outside of Timeslips - start > all programs >Timeslips > TSimport and see if that makes a difference
    The reason why you have to match the timekeeper each time is because you have not saved the template with the matching. Before you exit do a save and it will save the default matching.
  • 0 in reply to Caren2
    Caren
    Tried the temp delete before posting.
    Also, yes I had "saved" the template after matching timekeeper and matter (timestamp changed on the *.tpl each time) but the changes were really saved.
    I am on hold for Sage support right now, because now my program says my account number/serial number are invalid.
    Based upon the hold time, I don't think I am the only one having problems.
    Rich
  • 0 in reply to richjenkins
    typo "Also, yes I had "saved" the template after matching timekeeper and matter (timestamp changed on the *.tpl each time) but the changes were NOT really saved.
  • 0 in reply to richjenkins
    Would need to look at it to figure out the issue.