SQL Server Performance

Communication Link Failure

Discussion in 'General DBA Questions' started by hjyoungii, Sep 18, 2006.

  1. hjyoungii New Member

    We are running MSSQL 2000 and every so often we get the following when running jobs:

    Executed as user: MANSFIELDPVSQL. OLE DB provider 'MSDASQL' reported an error. [SQLSTATE 42000] (Error 7399) Driver's SQLSetConnectAttr failed] [SQLSTATE 01000] (Error 7312) Communication link failure. comm rc=12 - CWB0999 - Unexpected error: unexpected return code 12] [SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB Provider 'MSDASQL' IDBInitialize::Initialize returned 0x80004005: ]. [SQLSTATE 01000] (Error 7300). The step failed.

    If we reboot the server, we are able to run the job.

    Is there something we can do to get so this does not happen?

    I am new to MSSQL.
  2. dineshasanka Moderator

  3. hjyoungii New Member

    This does not tell what is wrong. The errors come out on jobs that start thru the job scheduler. Sometimes we can go for weeks without an error. Sometimes we get hit 2 or three times in one week.

    Error 7399 is for authority these jobs use SA. 7312 from what I see is for a linkage to Oracle. We do not use Oracle.

    Has anyone had similar errors? If so, how did this get solved?

    Anyone have any ideas on this?

Share This Page