次の方法で共有

Service Bus Gateway service struck in starting State

  • [アーティクル]

When configuring Service Bus Farm either while creating a
new Farm or when joining a new farm, you might experience the below issue        

“Starting Service bus gateway on
machine <servername> failed: timeout has expired and the operation has
not been completed”

 

And when you check the services it’s in starting state.

  

The above issue can occur due the below reasons

1)     
If there is antivirus service running and it
blocking the ports used by Service bus. You can find out the default port
numbers at the time of configuration.

2)     
Check if the Service Bus ports are opened in the
inbound and outbound rules of Firewall settings. you can collect network traces
at the time of configuration to know if the ports were blocked or not. Or you
can use portQry
tool to check the port status.

3)     
If the port that you have configured to use is
already taken by another process. You can check the same using PortQry tool or
using netstat –ano cmd.

4)     
This issue is also noticed when you are running
ServiceBus1.1 with Framework 4.6. Recently there is an update released for
SB1.1 to work with .Net Framework 4.6. download and install the update https://www.microsoft.com/en-us/download/details.aspx?id=49496
to resolve the issue.

Hope this helps!!

Comments

  • Anonymous
    January 22, 2016
    Thanks! This got me past the3 stuck on staring issue. I ended up having to download the update for it to work

  • Anonymous
    March 03, 2016
    Thanks a lot, its worked for me too after installing latest update of SB 1.1

  • Anonymous
    March 08, 2016
    Thanks! The install to update SB 1.1 worked for me as well!

  • Anonymous
    October 29, 2016
    We got the same issue and after a lot of troubleshooting, we found that the issue was with a Registry Entry.Go to the following path, take a back up of Protocols and remove the folder for TLS.HKey_Local_Machine\System\CurrentControlSet\Control\SecurityProviders \SCHANNEL\Protocols This has helped us resolve the issue. Hope it helps someone else too :)

    • Anonymous
      December 05, 2016
      Thanks Suprotim :)