topic Re: Issue while using Connector for Microsoft Power Platform in Digital Exchange

Issue while using Connector for Microsoft Power Platform

AnupamaJaiswal — Wed, 25 Aug 2021 13:24:44 GMT

Hi Team,

We are trying – “Connectors for Microsoft Power Platform” from Digital Exchange and facing below issue for which we will need your intervention or help.

While following the attached guides, we are updating the function host keys in “General Information” of Connectors,

Reading from our Azure Function (published as suggested in guides)-

Although during the test call, we are getting Unauthorised Error (404 Response) but the Request URL is displaying some different path, should it not be pointing to above mentioned host URL of Azure function?

URL - https://europe-001.azure-apim.net/apim/blue-20prism-5f95c943ae2f7220d9-5f1a0fbe1f3c371bc5/0c5a34ed213f41409bfb766011c91ba8/api/BluePrismRestInterface?code=PyHWvD18al105dHja9xB7mrrluoGVfhnPUsJuru9MOyP9KbYq9qS1A%3D%3D&resourceName=bnlweafqap20112.s2.ms.unilever.com&processName=BPPATest

Also, please note we were unable to create/publish the connector with the exact name as displayed in guide- “PowerPlatformConnector”, does it have any dependencies on the name?

Kindly let us know if you would need any input from our end to review this. It would be great if we can connect to understand the blockers here.

Thanks,

Anupama

Re: Issue while using Connector for Microsoft Power Platform

ewilson — Thu, 26 Aug 2021 11:39:29 GMT

Hi @AnupamaJaiswal,

Regarding your last question, no the function names does not need to match what's shown in the documentation exactly. Since the name you enter results in a URI being created in Azure it must be unique otherwise you run the risk of a name collision if someone posted a public Function App with the same name.

Now, regarding the main issue, when you defined the Custom Connector definition in Power Apps did you edit the resourceName, processName, and code sections?

And on the Security tab of the Custom Connector definition, did you specify anything (ex. Basic Authorization)?

Cheers,
Eric

Re: Issue while using Connector for Microsoft Power Platform

ewilson — Thu, 26 Aug 2021 16:59:11 GMT

BTW - The URL shown in the test request is based on what region your overall Azure account is tied to. For example, mine is tied to our Blue Prism HQ address in England, so my test request also use a Europe URL even though my Function is tied to a region in the US. Ultimately, Azure straightens it all out on the backend for the test requests. So thos would not be causing your authentication error.

I believe that is tied to you potentially not having the auth code defined for each of the 3 request definitions.

Cheers,
Eric

Re: Issue while using Connector for Microsoft Power Platform

AnupamaJaiswal — Mon, 30 Aug 2021 07:57:14 GMT

Hi Eric,

Thanks for your responses. To answer your below questions-

1. Yes, we have updated the required details in resourceName, code and processName.
2. We did not make any changes in Security tab, but in the Test section we provided BP login details in the connections prompted for username and password.

We are still stuck with the unauthorized error, please let us know if you have any further insights or would need more details to debug this.

Thanks,
Anupama

Re: Issue while using Connector for Microsoft Power Platform

ewilson — Mon, 30 Aug 2021 17:57:32 GMT

Hi @AnupamaJaiswal,

Ok, so the username and password that you enter on the Connection definition should only apply to the StartProcess action. You should be able to test GetProcessList and GetProcessSchema regardless of the username/password values entered on the connection because those actions are simply scraping the resource PC response you would see if you looked via the browser (ex. http://127.0.0.1:8181/ws/ is the equivalent of the GetProcessList call). Can you verify that performing a test of those two actions is successful?

Cheers,
Eric

Re: Issue while using Connector for Microsoft Power Platform

AnupamaJaiswal — Wed, 01 Sep 2021 05:22:26 GMT

Hi Eric,

Thanks for your response.

We tried other two tests and getting the similar 404 response. Please refer the screenshot below-

Appreciate any leads or documentation what we can refer here.

Thanks,
Anupama

Re: Issue while using Connector for Microsoft Power Platform

ewilson — Wed, 01 Sep 2021 10:34:01 GMT

@AnupamaJaiswal,

The resource name doesn't seem quite right. Typically, a runtime resource needs to be addressed with a specific port number (default is 8181). If you open a browser and enter the value of your resourceName entry with "/ws/" appended to the end do you get back a list of the published processes and VBOs?

Example:
http://bnlweafqap20112.s2.xxxxxxxxx.com/ws/

Cheers,
Eric

Re: Issue while using Connector for Microsoft Power Platform

AnupamaJaiswal — Wed, 01 Sep 2021 12:40:58 GMT

Hi Eric,

When I am opening this link- http://bnlxxxxx0112.s2.ms.xxxxxx.com:8181/ws/ in browser, it is landing to the published processes and VBO's below and giving error without the port number, i.e. - http://bnl xxxxx 20112.s2.ms.xxxxxxx.com/ws/

So, added port number as well to resource name in our "Test Operation" call of GetProcessList, and still getting similar 404 error.

In Summary, have tried with below 3 names in resource name and all gave same error-
a) bnlxxxxxxx20112.s2.ms.xxxxxx.com
b) http://bnlxxxxxxx20112.s2.ms.xxxxxx.com:8181/ ;
c) http://bnlxxxxxxx20112.s2.ms.xxxxxx.com:8181/ws/

