in

InaPlex Forums

Forums and downloads for InaPlex customers and partners.

MVException: no = 2064 Fail seeking on index CONTACT1

Last post 01-05-2009 3:00 by admin. 4 replies.
Page 1 of 1 (5 items)
Sort Posts: Previous Next
  • 12-30-2008 22:41

    MVException: no = 2064 Fail seeking on index CONTACT1

    Hi! I'm testing a simple import from Access 2003 to Goldmine 8.03.80716 on SQL Server 2005.

    This error pops up: MVException: no = 2064 Fail seeking on index CONTACT1 with value C3UXIK6)Z0)Z W<

    This RECID does exist in the CONTACT1 table, and I have rebuilt the index, but I still get the error.
    What am I missing? Or is this a database issue?

    Thanks in advance for direction,
    Sue Burke

     

    Sue Burke/IT
    The JESUS Film Project
    www.JesusFilm.org
    Filed under:
  • 12-31-2008 19:29 In reply to

    Re: MVException: no = 2064 Fail seeking on index CONTACT1

    Hi Sue

    This will almost certainly be a GoldMine problem of some kind. This error message is reported by GoldMine API when Inaport tries to position on a record.

    Might be worthwhile checking with your GoldMine partner to see if they can advise.

    Regards

    David

  • 12-31-2008 21:48 In reply to

    Re: MVException: no = 2064 Fail seeking on index CONTACT1

    Thank you. Will do.

    I sure appreciate the quick response to my issues. Thanks again!

    Sue Burke/IT
    The JESUS Film Project
    www.JesusFilm.org
  • 12-31-2008 23:40 In reply to

    Re: MVException: no = 2064 Fail seeking on index CONTACT1

    Our GM partner took a look at my profile and recommended a change from #RECID to #ACCOUNTNO in the Relationships tab. This has resolved the issue.

    With appreciation for your kind assistance, -s

    Sue Burke/IT
    The JESUS Film Project
    www.JesusFilm.org
  • 01-05-2009 3:00 In reply to

    Re: MVException: no = 2064 Fail seeking on index CONTACT1

    No problem

    Regards

    Admin

Page 1 of 1 (5 items)
InaPlex Limited 2011