Resolving 'EveresteCommerceDLL cannot be found' Error

Overview

When users try to access the e-commerce website, they find that the website is down and get an application error message which may vary depending on their e-commerse system but may be similar to:

Error!
Application error: Exception of type 'System.Web.HttpUnhandledException' was thrown.
Object reference not set to an instance of an object.
See error log for more information.

The Windows Event Viewer logs on the Everest server may show "EveresteCommerceDLL cannot be found" errors.

Solution

Follow these steps in sequence to isolate the root cause and resolve the issue:

  1. Restart the Everest COM+ components following the steps provided in this article.
  2. Reset the IIS by executing the following steps:
    1. Click the Start button, then Run
    2. Type CMD, which opens the command prompt window
    3. Execute the command: IISRESET
    4. Reload the eCommerce site to check whether it is functional now
  3. Reset the e-commerce Everest user password from File > Setup > Users > Users to the value specified in the web.config file for your site. The Password value can be found within the <appSettings> element in the IIS configuration file.
    Note: This issue commonly arises due to password expiry. Password expiration can be disabled by following the procedure outlined in Configuring Password Expiration but keeping in mind that this is a global setting that will apply to all Everest users.
  4. If still getting errors pointing to a web server configuration issue, disable IIS caching from the web.config file by updating the caching section (lines 111-117) as follows:
    <!-- caching section group for Web Pages -->
    <caching>
    <outputCacheSettings>
    <outputCacheProfiles>
    <add name="AppCache" enabled="false" />
    </outputCacheProfiles>
    </outputCacheSettings>
    </caching>
    <!-- caching section group for Web Pages -->
  5. Restart IIS

Testing

The e-commerce website should load successfully and allow users to log in without errors.

Back to top

Comments

0 comments

Please sign in to leave a comment.