Anything else we are missing here?

Re: Issue while using Connector for Microsoft Power Platform

ewilson — Wed, 01 Sep 2021 13:06:17 GMT

@AnupamaJaiswal,

The value of resourceName should just be the resource domain name and port, no HTTP. So it should look like this:

bnlxxxxx0112.s2.ms.xxxxxx.com:8181

Cheers,
Eric

Re: Issue while using Connector for Microsoft Power Platform

AnupamaJaiswal — Thu, 02 Sep 2021 05:31:54 GMT

Hi Eric,

No luck with this one as well-

In this test operation- GetProcessList, there are just two input-
a) resourceName- bnlxxxxx0112.s2.ms.xxxxxx.com:8181
b) code- we picked from Azure Function Apps- in default key below-

The Azure function and Blue Prism Connector file was picked from Digital Exchange.

Let us know if you see anything else we can try and test here.

Thanks,
Anupama

Re: Issue while using Connector for Microsoft Power Platform

ewilson — Thu, 02 Sep 2021 11:26:16 GMT

@AnupamaJaiswal,

So you’re getting a 404, not found, response. The function is located within Azure, in the cloud. Where is the BP runtime resource that you’re trying to communicate with? Is it an Azure VM or something within your corporate network?

While you can see the RR from your machine it seems anything running in the cloud cannot.

Cheers,
Eric

Re: Issue while using Connector for Microsoft Power Platform

pashupati.mishra20 — Fri, 03 Sep 2021 05:01:37 GMT

I made it work by deploying portable AZURE function locally on one of our VDI on internal network. Here's what I did:
1.I kept the function running on VDI, It is on localhost:port
2.Installed Microsoft On-Premise gateway on any VDI that is up 24x7.
3. Setup Custom connector Scheme : HTTP, and check Connect via On-Premise gateway.
4. Provide address of VDI that is running your azure function.
5. Select authentication as none ,as we will be authenticate by On-Premise gateway itself. (On-Premise gateway need to be shared with users who will be accessing this endpoint).
Again I used it in only test environment, You might need to add authorization part to azure function itself because it will be accessible by everyone on local network.

Re: Issue while using Connector for Microsoft Power Platform

AnupamaJaiswal — Mon, 13 Sep 2021 06:49:50 GMT

Hi Eric,

After further analysis it looks like there was no Functions/End points available in our Function app, even though it allowed us to publish the app and was appearing in our Azure Portal.

Please find the below comments from MS support team on trying to resolve this deployment/publishing issues-

As you were using zip deploy method to deploy the Function app code but due to having setting WEBSITE_RUN_FROM_PACKAGE enabled already it was failing.
After removing the setting, we created D:\home\data\SitePackages file and packagename.txt document in same directory and tried Zip deployment, but it failed too.
Then we tested Function app locally and it failed on runtime because the application code you downloaded from gibhub has been developed on ASP.NET Core 2.1 framework and your Visual studio was running on ASP.NET Standard Framework.
We found the same issue even after updating the ASP.NET Core 2.1 SDK in your Virtual Machine.
The function app you are trying to deploy needs to be build with .NET Core framework and published on Azure Functions.
We checked that the Visual Studio installed in your VM is not picking .NET core framework and that’s why we are getting an incompatible framework error in VS.

