Skip to content

x Want to ask a question or reply? Click here to join the group.
Options
  • State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 58 subscribers
  • Views 138 views
  • Users 0 members are here
Browse Forums
Sage Timeslips Anywhere Announcements
33
topics
7
replies
Sage Timeslips Anywhere General Discussion
72
topics
158
replies
Sage Timeslips Premium Announcements
94
topics
21
replies
Sage Timeslips Premium General Discussion
2k
topics
9k
replies

Timeslips Unresponsive When Connecting Through RDS

Connor
Suggested
Posted By

Hey All,

We've been having an issue with Timeslips where the application is occassionaly becoming unresponsive when connecting through RDS. We are using Timeslips Premium version 30.0.7.157. I have reviewed the Windows Event logs and see that the application generates an application hang event with an ID of 1002. After doing some research, this appears to be a generic error. Furthermore, I have reviewed the Firebird logs and see the following error.

INET/inet_error: read errno = 10054

Please note the following:

  • The application is becoming unresponsive immediately after entering login credentials
  • Users at the physical office are able to login without issue
  • Timeslip directories have been exempted from our 3rd party antivirus software
  • We created a script to restart the Firebird service if the event ID for the app is generated
  • The server's resources are only running at about 10%
  • The issue seems to resolve itself after about an hour or so

Unfortunately, Timeslips support has been unable to assist us since they claim that RDS is not supported and that it is an issue with our environment. However, users are able to initiate the RDS session just fine, the issue seems to be with the application itself.

I'm curious if anyone has run into this issue before. Also, interested to see how other offices have configured Timeslips for a hybrid environment. Any assistance would be greatly appreciated!



  • 0
    SUGGESTED

    Hi  — thanks for all the detail (version/build, Event ID, and the Firebird log line are especially helpful). For reference, here’s the thread: TimeSlips unresponsive when connecting through RDS .

    A couple of things stand out:

    • INET/inet_error: read errno = 10054 typically indicates a dropped TCP connection (“connection reset by peer”) between the client and the Firebird service — commonly tied to a network device/firewall/VPN dropping or resetting the socket.
    • Since this happens over RDS (and you mentioned it can “clear up” after some time), it’s worth confirming whether the RDS host and the database are truly close together (same LAN / same server segment), vs. an app-to-database connection that has to traverse VPN/WAN where timeouts/resets are more likely.

    Based on your symptoms (hang right after credentials, office users OK, resolves “after about an hour”), here are a few practical checks that often help narrow this down:

    1. Confirm where Firebird + the TimeSlips database live
      Best-case for stability: RDS server + TimeSlips + Firebird + data are on the same LAN (or ideally the same server/segment), and users RDP into that environment.
      If your RDS host is in a different site/cloud and connecting back to an on-prem Firebird/database over VPN/WAN, that often aligns with seeing intermittent connection resets.
    2. Look for anything that could be resetting Firebird connections
      Firewall/IPS session timeouts, VPN keepalive/idle policies, load balancers, NIC driver/power-saving settings, etc.
      Since you already excluded AV paths, also double-check any EDR/network inspection components that might still be touching RDS traffic or the Firebird port.
    3. Rule out “stuck” locks / login DB files
      If you ever see ERROR: “Failed to read from Streamed Data, the file was shorter than expected” , it can indicate TimeSlips can’t properly read/lock certain files. The KB steps include removing specific lock/login files (with all users out) to rebuild them cleanly.
    4. If you hit “Address violation…” in lists (separate symptom)
      If you run into Error: “Address violation error...” when opening Client list or Timekeeper list , there are quick UI/preference reset steps you can try.
    5. Hybrid workflow tip (for stability)
      If possible, keep the “work” consistent: either have everyone run through the same RDS host, or ensure the app + data stay close together (avoid “app here / database there” across a WAN).

    If you don’t mind sharing (even just at a high level): is the Firebird service/database on the same machine as the RDS host, or is the RDS server connecting over a VPN to an on-prem server? That one detail usually determines the best next step.

    If this helps, please mark it as verified White check mark Slight smile

*Community Hub is the new name for Sage City