Saltar al contenido principal

Búsqueda

Búsqueda

Error starting Integration service

Comentarios

6 comentarios

  • Avatar
    Sam King

    After checking the logs I found the following entry in Integration.Service.txt

    2023.06.27.124346|||ERROR|Failed to open MessagingQueueRelayServiceHost. Details: The service endpoint failed to listen on the URI 'net.tcp://localhost:5150/private/Seagull.Services.Messaging' because access was denied.  Verify that the current user is granted access in the appropriate allowAccounts section of SMSvcHost.exe.config. Access is denied

    I checked the SMSvcHost.config file in C:\Windows\Microsoft.NET\Framework64\v4.0.30319 and in C:\Windows\Microsoft.NET\Framework\v4.0.30319 and both indicate they already have the LocalSystem account set for both net.tcp and net.pipe.

    Does the service need to run under an admin or domain admin user account?  Are there other <system.serviceModel.activation> sections needed for the other BarTender services with <allowAccounts> entries for LocalSystem?

    0
  • Avatar
    Matty Brown

    I've got the exact same error message.  Brand new install of BarTender 2022 R6 on Windows Server 2022 Standard.

    Did you manage to resolve this?

    I'm just about to install all windows updates and update to R7 before contacting support.

    Thanks,

    Matty.

    0
  • Avatar
    Matty Brown

    After updating to BarTender 2022 R7, the service started normally.  Not sure if the new version fixed something, or if it was the Windows Updates or reboot that fixed it, but the service is now starting successfully.

    0
  • Avatar
    Sam King

    Hi Matty,

    Yes, we managed to get this resolved with Seagull support's help.  Ends up there's an executable for SQL server that BT expects to be on the C: drive like the path is hard coded.  My client had installed their SQL server on D:\

    The executable is named "SQLocalDB.exe" and can be found in the \Tools\Binn folder buried in C:\Program Files\Microsoft SQL.  Since each SQL server version has its own folder, the location can vary according to the version you're running.

    We duplicated the folder structure to C:\ and copied this file to the new corresponding folder, which resolved the problem.

    0
  • Avatar
    Tony Hammond

    Sam King really appreciate your post. We were having the same issue and like you our SQL instance is on the E: drive rather than the C: drive.

    For me i had to add "Tools" and "Binn" folders on the C: drive to complete the path C:\program files\microsoft sql server\120\tools\binn. Then I copied SQLlocaldb.exe from my E: drive to the new binn folder on the C: drive.

    I am now able to start the integration service successfully.

    0
  • Avatar
    Robert Adamietz

    BT2022 R7

    Same error.

    copied the folder "Binn" from a different computer to the server folder "C:\Program Files\Microsoft SQL Server\120\Tools" as the folder "Binn" was completely missing here.

    After the folder "Binn" was copied including the file "SQLlocaldb.exe" the Service "Bartender Integration Service" started without errors.

     

    0

Iniciar sesión para dejar un comentario.