On point 5 above, is there something which we can do to fix? Please let us know any steps/guide to follow specially on downloading the BP connector code and publishing to Azure, via Visual Studio. Any program or configuration dependency in deploying this?

Appreciate any help here! Let us know if you have any questions.

Thanks,
Anupama

Re: Issue while using Connector for Microsoft Power Platform

ewilson — Mon, 13 Sep 2021 15:47:05 GMT

Hi @AnupamaJaiswal,

I’m not sure where MS Support came away with the idea that the project was built using ASP.NET Core 2.1 unless that’s the only framework that’s available on the machine you published from. The project was built with .NET Standard 2.0 as shown the screenshot below:

If the machine you’re deploying from does not include the .NET Core 2.0 framework, you’ll want to install and then redeploy the Azure Function. Once deployed you should be able to look at the Functions runtime version by going to your Azure Portal, navigating to the Function app, and then selecting Settings → Configuration → Function runtime settings. It should show ~2 as depicted below:

Cheers,
Eric

Re: Issue while using Connector for Microsoft Power Platform

AnupamaJaiswal — Tue, 14 Sep 2021 14:47:09 GMT

Hi Eric,

Can you please help me understand the statement you mentioned below- "If the machine you’re deploying from does not include the .NET Core 2.0 framework, you’ll want to install and then redeploy the Azure Function"

We did try to install .NET Core Framework from the link here- https://dotnet.microsoft.com/download/visual-studio-sdks?utm_source=getdotnetsdk&utm_medium=referral but then it wasn't reflecting in out framework options, like below it shows .NET Standard Framework only.

Please note, when we are publishing the function for the second time (first time it didn't give us any error and hence was reflecting in Azure portal) its giving following build error-
"it was not possible to find any compatible framework version" & "metadata generation failed"

Also, the runtime version on the Azure portal is showing ~2 for us

Please let us know your views on it and kindly share any insights if you can gaze any probable error what we are doing here?

Thanks,
Anupama

Re: Issue while using Connector for Microsoft Power Platform

ewilson — Tue, 14 Sep 2021 16:07:16 GMT

Hi @AnupamaJaiswal,

Apologies on the .NET reference. I actually meant to type .NET Standard 2.0, not Core. Was this present when you published the function the first time? Also, did you see my message, from Sept 2nd, regarding access to the runtime resource?

Cheers,
Eric

Re: Issue while using Connector for Microsoft Power Platform

AnupamaJaiswal — Wed, 15 Sep 2021 08:50:31 GMT

Hi Eric,

Please find responses for your below ques-
1. Was this present when you published the function the first time? - yes it was showing .NET Standard framework and for first time we published in that framework and later anytime for testing while publishing again it threw build errors.
2. Where is the BP runtime resource that you’re trying to communicate with? Is it an Azure VM or something within your corporate network?- The BP run time resource is in our QA Azure VM environment., within our corporate network.

Please let us know if you or someone from team is available for a quick call for a faster resolution.

Thanks,
Anupama

Re: Issue while using Connector for Microsoft Power Platform

ewilson — Wed, 15 Sep 2021 14:09:55 GMT

@AnupamaJaiswal,

The examples you've shown for invoking the runtime resource do not include a port number. Do you know what port your runtime resource is running on? The default port is usually 8181, so if I wanted to call a runtime resource running on my local machine I would reference it as 127.0.0.1:8181. Please verify what port your RR is running on then update your Custom Connector definition in Power Automate to include the port number in the resourceName definition.

Cheers,
Eric

Re: Issue while using Connector for Microsoft Power Platform

AnupamaJaiswal — Thu, 16 Sep 2021 13:00:59 GMT

Hi Eric,

The Runtime resource is running on 8181 only, when we tried to add the port in the Resource name and update the connector-

Its showing that the connector is update-

But it is reverting back to the old resource name (without the port)-

I did test the connector after trying to update this 2-3 times and same 404 error is persistent.

Thanks,
Anupama

Re: Issue while using Connector for Microsoft Power Platform

ewilson — Thu, 16 Sep 2021 14:01:53 GMT

Hi @AnupamaJaiswal,

Ok, did you try manually adding the port definition to the resourceName entry on the Test screen? That should at least let you test using the exact port and will hopefully either show that it works or possibly give us a different error response.

Cheers,
Eric