It was me that encrypted the message and now I cannot read the reply. Even if I log into office.com and try and read it there.
Posted by: sirclesadmin - 20 June 2024 15:11:43
If you're unable to read an encrypted message that you originally sent, there are a few steps you can take to try and resolve the issue. Here are some common solutions:
Verify Your Access:
Make sure you are logged into Office 365 with the same account that was used to send the encrypted message.
Check Encryption Settings:
Ensure that your encryption settings are correctly configured. Sometimes, incorrect settings can prevent you from accessing encrypted messages.
Update Software:
Make sure that your Office 365 apps (Outlook, for example) are updated to the latest version. Older versions may have compatibility issues with encryption.
Clear Cache and Cookies:
Sometimes, clearing your browser's cache and cookies can resolve issues with accessing encrypted messages.
Try Different Browser or Device:
Attempt to access the message from a different web browser or device. Sometimes, browser-specific issues can cause problems with reading encrypted emails.
Decrypt the Message Manually:
If you used a specific tool or software to encrypt the message, try using the same tool to decrypt it manually. Ensure you have the correct decryption keys or passwords.
Contact IT Support:
If the above steps do not resolve the issue, contact your IT support team. They may have additional tools and insights into why you cannot read the encrypted message.
Check Permissions:
Make sure that the permissions for the encrypted message are correctly set to allow you to read it. You might need to update the permissions if they are incorrectly configured.
If these steps do not resolve the issue, please provide more details about how you encrypted the message and any error messages you receive when attempting to access it.
Posted by: berkscompsltd - 20 June 2024 15:12:54
I used the outlook option 'encrypt message' and now it will not let me read the response I received
Posted by: sirclesadmin - 20 June 2024 15:13:30
If you've used Outlook's "Encrypt Message" option and now cannot read the response, follow these steps to troubleshoot the issue:
1. Verify Office 365 Login
Ensure you are logged into Office 365 with the same account that was used to send the encrypted message.
2. Use Outlook Desktop App
If you're trying to read the encrypted message on the web, try using the Outlook desktop application. The desktop app often handles encrypted messages more effectively than the web version.
3. Check Permissions and Certificates
Ensure your account has the necessary permissions and certificates to read encrypted emails. Sometimes, encryption relies on certificates that must be installed on your device.
4. Update Outlook
Ensure that your Outlook application is up to date. Sometimes, updates include fixes for issues related to encryption.
5. Clear Browser Cache (If Using Web)
If you're accessing the message through a browser, clear your cache and cookies, then try again.
6. Open the Message in a New Browser
Try accessing the encrypted message in a different web browser to rule out browser-specific issues.
7. Download Message
Some email clients allow you to download the encrypted message. Download it and then open it using the appropriate application.
8. Check for IT Policies
If your organization has specific IT policies, they might interfere with your ability to read encrypted messages. Check with your IT department to ensure there are no such restrictions in place.
9. Decrypt Manually (If Applicable)
If you have the decryption key or password, try decrypting the message manually using an appropriate tool.
10. Contact IT Support
If none of the above steps work, contact your organization's IT support team. They may have more specific tools and knowledge to help resolve the issue.
If you continue to experience issues, please provide any specific error messages you receive when attempting to read the encrypted email. This information can help diagnose the problem more accurately.
Posted by: berkscompsltd - 20 June 2024 15:14:32
All I get is an extension with a .rpmsg extension called message message_v2
Posted by: sirclesadmin - 20 June 2024 15:15:04
A .rpmsg file (Rights-Protected Message file) indicates that the message is protected using Microsoft Rights Management Services (RMS). Here are the steps you can follow to open and read the .rpmsg file:
For Outlook Desktop Application:
Download the Message:
Save the .rpmsg file to your computer.
Open with Outlook:
Open the Outlook desktop application.
Drag and drop the .rpmsg file into the Outlook application, or use the "File" > "Open & Export" > "Open Outlook Data File" option to locate and open the file.
For Outlook Web Application:
Open via Outlook Web:
Log into your Office 365 account through your web browser.
Navigate to the email with the .rpmsg attachment.
Click on the attachment to open it. This should prompt Outlook Web to open the encrypted message.
For Mobile Devices:
Outlook Mobile App:
Ensure you have the Outlook app installed on your mobile device.
Download the .rpmsg file attachment.
Open the file using the Outlook app. The app should handle the decryption and display the message.
Additional Steps If Issues Persist:
Verify RMS Settings:
Ensure that your RMS settings and permissions are correctly configured. You might need to check with your IT department if there are any restrictions or specific settings that need to be adjusted.
Update Software:
Ensure that both your Outlook application and any related Office 365 software are up to date. Updates often include fixes for handling encrypted and protected messages.
Use Azure Information Protection Viewer:
Download and install the Azure Information Protection (AIP) Viewer from the Microsoft website.
Open the .rpmsg file using the AIP Viewer.
Clear Cache and Cookies (For Web):
If you are trying to open the message via Outlook Web, clear your browser cache and cookies and try again.
Contact IT Support:
If these steps do not resolve the issue, contact your organization's IT support team for further assistance. They may have additional tools and insights into why you cannot read the encrypted message.
If you encounter any specific error messages or additional issues during these steps, please share those details for more tailored assistance.
Posted by: berkscompsltd - 20 June 2024 15:22:04
All I get is an extension with a .rpmsg extension called message message_v2
All I can see is this:
[attach]92[/attach]
Posted by: berkscompsltd - 20 June 2024 15:25:44
The error I get is Request Id: fcb1cd49-910d-4da5-988c-019902a66400
Correlation Id: 7221b656-8df1-455e-b826-f2998f1f577f
Timestamp: 2024-06-20T14:23:02Z
Message: AADSTS90072: User account '[email protected] from identity provider 'https://sts.windows.net/3f610b88-r50r-474d-35ba-049b02b4744d/' does not exist in tenant 'XXXX Group' and cannot access the application 'd243cwweed6-52b3-4102-ee8ec-aad2292ab01c'(Microsoft Office) in that tenant. The account needs to be added as an external user in the tenant first. Sign out and sign in again with a different Azure Active Directory user account
Posted by: sirclesadmin - 20 June 2024 15:28:00
The error message indicates that there is a tenant mismatch issue. Your account [email protected] is not recognized within the XXXX Group tenant. Here are the steps to resolve this issue:
Steps to Resolve Tenant Mismatch Issue
Sign Out and Sign In Again:
Sign out of all Microsoft accounts on your device.
Clear your browser cache and cookies.
Sign in again to Office 365 with the correct account that has access to the message.
Access as an External User:
The administrator of the XXXX Group tenant needs to add your account [email protected] as a guest/external user.
They can do this by going to the Azure Active Directory admin center, navigating to the 'Users' section, and adding your account as a guest.
Adding a Guest User in Azure AD
If you are the admin or can request admin support, follow these steps:
Navigate to Azure AD:
Go to the Azure Active Directory admin center.
Sign in with an admin account for the XXXXX Group tenant.
Add Guest User:
In the left-hand menu, click on 'Users'.
Click on '+ New guest user'.
Enter your email address [email protected] and fill out the necessary details.
Click 'Invite'. You will receive an invitation email.
Accept the Invitation:
Check your email for the invitation.
Accept the invitation and follow the prompts to join the tenant.
Retry Accessing the Encrypted Email:
Once added as a guest user, sign back into Office 365.
Try accessing the encrypted email again.
Contact IT Support
If these steps do not resolve the issue, contact the IT support team for the XXXXXX Group tenant. They may need to verify and configure additional settings to allow external users to access encrypted messages.
Additional Troubleshooting Steps
Check Multiple Accounts: Ensure that you are not signed into multiple Microsoft accounts simultaneously, as this can sometimes cause conflicts.
Use Different Browser/Device: Try accessing the message from a different browser or device to rule out local issues.
If you follow these steps and still encounter issues, please provide any new error messages or details for further assistance.
Posted by: berkscompsltd - 20 June 2024 15:29:28
But I send encrypted messages to big companies all the time and I can always read them in OWA
Posted by: sirclesadmin - 20 June 2024 15:30:11
Given that you typically send and read encrypted messages without issue and are encountering a specific problem in this instance, it may be due to specific configurations or settings for the tenant or the recipient's configuration. Here are some targeted steps to resolve this issue:
Verify Account and Session
Clear Cache and Cookies:
Clear your browser cache and cookies to ensure there are no residual session issues.
Ensure Correct Account Sign-In:
Make sure you are signed into the correct Office 365 account ([email protected]).
Try Accessing in Different Ways
Outlook Web Access (OWA):
Log into Outlook Web Access.
Navigate to the email with the encrypted message and try opening it directly in OWA.
Outlook Desktop Application:
If you are not already, try accessing the message using the Outlook desktop application.
Save the .rpmsg file to your computer and open it with Outlook.
Addressing Specific Tenant Issues
Since the error message indicates a tenant mismatch, here are specific steps to address this:
Check Tenant Access:
Ensure that your account is properly set up to access the specific tenant (Begbies Traynor Group). This may involve coordination with their IT department.
Guest User Setup:
Begbies Traynor Group Admin Action: They need to add you as a guest user in their Azure AD.
Follow the steps outlined previously to invite you as a guest user.
Detailed Steps for Admins:
Adding a Guest User in Azure AD
Navigate to Azure AD:
Go to the Azure Active Directory admin center.
Sign in with an admin account for the Begbies Traynor Group tenant.
Add Guest User:
In the left-hand menu, click on 'Users'.
Click on '+ New guest user'.
Enter [email protected] and fill out the necessary details.
Click 'Invite'. You will receive an invitation email.
Accept the Invitation:
Check your email for the invitation.
Accept the invitation and follow the prompts to join the tenant.
Check Permissions and Settings
Recipient Permissions:
Ensure that the permissions set on the encrypted email allow you to read it. Sometimes, specific restrictions can prevent access.
Azure Information Protection Viewer
Install AIP Viewer:
Download and install the Azure Information Protection (AIP) Viewer.
Open the .rpmsg file using the AIP Viewer.
Contact IT Support
Coordinate with IT:
If you have followed these steps and still encounter issues, it may be necessary to coordinate with your IT support team or the IT team at Begbies Traynor Group to ensure all configurations are correct.
These steps should help resolve the issue. If you continue to experience problems, providing any new error messages or specific details can further aid in troubleshooting.
Posted by: berkscompsltd - 20 June 2024 15:37:11
But [b]I[/b] encrypted the message, not them!
Posted by: sirclesadmin - 20 June 2024 15:37:36
Since you are the one who encrypted the message and are now unable to read the response, let's focus on resolving this issue from your end. Here are some steps to troubleshoot and potentially resolve the problem:
Ensure Proper Account Access
Sign Out and Sign In:
Sign out of all Microsoft accounts on your device.
Sign in again to Office 365 with your account
Accessing Encrypted Messages
Using Outlook Web Access (OWA):
Go to Outlook Web Access.
Locate the email with the encrypted message.
Try opening the message directly in OWA.
Using Outlook Desktop Application:
Open the Outlook desktop application.
Locate the email with the .rpmsg file.
Open the .rpmsg attachment within the Outlook desktop application.
Dealing with .rpmsg Files
Azure Information Protection Viewer:
Download and install the Azure Information Protection (AIP) Viewer.
Open the .rpmsg file using the AIP Viewer.
Verify RMS Settings
Rights Management Settings:
Ensure that your Rights Management Services (RMS) settings are correctly configured.
Go to the Azure portal and verify that your account has the necessary permissions to access encrypted messages.
Clear Cache and Cookies
Browser Cache and Cookies:
Clear your browser cache and cookies.
Restart your browser and try accessing the message again.
Update Software
Office Updates:
Ensure that your Office applications are updated to the latest version.
Updates often include fixes for issues related to encryption and decryption.
Contact IT Support
If none of the above steps resolve the issue, you may need to contact your IT support team for further assistance. They may be able to provide additional tools or insights to help you access the encrypted message.
Additional Steps for Troubleshooting
Verify Encryption Method:
Confirm that the encryption method used is compatible with your current settings and applications.
Check for Multiple Accounts:
Ensure you are not signed into multiple Microsoft accounts simultaneously, as this can cause conflicts.
Retry Access
After performing these steps, try accessing the encrypted message again. If you encounter any new error messages or specific issues, please provide those details for further assistance.
Posted by: berkscompsltd - 20 June 2024 15:44:59
Outlook 365 does not open it
Posted by: sirclesadmin - 20 June 2024 15:45:45
Given that Outlook 365 is not opening the .rpmsg file, we need to take a few more steps to troubleshoot and resolve this issue. Here are detailed steps:
Confirm Permissions
Check Permissions on the Encrypted Message:
Ensure that the encrypted message’s permissions include your account.
You might need to adjust the permissions or re-encrypt the message to ensure it includes your account.
Using Azure Information Protection Viewer
Download and Install the Viewer:
Download Azure Information Protection (AIP) Viewer.
Install the AIP Viewer on your device.
Open the .rpmsg File:
Launch the AIP Viewer.
Open the .rpmsg file with the AIP Viewer to read the encrypted message.
Check for Multiple Account Conflicts
Ensure Single Account Sign-In:
Ensure you are only signed into Office 365 with the account that encrypted the message.
Sign out of any other Microsoft accounts.
Update Office 365 and Related Applications
Ensure All Software is Up-to-Date:
Update your Office 365 applications to the latest versions.
Sometimes, encryption and decryption issues are resolved in newer updates.
Re-Send the Encrypted Email
Send a New Encrypted Email to Yourself:
Try sending a new encrypted email to yourself to see if you can open it.
If this works, the issue might be with the original encrypted message.
Contact IT Support
Escalate to IT Support:
If none of the above steps work, contact your IT support team for further assistance.
Provide them with the error details and the steps you have already taken.
Try Different Methods
Different Browser or Device:
If you are trying to open the email in a web browser, try a different browser or device.
Sometimes, specific browser settings or issues can prevent opening encrypted messages.
Use Different Network:
Try accessing the message from a different network to rule out any network-related issues.
Clear All Credentials
Clear All Stored Credentials:
Clear any stored credentials on your device using the Credential Manager (Windows) or Keychain Access (Mac).
Steps for Re-Encrypting (if Needed)
Re-Encrypt the Message:
Open the original message in your Sent Items.
Re-send the message with the "Encrypt" option selected to ensure proper permissions are applied.
By following these detailed steps, you should be able to troubleshoot and potentially resolve the issue with opening the .rpmsg file. If you continue to experience problems, providing specific error messages or behavior observed during these steps will be crucial for further assistance.
Posted by: berkscompsltd - 20 June 2024 15:50:20
It says it doesn't support that kind of file
Posted by: sirclesadmin - 20 June 2024 15:52:02
If the Azure Information Protection Viewer says it doesn't support the .rpmsg file, we can try a few more steps to troubleshoot and resolve the issue.
Use Outlook Web Access (OWA)
Access via OWA:
Open a web browser and navigate to Outlook Web Access.
Sign in with your Office 365 account.
Locate the email with the .rpmsg file and try to open it directly in the web interface.
Verify RMS and Encryption Settings
Check Azure RMS Configuration:
Ensure that your organization’s Azure RMS (Rights Management Services) settings are correctly configured to handle .rpmsg files.
Use Different Office 365 Tools
Office Message Encryption (OME) Portal:
Sometimes, you can view encrypted messages through the Office Message Encryption (OME) portal.
When you receive an encrypted message, there should be a link or instructions on how to view the encrypted message through the OME portal. Follow those instructions.
Alternative Method to Open .rpmsg File
Open in Different Email Client:
Try opening the .rpmsg file in a different email client that supports Microsoft encrypted messages, such as another instance of Outlook or a third-party email client that supports RMS.
Steps to Re-Send or Re-Encrypt
Re-Send the Encrypted Email:
Open the original email in your Sent Items folder.
Click on "Forward" and send it to yourself again with the "Encrypt" option to ensure the encryption settings are correct.
Decrypt and Re-Encrypt Using Different Options:
If you have the original unencrypted message, decrypt it and then re-encrypt it using a different encryption method or settings.
Contact Microsoft Support
Microsoft Support:
If none of the above steps work, you may need to contact Microsoft Support for further assistance.
Provide them with the error message and details about the issue.
Step-by-Step Guide to Adding a Guest User (If Applicable)
Add as Guest User:
Ensure that your account is added as a guest user in the necessary tenant (Begbies Traynor Group).
This can sometimes resolve issues with access permissions.
Troubleshoot on Different Device or Browser
Different Device or Browser:
Try opening the encrypted email on a different device or using a different web browser.
Sometimes specific device or browser configurations can cause issues with encrypted messages.
Detailed Steps for Checking and Adjusting Encryption
Open the Original Message:
In your Sent Items, find the original encrypted email.
Check the encryption settings used and ensure they are correctly applied.
Re-Send with Proper Encryption Settings:
If you are unsure of the settings, re-send the email with the "Encrypt" option to ensure the settings are correct.
By following these steps, you should be able to troubleshoot and resolve the issue with the .rpmsg file. If you continue to experience issues, providing any new error messages or behavior observed during these steps will be crucial for further assistance.
Posted by: berkscompsltd - 20 June 2024 15:52:46
Normally there is a 'Read the Message' link that I can click on but this time there isn't!
Posted by: sirclesadmin - 20 June 2024 15:53:43
If the usual "Read the Message" link is missing, here are some steps you can take to troubleshoot and resolve this issue:
Verify Email Client
Open in Outlook Web Access (OWA)
Open a web browser and navigate to Outlook Web Access.
Sign in with your Office 365 account ([email protected]).
Locate the email and check if the "Read the Message" link appears there.
Verify Email Format and Content
Check Email Format
Sometimes the email client might render the message incorrectly. Forward the message to another email address you own and check if the link appears there.
Manual Access via OME Portal
Office Message Encryption (OME) Portal
Go to the Office Message Encryption (OME) Portal.
Sign in with your Office 365 account.
Look for the encrypted message in the portal.
Check Encryption Settings and Permissions
Verify Encryption Settings
Ensure that the email was sent with the correct encryption settings. Sometimes incorrect settings can cause the link to be omitted.
Re-send the encrypted email to yourself to ensure the settings are correct.
Clear Browser Cache and Cookies
Clear Cache and Cookies
Clear your browser's cache and cookies.
Sign in again to Office 365 and check the email for the missing link.
Try Different Browsers or Devices
Use Different Browser
Try opening the email in a different web browser to rule out browser-specific issues.
Try a Different Device
Check the email on a different device to ensure it's not a device-specific issue.
Contact IT Support
IT Support
If the issue persists, contact your organization's IT support team. They can help ensure that all necessary configurations and permissions are in place.
Re-Send the Email
Re-Send with Encryption
Open the original email in your Sent Items.
Forward the email to yourself with the "Encrypt" option selected to ensure proper encryption settings are applied.
Accessing Encrypted Email in Outlook Desktop
Outlook Desktop Application
Open the Outlook desktop application.
Locate the encrypted email and check if the "Read the Message" link appears in the desktop client.
Additional Steps for Ensuring Access
Check Message Details
Verify that the email message was correctly formatted and contains all necessary elements for decryption.
Ensure that there are no issues with the email's HTML rendering that might cause the link to disappear.
Manually Save and Open .rpmsg File
Save the .rpmsg file to your computer.
Try opening it with the Outlook desktop application or other supported email clients.
Detailed Steps for IT and Permissions
Verify User Permissions
Ensure that your account has the necessary permissions to view encrypted messages.
Check with IT to verify that no policies are preventing access.
Check Organizational Settings
Ensure that your organization's settings for encrypted emails are correctly configured.
If these steps do not resolve the issue, providing any new error messages or specific behaviors observed during these steps will be crucial for further assistance.
Posted by: sirclesadmin - 20 June 2024 15:53:43
If the usual "Read the Message" link is missing, here are some steps you can take to troubleshoot and resolve this issue:
Verify Email Client
Open in Outlook Web Access (OWA)
Open a web browser and navigate to Outlook Web Access.
Sign in with your Office 365 account ([email protected]).
Locate the email and check if the "Read the Message" link appears there.
Verify Email Format and Content
Check Email Format
Sometimes the email client might render the message incorrectly. Forward the message to another email address you own and check if the link appears there.
Manual Access via OME Portal
Office Message Encryption (OME) Portal
Go to the Office Message Encryption (OME) Portal.
Sign in with your Office 365 account.
Look for the encrypted message in the portal.
Check Encryption Settings and Permissions
Verify Encryption Settings
Ensure that the email was sent with the correct encryption settings. Sometimes incorrect settings can cause the link to be omitted.
Re-send the encrypted email to yourself to ensure the settings are correct.
Clear Browser Cache and Cookies
Clear Cache and Cookies
Clear your browser's cache and cookies.
Sign in again to Office 365 and check the email for the missing link.
Try Different Browsers or Devices
Use Different Browser
Try opening the email in a different web browser to rule out browser-specific issues.
Try a Different Device
Check the email on a different device to ensure it's not a device-specific issue.
Contact IT Support
IT Support
If the issue persists, contact your organization's IT support team. They can help ensure that all necessary configurations and permissions are in place.
Re-Send the Email
Re-Send with Encryption
Open the original email in your Sent Items.
Forward the email to yourself with the "Encrypt" option selected to ensure proper encryption settings are applied.
Accessing Encrypted Email in Outlook Desktop
Outlook Desktop Application
Open the Outlook desktop application.
Locate the encrypted email and check if the "Read the Message" link appears in the desktop client.
Additional Steps for Ensuring Access
Check Message Details
Verify that the email message was correctly formatted and contains all necessary elements for decryption.
Ensure that there are no issues with the email's HTML rendering that might cause the link to disappear.
Manually Save and Open .rpmsg File
Save the .rpmsg file to your computer.
Try opening it with the Outlook desktop application or other supported email clients.
Detailed Steps for IT and Permissions
Verify User Permissions
Ensure that your account has the necessary permissions to view encrypted messages.
Check with IT to verify that no policies are preventing access.
Check Organizational Settings
Ensure that your organization's settings for encrypted emails are correctly configured.
If these steps do not resolve the issue, providing any new error messages or specific behaviors observed during these steps will be crucial for further assistance.
Posted by: berkscompsltd - 20 June 2024 15:59:38
It tells me I need to install this:
https://www.microsoft.com/en-us/download/details.aspx?id=54536&WT.mc_id=rss_alldownloads_all
But the installation fails even as an admin user and I see this:
[attach]93[/attach]
Posted by: sirclesadmin - 20 June 2024 16:01:20
The link you provided directs to the Microsoft Rights Management Service (RMS) Client. If the installation fails, here are some steps to troubleshoot and resolve the installation issue:
Steps to Troubleshoot Installation Issues
Ensure System Requirements
Verify that your system meets the requirements for the RMS client.
Check the operating system version, .NET Framework version, and other prerequisites mentioned on the download page.
Run as Administrator
Right-click the installer file and select "Run as administrator" to ensure it has the necessary permissions to install.
Disable Antivirus and Firewall
Temporarily disable any antivirus or firewall software that might be interfering with the installation.
Clear Temp Files
Clear your temporary files folder to ensure no corrupted files are causing the issue.
Open the Run dialog (Win + R), type %temp%, and delete all files in the folder.
Check Disk Space
Ensure you have enough disk space available for the installation.
Download Fresh Copy
Download a fresh copy of the installer from the provided link to ensure it is not corrupted.
Check Event Viewer
Open Event Viewer (type "Event Viewer" in the Start menu) and check the Application logs for any specific errors related to the installation. This might provide more insight into why the installation is failing.
Install .NET Framework
Ensure you have the correct version of the .NET Framework installed. The RMS client might require a specific version.
You can download and install the latest version of the .NET Framework from the Microsoft .NET download page.
Use Compatibility Mode
Right-click the installer file, go to Properties, and select the Compatibility tab.
Check the box for "Run this program in compatibility mode for" and select your operating system.
Detailed Steps for Installation
Verify System Requirements:
Check that your system meets all the requirements listed on the download page.
Run Installer as Administrator:
Download the installer.
Right-click on the installer and select "Run as administrator".
Disable Antivirus and Firewall Temporarily:
Disable any antivirus or firewall software.
Run the installer again.
Clear Temporary Files:
Press Win + R, type %temp%, and press Enter.
Delete all files in the temporary folder.
Check Disk Space:
Ensure you have sufficient disk space for the installation.
Download a Fresh Copy:
Download the installer again from the provided link.
Check Event Viewer for Errors:
Open Event Viewer from the Start menu.
Check the Application logs for errors related to the installation.
Ensure .NET Framework is Installed:
Download and install the latest .NET Framework.
Run in Compatibility Mode:
Right-click the installer, select Properties, and go to the Compatibility tab.
Enable "Run this program in compatibility mode for" and choose your operating system.
Reattempt Installation
After performing these steps, try running the installer again. If the installation still fails, provide the specific error message or screenshot you encounter for further assistance. If you have access to another machine, you might also try installing it there to see if the issue is specific to your current setup.
Posted by: berkscompsltd - 20 June 2024 16:03:02
The log file says this:
[4BD0:0F1C][2024-06-20T16:01:38]i001: Burn v3.14.0.1316, Windows v10.0 (Build 22000: Service Pack 0), path: C:\Users\user\AppData\Local\Temp\{BA1A8A2A-362A-4604-B42A-5388C337FE6D}\.cr\PurviewInfoProtectionViewer.exe
[4BD0:0F1C][2024-06-20T16:01:38]i000: Initializing string variable 'AllowTelemetry' to value '-1'
[4BD0:0F1C][2024-06-20T16:01:38]i009: Command Line: '-burn.clean.room=C:\Users\user\AppData\Local\Temp\MicrosoftEdgeDownloads\1ae42c33-7cfd-4c02-ad62-d4221d26269f\PurviewInfoProtectionViewer.exe -burn.filehandle.attached=588 -burn.filehandle.self=596'
[4BD0:0F1C][2024-06-20T16:01:38]i000: Setting string variable 'WixBundleOriginalSource' to value 'C:\Users\user\AppData\Local\Temp\MicrosoftEdgeDownloads\1ae42c33-7cfd-4c02-ad62-d4221d26269f\PurviewInfoProtectionViewer.exe'
[4BD0:0F1C][2024-06-20T16:01:38]i000: Setting string variable 'WixBundleOriginalSourceFolder' to value 'C:\Users\user\AppData\Local\Temp\MicrosoftEdgeDownloads\1ae42c33-7cfd-4c02-ad62-d4221d26269f\'
[4BD0:0F1C][2024-06-20T16:01:38]i000: Setting string variable 'WixBundleLog' to value 'C:\Users\user\AppData\Local\Temp\Information_Protection_Viewer_20240620160138.log'
[4BD0:0F1C][2024-06-20T16:01:38]i000: Setting string variable 'WixBundleName' to value 'Information Protection Viewer'
[4BD0:0F1C][2024-06-20T16:01:38]i000: Setting string variable 'WixBundleManufacturer' to value 'Microsoft Corporation'
[4BD0:5548][2024-06-20T16:01:38]i000: Setting numeric variable 'WixStdBALanguageId' to value 1033
[4BD0:5548][2024-06-20T16:01:38]i000: Setting version variable 'WixBundleFileVersion' to value '3.0.58.0'
[4BD0:0F1C][2024-06-20T16:01:38]i100: Detect begin, 1 packages
[4BD0:0F1C][2024-06-20T16:01:38]i000: Setting string variable 'MSIPInstalled' to value '1'
[4BD0:0F1C][2024-06-20T16:01:38]i000: Setting string variable 'NETFRAMEWORK45' to value '533325'
[4BD0:0F1C][2024-06-20T16:01:38]i101: Detected package: MSIP.Viewer.Setup.msi, state: Absent, cached: None
[4BD0:0F1C][2024-06-20T16:01:38]i052: Condition 'WixBundleInstalled OR (VersionNT > v6.1) OR (VersionNT = v6.1 AND ServicePackLevel >= 1)' evaluates to true.
[4BD0:0F1C][2024-06-20T16:01:38]i052: Condition 'WixBundleInstalled OR (NETFRAMEWORK45 >= "378675")' evaluates to true.
[4BD0:0F1C][2024-06-20T16:01:38]i052: Condition '(MSIPInstalled "1") OR WixBundleInstalled' evaluates to false.
[4BD0:0F1C][2024-06-20T16:01:38]e000: Setup has detected that the Microsoft Purview Information Protection client is installed, which includes the Information Protection Viewer. To install this viewer separately, first uninstall the client.
[4BD0:0F1C][2024-06-20T16:01:38]e000: Error 0x81f40001: Bundle condition evaluated to false: (MSIPInstalled "1") OR WixBundleInstalled
[4BD0:0F1C][2024-06-20T16:01:38]i199: Detect complete, result: 0x0
Posted by: berkscompsltd - 20 June 2024 16:27:23
Still seeing:
[attach]94[/attach]
Which I don't understand as I added the encryption. :(