on-premise data gateway - No Instance name found
Question
Sunday, October 23, 2016 6:19 PM
I am not able to create on-premise data gateway because an error shows the below
"No installed Instances were found for the current user"
Please advise whats the issue ?
All replies (16)
Monday, October 24, 2016 8:34 AM ✅Answered | 1 vote
Hi Baran,
Did you follow the steps from Jeff Hollan's article, from here?
https://azure.microsoft.com/en-us/documentation/articles/app-service-logic-gateway-install/
In summary you need to:
1) Install and configure the gateway on your local computer (this will install a service on the local computer that acts as the gateway) - step 1 on the article.
2) Create a Logic Apps Gateway using the gateway created above (step 2 in the article).
3) Consume the Gateway on your own Logic Apps.
I also have the impression that the account used to setup the local gateway (in one of the steps it requests a work/school account), must be the same connected on Azure during step 2.
I hope this helps, Wagner.
Thursday, May 11, 2017 7:59 PM ✅Answered | 2 votes
As Wagner said, you must install the gateway first on a local computer, as described in the topic he linked:
Install the on-premises data gateway for Azure Logic Apps
This topic should also help explain why you see this message:
Access data on premises from Azure Logic Apps
Also, you can associate only one gateway resource per gateway installation.
With the on-premises data gateway now generally available, you can use different locations for your gateway resource and logic app. Previously, you had to use the same location for your gateway resource and logic app so that your gateway would appear when you went to select the gateway in your logic app.
Also, during gateway installation, you can now select the location for the gateway cloud service that you use to route queries and results between your logic app and your on-premises data source.
Note: Your gateway resource location must match the gateway cloud service location that's selected during gateway installation. Otherwise, you won't see your installed gateways in the Installation list.
If you already installed a gateway, but want to use a gateway in a different location, you can use the latest installer to set up a new gateway in the location that you want, but you can't change the location for an existing gateway.
Esther Fan | Azure Logic Apps | If a post answers your question, please mark it as the answer. Thanks!
Tuesday, July 25, 2017 6:32 AM
I am facing this exact same issue and have spent all night and morning trying to fix this. How did this resolve?
Friday, July 13, 2018 8:10 PM | 2 votes
I am facing this exact same issue and have spent all night and morning trying to fix this. How did this resolve?
I'm also facing the same issue. I've followed the steps, and used the same Azure AD account both in the portal and when installing the on-premises gateway. However it's not possible to choose location when installing the gateway. The latest version 14.16.6745.2 (June 2018) doesn't give me that option. But the install logs says it's located at:
"BackendUri": "https://wabi-west-europe-b-primary-redirect.analysis.windows.net/"
But I get the "No instances found" message when I try to create the resource in Azure Portal after selecting West Europe as location. I've also tried switching to almost all other locations, but get the same message on all that I've tried.
eloekset
Tuesday, July 17, 2018 2:49 PM
I've got the exact same issue and I have followed guide after guide with no joy whatsoever. Is it because I am on a PAYG subscription?
Wednesday, July 18, 2018 3:56 AM
What is your operating system?
Wednesday, July 18, 2018 6:14 AM
What is your operating system?
Windows Server 2016 Datacenter.
I've:
Logged into the server as the Azure AD user
Installed the data gateway and signed into it using the Azure AD user account.
Logged into Azure portal as the same Azure AD user account.
Given contribute permissions on the Subscription to this account
Yet i still get 'No instances found'.
I've tried it from my PC too, and using different accounts, all not working.
Wednesday, July 18, 2018 8:43 AM | 1 vote
as I said in the other thread; I guess there is some conflict in the regions and for some, it doesn't appear in Azure,
Keep selecting the regions when creating the Gateway resource in the portal and you may see it appear
Hope it help.
**Mark it as Answer **OR **Please Vote as Helpful **by clicking the upward arrow mark
Wednesday, July 18, 2018 9:01 AM
Thanks for the reply. I have gone through all the regions and there is nothing to display at all.
Wednesday, July 18, 2018 9:18 AM
Is there something I need to do with the Windows Service account used for the service in terms of giving it rights?
Wednesday, July 18, 2018 11:17 AM
as I said in the other thread; I guess there is some conflict in the regions and for some, it doesn't appear in Azure,
Keep selecting the regions when creating the Gateway resource in the portal and you may see it appear
Hope it help.
**Mark it as Answer **OR **Please Vote as Helpful **by clicking the upward arrow mark
We do not see it in Azure but it is displaying in PowerApps. The image is uploaded here: https://imgur.com/ZjzhmDY
Thursday, July 19, 2018 9:17 AM
I am facing this exact same issue and have spent all night and morning trying to fix this. How did this resolve?
I'm also facing the same issue. I've followed the steps, and used the same Azure AD account both in the portal and when installing the on-premises gateway. However it's not possible to choose location when installing the gateway. The latest version 14.16.6745.2 (June 2018) doesn't give me that option. But the install logs says it's located at:
"BackendUri": "https://wabi-west-europe-b-primary-redirect.analysis.windows.net/"
But I get the "No instances found" message when I try to create the resource in Azure Portal after selecting West Europe as location. I've also tried switching to almost all other locations, but get the same message on all that I've tried.
eloekset
Exactly the same issue I'm having at a customer right now. Subscription in my case is a CSP subscription. I´m in contact with MS Support and they forwarded the issue at the Product Group today. Expecting an answer soon!
Thursday, July 19, 2018 4:53 PM
when you created the Installed the gateway; have you used the Work or School Account ? OR a tenant account. I know its trivial but just asking.
When I personally installed locally; I created a tenant account like this in Azure Active Directory :
RogerFederarTenant@Winbledon.onmicrosoft.com
Also, the windows services which I am running locally is running under NT Service account; I remember playing around which account to use for this service also.
Thursday, August 16, 2018 9:44 AM
I have been in intensive contact with the OPDG PT via Microsoft Support. They have released a new version yesterday, and now it works! Version is 14.16.6792.1 and can be downloaded here.
Thursday, August 16, 2018 9:46 AM
There was still an issue with CSP subscriptions. I have been in intensive contact with the OPDG PT via Microsoft Support. They have released a new version yesterday, and now it also works for CSP subscriptions! Version is 14.16.6792.1 and can be downloaded here.
Wednesday, November 7, 2018 8:03 PM
This worked for me , I had to click regions until it showed up in the list . Thanks