This is the login panel

 

Home|Account

Return to Product Support > Learning Center > Developer References > Installation and Setup

Installation Problem Isolation

Installation Problem Isolation

If, after installing, the web site is still not available, follow these steps to isolate the problem.

  1. Check Web server functionality
    If the web site is returning an error and not a web page, check that the server is running correctly. A simple HelloWorld.htm page is provided in the Admin site at the following address. (http://YourDomain.com/admin/HellowWorld.htm).  You should expect a page with “Hello World”.  If this returns an error, verify the IIS configuration. This is not a Contensive error, but a server configuration problem.
  2. Check ASP functionality
    A simple HelloWorld.asp page is provided in the Admin site at the following address. You should expect a page with “ASP Hello World”.  (http://YourDomain.com/admin/HellowWorld.asp)  If this returns an error, verify the IIS configuration. This is not a Contensive error, but a server configuration problem.
  3. Check Contensive functionality
    If the previous tests passed, test the Contensive status method (http://YourDomain.com/admin/Index.asp?method=status) This should return “Contensive OK”. If it returns any other response, check the page source for an error comment. The most common issues are:
    1. Contensive Application Not Found - Open the Contensive Application Manager and verify your application is running. If it is, the problem may be DCom permissions.
    2. Connection Error opening Datasource Default or Audit - There is a problem with the database, the connection string, or the connection to the machine holding the database.
  4. Check the Contensive Trace Log A trace log is created for all internal Contensive errors. The log is located at [Program Files]\kma\contensive\logs\Tracexxxxx.log. There may be several lines for each error, grouped together by the time of the error. Check the first line of each error group. Generally, the information most likely to assist you will be at the end of the line.
  5. Windows 2003 - If you can not upload, IIS may be limiting the upload size. Use the IIS Metabase editor to set the upload size limit
  6. Windows 2003 - If ASP/ASPX pages will not run, IIS may be blocking them.

This page was last reviewed Saturday, April 04, 2009

Support

Home

Search

FAQ



space
Login
space