Summary
After clicking the Deploy button, the Policy Management window becomes unresponsive, and succeeding actions cannot be made.
Root Cause Analysis
Some issues are observed in the following log files:
- "'Invalid parameter' failure. Error code: -1" is seen in the Apex Central diagnostic.log located at ..\Control Manager\WebUI\WebApp\widget\repository\log\
2019-12-18 17:10:30,836,DEBUG,null,null,[PROXY-REQUEST] proxy exec.
2019-12-18 17:10:30,836,DEBUG,null,null,[modScloud] exec result:{
"DocumentElement":
{"Result":-1,"Message":"GetTargetURLList: sp_Policy_GetTargetUrlList 'Invalid parameter' failure. Error code: -1","Data":null}
}
2019-12-18 17:10:30,836,DEBUG,null,null,[PROXY-REQUEST] proxy output.
2019-12-18 17:11:02,409,DEBUG,null,null,[modScloud] Init Action:UpdateInheritedPolicy
2019-12-18 17:11:02,409,DEBUG,null,null,[PROXY-REQUEST] proxy exec.
- "Request Entity Too Large" error is seen in the Apex Central php-errors log located at ..\Control Manager\DebugLog\:
[18-Dec-2019 17:11:02 Asia/Dubai] PHP Fatal error: Uncaught SoapFault exception:
[HTTP] Request Entity Too Large in C:\Program Files (x86)\Trend Micro\Control Manager\
WebUI\WebApp\widget\repository\widgetPool\wp1\proxy\modSCloud\WGFServiceApi.abstract.php:45
Based from the log findings above, issue happens when an exception occurs because the parameter content is too large in the request, which results to an unresponsive web page after clicking the Deploy button. The issue is related to the IIS setting in the environment.
To fix the issue, adjust the value of the UploadReadAheadSize in IIS settings. Do the steps below:
- Open Internet Information Services (IIS) Manager.
- Expand the Server field.
- Expand Sites.
- Select Default Web Site.
By default, Apex Central / Control Manager is installed on Default Web Site.
- In the Features section, double-click Configuration Editor, located under Management.
- Under "Section", select system.webServer > serverRuntime.
![]()
- Adjust the uploadReadAheadSize to "52428800".
The uploadReadAheadSize is in bytes.
- Re-deploy the policy to verify if the issue still happens.
Further information about the "Request Entity too large" message can be found in the following Microsoft KB article:
Large file upload failure for Web application calling WCF service - 413 Request entity too large
If the issue still happens after completing the steps above, do the following:
- Collect CDT Logs by following this KB article.
- Submit support ticket to Technical Support.
