Results 1 to 3 of 3

Thread: SQL Error on Case save/creation

  1. #1
    dstrickler is offline Sugar Community Member
    Join Date
    Mar 2006
    Posts
    77

    Default SQL Error on Case save/creation

    At some point today, we started getting the wollowing SQL error (comes up on its own white screen):

    Query Failed:INSERT into cases set id='7995471e-3a2d-328f-b5af-44b2ad09f4a6', date_entered='2006-07-10 19:41:54', date_modified='2006-07-10 19:41:54', modified_user_id='3c912dc3-d63f-b27e-7424-4459113672b8', assigned_user_id='3c912dc3-d63f-b27e-7424-4459113672b8', created_by='3c912dc3-d63f-b27e-7424-4459113672b8', team_id='dd8a66ba-3317-9347-4bc2-44370550fe54', deleted='0', name='test', account_name='SPN, Inc.', account_id='09873b16a70da330d7c73345860b8da9', status='New', priority='P2', description='test', resolution=null, system_id='1'::MySQL error 1062: Duplicate entry '2147483647-1' for key 2

    I can't figure out why this is happening, and when I try and Repair the database, I get a "Not A Valid Entry Point" when it tries to run the SQL commands.

    Config:SuSE 10, MySQL, Sugar v4.2 Pro

    Any clues?
    Dave Strickler
    MailWise LLC
    www.mailwise.com
    Intelligent Email Protection, compatible with Sugar




  2. #2
    dstrickler is offline Sugar Community Member
    Join Date
    Mar 2006
    Posts
    77

    Default Re: SQL Error on Case save/creation

    Support solved this one for me. It was because I imported all the data into Cases via PHP code I wrote, and I didn't reset the auto increment counter in SQL. So, the next Case was the whopping big number, and MySQL was choking on it.

    By doing an ALTER TABLE, I was able to reset the Auto Increment number to the next case number that should be created, and it worked just fine.
    Dave Strickler
    MailWise LLC
    www.mailwise.com
    Intelligent Email Protection, compatible with Sugar




  3. #3
    jgyc430 is offline Sugar Community Member
    Join Date
    Mar 2008
    Posts
    19

    Default Convert Lead error:

    Hi,

    I hope someone can help me out. It just happened 2 hours ago that when i convert a lead to contacts it showed the following error.

    It says at the end MySQL error 1062: Duplicate entry '48a3e7f7-8543-07d2-8c93-4a8c46878af9' for key 1. Contact was created, no problem. However, Leads status was not changed to "Converted".

    Please Help me.....
    Attached Images Attached Images  

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •