Cannot open Protected message from client

%3CLINGO-SUB%20id%3D%22lingo-sub-2267165%22%20slang%3D%22en-US%22%3ECannot%20open%20Protected%20message%20from%20client%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2267165%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20used%20to%20be%20very%20straightforward%20-%20we%20simply%20sign%20in%20on%20the%20outlook%20page%2C%20and%20we%20could%20view%20the%20message%20right%20away.%20It%20now%20gives%20me%20(and%20other%20users%20in%20our%20company)%20the%20following%20message%2C%20and%20we%20aren't%20able%20to%20open%20the%20message%20or%20to%20view%20it.%20Our%20service%20provider%20is%20Godaddy.%20We%20called%20and%20our%20licenses%20are%20all%20up%20to%20date.%20Please%20help.%20Thanks.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Jean-11C_0-1618197257944.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F271864i593B9B970E233F9B%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22Jean-11C_0-1618197257944.png%22%20alt%3D%22Jean-11C_0-1618197257944.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2267165%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Visitor

It used to be very straightforward - we simply sign in on the outlook page, and we could view the message right away. It now gives me (and other users in our company) the following message, and we aren't able to open the message or to view it. Our service provider is Godaddy. We called and our licenses are all up to date. Please help. Thanks.

Jean-11C_0-1618197257944.png

 

2 Replies
We are having the same issues since 4/9/21. Have you gotten a resolution?

Hi Jean,
Do you use Hosted Exchange or Exchange Online? It sounds like hosted Exchange. In which case you may need to request from GoDaddy that they implement the below fix:

This issue often occurs when the setting ClientAccessServerEnabled is not enabled in your IRM Configuration. If you check this by running "Get-IRMConfiguration" in Exchange Management Shell you should make sure it is set to True. If it's not, then you'll need to run the below to update it:

Set-IRMConfiguration -ClientAccessServerEnabled:$true

Then wait up to 24 hours and retest.

For reference:

-ClientAccessServerEnabled
This parameter is available only in on-premises Exchange.

The ClientAccessServerEnabled parameter specifies whether Exchange Client Access servers are allowed to authenticate clients that do not have direct access to AD RMS (for example, Outlook on the web, Exchange ActiveSync or remote Outlook Anywhere clients). Valid values are:

$true: Client Access servers are allowed to authenticate clients. This is the default value. Note that enabling IRM in Outlook on the web requires additional configuration on AD RMS servers. For more information, see Information Rights Management in Outlook Web App.
$false: Client Access servers aren't allowed to authenticate clients.

 

https://docs.microsoft.com/en-us/powershell/module/exchange/set-irmconfiguration?view=exchange-ps