Error 1075: Could not start BarTender System Service on local computer Follow

Avatar
Domingo Rodriguez
Updated

Symptom

  • BarTender fails to start and throws an error message related to BT System Service not started.
  • BarTender System Service fails to start with error message 1075. 
    
            Error 1075: Could not start BarTender System Services on local computer.
            The dependency does not exist or has been marked for deletion.

Environment

  • BarTender 2019

Fix

The computer is probably missing one of the services that the BarTender System Service depends on for normal operation.

There are three dependencies for the BarTender System Service:

  • Message Queuing
  • Net. Tcp Port Sharing Service
  • SQL Server (BARTENDER)

So, whenever you get those symptoms for the BT System Service start, first determine which of these dependencies isn't available:

  1. In Windows, go to the Start Menu and select Run.
  2. Type services.msc and hit Enter.
  3. Locate the BarTender System Service, right click and choose "Properties".
  4. Select the "Dependencies" Tab. Find out what dependencies are missing.

Once you've determined which service(s) are missing, proceed to the correct section to enable the service:

Install Message Queuing Service

To enable Message Queuing in Windows, you can use Powershell or you can follow a set of steps specific to your operating system.

Powershell

Message Queuing can be enabled on any Windows Operating system using Powershell.

  1. Go to the Windows Start Menu
  2. Find and Open Powershell
  3. Paste the following command into the Powershell window 
    
            Enable-WindowsOptionalFeature -Online -FeatureName MSMQ-HTTP -AllEnable-WindowsOptionalFeature -Online -FeatureName MSMQ-Server –All
  4. You command should look something like this: Image
  5. Press Enter

If you don't want to use Powershell, please follow the section for your operating system.

Windows Server 2012 or 2016
  1. Open Server Manager
  2. Click Add Roles and Features
  3. Click Installation Type
  4. Click Role-based or feature-based installation
  5. Click Next
  6. Click Features
  7. Expand Message Queuing
  8. Click Message Queuing Server
  9. Click Directory Service Integration
  10. Click HTTP Support
  11. Click Next
  12. Click Install
Windows Server 2008 or Windows Server 2008 R2
  1. In Server Manager, click Features.
  2. In the right-hand pane under Features Summary, click Add Features.
  3. In the resulting window, expand Message Queuing.
  4. Expand Message Queuing Services.
  5. Click Directory Services Integration (for computers joined to a Domain), then click HTTP Support.
  6. Click Next, then click Install.
Windows 10 and Windows 7
  1. Open Control Panel
  2. Click Programs and then, under Programs and Features, click Turn Windows Features on and off
  3. Expand Microsoft Message Queue (MSMQ) Server, expand Microsoft Message Queue (MSMQ) Server Core, and then select the check boxes for the following Message Queuing features to install:
    • MSMQ Active Directory Domain Services Integration
    • MSMQ HTTP Support
  4. Click OK
  5. If you are prompted to restart the computer, click OK to complete the installation

Enable NET. Tcp Port Sharing Service

Even though this service is installed on all Windows systems it is not started by default. Therefore, during BarTender’s install process we automatically start the service and change its Startup Type to “Automatic”. This installation is performed implicitly when the Seagull installer calls the Integration service command line Integration.Service.exe /install.

If the service exists, but, for some reason, isn't started, please follow these steps:

  1. Open the Windows services management console
    1. Go to the Start Menu
    2. Choose Run
    3. Type in services.msc
  2. Scroll through the list of services until you find NET. Tcp Port Sharing Service
  3. Double click the service to open it's Properties
  4. Click the Start button to start the service
  5. Change the Startup Type to Automatic

This will ensure that the service always starts whenever your computer powers on.

Install BarTender SQL Server instance

All BarTender 2019 installations require a local SQL Server for internal application functions. This is required regardless of whether or not you are using a local or remote BarTender System Database for logging purposes.

The SQL Server should have been installed automatically during BarTender installation. It's possible the service may not be started. To check this:

  1. Open the Windows services management console
    1. Go to the Start Menu
    2. Choose Run
    3. Type in services.msc
  2. Scroll through the list of services until you find SQL Server (BARTENDER)
  3. Double click the service to open it's Properties
  4. Click the Start button to start the service
  5. Change the Startup Type to Automatic

