Results 1 to 8 of 8
  1. #1
    5 Star Lounger AndrewKKWalker's Avatar
    Join Date
    Apr 2001
    Location
    Cambridge, UK
    Posts
    1,020
    Thanks
    0
    Thanked 3 Times in 3 Posts

    Index Not Found Synchronization Error (2000 SP3)

    I have a database that has been working fine for 6 months.
    Recently we got the error

    Index not found

    When attempting to synchronise the master
    with a replica.
    There is no indication at which point, or which table or record that the missing
    index occurs in. It doesn't even say which database.
    Fantastic error reporting from Microsoft eh....

    The synchronisation fails at this point with no come back.

    I have tries a compact and repair, and this works fine
    but makes no difference to the synchronisation error.

    Anyone got any ideas or experienced this before?
    I would love an answer, even if it is just to say

    Go get the last good backups fella.

    I have attached a copy of the error screen.

    Thanks in anticipation
    Attached Images Attached Images
    Andrew

  2. #2
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Index Not Found Synchronization Error (2000 SP3)

    Is this a full or partial replica? In either case, take a look at Michael Kaplin's site http://www.trigeminal.com. He wrote a substitute for replication manager that might interest you.
    Charlotte

  3. #3
    5 Star Lounger AndrewKKWalker's Avatar
    Join Date
    Apr 2001
    Location
    Cambridge, UK
    Posts
    1,020
    Thanks
    0
    Thanked 3 Times in 3 Posts

    Re: Index Not Found Synchronization Error (2000 SP3)

    It is a full Replica.

    One is the Design Master, the other is a First Generation Full Replica.
    Andrew

  4. #4
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Index Not Found Synchronization Error (2000 SP3)

    Do you have cascading deletes turned on? Is this a front or back end? Were any design changes made, like tables, fields or indexes removed?
    Charlotte

  5. #5
    5 Star Lounger AndrewKKWalker's Avatar
    Join Date
    Apr 2001
    Location
    Cambridge, UK
    Posts
    1,020
    Thanks
    0
    Thanked 3 Times in 3 Posts

    Re: Index Not Found Synchronization Error (2000 SP3)

    To answer the questions in sequence

    1. Yes Cascade Deletes is turned on.
    I do not know if any deletes took place

    2. It is a back end containing only the data tables.

    3. NO design changes of any sort were made to any of the tables.
    Nor were any indexes changed, removed or added in either of the databases.
    This end users do not see this database for any form of design access.
    Andrew

  6. #6
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Index Not Found Synchronization Error (2000 SP3)

    I asked about the cascading deletes because Michael Kaplin seems to identify that setting with synchornization problems. Since I don't use it very often, I've never run across that particular bug. However, deletes may not be handled in the correct order in synchronization, so you might try turning it off in the master to see if it makes a difference.

    I asked about design changes because they get synced first, before data changes, which can lead to some interesting problems when synchronizing both, especially if you delete a table or a field. <img src=/S/nuts.gif border=0 alt=nuts width=15 height=15>
    Charlotte

  7. #7
    5 Star Lounger AndrewKKWalker's Avatar
    Join Date
    Apr 2001
    Location
    Cambridge, UK
    Posts
    1,020
    Thanks
    0
    Thanked 3 Times in 3 Posts

    Re: Index Not Found Synchronization Error (2000 SP3)

    Found the Problem and Corrected, but a pain to do because NO simple fix.
    I looked at the Link field (Autonumber-Random) in the data tables in both.

    Matched against these.
    In one Parent table I found that an Identical record in the two tables had a different Unique Random ID.
    This was the Only Data Difference other than the fact that there was a Child table record in one database and not the other.

    Correction... Delete rogue record in Child of Replica and allow Synchronisation to Re-Create it from the Master.

    Cause???

    Probably the following Scenario.

    On one Replica a Record had been Deleted and then Re-Created Manually (Getting a different Unique ID)
    On the other Replica it still existed.

    This infringed some Unique Index rules on other fields.

    Result I believe Synchronization error
    and unbelievably poor error trapping and reporting from a Microsoft Routine, (no suprise there then eh!)
    Since Synchronization must check at transaction level there is NO reason why it cannot determine
    where the error is occuring.

    PHEW!!!!

    Thanks for help because it pointed me to deletion as a probable cause.

    NEW rules now in place for users, and the person responsible terminated.
    Andrew

  8. #8
    5 Star Lounger AndrewKKWalker's Avatar
    Join Date
    Apr 2001
    Location
    Cambridge, UK
    Posts
    1,020
    Thanks
    0
    Thanked 3 Times in 3 Posts

    Re: Index Not Found Synchronization Error (2000 SP3)

    NOPE, that was not the cause.

    I did fix the problem, but having tried to re-create the problem by doing stupid things
    I cannot.

    Very odd.

    In that case I have NO idea why it went ape, but at least it's fixed
    Andrew

Posting Permissions

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