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!

    BuildMaster service (bmservice) not restarting

    Scheduled Pinned Locked Moved Support
    servicebuildmaster
    2 Posts 1 Posters 9 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

      System:
      Windows Server 2003, Enterprise Edition, Service Pack 2

      Issue:
      If the server is shutdown for maintenance or because of other issue and is restarted, the BuildMaster service does not restart. It attempts to restart but fails which then chains to the BuildMaster Web server failing to start. Both services are set to "Startup Type: Automatic". The Application Event Log provides the error details below.

      I attempted to add an exception handler to the Web.config file but was unsuccessful in getting it to log on initial start up.

      Is it possible to get BuildMaster to consistently start on system start up? If so, what am I missing?

      [EventLog details]
      "Date, time, user, computer"
      Type: Error
      Source: .NET Runtime 2.0 Error
      Category: None
      Event ID: 5000
      Description: EventType clr20r3, P1 bmservice.exe, P2 3.5.8.30, P3 5159f602, P4 bmservice, P5 3.5.8.30, P6 5159f602 P7 2d, P8 34, P9 system.typeinitialization, P10 NIL.
      [/EventLog details]

      Product: BuildMaster
      Version: 3.5.8

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

        This is a known issue with .NET-based services on low-spec servers running Windows Server 2003. Basically, the CLR cannot load in time, triggering an error. In newer server operating systems, you can specify Delay Start, which solves the problem, but it's not possible on 2003.

        There is a workaround available from Microsoft, KB#193888.

        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