Post reply

Error msg , not sure where to go next ?

  • December 12, 2006 at 8:35 am

    #114877

    Afternoon everyone.

    Getting this error msg from a developer.

    IN ERROR HANDLER: 'Column number out of range.'

    IN ERROR HANDLER: 'Attempt to initiate a new SQL Server operation with results p

    ending.'

    Could not retrieve messages for subsystem 'adp'

    Cannot get message for code 0x600033 (subsystem=adp)

     

    Nothing written to event log , or sql log.

    Any ideas of what or where to look ?

    Is it an SQL issue or Developer issue ?

     

    Thanks everyone

    SQL is SQL 2000 , sp 4

  • December 12, 2006 at 8:37 am

    #677500

    >>IN ERROR HANDLER: 'Column number out of range.'

    I would guess an issue with referencing columns in a resultset by ordinal position instead of name.

    This is often seen where a developer performs a "SELECT * FROM .." statement, assuming that "*" is a certain number of table columns. If someone changes the table or view definition to contain less columns, their assumptions about number of column ordinal positions is wrong.

    Just a guess ...

  • December 12, 2006 at 8:38 am

    #677501

    This is the closest error I can think of in SQL server (which comes from a bad practice but I guess you already know that .

    Select name from dbo.SysObjects ORDER BY 2 --(2nd column of the query)

  • December 12, 2006 at 8:41 am

    #677502

    this sounds like an error returned from a program, not a SQL server error. you'll need to review the source code of the application raising the error.

    you might want to look for a loop that is saying something like For i=0 to rs.Fields.Count instead if rs.Fields.Count -1

     

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • December 12, 2006 at 8:47 am

    #677504

    many thanks everyone , all good stuff. Keep em coming so I have something to back with !

  • December 12, 2006 at 3:16 pm

    #677648

    Check what are the procedure/statements executed by the error page.

    Run the sql trace to see the procs are executed or not..

    Include error and warning in sql trace to find sql error which are not logged in sql error log or event log...

     

    MohammedU
    Microsoft SQL Server MVP

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

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