> For the complete documentation index, see [llms.txt](https://docs.opshub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opshub.com/v7.235/help-center-index/troubleshooting-index/errors-index/microfocus-error-solutions/oh-microfocus-012616.md). # OH-Micro Focus ALM/QC-012616 ## Description When user encounters OH-Micro Focus ALM/QC-012656, following error message will appear: * Micro Focus ALM/QC-012616: Rest request processing Error : 500 Server Error : Probable cause for this error can be either the password entered in the System configuration form is wrong or the server has encountered the condition, which cannot process your request `` (Please check the logs for the detailed response from server). `OpsHub-012654: Error Occurred in HPQC CRUD Request execution for operation getMaxUpdateTime org.hp.qc.api.entities.InvalidValueForFieldException: Failed to convert the 'time' field of a 'audit-log'. The object 2000-01-01+00:00:00 cannot be converted to type QcDate ` * Micro Focus ALM/QC-012616: Rest request processing Error : 500 Internal Server Error : Probable cause for this error can be either the password entered in the System configuration form is wrong or the server has encountered the condition, which cannot process your request (Please check the logs for the detailed response from server). `OpsHub-012654: Error Occurred in HPQC CRUD Request execution for operation getEntityHistorySince org.hp.qc.api.entities.AuditLog$AuditAction.CA_GLXeSignature: No enum const class org.hp.qc.api.entities.AuditLog$AuditAction.CA_GLXeSignature` ## Cause User will encounter this error in the following scenarios: * When the user is running integration(s) of release-cycle in space.vars.OIM having version 7.141 or above **and** your legacy Micro Focus application only accepts `%20` as the encoding of the (space character) in its API. * When the Micro Focus ALM/QC server contains an eSignature-related action (`CA_GLXeSignature`) in its audit records that it cannot process, the audit history request fails with 500 Internal Server error. ## Solution 1. If the error occurs because the **`time` field of the audit log cannot be converted**, then: * Open the directory where space.vars.OIM is installed and navigate to the `OpsHub_Resources/config` directory. * **Duplicate** the `HPQCProperty.properties.sample` file and **rename** it to `HPQCProperty.properties`. * Set the `hpQueryParamEncoding` flag to `true` and restart the OpsHub server service. 2. If the error occurs because of the **`CA_GLXeSignature` audit action**, then: * Navigate to the **Entity level advance configuration** section at the **integration level**. * Locate the **Audit Filter Query** field. * Set the **Audit Filter Query** field to the following value: `action[<>CA_GLXeSignature]`
* The configured audit filter excludes the unsupported `CA_GLXeSignature` audit action from the audit API request, allowing the remaining audit history to be retrieved successfully. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.opshub.com/v7.235/help-center-index/troubleshooting-index/errors-index/microfocus-error-solutions/oh-microfocus-012616.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.