Progress Error 54:如何根据证书ID 6ae7a2a5.0查找对应证书名称?
Troubleshooting Progress Error 54: Unable to Get Local Issuer Certificate
Let’s break down how to fix this issue step by step—since you’ve already imported the WSDL-related certificates and narrowed it down to IE-specific PDF rendering after switching to HTTPS, here’s what to focus on:
First: Identify the Certificate Behind 6ae7a2a5.0
That alphanumeric ID is OpenEdge’s internal reference to a certificate’s MD5 hash. To find the actual certificate entry or file:
- Open Windows Certificate Manager (
certmgr.msc) and navigate through all stores (Personal, Trusted Root Certification Authorities, Intermediate Certification Authorities). For each certificate, go to its Details tab—look for the MD5 Hash (you may need to add this field via "Add Fields" if it’s not visible). Compare the first 8 characters of the hash to6ae7a2a5to match the correct certificate. - Alternatively, use OpenEdge’s
proenvcommand prompt: runcertmgr listto see all certificates registered in OpenEdge’s store, and look for the entry with the ID6ae7a2a5.0.
Fix the Trust Chain Issue
Error -54 almost always means OpenEdge can’t verify the full certificate chain, even if you’ve imported the server certificate. Here’s how to resolve it:
- Ensure the full certificate chain is installed:
- If the matched certificate is a server certificate, check if its intermediate and root CA certificates are also installed in both Windows’ certificate store and OpenEdge’s
certdirectory (c:\Program Files(86)\OpenEdge_113\cert). - Run
certutil -verifyurl https://example.com/OnLineService.asmx?wsdlin Command Prompt to check for missing chain certificates—this will flag any gaps in the trust path.
- If the matched certificate is a server certificate, check if its intermediate and root CA certificates are also installed in both Windows’ certificate store and OpenEdge’s
- Point OpenEdge directly to the certificate:
Modify yourconnectcall to explicitly reference the trusted certificate or trust store. For example:
Note: Use double quotes around paths with spaces to avoid parsing errors.create server hWeb. hWeb:connect("-wsdl -WSDL https://example.com/OnLineService.asmx?wsdl -truststore ""c:\Program Files(86)\OpenEdge_113\cert\cacerts.pem"" -cert ""c:\path\to\your\matching-cert.crt""") no-error. - Tweak IE’s certificate and security settings:
IE uses Windows’ certificate store but has stricter defaults for PDF rendering:- Go to Internet Options > Content > Certificates and confirm the matching certificate (and its chain) are in the Trusted Root Certification Authorities tab.
- Add
https://example.comto IE’s Trusted Sites (Internet Options > Security > Trusted Sites > Sites) and lower the security level temporarily to test if that’s blocking the certificate.
Debug Further with Extended Error Details
Instead of only grabbing the first error message, modify your code to retrieve all error details—this might reveal hidden issues with the certificate chain:
create server hWeb. hWeb:connect(cWSDL) no-error. if not hWeb:connected() then do: pcMeddelande = "". do i = 1 to error-status:num-messages: pcMeddelande = pcMeddelande + error-status:get-message(i) + chr(10). end. message pcMeddelande view-as alert-box. hWeb:disconnect(). delete object hPortType no-error. delete object hWeb no-error. return. end.
内容的提问来源于stack exchange,提问作者Karthikeyan
相关产品推荐
相关产品推荐

