Post reply

failed intergrity check job

  • May 7, 2010 at 11:06 am

    #140848

    Hi experts,

    Last day we had created an integrity check job on one of our production servers.But it fails evrytime and we then created a job to execute "DBCC CHECKDB" command.But we found that a "communication link failure" occurred during the execution of the job. So the job execution failed at that moment with the following error messages.

    1. [sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746; message = [Microsoft][SQL Native Client]TCP Provider: An existing

    connection was forcibly closed by the remote host.

    2. [sqsrvres] printODBCError: sqlstate = 08S01; native error = 2746; message = [Microsoft][SQL Native Client]Communication link failure

    3. [sqsrvres] OnlineThread: QP is not online.

    4. [sqsrvres] CheckQueryProcessorAlive: sqlexecdirect failed.

    Please advice on this....

    Thanks And Regards,

    J

  • May 10, 2010 at 4:48 am

    #1164908

    Are you using windows authentication??

    Whats your server configuration?

    Are you remotely accessing the server or configuring job from any client machine??

    whats your query timeout??

    Hope you tried DBCC CHECKDB from query windows,wats the result?

    The error seems like a network issue.Think its time for your network team to do some work 😀

    If your server is in cluster ,check heart beat. Also check netbios/wins disabled or enabled?

  • May 10, 2010 at 5:03 am

    #1164909

    Do you have any other heavy jobs running at the same time??

  • May 10, 2010 at 8:02 am

    #1164999

    Hi ,

    Pls find the latest error while running the DBCC CHECKDB Command

    1.Msg 64, Sev 16, State 1: TCP Provider: The specified network name is no longer available. [SQLSTATE 08S01]

    2.Msg 64, Sev 16, State 1: Communication link failure [SQLSTATE 08S01].

    We ran the CHECKDB command thrice and found the same error specified above

    Ist attempt failed after 14 minutes while running the Job

    2nd attempt failed after 55 seconds

    3rd attempt failed after 1hr.30 min

    But when we run through query analyzer in same server it will complete successfully in around 3 hours.

    But when we run this as maint.plan task or as a job it fails

    We created a maint.plan in another server with the same query as a t-sql task and run the same and it worked.(But this cannot implemented )..!!!!

    My doubts are

    1)Why this is not running as task in maint.plan or as a job in the same server?

    2) Is this because of Cluster environment.

    3) It there a method to overcome this Issue

    Kindly Help

    Regards

    Milesh

  • May 10, 2010 at 10:40 am

    #1165113

    Ratheesh,

    We are using windows authentication for login.

    Its a windows 2003 server holding an sql2005 enterprose edition.

    Its a very critical production server.

    We are having windows authentication with full privileges on that server and we connect remotely to machine after establishing a VPN.

    And the server is a cluster.

    Think Milesh had posted replies for al other queries.

    Any more questions????

  • May 10, 2010 at 10:19 pm

    #1165325

    Milesh,

    This is the same thing am looking for!!!:-)

  • May 11, 2010 at 11:09 am

    #1165708

    Jobychetta,

    u too

  • May 12, 2010 at 8:53 pm

    #1166601

    Try using SQL Authentication..

Viewing 8 posts - 1 through 7 (of 7 total)

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