Error: Error reading socket, ret 10054, error 2. (778) ***Incomplete write when writing to the server (735) - when in FIMS
- 03 Oct 2023
- Contributors
- Print
- DarkLight
- PDF
Error: Error reading socket, ret 10054, error 2. (778) ***Incomplete write when writing to the server (735) - when in FIMS
- Updated on 03 Oct 2023
- Contributors
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
User gets "kicked out" of FIMS. The errors user gets are: "Error reading socket, ret=10054, error=2. (778) followed by ... ***Incomplete write when writing to the server (735)" When the user click "OK" on the message, FIMS shuts down and opens back up to the login menu.
Answer:
These errors are network related. The computer where the user is using FIMS is having difficulty communicating with the database server.
This typically occurs if the user has left FIMS open and is no longer actively using it. We recommend that users close FIMS if not using.
During the troubleshooting process, the following questions are relevant:
1. Does this occur for just one user or multiple?
2. Does this issue occur when using FIMS on workstations or on a remote desktop server that multiple users use?
Steps to resolve:
1. Does this occur for just one user or multiple?
2. Does this issue occur when using FIMS on workstations or on a remote desktop server that multiple users use?
Steps to resolve:
1. If this occurs for just one user on their workstation, reboot the workstation.
2. If this issue occurs for multiple users reboot the FIMS database server and remote desktop server if you have one.
3. Investigate the network hardware between the FIMS server and the workstation for defects, specifically the workstation's Ethernet cable/card/switch port.
2. If this issue occurs for multiple users reboot the FIMS database server and remote desktop server if you have one.
3. Investigate the network hardware between the FIMS server and the workstation for defects, specifically the workstation's Ethernet cable/card/switch port.
4. See if anti-virus is a factor; this issue can be caused by active antivirus scanning of the NPO folder. Please see the following article:
5. This issue can additionally be caused by a network security device having a session timeout set for 30 seconds. Increasing the session timeout on the security device can resolve this issue.
6. There is a setting in the ubroker.properties file that can be changed. Please create a support case to assistance with changing this setting:
7. Alternatively, if you want users to be able to keep FIMS open even if they are not using it, you can setup keep alive pings between servers such as a remote desktop where users are using FIMS and the database server to keep port open so that users do not get kicked out of FIMS.
Was this article helpful?