If you do not see this service present, then it's likely the installation failed for some reason. To fix this issue, you must correct the errors that are happening during SQL Server Express installation. To do this, please follow Install BarTender SQL Server Express Manually.

10 comments
0
Avatar
Jan Zapletal
Comment actions Permalink

Hello, in dependencies in Bartender local services I have no SQL Server (Bartender). But SQL Server (Bartender) is installed and it is running - I see it. 

Thank you very much for your help

0
Avatar
Trey Holst
Comment actions Permalink

Jan, I found the exact same issue you did, that the SQL Server (BarTender) dependency was missing, but it was active and running.  The answer is that as of version 2019 R5, this specific dependency is no longer required.

My issue with the BarTender System Service was that I changed the login credentials.  Once things stopped working I changed it back to Local Service but it would not start.  The trick is to change it back to the Local Service account, and start the service twice.  It fails the first time and successfully starts thereafter.  Once I had the service running with the local service account, I could start BarTender apps.

I hope this is helpful for others having this issue.

0
Avatar
James Radigan
Comment actions Permalink

Installed on local pc no issue, went to install on Server 2012 R2 and getting the same error above. Have reinstalled SQL, restarted services and still nothing. 

 

Hello, in dependencies in Bartender local services I have no SQL Server (Bartender). But SQL Server (Bartender) is installed and it is running - I see it. 

 

Is there a new resolution? 

 

James R 

0
Avatar
Gniewomir Kaliński
Comment actions Permalink

Any known solutions for this problem?

0
Avatar
David Girardi
Comment actions Permalink

Something I ran into that may help someone else.  After installing Bartender R7 and getting the above error with the Bartender System Service not running.  I brought up the properties on the service noticed that it was not "logged on" as a local system account.  It was logging in with a "network" account or something like that.  I changed it to a local system account and started the service and everything worked fine.

-Dave

0
Avatar
Domingo Rodriguez
Moderator
Comment actions Permalink

Hello David,

Thanks for leaving this comment.

Running the BarTender System Service under the Local System account is indeed a good practice. You might need elevated permissions in case you are also connected to the BarTender System Database (SQL Server based database), but you could easily avoid possible permission issues by setting up SQL Server credentials instead (which will allow you to keep running the System Service under Local System account).

Best Regards,

0
Avatar
Loren Thiel
Comment actions Permalink

The instructions for installing the message Queuing Service via powershell is incorrect.

The corresponding powershell window picture is also absolutely wrong.

The correct 2 commands would be:

Enable-WindowsOptionalFeature -Online -FeatureName MSMQ-HTTP -All

Enable-WindowsOptionalFeature -Online -FeatureName MSMQ-Server -All

 

0
Avatar
Laura Vela
Moderator
Comment actions Permalink

Hello everyone but specially @Gniewomir, @James and @Jan.

 

As @Trey mentioned, since BarTender v2019 R5 the dependency that the BarTender System service had on the SQL Server component has been removed. This means that even if there is a failure on this service, the BarTender System service can be started anyway.

 

If you are using a BarTender version older than R5, I would suggest you try and upgrade to the latest release available R9, which can be downloaded from here:

https://portal.seagullscientific.com/

 

If you are using BarTender v2019 R5 or later and you are still getting that error, my first recommendation would be to check the status of the other two dependencies:

 

And if you keep experiencing any issues starting the service, I would advise you Contact us by any of our available means so that we can try and find the root cause for this issue for your particular case.

I hope this helps and don't hesitate to reach us!

 

Greetings,

Laura

0
Avatar
Laura Vela
Moderator
Comment actions Permalink

Hello @Loren,

Thank you for your comment.

Indeed the screenshot seems to be incorrect (there seems to be a missing blank space on one of the commands that is affecting all following commands).

The correct commands are the ones you pointed out:

Enable-WindowsOptionalFeature -Online -FeatureName MSMQ-HTTP -All

Enable-WindowsOptionalFeature -Online -FeatureName MSMQ-Server -All

 

As the article should be updated as well (to mention that the BarTender System Service does no longer have a dependency on the SQL SERVER component), I will take note for the image to be corrected, so thank you for pointing this out!

 

Greetings,

Laura

0
Avatar
Jan Zapletal
Comment actions Permalink

Hi, after few months we discovered our issue - firewall in Avast Business Antivirus. 

Please sign in to leave a comment.