Documentum与.NET集成后上传文档报错：Execute服务调用失败

Hey there, let's break down this frustrating error you're hitting when uploading documents to Documentum from your .NET app. That "no endpoint listening" message usually boils down to a handful of common misconfigurations or network issues—let's walk through them step by step to get you back on track:

1. Double-Check the Endpoint URL #

First things first: verify that the URL https://dfs-uat.abc.com:800/services/core/QueryService is 100% correct.

• Typos happen easily—double-check the domain, port (800), and path. UAT environments often have slightly different addresses than production or staging, so confirm the exact URL with your Documentum admin if you're unsure.
• Test the URL directly in a browser or tool like Postman/curl. If you get a 404, timeout, or "cannot connect" error, the address itself is invalid or unreachable from your network.
• For HTTPS endpoints: Make sure your .NET app trusts the SSL certificate used by the UAT DFS server. Self-signed certificates (common in UAT) aren't trusted by default—you'll need to import the certificate into your app's trusted store or configure the client to bypass validation temporarily (only for testing!).

2. Validate SOAP Action & WCF Configuration #

The error explicitly calls out a possible SOAP action misconfiguration, so let's dig into that:

• If you're using WCF to call DFS services, check your app.config or web.config for the <endpoint> section matching the QueryService. Ensure:
  • The address matches the exact endpoint URL
  • The binding (e.g., basicHttpBinding or wsHttpBinding) matches what the DFS server is configured to use
  • The contract points to the correct generated service interface (e.g., YourNamespace.IQueryService)
• The SOAP action for the Execute method should align with Documentum's DFS specs. For QueryService, it typically looks like http://documentum.com/dfs/core/QueryService/Execute—you can verify this by checking the WSDL of the DFS service (append ?wsdl to the endpoint URL in a browser to view it).

Here's an example of a valid WCF endpoint configuration snippet to reference:

<system.serviceModel>
  <client>
    <endpoint 
      address="https://dfs-uat.abc.com:800/services/core/QueryService"
      binding="basicHttpBinding"
      bindingConfiguration="BasicHttpBinding_IQueryService"
      contract="QueryService.IQueryService"
      name="BasicHttpBinding_IQueryService"
    />
  </client>
</system.serviceModel>

3. Rule Out Network & Firewall Blockages #

More often than not, this error is caused by network restrictions:

• Test connectivity from your app server to the DFS server:
  • Use ping dfs-uat.abc.com to confirm the server is reachable
  • Use telnet dfs-uat.abc.com 800 to check if the port is open
• If either test fails, work with your network team to confirm:
  • Firewall rules allow outbound traffic from your app server to port 800 on the DFS UAT server
  • No proxy server is blocking the request (if you use a proxy, ensure your .NET app is configured to use it via config or code)

4. Confirm Documentum DFS Service Status #

Don't overlook the server-side:

• Reach out to your Documentum administrator to verify that the QueryService is running properly in the UAT environment. Services can crash, fail to deploy, or be misconfigured—ask them to check the DFS service logs for startup errors or incoming request failures.
• Ensure the QueryService is deployed to the exact path specified in your endpoint URL (sometimes deployments can accidentally change the service path).

5. Dig Into the InnerException #

The error message mentions checking the InnerException—do this! It will give you granular details that the top-level error hides. For example:

• An SSL-related InnerException might say "Remote certificate is invalid according to the validation procedure" (pointing to certificate trust issues)
• A timeout exception will tell you the connection is taking too long (likely network/firewall)
• An HTTP 401 error indicates authentication issues (check if your app is sending the correct credentials to DFS)

By following these steps, you should be able to narrow down the root cause and fix the endpoint connectivity issue.

内容的提问来源于stack exchange，提问作者sai