com.microsoft.sqlserver.jdbc.SQLServerException

The TDS protocol stream is not valid.

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web114

  • via Unknown by 2747946,
  • via Unknown by Unknown author,
  • Stack trace

    • com.microsoft.sqlserver.jdbc.SQLServerException: The TDS protocol stream is not valid. at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.throwInvalidTDS(Unknown Source) at com.microsoft.sqlserver.jdbc.TDSReader.throwInvalidTDS(Unknown Source) at com.microsoft.sqlserver.jdbc.TDSReader.skip(Unknown Source) at com.microsoft.sqlserver.jdbc.ServerDTVImpl.skipValue(Unknown Source) at com.microsoft.sqlserver.jdbc.DTV.skipValue(Unknown Source) at com.microsoft.sqlserver.jdbc.Column.skipValue(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerResultSet.skipColumns(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerResultSet.discardCurrentRow(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerResultSet.fetchBufferNext(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerResultSet.close(Unknown Source) at oracle.odi.runtime.agent.execution.sql.concurrent.FastJDBCRecordSet.close(FastJDBCRecordSet.java:124) at oracle.odi.runtime.agent.execution.DataMovementTaskExecutionHandler.handleTask(DataMovementTaskExecutionHandler.java:103) at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2913) at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2625) at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:558) at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:464) at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:2093) at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$2.doAction(StartSessRequestProcessor.java:366) at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:216) at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.doProcessStartSessTask(StartSessRequestProcessor.java:300) at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor.access$0(StartSessRequestProcessor.java:292) at oracle.odi.runtime.agent.processor.impl.StartSessRequestProcessor$StartSessTask.doExecute(StartSessRequestProcessor.java:855) at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:126) at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$2.run(DefaultAgentTaskExecutor.java:82) at java.lang.Thread.run(Thread.java:724)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown visitor
    Unknown visitor2 times, last one
    SteVio1989SteVio1989
    2 times, last one
    Andreas HäberAndreas Häber
    10 times, last one
    abrazenebabrazeneb
    28 times, last one
    Unknown visitor
    Unknown visitorOnce,
    19 more bugmates