This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 79%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER%3C/text%3E%3C/svg%3E)
Hi,
We are running SQL Server 2012R2 on Windows 2016 Server.
There is an application that fails occassionally. We have uploaded the Application Server and Database Server log to him.
His finding is there are a number of errors
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionWrite (send()).
I/O function: R, mode: 0, on driver: MSS
[Microsoft][ODBC SQL Server Driver]Communication link failure
I/O function: A, mode: 0, on driver: MSS
[Microsoft][ODBC Driver Manager] Invalid transaction state
May I ask
Thanks
Hi @RogerW ,
Agree with Erland, please check your SQL server error log first.
> If there is error in SQL Server Error Log, would backup / antivirus causes the error ?
It’s hard to find the root cause, when we did not get any information from your error log. Please check your SQL error log first, and share us the information you got from the log, then we can continue to troubleshoot this issue.
Hi @RogerW ,
Any update for this thread? Could you please share us the information from error log ?
I would check the SQL Server error log for crash dumps. That is, these errors could be due to crashes in SQL Server, so that SQL Server severs the connection.
If you don't find any crash dumps, I'm inclined to think that these are tokens of glitches in your network.
Dear Erland,
Thanks for your advice.
I will check the SQL Server Error Log per your advice.
Is it reasonable to get those error messages from Uniface application on the Application Server ?
If there is error in SQL Server Error Log, would backup / antivirus causes the error ?
Thanks
The errors I have in mind are due to bugs in SQL Server or corruption in the database. What is written to the SQL Server errorlog in this case is not available to the application. Keep in mind that these are exceptional events, and they are not due to user errors.
But let's not get ahead of things. First check the SQL Server errorlog, and you find something, let's discuss it at that point.