08s01 Error 64 Communication Link
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: SQL Server Agent Error After Server Restart - error 08s01 microsoft sql native client communication link failure Waiting for SQL Server to recover database 'msdb' SQL Server >
Sqlstate 08s01 Communication Link Failure
SQL Server Tools Question 0 Sign in to vote I have a SQL Server 2012 (sp1) standalone server. error 08s01 sybase odbc driver When I reboot the server, SQL Server restarts without any issues but SQL Server Agent cannot start its jobs according to the schedules set. I am receiving the following error 08s01 datadirect odbc progress openedge wire protocol driver socket closed SQL Server Agent errors: 07/09/2014 13:16:41,,Error,[393] Waiting for SQL Server to recover database 'msdb'... 07/09/2014 13:16:41,,Error,[298] SQLServer Error: 16389
Communication Link Failure Sql
Communication link failure [SQLSTATE 08S01] 07/09/2014 13:16:11,,Error,[298] SQLServer Error: 1236
up Recent PostsRecent Posts Popular TopicsPopular Topics Home Search 08s01 communication link failure Members Calendar Who's On Home » SQL Server 2005 » microsoft sql server native client 10.0 communication link failure SQL Server 2005 General Discussion » Communication Link failure Communication Link failure Rate Topic Display Mode Topic
Communication Link Failure Ssis
Options Author Message scorpianprincescorpianprince Posted Tuesday, January 18, 2011 4:00 AM SSC Rookie Group: General Forum Members Last Login: Monday, April 4, 2011 7:07 AM Points: 28, https://social.technet.microsoft.com/Forums/en-US/c8e969d0-2dee-4510-909c-ecd051357a24/sql-server-agent-error-after-server-restart-waiting-for-sql-server-to-recover-database-msdb?forum=sqltools Visits: 53 Hi all,can anyone tell me about the error that i am getting in the error log and what can be the cause of this error and what can be done to resolve this error :-Date 1/18/2011 2:14:32 PMLog SQL Agent (Current - 1/18/2011 2:14:00 PM)Message[298] SQLServer Error: 16389, Communication link failure [SQLSTATE 08S01] http://www.sqlservercentral.com/Forums/Topic1049183-149-1.aspx NEVER NEVER EVER GIVE UP Post #1049183 AdigaAdiga Posted Tuesday, January 18, 2011 6:18 AM SSCommitted Group: General Forum Members Last Login: Sunday, January 17, 2016 1:26 AM Points: 1,618, Visits: 21,012 These errors are usually logged in the Agent Log or by the application when the SQL Server instance low on memory or the underlying storage is having some issues. You may find the below links useful.http://sqlblog.com/blogs/merrill_aldrich/archive/2010/06/22/long-i-os-and-tcp-timeouts-are-not-a-sql-server-problem-except-when-they-are.aspxhttp://social.msdn.microsoft.com/Forums/en/sqldatabaseengine/thread/1536b610-e548-40c1-b9d0-1be3ad19a823 Pradeep Adiga Blog: sqldbadiaries.comTwitter: @pradeepadiga Post #1049274 scorpianprincescorpianprince Posted Wednesday, January 19, 2011 4:15 AM SSC Rookie Group: General Forum Members Last Login: Monday, April 4, 2011 7:07 AM Points: 28, Visits: 53 Thanks for the Reply. The Links are really helpfulAbout my findings:-The main reason after our analysis is coming out to be the I/O latch and the avg cpu utilisation of the server is 40% and most of the time the SQL server is waiting to read from the disk drive.Also the Db files are actively/continuously scanned by the AntivirusSo can you
are being logged in the Process Engine elogs, how can they be corrected? Technote (troubleshooting) Problem(Abstract) http://www-01.ibm.com/support/docview.wss?uid=swg21609058 Process Engine 4.5.1.x running on Windows using Microsoft SQL Server database will intermittently log the following errors: 2012/06/05 10:06:38.492 121,0,41