Inedo Community Forums Forums
    • Recent
    • Tags
    • Popular
    • Login

    Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

    If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

    Database Connectivity issue

    Scheduled Pinned Locked Moved Support
    sql-serverbuildmaster
    2 Posts 1 Posters 3 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • ? This user is from outside of this forum
      Guest
      last edited by

      We have BuildMaster periodically reporting issues connecting to the SQL server database - but when we investigate, there is no issue between the two servers. Restarting the BuildMaster service from the admin tab does not reset the error, but restarting the machine does.

      Based on a suggestion in this support q - http://inedo.com/support/questions/3101 - I disabled connection pooling and have not had this issue recur. However, I am wondering what the consequences of this will be - we plan to have a number of applications configured on the build server - what are the limitations if we do not have connection pooling? Is there a better way to solve this problem?

      Could not connect to the BuildMaster database. BuildMaster will not function property until this is resolved. The specific error message is: Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=28; handshake=14979;

      Product: BuildMaster
      Version: 4.8.6

      1 Reply Last reply Reply Quote 0
      • ? This user is from outside of this forum
        Guest
        last edited by

        This is fairly easy to reproduce -- just turn off the SQL Server. As to why it's happening, that's hard to say... perhaps it's being rebooted? Or you have network connectivity issues?

        If this is happening, I wouldn't disable pooling --- instead, just try to restart the web app by going to, Admin > All Settings > Save. This will re-establish a connection to the service on restart, and should clear this error.

        Another thing you may want to do, is to configure the service to crash on database errors; then set auto-recovery. You can do this by setting a value in your service's application configuration file, "CrashOnDbFailure" to "True", and changing the recovery settings in Windows.

        1 Reply Last reply Reply Quote 0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        • 1 / 1
        • First post
          Last post
        Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation