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!

    Service won't start after 2.1.1 Upgrade

    Scheduled Pinned Locked Moved Support
    otter
    4 Posts 3 Posters 8 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.
    • Jonathan.EngstromJ Offline
      Jonathan.Engstrom
      last edited by

      I get a "Service cannot be started. System.Data.SqlClient.SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. ---> " in my event log. I have restarted the machine after trying to restart services, no change yet. SQL is working as other DB's for other apps are working fine. Ideas?

      Product: Otter
      Version: 2.1.1

      1 Reply Last reply Reply Quote 0
      • atrippA Offline
        atripp inedo-engineer
        last edited by

        Hello; this errro means that OTter can't connect to the database. Maybe the connection string changed?

        I would check the database connection string in Otter's configuration file.

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

          If I try like 10 times or so, it will finally start. The DB has not changed as other services are still connecting and working to the same instance. 9/10 times, the Otter service will time out and I have to try again. Seems to be some type of timeout after 15-20 seconds or so.

          1 Reply Last reply Reply Quote 0
          • atrippA Offline
            atripp inedo-engineer
            last edited by

            There have been no changes to the way our products connect to databases in many years, so this is unrelated to an upgrade.

            However, it seems to be some sort of indication that SQL Server must be overloaded, or a network problem. This can typically be diagnosed / reviewed by the SQL Server DBA, who can see incoming connections, and which queries are taking too long, etc.

            But in my experience, just restarting the server you have SQL Server installed on fixes it like 80% of the time.

            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