Post reply

"Query timeout expired"

  • November 1, 2010 at 9:00 am

    #143326

    Hi, ALL

    CAN SOME TELL ME WHATS GOING ON HERE OR ANY SUGGESTIONS

    OLE DB provider "SQLNCLI" for linked server "TFSQL04" returned message "Query timeout expired".

    Msg 7399, Level 16, State 1, Procedure reportTecsysReconciliation, Line 34

    The OLE DB provider "SQLNCLI" for linked server "TFSQL04" reported an error. Execution terminated by the provider because a resource limit was reached.

    Msg 7421, Level 16, State 2, Procedure reportTecsysReconciliation, Line 34

    Cannot fetch the rowset from OLE DB provider "SQLNCLI" for linked server "TFSQL04". .

    THANKS FOR LOOKING INTO IT

  • November 1, 2010 at 9:27 am

    #1244885

    @ harita

    When do you get this error, while running a proc?

    Can you check if your sql services are running?

    Or see errors in sql logs?

    Regards,

    Sushant

    Regards
    Sushant Kumar
    MCTS,MCP

  • November 1, 2010 at 9:32 am

    #1244888

    Hi,

    i am getting this error when i run a stored pro

  • November 1, 2010 at 9:35 am

    #1244889

    @ harita

    You need to increase the remote query timeout option in SSMS

    SSMS-->prop-->connections-->remote qery timeout--> wats the value??

    Regards,

    Sushant

    Regards
    Sushant Kumar
    MCTS,MCP

  • November 1, 2010 at 9:45 am

    #1244893

    i think the value is 0

  • November 1, 2010 at 9:50 am

    #1244895

    i didnt understand the path

    SSMS-->prop-->connections-->remote qery timeout--> wats the value??

    can you be more specific

  • November 1, 2010 at 9:51 am

    #1244898

    which sql server version are you running?

    Regards
    Sushant Kumar
    MCTS,MCP

  • November 1, 2010 at 9:52 am

    #1244899

    ya i found it teh remote query timeout is 600

  • November 1, 2010 at 9:54 am

    #1244901

    change it to 0 and then again run the stored proc

    Regards,

    Sushant

    Regards
    Sushant Kumar
    MCTS,MCP

  • November 1, 2010 at 10:11 am

    #1244911

    yes i did change it to 0 , but can you explain me whats going on here, we run this report every moth and never had this problem but y now

  • November 1, 2010 at 10:18 am

    #1244918

    Did it run now or not?

    You may be running this every month, but usually it got run under 600 secs (10 mins) but now, maybe due to more data or slower speed thru network that query might be taking more than 10 mins to run and so it fails accordin to that setting.

    Regards,

    Sushant

    Regards
    Sushant Kumar
    MCTS,MCP

  • November 1, 2010 at 12:05 pm

    #1244984

    harita (11/1/2010)

    yes i did change it to 0 , but can you explain me whats going on here, we run this report every moth and never had this problem but y now

    Perhaps indexes have become fragmented or other performance problems have arisn.

Viewing 12 posts - 1 through 11 (of 11 total)

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