Summary
Details
Apex Central
| Issue | Description | KB Article |
|---|---|---|
| Policy Management window of Apex Central freezes after clicking the Deploy button | The Apex Central Policy Management window becomes unresponsive, after initiating deployment. This issue is caused by large parameter content, related to the IIS setting in the environment. | KB 000256631 |
| Missing entry in the php.ini file causes "System error. Error ID: -1" when deploying policies from Apex Central | Policy Deployment status shows "Unable to deploy: See Command Tracking". This is due to a missing php_Ofc.dll entry from the php.ini file. | KB 000256632 |
| Product Directory is empty when creating/modifying a policy while using the "Filter by Criteria" option in Apex Central | Product Directory is empty when using the "Filter by Criteria" in Apex Central. This is due to a possible abnormal data in the Apex Central database in the SQL Server. | KB 000256633 |
| Policy deployment failure after upgrade from Control Manager (TMCM) 6.0 to Apex Central | Upgrading from TMCM 6.0 to Apex Central results to a policy deployment failure, due to a bug in the Apex Central installer. | KB 000255969 |
Apex One
| Issue | Description | KB Article |
|---|---|---|
| Policy status "Pending: Managed Server deploying" due to conflicting subjectNames in Apex One | Conflicting Master_DomainName in OfcUninst.txt and Ofcscan.ini causes a pending status in policy deployment. | KB 000250575 |
| Failure to deploy policy in Apex One | An IP address conflict triggered by TwoWay-communication setting for NAT causes failure in policy deployment in Apex One. | KB 000250609 |
| "System Error. Error ID:-1" error is returned after failure of Policy Deployment from Apex Central to Apex One | Single sign-on (SSO) service issue which may be caused by HTTP conflict causes policy deployment failure from Apex Central to Apex One. | KB 000249248 |
| "Unable to automatically log on to product" error appears in the Command Tracking section of Apex Central | Policy deployment and SSO request both fail due to changed IP address during initial installation of Apex Central. | KB 000249448 |
| Policies are in pending state "Managed Server Deploying" in Apex One | Policies are pending and stuck in "Managed server deploying" status. Both Application Control and Vulnerability Protection services will start but eventually stop for some reason. | KB 000250610 |
| Policy deployment status stuck on "Pending: Managed server deploying" on Apex Central | Deployment status is stuck on "Pending: Managed server deploying" due to missing certificate, OfcOSFWebApp, in Apex One certificate store. | KB 000255970 |
| "Pending: Managed server deploying" status shows when deploying policies from Apex Central to Apex One | The policy deployment from Apex Central to Apex One fails. A missing stored procedure sp_Policy_GetServer from the Apex Central database may cause this issue. | KB 000250594 |
| Database login failure causes policy deployment issues in Apex Central | Incorrect login information to the Apex One database causes the Policy Deployment from Apex Central to Apex One to fail. | KB 000250396 |
| Special characters used in the SQL account password cause failure of the Policy Deployment from Apex Central to Apex One | Issue occurs when special characters are used in the password of the SQL database. A password mismatch between ofcserver.ini and web.config file of OSF will cause policy deployment failure. | KB 000250397 |
| "Pending: Managed server deploying" status is displayed when deploying policies from Apex Central to Apex One features | Policy deployment is stuck on "Pending: Managed server deploying", along with errors, "failed to get private key" and "No client certificate, Authenticate failed". | KB 000256611 |
Apex One Endpoint Sensor
| Issue | Description | KB Article |
|---|---|---|
| Unable to deploy Endpoint Sensor license | Endpoint Sensor license cannot be deployed, which may be caused by SQL permissions in the Endpoint Sensor database. | KB 000250613 |
| Database issue when deploying policy from Apex Central | An issue in the Endpoint Sensor server connecting to the database causes deployment policy problems from Apex Central. | KB 000250839 |
| "System Error. Error ID:-1" error appears when deploying policy from Apex Central to Apex One | Policy deployment from Apex Central to Apex One Endpoint Sensor fails which is caused by an invalid REDIS memory size. | KB 000249804 |
| Policy Description "Endpoint Sensor Service: System error. Error ID: 420" in Apex One | "Unable to get the registered server list. There are no registered servers." error also appears on the Apex Central "Preliminary Investigation" page. This issue is resolved by installing Apex One Hot Fix Build 1141. | KB 000250014 |
Apex One Vulnerability Protection
| Issue | Description | KB Article |
|---|---|---|
| Unable to deploy license to activate Vulnerability Protection in Apex Central | Error "License deployment was unsuccessful" is encountered. This issue is occurs when Apex One uses a certificate with private key un-exportable, which conflicts with Vulnerability Protection constraints. | KB 000250013 |
| "Product communication error" is encountered when deploying policy from Apex Central to Apex One | When deploying policies to Apex One Vulnerability Protection, the message "Product communication error" is encountered. This is caused by the use of HTTP/2. | KB 000250597 |
| "System Error. Error ID:-1" error message appears when deploying Vulnerability Protection (VP) from Apex Central | Apex One Vulnerability Protection fails to deploy because of improper database configuration, causing the connection failure (timeout) when the Vulnerability Protection server tries to connect to the database. | KB 000249246 |
| Policy deployment from Apex Central to Apex One Application Control fails | The policy deployment Apex Central to Apex One Vulnerability Protection fails caused by agent-server communication issue specifically the ofcipcer.dat file in the agent and server being the same. | KB 000250838 |
| Communication issue with iVP agent causes pending policy deployment in Apex One | Error message "Pending: managed server deploying" is encountered. The Apex One Vulnerability Protection agent fails to communicate with the server because of a certificate conflict. | KB 000250611 |
| Policy deployment in OfficeScan is stuck in pending state | This policy deployment problem is caused by Apex One Vulnerability Protection server failing to start due to a certificate issue. | KB 000250840 |
| Failure to activate Vulnerability Protection Service when TCP/IP protocol is disabled on SQL server | When deploying license from Apex Central to Apex One Server, it shows that it is unable to deploy the Activation Code to specified products. This occurs when TCP/IP protocol is disabled on SQL server. | KB 000250009 |
| Failure activating Vulnerability Protection Service when TLS 1.0 is disabled on Apex One Server | Vulnerability Protection Service cannot be activated because it only supports TLS 1.0. When TLS 1.0 is disabled on the server, it causes a communication issue between Vulnerability Protection and the Apex One server. | KB 000250010 |
| Policy deployment failure in OfficeScan | Policy deployment fails with status, "Pending: managed server deploying" and "Failed to start iVP server." in iVP_server0.log. | KB 000250842 |
Apex One Application Control & Vulnerability Protection
| Issue | Description | KB Article |
|---|---|---|
| Unable to deploy Application Control / Vulnerability Protection license in Apex Central | Error "Unable to deploy the Activation Code to specified products" is shown when activating licenses due to web service framework access permission conflict. | KB 000250577 |
| Unable to activate managed product licenses in Apex One due to incorrect SQL account credentials | Managed product licenses cannot be activated and updated policies are not sent to security agents, when managing the Apex One server. | KB 000250576 |
Apex One Endpoint Sensor, Application Control & Vulnerability Protection
| Issue | Description | KB Article |
|---|---|---|
| Policy status "Pending: Managed Server deploying" when enabling iProduct in Apex One | An invalid certificate causes the status "Pending: Managed Server deploying" when enabling iProduct in Apex One. | KB 000250012 |
| Time out encountered when deploying policies from Apex Central to Apex One | Time out is encountered when deploying policy from Apex Central to Apex One, due to an invalid Activation Code | KB 000250393 |
| Apex One Vulnerability Protection policies are not deploying | Missing virtual directories causes Vulnerability Protection not being deployed to Apex One. | KB 000250612 |
Apex One Integrated Modules
| Issue | Description | KB Article |
|---|---|---|
| "Unactivated licenses" error when enabling Apex One feature through policy deployment | Getting "[Error]Failed with exception: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.", when enabling Apex One through policy deployment. | KB 000250008 |
| "Waiting for product agent" status is displayed when deploying policies from Apex Central to Apex One | Too many requests being handled by the IIS server causes the error "Waiting for product agent" status when deploying policies to Apex One. | KB 000250835 |
OfficeScan
| Issue | Description | KB Article |
|---|---|---|
| Control Manager (TMCM) issue deploying policy to the OfficeScan server | TMCM is not able to deploy the policy to the OfficeScan server. This is due to server name mismatch between the OfficeScan and the TMCM servers. | KB 000250625 |
