Microsoft sql native client error 80040e31 query timeout expired

Knowledge Base Toggle local menu Menus About the team. Knowledge Base Search. Log in. Options Help Chat with a consultant. Include archived documents. Information here may no longer be accurate, and links may no longer be available or reliable. Article: Last Published: Ratings: 0 1. Product s : Backup Exec.

Solution 1. Stop all the Backup Exec services. Additional Step if the registry settings do not change the timeout behavior : Increase the SQL " Remote Query Timeout " value to which is 15 min 4. I changes the script timeout to secs, I herd we need to upgrade MDAC or we need to change connection timeout or we need to cahnge the code.

Can somebody help me with the possible solution. Tuesday, October 30, AM. I tried foll. Its wierd but try once it may work for you. Hope this will help you. Wednesday, November 14, PM. Friday, November 16, AM. Learn more. How to prevent 'query timeout expired'? Asked 7 years, 10 months ago. Active 5 years, 2 months ago. Viewed k times. Connection" Conn.

This is driving me mad. There is no solution, no workaround and worst of all no ideas! Throw me some ideas if you have got them because I'm running out for real now. Only tried to set confirmed to false but still got a time out. So now we know it isn't post specific.

NET Framework: 4. Hate it when it turns out to be so simple after trying so hard. If you are using SqlCommand mySql, then try mySql.

I know its SQL server. Which class do you use to store and execute your SQL command? Sorry, I don't know what you mean. I'm new to it, just changed all databases from the old Access type where this code worked fine. If you mean in my code, I don't have any classes. Maybe you mean what object I use to execute the SQL command?

I will add it to my post, please hang on a second. Show 23 more comments. Active Oldest Votes. Execute This type of recordset is supposed to be read-only and when I was using MS Access as database it did not lock anything.