Solved: Re: Winautomation login with Power Automate Licenc...

3TA · ‎11-03-2022

Hi

As of today WinAutomation with Power Automate Licence Login has stopped working.

I have a per user Power Automate Attended RPA licence.

I have just had a windows update (Windows 10) and since then WinAutomation has asked me to log in again. When I submit my Power Automate / Azure email credential I get the following.

Sign in

Sorry, but we’re having trouble with signing you in.

AADSTS700016: Application with identifier '7afbe641-8db0-4580-96d1-b2b58538a3f3' was not found in the directory 'XXXXXXXXXXXXX'. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant.

Troubleshooting details

If you contact your administrator, send this info to them.

Copy info to clipboard

Request Id: d8c6c13e-e816-4bab-999c-9020aca34700

Correlation Id: 34e8b54b-dc22-4f27-bfdd-348299f6bdc4

Timestamp: 2022-11-03T17:24:56Z

Message: AADSTS700016: Application with identifier '7afbe641-8db0-4580-96d1-b2b58538a3f3' was not found in the directory 'XXXXXXXXXXXX'. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant.

Flag sign-in errors for review: Enable flagging

If you plan on getting help for this problem, enable flagging and try to reproduce the error within 20 minutes. Flagged events make diagnostics available and are raised to admin attention.

I checked in Azure and WinAutomation was present in the Enterprise Apps section. I tried setting the flag but it did not show up in Azure. I deleted it from there thinking it would reset when I signed in but it has not and I dont know how to get it back or restore function to WinAutomation.

I need WinAutomation to work again, I am in the middle of a business-critical development and I have thousands of hours of work in my WinAutomation database, going back since 2015. There are numerous problems moving this over to PAD which I will not go into here, but it is going to be an enormous undertaking. I need WinAutomation to function.

I have tried to get support through the Power Automate licence route but when I try to log in it does not recognize my Azure/Power Automate credentials.

Please help.

Please advise how I can restore full functionality to WinAutomation with my Power Automate Unattended RPA licence using my Azure login details as before.

carlos_slim · ‎11-05-2022

My latest: I have a solution now. As mentioned earlier I got the license file from Microsoft, which is valid for half a year. I could not activate it however, but that had to do with the fact I was on WA release 9.2.3.5816. The Microsoft support employee directed me to https://go.microsoft.com/fwlink/?linkid=2133567 in order to download and install release 9.2.4.5905. With this I could activate the software. So I am back in.

I repeated my question why the license is only valid for half a year. Since I bought the perpetual WA software in 2017, for which I bought maintenance each year until the WA acquisition. Instead of just simply answering the question, he asked if I am available for a Teams next week. I am, so will await what this brings. And I will post it here.

Last: I earlier emphasized using old software is a dead end at some point. Exchange, browsers, OS etc. will all evolve, so at some point WA will stop being usable anyhow. Plus all new features/connections will be in PA, so it is not a matter of IF ben WHEN. But as I have stated, and I see other forum members stating this more bluntly: WA has a much, much clearer UI, the desktop triggers (e.g. CTRL combos) cannot be used in PAD, the overview of flows is much clearer in WA (PA has no tree like structure) and lastly PA is much slower starting the processes; once a process runs I cannot see at the moment that this is slower, for sure one can see that starting a process takes up to seconds, whil WA was immediate.

View solution in original post

carlos_slim · ‎11-03-2022

Same here. I have too many processes that can be migrated in a matter of days.

ApexOrigin · ‎11-03-2022

Same error for me.

Says to "contact the administrator." Don't you just love it when you get that message and you are the administrator!

ApexOrigin · ‎11-03-2022

Has anyone opened a ticket yet?

prit6690 · ‎11-03-2022

Did any one get solution ?

ApexOrigin · ‎11-03-2022

I am still waiting on a call back from support. It was difficult opening a ticket with their awkward automated system, but I am finally in the queue after being bounced around. Ticket said they would contact me in 8, but didn’t say mins, days, weeks, months, years, decades, centuries….

3TA · ‎11-03-2022

How did you open a ticket?

I am going to have to spend today finding a solution to this.

Also I have noticed WinAutomation has disappeared from my apps in power automate admin. But I now have some kind of health app, and dynamics 365 apps in there.

Does anyone have the same?

Could be because I deleted the app from Enterprise apps in Azure.

Any body from power platform or azure in here I can tag?

3TA · ‎11-03-2022

Also can anybody else confirm that this occurred after a windows 10 update? A "feature" update I believe.

MathiasRT93 · ‎11-04-2022

Hi,

We are experiencing the same issue.

Has anyone heard from Microsoft on the matter?

3TA · ‎11-04-2022

