cancel
Showing results for 
Search instead for 
Did you mean: 

DDS & Platter Management

Dora_Compis
Champ in-the-making
Champ in-the-making

Platter Management Failure          Platter Management Error: DDS Error detected [-29 : 10053] : DDS server (FileServerName:2185) has gone off-line.

What does the -29:10053 mean?    Is it just a code for the DDS Error detected message?

1 ACCEPTED ANSWER

AdamShaneHyland
Employee
Employee

As a correction, a software change in SCR: #229373 (DDS v2.0.3-b8) fixed this issue.  The problem was caused by sessions being killed if opened for longer than 10 minutes while there is other activity on the DDS Server.  The change in the SCR added the ability to configure a timeout period for idle DDS connections within the INI file.  The new setting is called conntimeoutminutes.  By defult the setting is 10 minutes, but in cases where you are receiving the 10053 error, I recommend updating the settings to 60 minutes.  If you still receive the error, continue to increase the value.

Take care.

View answer in original post

9 REPLIES 9

Connor_Marment1
Confirmed Champ
Confirmed Champ

Has anyone that has gotten this error found a fix? We are getting quite a few of these errors daily but have not been able to track down what is causing it. It just looks like the thick client loses connection with the DDS server randomly. 

AdamShaneHyland
Employee
Employee

Hi Dora (Pawel and Conner),

Thanks for this post.  While you may have already found an response to this issue, I wanted to follow up for others who may be researching this in the future.

To date, there is no specific single cause of this issue and further troubleshooting with your first line of support is recommend to get to the bottom it.  While we haven't been able to recreate the issue internally, it is speculated that the issues is cause by a session being reset.  The error code (10053 - WSAECONNABBORTED) is a Windows Socket Error Code (link). 

If you run into this issue again, please reach out to your first line of support for further troubleshooting.

Thanks.

AdamShaneHyland
Employee
Employee

As a correction, a software change in SCR: #229373 (DDS v2.0.3-b8) fixed this issue.  The problem was caused by sessions being killed if opened for longer than 10 minutes while there is other activity on the DDS Server.  The change in the SCR added the ability to configure a timeout period for idle DDS connections within the INI file.  The new setting is called conntimeoutminutes.  By defult the setting is 10 minutes, but in cases where you are receiving the 10053 error, I recommend updating the settings to 60 minutes.  If you still receive the error, continue to increase the value.

Take care.

Hi Adam,

Can you confirm which version of OnBase was the SCR (#229373 ) implemented for? My organization is running version 14 and believe we are also experiencing the issue.

Regards,
Ed Cabrera
Columbia University

Hello Ed,

Enhancement SCR #229373 was completed for OnBase 16.

Thanks.
Jonathan Finney
Hyland Software Tech Support team Leader
Getting started

Find what you came for

We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.