Message sequencing error

  • We extract data daily from an Cache database using the OpenQuery method of data extract from Cache. We have received a "Message sequencing error" exception from this process. The SQL code used in the OpenQuery for the Cache extract runs correctly on the Cache server with no errors.

    Is there any place I can find what this message actually means?

    The complete message is:

    OLE DB provider "MSDASQL" for linked server "PGH_CACHE" returned message "[Cache ODBC][State : 08S01][Native Code 452]

    [C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe]

    Message sequencing error".

    Msg 7320, Level 16, State 2, Line 1

    Cannot execute the query "SELECT

    a.IEN,

    a.Number,

    a.PatientID,

    a.AdmissionDate,

    %internal(a.AdmissionDate) as AdmissionDateint,

    a.Drg,

    a.DischargeDate,

    %internal(a.DischargeDate) as DischargeDateint

    FROM PTHLDR.Ptf_45 a

    Where a.IEN in(288695,288740,288741)" against OLE DB provider "MSDASQL" for linked server "PGH_CACHE".

    --

    The field that causes the exception is Drg. If I comment out this field the extract works.

    Any help or direction is appreciated.

    Thanks.

  • Have you contacted the vendor?

    “Write the query the simplest way. If through testing it becomes clear that the performance is inadequate, consider alternative query forms.” - Gail Shaw

    For fast, accurate and documented assistance in answering your questions, please read this article.
    Understanding and using APPLY, (I) and (II) Paul White
    Hidden RBAR: Triangular Joins / The "Numbers" or "Tally" Table: What it is and how it replaces a loop Jeff Moden

  • Yes. I have contacted them and an individual has been assigned but no response at this time. My previous contacts with issues have been that when the vendor sees an indication of a SQL message vs. Cache message, coupled with the fact that the query runs correctly on the Cache server, the response is "not my problem".

    I have not actually received this response yet, but will not be surprised.

    Thanks.

  • Did you ever get a response from InterSystems on this? I get the same error occasionally and would like to resolve it if I can.

Viewing 4 posts - 1 through 3 (of 3 total)

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