Skip to main content
Related Search Topics: Errors & Troubleshooting
Print this support article

Resolve "Declare DLL call caused an exception" when opening DDX Connection in SendSuite Xpress or Ascent

Learn how to resolve the error "Declare DLL call caused an exception" when opening DDX Connection in SendSuite Xpress or Ascent.
Products affected: SendSuite® Xpress, Ascent™

Issue

When opening the shipping screen and selecting to use the DDX, the following error message is displayed, or the system crashes:
 
Version 9.90.0011.0000 Build: WIN 95 OS: Windows 6.01 
Shipping Station: 6 
User Name: MASTER USER 
Computer Name: WKS-311 
Error Number: 2027 
Error Message: Declare DLL call caused an exception. 
Line of code with Error: 
Line Number of Error: 383 
Current Active Table: - 
Current Record number: 0 
Program with Error: PROCEDURE SHIPFORM.SC_SL1.CONNECT SHC_INTF.FXP 
Current Datasession ID: 2 
Date/Time: 11/03/16 13:50:25

Cause

  • The Ehlapi32.dll file may be corrupted.
  • The Session ID in Rumba may not match Session ID in SendSuite® Xpress or Ascent™.
  • The user profile may be corrupt.

Resolution

Caution: Contact your IT department to perform these tasks.
  1. On a working peer station:
    1. Use the Windows search box to search for Ehlapi.dll.
    2. Copy the Ehlapi32.dll file to a removable drive or network drive that can be used to copy it onto the station having the issue.
  2. On the station having the issue:
    1. Locate Ehlapi32.dll and open the folder that contains it.
    2. Make a backup of the existing Ehlapi32.dll file (either rename the file or move it to a different folder).
    3. Delete the existing Ehlapi32.dll file.
    4. Paste the copy of Ehlapi32.dll you made from the working peer station into this folder.
    5. Test to see if the issue has been resolved. If not, proceed with the remaining steps.
  3. On the station having the issue:
    1. Open Ascent/Xpress Setup program.
    2. Navigate to Tools > DDX.
    3. Select the List button at the top and select the script you are using.
    4. Go to the Session ID field and see which Session it is on (the default is A).
    5. Open Rumba.
    6. When Rumba is opening, see which Session ID is listed when opening. The Session ID in Ascent/Xpress Setup and Rumba should match. If they do not, change the Session ID in Ascent/Xpress Setup to match Rumba.
    7. Test to see if the issue has been resolved. If not, proceed with the remaining steps.
  4. On the station having the issue:
    1. Sign out as the current user.
    2. Sign in as a different user.
    3. Test to see if the issue occurs with this user profile.
    4. If the issue does not occur with a different user profile, then the original user profile is corrupt and will need to be corrected or removed.
If the issue persists, contact software support for further assistance.

UPDATED: August 14, 2021