Microsoft Secure Tech Accelerator
Apr 03 2024, 07:00 AM - 11:00 AM (PDT)
Microsoft Tech Community
SOLVED

Failed Downloading Information Protection Policy - Firewall error

Copper Contributor

Hi all,

I encountered the same error when deploying in the corporate environment (It worked well in a environment without firewall):

 

The error said that:

 

"Event.ErrorType: [NetworkError], Pii: [None]
Event.Failed.File: [src\core\api_impl\http\http_director_impl.cpp], Pii: [None]
Event.Failed.Func: [mipns::HttpTelemetryHelper::NotifyOperationComplete], Pii: [None]
Event.Failed.Line: [312], Pii: [None]
Event.Failed.Message: [No HTTP response. Failed with: [NetworkError: 'SSL failure Inner exception: [http_exception: 'WinHttpReceiveResponse: 12175: A security error occurred'], NetworkError.Category=SSL, HttpRequest.SanitizedUrl=https://apc01.dataservice.protection.outlook.com/PsorWebService/v1/ClientSyncFile/MipPolicies, HttpRequest.Id={79181A37-C29C-4402-97B6-F9DF866A1093}']], Pii: [None]"

 

Tried to contact the sysadmin guy and asked him to configure the firewall in accordance with the relevant Microsoft guide, but the problem still persists. 

 

Hope that you guys can help me. A detailed guide on the firewall configuration is expected because the error now is narrowed down to this matter only. 

1 Reply
best response confirmed by Nam-Tran (Copper Contributor)
Solution

Thank your for anyone interested in this topic. It's the matter of the certificate problem with the url "https://apc01.dataservice.protection.outlook.com/PsorWebService/v1/ClientSyncFile/MipPolicies". Fortunately, it has been successfully resolved. For details of the relevant log, see "C:\Users\<username>\AppData\Local\Microsoft\MSIP\mip\WINWORD.EXE\mip\logs\mip_sdk.miplog"  

1 best response

Accepted Solutions
best response confirmed by Nam-Tran (Copper Contributor)
Solution

Thank your for anyone interested in this topic. It's the matter of the certificate problem with the url "https://apc01.dataservice.protection.outlook.com/PsorWebService/v1/ClientSyncFile/MipPolicies". Fortunately, it has been successfully resolved. For details of the relevant log, see "C:\Users\<username>\AppData\Local\Microsoft\MSIP\mip\WINWORD.EXE\mip\logs\mip_sdk.miplog"  

View solution in original post