Troubleshooting after install

 

Below is a list of typical errors that may occur during the use of the administration program, coupled with explanations of what to do.  Note that most errors that occur with matchIT web will be logged in the custom event log called ‘findIT S2 Log’, which can be found in the event viewer - Start > Settings > Control Panel > Administrative Tools > Event Viewer.  Generally more detail can be found about specific errors in the Event Log.

 

Installation Errors

  1. Virtual directory could not be created error

If the virtual directories failed to be created during the installation process, they will have to be created manually in IIS.

Web Service Virtual Directory – create a virtual directory under the default website in IIS called ‘findITS2Service’ and point it to the relevant findITS2Service folder that was installed (c:\{matchIT web Path}\website\findITS2Service), making sure that ‘Read’ and ‘Run Scripts’ were checked.  Once created, make sure that the default document is ‘Service1.asmx’ andthat the directory is configured to run on ASP.NET version 2.0 (which covers ASP.NET 3.5).  You should then be able to browse to the landing page of the web service in IIS and see a list of the available web methods.

Web Site Virtual Directory – create a virtual directory under the default website in IIS called ‘findITS2Site’ and point it to the relevant findITS2Site folder that was installed (c:\{matchIT web Path}\website\findITS2Site), making sure that ‘Read’ and ‘Run Scripts’ were checked.  Once created, make sure that the default document is ‘Default.aspx’ and that the directory is configured to run on ASP.NET version 2.0 (which covers ASP.NET 3.5).  You should then be able to browse to the landing page of the web site in IIS and see the data input form.

 

Web Browser Errors

  1. The web service or sample website cannot be browsed to –

A common cause of this is that IIS is not running, so check that.  Otherwise, check whether or not the virtual directories findITS2Site or findITS2Service actually exist in IIS.  If not, there was an error on installation that caused the virtual directories to not get created.  In this case they will have to be created manually, and point to :

c:/{matchIT web app path}/website/findITS2Site 

and

c:/{matchIT web app path}/website/findITS2Service respectively.

  1. ‘Error with the Configuration Class’ message

When performing a search on the sample web site (or just retrieving a results XML string from the web service) and you receive this message, it normally means that the web service configuration is unavailable.  A common cause of this is that the XML configuration file has not been loaded, or the configuration status has been disabled in the admin program.  To fix this, simply reload the XML configuration in the findIT S2 Administration program.

 

Administration Program Errors

  1. Cannot connect to Web Server

If you receive an error message when trying to load the XML configuration file stating that the web service cannot be connected to, the common cause of this is that either IIS is not running as a service, or the findITS2Service virtual directory is not running in IIS.  Check that both of these are indeed running.

  1. Configuration File Formatting Error

Errors with the configuration file when trying to load the configuration are normally down to bad formatting of the configuration file – unclosed tags and missing quotation marks are just two examples of common mistakes.  The easiest way to check if the XML file formatting is valid is to view it in an internet browser, like internet explorer – If it is not valid an error message will be displayed and an explanation of where the error has occurred.

  1. Datasource connection error

If you get an error saying that there is an error with the datasource connection, this means that there is probably an error with your connection string specified in the XML.  Check that the data source, initial catalog and other credentials are correct.  If you still cannot connect check that the user specified in the connection string has access to the database in question.  Another thing worth checking in the case of SQL Server is whether SQL Server is running in mixed mode (Windows and SQL Authentication).

  1. Table does not exist error

An error stating that a particular table does not exist normally points to a spelling mistake in a table name in the XML.  Double check all the tables in the XML for the datasource in question.

  1. Column does not exist error

This error means that the column name in question does not exist for the tables that you have specified in your datasource. Double check the field mapping in the XML and check that the database column is spelt correctly, and that the column specified actually does exist.

  1. Addition Error Information

In addition to the on screen message, users are encouraged to view the windows event log for any -2 return codes for the findIT S2 admin tool. You can access this via

Control Panel --> Administrative Tools --> Event Viewer

The below features additional information returned where there is a configuration load error due to a badly formatted findITConfiguration.xml file.

  1. Unable to open Accumail database for processing

When calling the address web service, and receiving the following message returned :

<?xml version="1.0" encoding="utf-8" ?>

<string xmlns="http://tempuri.org/">Unable to open Accumail database for processing.</string>

normally means either

  • a) the addressIT data was not installed on your machine properly.
  • b) You have not installed the latest dataset – the addressIT datasets expire every 2 months and the addressing service will not function if your data is out of date.
  • c) You may need to grant read/write permissions to the addressIT install directory
  • d) You can stop/start the app pool as a domain account that does have read/write permissions.