Altiris Error 11 General Network Error. Check Your Network Documentation
Contents |
24, 20082 0 0 0 This is a proper netwrok microsoft odbc driver 11 for sql server communication link failure error and has nothing to do with the [dbnetlib][connectionread (recv()).]general network error. check your network documentation. coding if any of your jobs/queries/packages fail with this message. Please refer the dbnetlib connectionwrite (send()). general network error. check your network documentation following article for the workaround. http://support.microsoft.com/kb/942861/en-us Another work around we tried and succeeded in our project was as follows: There is error [08s01] [microsoft][sql native client]communication link failure something called Network Speed setting which is usually set toAUTO or a fixed value. You can check this from Start->Control Panel->Network Connections->Local Area Connection->Properties->Configure->Advanced->Speed &Duplex property. Change it to 100 MBPS full or whatever value that matches the configuration of the n/w port
Communication Link Failure Ssis
on the switch side. It solved the issue for us.
Comments (2) Cancel reply Name * Email * Website General Network error. Check your network documentation. | Coded Style says: December 24, 2008 at 2:08 am PingBack from http://www.codedstyle.com/general-network-error-check-your-network-documentation/ Reply Abdul Hadi says: September 7, 2015 at 9:32 pm If some one using programming language and facing this error, then use timeout method (e.g. for C# and VB.Net it is SqlCommand.TimeOut = 600). it will give extra time for your transaction process. Reply Follow UsArchives January 2011(1) July 2010(1) June 2010(1) May 2010(1) January 2010(1) December 2009(1) November 2009(2) August 2009(2) July 2009(1) All of 2011(1) All of 2010(4) All of 2009(7) All of 2008(7) Privacy & Cookies Terms of Use Trademarks © 2016 Microsoftof a sudden .... One of our DS servers has been displaying the following error in the event log: Event Type: Error Event Source: AltirisDataManager Event Category: None Event ID: 0 Date: 1/09/2007 Time: 12:22:15
Communication Link Failure Sql Server 2012
PM User: N/A Computer: XXXXLIALT Description: eXpressDatabase Error 11: General network error. Check your network sql server error 10054 communication link failure documentation. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Then followed by: Event Type: Error Event Source: AltirisDataManager Event Category: tcp provider: an existing connection was forcibly closed by the remote host. None Event ID: 0 Date: 1/09/2007 Time: 12:29:17 PM User: N/A Computer: XXXXLIALT Description: eXpressDatabase Error -2: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. For https://blogs.msdn.microsoft.com/ramoji/2008/12/24/general-network-error-check-your-network-documentation/ more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Once this occurs the DS is very slow and cannot remote any PC’s. I have had a look at the following article: http://forums.altiris.com/messageview.aspx?catid=3&threadid=31855&enterthread=y The only solution appears to be a restart of the Express service or restart the server. This seems to occur every 2nd or 3rd day. The server is Windows Server 2003 R2 SP1, SQL2005 SP1 using DS 6.8 with aclient 6.8.282. http://www.altirigos.com/forums/threads/deployment-server-6-8-206.7439/ Any ideas anyone? geomil, Sep 3, 2007 #1 Sachiv New Member Hrmm You may want to look into something about opportunistic locking which can cause problems in some versions of DS (just clutching at straws). Are you able to move the DB to another SQL server or onto the same server itself? Basically stop services, move the db.. update the system dsn on on the box and start the services (or just restart the box so everything comes up in the proper order). Sachiv, Sep 4, 2007 #2 geomil New Member I can stop and restart the Express service the problem goes away. Can you be a bit more specific with your previous post? geomil, Sep 5, 2007 #3 tmsmith2 Member I too am having this issue Any fix for the Error 11: General network error? tmsmith2, Sep 19, 2008 #4 andykn Altiris Guru tmsmith2 said: ↑ Any fix for the Error 11: General network error? Have you got the latest patches installed? https://kb.altiris.com/article.asp?article=41787&p=1 andykn, Sep 22, 2008 #5 tmsmith2 Member DS still having issues. All patches applied. Now at 6.9 SP1 tmsmith2, Feb 11, 2009 #6 andykn Altiris Guru Are you sure it's not a network issue rather than an Altiris issue? Try writing a batch file, say ping.bat, where you ping another computer on the network
a very botchy instal of RDP 3.81. I hoped an immediate upgrade would have corrected something, but with the amount of errors and prior mis-configurations, I havn't been so lucky. Is there anything in particular http://www.altirigos.com/forums/threads/help-with-clean-install-of-rdp-3-82.10314/ I should be careful to ensure is backed and saved elsewhere if I http://news.support.veritas.com/connect/search/apachesolr_search/svs%20memory%20read?page=8&filters=language%3Aen%20created%3A%5B2011-01-01T00%3A00%3A00Z%20TO%202012-01-01T00%3A00%3A00Z%5D&solrsort=created%20desc&facet_click=1 was to go ahead with a complete uninstall before installing RDP 3.82? Thank you in advance, -Aaron Cheshire, Dec 31, 2008 #1 Brandon Active Member Export all the (custom) jobs in 3.81 first to a bin file. Then perform an upgrade to 3.82 and back them up in the format as well. Then re-do communication link a clean installation. If you don't have custom jobs then it doesn't matter. The problem is you can't import a 3.81 job into a 3.82 console I believe. To be safe I would back up the db as well (eXpress). Brandon, Dec 31, 2008 #2 Cheshire New Member Thanks Brandon, I'll try that and get back to you. -Aaron Cheshire, Jan 2, 2009 #3 Cheshire New Member communication link failure Alright, so I've completed the full uninstall and re-install. Unfortunatly the same issue is still there. I've enabled any log files I could find associated with Altiris / SQL and looked over the computer's logs. This is what it's turned up: ----------- axengine.log; - Unknown exception was caught in CRxEngineMMConnection::Connect. - Error reading from socket (2068), Error: 10053 (10053 (WSAECONNABORTED)) - Error 10053 (WSAECONNABORTED) during recv () on socket (2068). Agent communications with engine is clean. SQL Server Logs are all empty. SQL activity monitor has multiple entries with DOMAIN1/USER1 associated with the eXpress database & sleeping. Altiris Console Log is clean. Altiris Data Manager; -eXpressDatabase; Error 11: General network error. Check your network documentation. -eXpressDatabase Error 4060: Cannot open database "eXpress" requested by the login. The login failed. Login failed for user 'DOMAIN1\USER1'. Application Log; -Altiris Deployment Server; Service cannot be started. The service process could not connect to the service controller. -Altiris Deployment Server; Event ID 3; Incorrect syntax near the keyword 'and'. Statement(s) could not be prepared. -MSSQLSERVER; Event ID 17187; SQL Server is not ready to accept new client connections; -Altiris Deployment Server; Event ID 3;SQL Server does not exist or access denied. ConnectionOpen (Connect())