Solusi Error 26 Sql Server Saat Connect Ke Server
Problem: I have a 2 WFE & 1 App server in my SharePoint 2013 Enterprise Edition SharePoint farm. My WFE 2 and App servers connect all the time to the SQL Server using a SQL alias. My WFE1 server work 80% of thetime. It is setup exactly like WFE2 except periodically 1 web app/site collection will stop working and throw the following error:' A network-related or instance-specific error occurred while establishing aconnection to SQL Server. The server was not found or was not accessible.
Verifythat the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)'When I log into WFE1 I can connect to SQL using the alias using a udl file and telnet to verify the SQL alias is connected.Hypothesis/guess: It appears like WFE1 periodically looses networking but only for 1 specific site collection.Any ideas are most welcome? Hi Aries,. I can rule out SQL Server ( AOAG) Always-on as the farm doesn't use it. 'max worker threads' is set to 512 with 4CPU's. Rule out.From the log and looking at the breakdown of the SharePoint request, the request is hitting the WFE2 server which in turn is trying to connect to the content database. The connection string/instance is not available.
In summary, I believe theissue is WFE2 periodically cannot connect to the SQL instance. At the same time WFE1 is working so we know it isn't the SQL server. WFE1 & WFE 2 are on the same VLAN and both appear connected and can see the SQL database using a udl file.WFE2 has other web applications that are working while the erring web site fails. An IIS reset fixes the issue and restarting the 'App pool' for the offending IIS website also fixes the problem. This tells me the issueis the IIS process. When it tries to connect to SQL /the content database it fails.I already raised the ticket with MS, the engineer has been looking at it with me, we have tried to identify the issue and also looked at TCP Chimney offload being a possible issue.
As my servers is Windows Server 2012, all the servers have the default'TCP Chimney Offload' setting set to 'disabled'. WFE1, WFE2, APP1 and SQL have the same setting so this is not the issue.
Saat Anda menambahkan NT AUTHORITY ANONYMOUS LOGON login ke contoh Microsoft SQL Server 2000 atau Microsoft SQL Server 2005 sehingga contoh SQL Server menerima anonim login melalui Microsoft Terpadu Windows keamanan dan kemudian Anda mencoba untuk menyambung ke contoh SQL Server sebagai pengguna anonim, usaha koneksi mungkin tidak berhasil dan Anda mungkin menerima pesan galat berikut. Saat menyambung ke contoh bernama, pustaka jaringan klien mengirim paket permintaan User Datagram Protocol (UDP) ke alamat IP contoh bernama. Kemudian, SQL Server Browser mengembalikan respons paket UDP yang berisi informasi tentang sambungan akhir. Akan muncul jendela baru, carilah di jendela sebelah kanan SQL Server(SQLEXPRESS) lalu pastikan services tersebut berjalan (ada beberapa tombol resume, start, stop, pause dan restart services di bagian atas). Pastikan bahwa anda benar dalam menuliskan servername/nama komputer anda ketika mengkoneksikan ke server.
At least this has been ruled out.I will keep posting about the problem, hopefully MS support can escalate and the root cause can be determined.' The bottleneck is on the WFE2 server process trying to communicate with SQL. SQL is up and listening.
Only 1 of the website/WebApplication on WFE fail for 15-20 minutes while the other websites are fine.' Hi paulb32,i think you may need to get the memory dump from the process in the wfe2.you can grab the dump from the task manager and choose to create dump file. The engineer may able to help you to analyze the dump and trace the process to know which thread cause the bottleneck.Regards,AriesMicrosoft Online Community SupportPlease remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Hi paulb32,may i know your SQL version that you are using at this moment?as i know, this issue usually appear when there was a bottle-neck, so the response of handshake was not a success.
Some root cause may cause this issue happened, such as authentication, firewall, antivirus, port block, etc.please have a check this article, and if you find the symptoms are similar, you may try the hotfix,if should this issue persist, i may suggest you to open a thread at SQL products as well, perhaps there will be more experienced users with SQL products.Regards,AriesMicrosoft Online Community SupportPlease remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Hi Aries,My SQL database is SQL 2012 SP1 CU6.Microsoft SQL Server 2012 (SP1) - 11.0.3381.0 (X64) Standard Edition (64-bit).I guess it could be a bottleneck, the connection string doesn't work then. but I don't think it is the firewall etc. As the other web app is working on the same server at the same time. Also the other server works for both Web Apps.To me it is around the connection string on the Web App server and not SQL as SQL is taking other request.I raise MS support ticket last week - no response as of now.Thank-you for the reply, I appreciate your time and thoughts. I have included my ULS log snippet - I don't see any new additional info but I thought I would post anyway.EventID: 5586 Level: CriticalUnknown SQL Exception -1 occurred. Additional error information from SQL Server is included below.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible.Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)ConnectionString: 'Data Source=SQLAlias;Initial Catalog=WSSContentxx;Integrated Security=True;Enlist=False;Pooling=True;Min Pool Size=0;Max Pool Size=100;Connect Timeout=15' Partition: 000-0000-0000000ffffffff-ffff-ffff-ffff-ffffffffffffConnectionState: Closed ConnectionTimeout: 15. Hi paulb32,as we may need more detailed checking regarding this issue, it is quite a challenge for us in forum support to give some suggestions, as we are not able to give the right workaround without the memory dump logs at IIS process for the w3wp.exe.one of my colleague was had 5586 event also, and we turn off the always-on feature in the sql 2012, for temporary and the issue was not reproduced.as i know, sharepoint request to sql have some general phases,1. Request sent from web app goes to IIS, at IIS have IIS worker, that should handle the request, if should this worker is not available, it will be put as pending, and after some of moment it may lead to time-out as there was no response from the sql. Aperformance tuning may needed:;2.
After IIS sent the request it will goes to network and some checking like authentications, firewall, etc may happened at this level3. When the request arrived at sql, sql itself have some worker threads, if should the worker was out, then no response will be sent, and it may cause a time-out. Some optimization may appear to be needed here,;if only when we can identify the bottleneck, then we may have the best workaround for this issue,if should you may have concerns regarding the ticket that you openend, you may contact our customer service at support.microsoft.com, and if you have a premier contract then you may also contact the TAM.Regards,AriesMicrosoft Online Community SupportPlease remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Hi Aries,. I can rule out SQL Server ( AOAG) Always-on as the farm doesn't use it. 'max worker threads' is set to 512 with 4CPU's.
Rule out.From the log and looking at the breakdown of the SharePoint request, the request is hitting the WFE2 server which in turn is trying to connect to the content database. The connection string/instance is not available.
In summary, I believe theissue is WFE2 periodically cannot connect to the SQL instance. At the same time WFE1 is working so we know it isn't the SQL server. WFE1 & WFE 2 are on the same VLAN and both appear connected and can see the SQL database using a udl file.WFE2 has other web applications that are working while the erring web site fails.
An IIS reset fixes the issue and restarting the 'App pool' for the offending IIS website also fixes the problem. This tells me the issueis the IIS process. When it tries to connect to SQL /the content database it fails.I already raised the ticket with MS, the engineer has been looking at it with me, we have tried to identify the issue and also looked at TCP Chimney offload being a possible issue. As my servers is Windows Server 2012, all the servers have the default'TCP Chimney Offload' setting set to 'disabled'.
WFE1, WFE2, APP1 and SQL have the same setting so this is not the issue. At least this has been ruled out.I will keep posting about the problem, hopefully MS support can escalate and the root cause can be determined.' The bottleneck is on the WFE2 server process trying to communicate with SQL. SQL is up and listening. Only 1 of the website/WebApplication on WFE fail for 15-20 minutes while the other websites are fine.'
Solusi Error 26 Sql Server Saat Connect Ke Server Download
Hi paulb32,i think you may need to get the memory dump from the process in the wfe2.you can grab the dump from the task manager and choose to create dump file. The engineer may able to help you to analyze the dump and trace the process to know which thread cause the bottleneck.Regards,AriesMicrosoft Online Community SupportPlease remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.