Sage 100

 View Only
  • 1.  V2015 Std. Getting this error message when updati

    Posted 06-17-2016 10:23
      |   view attached
    V2015 Std. Getting this error message when updating PO ROI (batches on) - Error 105 program CI_UpdateInvoiceToAP.pvc Line 866. No nuggets on KB. Any thoughts before I call tech support for the first time this year????


  • 2.  RE: V2015 Std. Getting this error message when updati

    Posted 06-17-2016 10:28
    Check the file in DFDM. See if any record has an odd-looking key. Delete that record. If it's a line record, you should be able to go back and re-enter. If it's a header record, it may not work well. Or you could try rebuilding sort/key files. Here's an ancient link: http://sagecity.na.sage.com/support_communities/sage100_erp/f/92/t/33385


  • 3.  RE: V2015 Std. Getting this error message when updati

    Posted 06-17-2016 10:29
    Some other guy out there :-) has this: http://www.s-consult.com/2008/10/13/support-faq-error-message-105-keyed-file-error/


  • 4.  RE: V2015 Std. Getting this error message when updati

    Posted 06-17-2016 10:35
    Tried rebuilding the AP_InvoiceHIstoryDetail file listed in the error?


  • 5.  RE: V2015 Std. Getting this error message when updati

    Posted 06-17-2016 10:39
    It is just tiring to get people out of the system first but will look at that one first. Thanks everyone!!!


  • 6.  RE: V2015 Std. Getting this error message when updati

    Posted 06-17-2016 11:01
    Jeff - Err 105 is a key block error indicating that the key portion of the data file is corrupt somehow... rebuilding the keys is your only fix... AP_InvoiceHistoryDetail is a reasonable place to start


  • 7.  RE: V2015 Std. Getting this error message when updati

    Posted 06-17-2016 12:54
    that line is for AP_InvoiceHistoryDetail


  • 8.  RE: V2015 Std. Getting this error message when updati

    Posted 06-17-2016 12:55
    Thanks...


  • 9.  RE: V2015 Std. Getting this error message when updati

    Posted 06-19-2016 18:57
    Rebuilding the AP InvoiceHistoryDetail cleared the error. Thanks to everyone.