Forum Discussion

ChiruGalla's avatar
ChiruGalla
Icon for Helper I rankHelper I
1 year ago
Solved

I was getting "failed to create gateway, please try again" error while cofniguring the gateway on-pr

I was getting the "failed to create gateway, please try again" error while configuring the gateway on-premises.

 

The installation of the on-premise data Gateway is through; however, while configuring the gateway, I am getting the above error.  When I was reading online articles, and when I validated the below commands, the gateway and servicebus are not through, and i am getting a warning message as 'WARNING: Name resolution of gateway.prod.microsoft.com failed' . 'WARNING: Name resolution of *.servicebus.windows.net failed'

 

Test-NetConnection -ComputerName gateway.prod.microsoft.com -Port 443
Test-NetConnection -ComputerName login.microsoftonline.com -Port 443
Test-NetConnection -ComputerName *.servicebus.windows.net -Port 443 

 

I think the DNS issues have to be fixed in order to get the data gateway registered. Please let me know otherwise, and if I am missing anything else here?

Need Help
  • ChiruGalla's avatar
    ChiruGalla
    1 year ago

    Upon further investigation of the logs, I see a forbidden error with a 403 code. It seems the Windows server time is not in sync. 

     

    I have restarted the 'Windows Time Service (Win32Time)', and then I have tried again; it was successful.

6 Replies

  • DataVitalizer's avatar
    DataVitalizer
    Icon for Super User rankSuper User
    1 year ago

    Hi ChiruGalla 

    To resolve that issue I suggest you start by checking your DNS settings and perform DNS resolution tests with commands such as nslookup gateway.prod.microsoft.com.

    When DNS resolution fails you need to update your DNS server settings and execute ipconfig /flushdns.

     

    Also verify that your firewall and network rules permit outbound traffic on port 443 to gateway.prod.microsoft.com and *.servicebus.windows.net, the traffic must be allowed through your proxy when you are behind one.

     

    After fixing DNS and network connectivity issues proceed to set up the gateway again.

     

    Did it work? 👍 A kudos would be appreciated
    🟨 Mark it as a solution to help spread knowledge 💡

     

    🟩 Follow me on LinkedIn

  • ChiruGalla's avatar
    ChiruGalla
    Icon for Helper I rankHelper I
    1 year ago

    My initial troubleshooting was in that direction, and I am sure the outbound 443 was open.

    However,  upon further investigation into the logs, I see a 403 error.

     

    I had to sync the time, and then tried to reconfigure, which went well. 

     

    Thank DataVitalizer, for your quick response, though.

  • v-karpurapud's avatar
    v-karpurapud
    Icon for Community Support rankCommunity Support
    1 year ago

    Hi ChiruGalla 

    Thank you for posting your question on the Microsoft Fabric Community Forum, and thanks as well DataVitalizer  for the ongoing support and assistance.

     

    Could you let us know if the suggested solution resolved your issue? This information can assist other community members facing similar challenges.

    Thank you.

     

    • ChiruGalla's avatar
      ChiruGalla
      Icon for Helper I rankHelper I
      1 year ago

      Upon further investigation of the logs, I see a forbidden error with a 403 code. It seems the Windows server time is not in sync. 

       

      I have restarted the 'Windows Time Service (Win32Time)', and then I have tried again; it was successful.

      • v-karpurapud's avatar
        v-karpurapud
        Icon for Community Support rankCommunity Support
        1 year ago

        Hi ChiruGalla 

        Thanks for the update. If you have any further questions, please let us know. We will be happy to assist you.

        Regards,
        Karpurapu D.