Nothing here so far.
Can I ask did your issue occur after a Windows 10 upate?

MathiasRT93 · ‎11-04-2022

I thought so initially, but i have the same error on a machine running Server OS

MarcusSch · ‎11-04-2022

Hi All,

we are facing the exact same issue. It is a nightmare as we automated a lot with WinAutomation.

We are using WinAutomation version 9.2.3. on Microsoft Windows Server 2016 Standard (Version 10.0.14393 Build 14393). We are using "Power Automate per user with attended RPA plan".

If anyone finds a solution then please post it here. Thanks!

3TA · ‎11-04-2022

I have tried accessing my Azure portal to register an app and every time I click on the automation icon it just sends me back to the "Welcome to Azure" page. So I cannot even attempt to fix this issue myself. Apparently it wants me to take out an Azure subscription. I am already paying a Power Automate per user licence.

I have also tried using the Power Automate support and that simply wants to funnel me into a bot, with no option to create an actual ticket. And no option to even describe my problem, without it being changed to something else. There is not even enough space to post the error message with the problem description because it exceeds the 256 character limit.

An absolutely infuriating situation, where every avenue is blocked to try to resolve it, without paying for support, or paying for an Azure sub I dont need because all I want to do is use WinAutomation.

Does anybody know who I should be talking to about this, or what avenue of support I should be using? Any suggestions welcome.

3TA · ‎11-04-2022

Does anybody know what I have to purchase to get actually effective real support instead of the automated bot?

Agnius · ‎11-04-2022

Nothing, really, as WinAutomation is past its end of life, so no one in MS is really supporting it, regardless of how much you want to pay for it.

-------------------------------------------------------------------------------------------------------------------------
If I have answered your question, please mark it as the preferred solution. If you like my response, please give it a Thumbs Up.
Regards, Agnius Bartninkas

3TA · ‎11-04-2022

WinAutomation is not the issue here though. It is the sign in with Power Automate per User licence that is broken. And that is one of the features of the licence that it enables continued use of WinAutomation. I am not asking for support for WinAutomation, I am asking for support for Power Automate per User licence to work as advertised.
Do you have any suggestions as to how I can obtain that support?

Agnius · ‎11-04-2022

But it only does not work with WinAutomation as an app in your Azure Portal. Not Power Automate Desktop, which works perfectly fine. So, it is support for WinAutomation technically.

-------------------------------------------------------------------------------------------------------------------------
If I have answered your question, please mark it as the preferred solution. If you like my response, please give it a Thumbs Up.
Regards, Agnius Bartninkas

3TA · ‎11-04-2022

"But it only does not work with WinAutomation as an app in your Azure Portal". WinAutomation (WA) is desktop based app - the Azure aspect is part of the licensing framework. The issue is that the changes made to the licensing have meant that it does not work with WA on the deskop, which it is intended to do.
Again, do you have any suggestions as to how I can obtain actual support for the issue outlined: the power automate licence functionality?

3TA · ‎11-04-2022

So my question is, how do I access this support pledge? Bots do not allow a case to be graded as critical, only "C - Minimal Impact".
Can you help with this?

carlos_slim · ‎11-04-2022

Hello all. A quick update from my side, getting a bit more positive.

First off: I am a WinAutomation user for years. Bought the WinAutomation Professional Plus license, with maintenance, so I am also eligible for a perpetual license. After Microsoft bought the company, in December 2021 I got my license file, but somehow this could not activate. So I subscribed to Power Automate with attended RPA. Because I have hundreds of processes etc. Like probably most of you.

Worked fine, but since yesterday we do not seem to be able to login. While I had planned to migrate my WA processes to PAD, I did not have the time yet, and actually was planning to work on it this month. I already tried the migration tool, and found out that this works pretty well, with some important caveats, e.g. it does not migrate schedules/triggers, and all “Start Process Actions” that are migrated are empty after the migration, and since I have hundreds of processes, it is very difficult to see what processes were needed at that point. Things making people to be reluctant to migrate, if you have so many processes you worked on for years, and that are working like a charm already (and in all honesty, I like the WA interface much better, it is cleaner and gives a much better interface, and the schedules/triggers are much easier to use in WA).

But here we are. Last update from my side: I got into contact with Microsoft support, raised a ticket via https://admin.powerplatform.microsoft.com/support . Since I am eligible for the license file, I have requested to get this one. Also since I don't have high expectations Microsoft fixing the login issue on a short notice. As soon as I have WA up and running, I will migrate my most important processes since I will then be able to check the missing info. Again, not that I like PAD from what I have seen so far, but I also understand that working with software that is ageing is a dead end and risky, as we can all see now.

Will keep you posted. Good luck.