Answered by:
Connection reset

Question
-
Hello,
we are having a JDBC connection from one of our internal server to the SQL Server on port 1433 and we are connect reset errors very often. below is the error.
[ART.117.4002] Adapter Runtime (Adapter Service): Unable to invoke adapter service JDBC:TruncateBULKEQUIPMENTTable.
[ADA.1.316] Cannot execute the SQL statement "TRUNCATE TABLE pki_onesource.dbo.EQUIPMENT_MASTER_BULKUPLOAD;". "
(08S01/0) Connection reset"
Connection reset
can you please help us figure out what the issue is?Thursday, August 25, 2016 6:37 PM
Answers
-
Greetings,
as you got an error that you can't truncate the table i would solve that first.
I dont think JDBC will call reset-connection out of the blue but it might do it as precaution to avoid further errors.So grant the user truncate-priviledges and see if the error goes away.
Sebastian
- Proposed as answer by Kalman Toth Friday, August 26, 2016 3:56 PM
- Marked as answer by Lydia ZhangMicrosoft contingent staff Friday, September 9, 2016 1:54 AM
Friday, August 26, 2016 7:57 AM -
Good day ,
I agree with Sebastian. Seems like your issue is with truncating a table.
Make sure that your case fit the truncate restrictions:
You cannot use TRUNCATE TABLE on tables that: (1) referenced by a FOREIGN KEY constraint in different table. (2) Participate in an indexed view. (3) published by using transactional replication or merge replication.
* I am guessing that issue is not related to permission, as the error do not mentioned permission issue (unless you have additional errors that you did not post). Missing permission should raise error: Cannot find the object "<table name>" because it does not exist or you do not have permissions.
Ronen Ariely
[Personal Site] [Blog] [Facebook] [Linkedin]- Edited by pituachMVP Friday, August 26, 2016 3:39 PM
- Proposed as answer by Kalman Toth Friday, August 26, 2016 3:56 PM
- Marked as answer by Lydia ZhangMicrosoft contingent staff Friday, September 9, 2016 1:54 AM
Friday, August 26, 2016 2:52 PM -
Hello,
As Sebastian wrote the main cause is the SQL error and here especially the Severity Level of the error, see RAISERROR (Transact-SQL) => Caution: "Severity levels from 20 through 25 are considered fatal. If a fatal severity level is encountered, the client connection is terminated after receiving the message, and the error is logged in the error and application logs."
Olaf Helper
[ Blog] [ Xing] [ MVP]- Proposed as answer by Kalman Toth Friday, August 26, 2016 3:56 PM
- Marked as answer by Lydia ZhangMicrosoft contingent staff Friday, September 9, 2016 1:54 AM
Friday, August 26, 2016 3:48 PM
All replies
-
Hi i-Bro,
Please check if AutoClose option in the target SQL Server:
Friday, August 26, 2016 7:22 AM -
Greetings,
as you got an error that you can't truncate the table i would solve that first.
I dont think JDBC will call reset-connection out of the blue but it might do it as precaution to avoid further errors.So grant the user truncate-priviledges and see if the error goes away.
Sebastian
- Proposed as answer by Kalman Toth Friday, August 26, 2016 3:56 PM
- Marked as answer by Lydia ZhangMicrosoft contingent staff Friday, September 9, 2016 1:54 AM
Friday, August 26, 2016 7:57 AM -
Good day ,
I agree with Sebastian. Seems like your issue is with truncating a table.
Make sure that your case fit the truncate restrictions:
You cannot use TRUNCATE TABLE on tables that: (1) referenced by a FOREIGN KEY constraint in different table. (2) Participate in an indexed view. (3) published by using transactional replication or merge replication.
* I am guessing that issue is not related to permission, as the error do not mentioned permission issue (unless you have additional errors that you did not post). Missing permission should raise error: Cannot find the object "<table name>" because it does not exist or you do not have permissions.
Ronen Ariely
[Personal Site] [Blog] [Facebook] [Linkedin]- Edited by pituachMVP Friday, August 26, 2016 3:39 PM
- Proposed as answer by Kalman Toth Friday, August 26, 2016 3:56 PM
- Marked as answer by Lydia ZhangMicrosoft contingent staff Friday, September 9, 2016 1:54 AM
Friday, August 26, 2016 2:52 PM -
Hello,
As Sebastian wrote the main cause is the SQL error and here especially the Severity Level of the error, see RAISERROR (Transact-SQL) => Caution: "Severity levels from 20 through 25 are considered fatal. If a fatal severity level is encountered, the client connection is terminated after receiving the message, and the error is logged in the error and application logs."
Olaf Helper
[ Blog] [ Xing] [ MVP]- Proposed as answer by Kalman Toth Friday, August 26, 2016 3:56 PM
- Marked as answer by Lydia ZhangMicrosoft contingent staff Friday, September 9, 2016 1:54 AM
Friday, August 26, 2016 3:48 PM