could not find the index entry for rid

  • Hello ,

     

    I've got a table that gives me above error for the id column.

    I've tried to reindex , repair,checktable the table but then i receive the following error

    [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData (CheckforData()).

    Server: Msg 11, Level 16, State 1, Line 0

    General network error. Check your network documentation.

    Connection Broken

    But there's nothing wrong with the network , when i'll do the same on an other db but the same table it gives no errors.

    Please any help would be very appreciated

    tx

    grtz

    stanja

     

  • Has this connection ever worked? Is the SQL Server a default or named instance? What type of conection are you using a DNS or DNSless connection. This looks like a issue with your connection info like the port is wrong. Please provide the conection string should it be a DNSless connection.

  • The connection is ok , i'll executed the task via the entreprise manager.

    I did the same task at the same table from another db on the same sqlserver and that went well.

    I also loaded the db to my local sql server and then it hangs for 2days without giving  any  error , in fact no message at all

  • Ok, please be more specific what you are trying to do. What are you trying to execute against the SQL Server? A stored Procedure? In-line SQL, a web page from another host?

  • i've received the error message 'could not find the index entry for rid ...' in an asp program.

    So i'm trying to fix this from the query analyzer and i've tried a dbrepair,dbreindexn,dbcheck ,... but none of them fixes the problem

     

  • Please include all the error message you receive besides the one in the initial post noted below.

    [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionCheckForData (CheckforData()).

    Server: Msg 11, Level 16, State 1, Line 0

    General network error. Check your network documentation.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply