This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(124.80000000000001, 64%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVL%3C/text%3E%3C/svg%3E)
When connecting a user to desktop Outlook, this error pops up, but the user logs in normally via the web interface and on another computer to the desktop version of Outlook as well, only on that computer it throws this error
Hello,
the user is synchronized with an Active Directory?
Is the first time that happens to this profile? So I mean, in the past have normally used the application without problems?
Have you tried to see if the network informations are normally configured? An example: often happens that a VPN or a proxy avoid to an application to reach the net, in case something it's not setted correctly.
Another test that you can do is to delete his .pst file inside Windows, fromw the Control Panel > Mail (Microsoft Outlook) > Profiles > Show profiles...> and Delete the one (or more) that you're using. Once completed this step, retry to open Outlook from his desktop Icon, put the name of a new Mail profile (that will generate a new one into this Control Panel section) and try to see if the issue persists.
Removing the account from the control panel was also tried, the user has multifactor authentication and that was reset as well, Office was uninstalled from the computer just in case and that didn't help either
What version of Outlook are you using?
In the Network configuration, you're using a proxy or a vpn?
Have you already tried to see if using another laptop/PC the same issue happens?
User has Office 2019 Home and Business, the user has vpn, but it has been tried without it, on another computer the account can be connected to another Outlook without any problem, i think there is something wrong in the registry or the error message is related to the expired authorization token as seen in the screenshot, but I don't know how to remove it from the computer
This 2019 article reports a similar issue, check it:
It explains that is an error caused by the api tool, you can switch to postman to get the token.
2.When creating a user, you must ensure that the user you log in is granted at least the role of user administrator.
Differently, you can try to apply even to refresh the token, when using Office365 activity an error is thrown: "AADSTS700082 The refresh token has expired due to inactivity"
Depending on the flow being used it can manually be deleted from the machine and do the authentication once more:
or
It is also recommended to upgrade to the UiPath.MicrosoftOffice365.Activites 1.6.0 version, as the "Access token has expired".
Both answers have been tried and the paths in which the token should be located on the computer are not
Are you using Windows 10 or 11?
Windows 10
Why don't you try to upgrade on Windows 11?
Because the user who is using that pc doesn't want Windows 11 yet, but upgrading to Windows 11 i think won't solve the problem, reinstalling the computer would certainly solve the problem, but that's the last choice for us
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(41.6, 80%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAL%3C/text%3E%3C/svg%3E)
Hi,
Just want to confirm that the Office app of the computer in question is activated? Does trying to sign in to this client with a different account work?
Hi, It has been a few days and I am checking in to see how things are going on with this issue.
The problem was solved by reinstalling the pc, probably the expired authentication token was stuck somewhere in the registry