Document Actions
8.
Cannot Connect to the DMS Through a Web Browser or Go-Between
Up one level
Previous:
Get Error Messages in the Web Browser interface after upgrading the DMS
The problem may be the network connection. Local Solution users can check if they are able to ping the computer or access it through Windows Explorer.
Firms can not run another HTTP server, such as Apache or IIS on the same server, unless you specifically configure them to work together with the OpenEngagement DMS. In some cases, OpenEngagement may be accessible intermittently on servers running both OpenEngagement and IIS. Therefore, users may initially find they do not have problems running both. However, doing this, OpenEngagement may be inaccessible from time to time. To determine if IIS is running, users may check http://localhost through a web browser.
Ensure you are using the correct case in the URL. The OpenEngagement DMS is case-sensitive. For example, if the server is located at http://localhost/CMS, entering http://localhost/cms will not work.
If the server is installed on a computer using the Windows 2003 operating system, there's an application called inetmgr which may be running on port 80. It's possible for this to run on other operating systems as well. Since the CMS also uses port 80, this results in a conflict, and inetmgr may receive traffic intended for the OpenEngagement CMS. One fix for this is to modify the port used by the CMS, which is set in the zope.conf file. Another is to un-install inetmgr or to change the port it uses.