|
Mascot Daemon requires Microsoft Windows NT 4.0 SP6, Windows 2000,
Windows XP Professional, Windows Server 2003, or Windows Vista.
It will not run under Windows 9x or Windows Me.
In addition, Microsoft Internet Explorer 4.01 SP2 or later must
be installed and operational.
Once Mascot Daemon is installed, refer to its on-line help for
detailed information on configuration and use. The on-line help
is context sensitive, so you can jump to a relevant page at any time by
pressing F1.
Note: It is intended that Mascot Server
and Mascot Daemon share the same version number, (e.g. both 2.1 or both 2.2).
In exceptional circumstances, it is possible to use Mascot Daemon 2.2 with
Mascot Server 2.0. This requires the Mascot Server to be updated by
downloading
file updates from the Mascot support page.
If upgrading from an earlier version of Mascot
Daemon, switch to the Upgrading topic Using Microsoft Internet Explorer 4.01 SP2 or later, verify that
it is possible to connect to your Mascot server from the PC on which Mascot
Daemon is to be installed. If there are any problems running a search
from a browser, these must be
resolved before installing Mascot Daemon. There are troubleshooting tips
here. Windows
NT4 (only): Execute HHUPD.EXE by
clicking the link and choosing Run.
This will automatically install or update the Microsoft HTML Help system,
so as to support the Mascot Daemon on-line help. If your system is already
up to date, nothing will be changed. Windows NT4 and 2000 (only): Installation requires the Microsoft
Windows Installer 2.0. This was not part of the original Windows NT4
and 2000 distributions, so the installation may fail and
report that a later version is required.
If so, execute the Windows Installer 2.0 Redistributable for Windows NT 4.0
and 2000 by clicking on this link, InstMsiW.exe,
and choosing Run. You will have to re-boot after this update. Install Mascot Daemon by clicking on this link,
Daemon.msi, and choosing Run or Open. You may see the following message:
If so, execute mdac_typ.exe by clicking on the
link and choosing Run.
This will automatically install or upgrade Windows ODBC drivers to MDAC 2.5 SP3. After re-booting your system, you can
then proceed to install Mascot Daemon by clicking on this link,
Daemon.msi, and choosing Run or Open. Windows Vista (only): Before running Daemon for the first time, it
is essential to give the executables elevated privileges. Open Windows Explorer
and navigate to the Directory where Daemon is installed, (C:\Program Files\Matrix Science\Mascot Daemon
by default). Select Daemon.exe, right click, and choose Properties. On the
Compatibility tab, check Run this program as an administrator. Then do the same for
DaemonService.exe
Start Mascot Daemon from the Windows Start Menu.
Shortly after displaying the splash screen, you will be presented with
the Preferences dialog:
You must enter a valid Mascot server
URL, up to and including the cgi directory. (Note that Mascot Daemon
cannot be used to submit searches to the Matrix Science public web site). If
the web server requires authentication by username and password, these
must be included in the URL, e.g. http://myname:mypass@myserver/mascot/cgi/
The HTTP parameter
settings can be used to modify the way in which Mascot Daemon connects
to the Mascot server. In most cases, the defaults shown above will be
appropriate. The timeout setting is used by the service when submitting
searches, and should not be changed unless you encounter timeout problems.
If you wish to use a different database engine for the task database,
you can specify this from the ADO
connection tab. However, it might be better to do this after
verifying that your system is fully functional
by following the Tutorial in the Mascot Daemon on-line help.
If Mascot Security is enabled, and Mascot requires a user name and
password for login, these must be entered on the Mascot
login tab.
Choose Save.
If you see the following error message:
the Jet 4.0 (Access 2000) ODBC driver is missing or damaged. Follow the
troubleshooting suggestions. Assuming Mascot Daemon is able to communicate
with the Mascot server, the main form will now be displayed
and Mascot Daemon is ready to go.
Tip:
The quickest way to familiarise yourself with Mascot Daemon is to follow
through the Tutorial in the on-line help.
Note:
By default, the service is installed to run under the Local System account,
which cannot access network file shares. You may wish to change the service
properties so that the service runs as a named user, as discussed
in the on-line help topic: In Depth; Mascot Daemon Service.
Note:
If upgrading from Mascot Daemon 1.9 or earlier: Mascot Daemon has been
divided into two components: a Graphical User Interface (GUI) and a Service.
One consequence of this is that the previous registry settings will be
lost. We have also taken the opportunity to change the default installation
path, so that "Mascot" applications can all be found under a
common "Matrix Science" folder.
Note: It is intended that Mascot Server
and Mascot Daemon share the same version number, (e.g. both 2.1 or both 2.2).
In exceptional circumstances, it is possible to use Mascot Daemon 2.2 with
Mascot Server 2.0. This requires the Mascot Server to be updated by
downloading
file updates from the Mascot support page.
If this is a clean installation of Mascot Daemon,
switch to the Installing topic If upgrading from Mascot Daemon 2.0, stop the Mascot Daemon service
using the services control panel. This can be accessed from the Start menu by
choosing Settings; Control Panel; Administrative tools; Services.
Select the entry for Mascot Daemon Service and choose the stop button on the toolbar.
If you wish to keep your existing Task database,
and it is called TaskDB.mdb and is located in the existing application
folder, temporarily move the file to another folder to ensure it is not
accidentally deleted when the old files are uninstalled. Uninstall the previous version of Mascot Daemon,
(this will not delete files that have been added since installation, such
as new parameter files):
From the Windows Start menu, select Settings. Select Control Panel Double-click Add/Remove Programs From the applications list, select Mascot
Daemon and choose Change/Remove.
Windows
NT4 (only): Execute HHUPD.EXE by
clicking the link and choosing Run.
This will automatically install or update the Microsoft HTML Help system,
so as to support the Mascot Daemon on-line help. If your system is already
up to date, nothing will be changed. Windows NT4 and 2000 (only):Installation requires the Microsoft
Windows Installer 2.0. This version was not part of the original Windows NT4
and 2000 distributions, so the installation may fail and
report that a later version is required.
If so, execute the Windows Installer 2.0 Redistributable for Windows NT 4.0
and 2000 by clicking on this link, InstMsiW.exe,
and choosing Run. You will have to re-boot after this update. Install Mascot Daemon by clicking on this link,
Daemon.msi, and choosing Run or Open. You may see the following message:
If so, execute mdac_typ.exe by clicking on the
link and choosing Run.
This will automatically install or upgrade Windows ODBC drivers to MDAC 2.5 SP3. After re-booting your system, you can
then proceed to install Mascot Daemon by clicking on this link,
Daemon.msi, and choosing Run or Open. If you want to retain any of your existing parameter
files, copy the *.par files to the new application folder. By default,
this is C:\Program Files\Matrix Science\Mascot
Daemon. If you decided to retain your old task database,
and it was the default Jet (Microsoft Access) database, called TaskDB.mdb,
then copy it to the new application folder, replacing the empty database
just installed. If your old task database uses a different provider or
has a different name, there is no particular advantage to moving it.
There have been several changes in the task database schema. If your
task database provider is Jet, then Mascot Daemon will update it automatically.
Otherwise, you must modify the database yourself. Refer to the relevant
script in the SQL folder to identify the required changes. Windows Vista (only): Before running Daemon for the first time, it
is essential to give the executables elevated privileges. Open Windows Explorer
and navigate to the Directory where Daemon is installed, (C:\Program Files\Matrix Science\Mascot Daemon
by default). Select Daemon.exe, right click, and choose Properties. On the
Compatibility tab, check Run this program as an administrator. Then do the same for
DaemonService.exe
Start Mascot Daemon from the Windows Start Menu.
Shortly after displaying the splash screen, you will be presented with
the Preferences dialog:
You must enter a valid Mascot server
URL, up to and including the cgi directory. (Note that Mascot Daemon
cannot be used to submit searches to the Matrix Science public web site). If
the web server requires authentication by username and password, these
must be included in the URL, e.g. http://myname:mypass@myserver/mascot/cgi/
The HTTP parameter
settings can be used to modify the way in which Mascot Daemon connects
to the Mascot server. In most cases, the defaults shown above will be
appropriate. The timeout setting is used by the service when submitting
searches, and should not be changed unless you encounter timeout problems.
If you decided to retain your existing task database, you may need to change the
ADO connection tab settings.
If Mascot Security is enabled, and Mascot requires a user name and
password for login, these must be entered on the Mascot
login tab.
Choose Save.
If you are retaining an existing Jet task database,
the following message will be displayed:
Choose OK and, assuming Mascot
Daemon is able to communicate successfully with the Mascot server, the
main form will now be displayed and Mascot Daemon is ready to go.
Note:
By default, the service is installed to run under the Local System account,
which cannot access network file shares. You may wish to change the service
properties so that the service runs as a named user, as discussed
in the on-line help topic: In Depth; Mascot Daemon Service.
Mascot Daemon cannot access files across a network
By default, the service is installed to run under the Local System account,
which cannot access network file shares. You may wish to change the service
properties so that the service runs as a named user, as discussed
in the on-line help topic: In Depth; Mascot Daemon Service.
Problems communicating with the Mascot server
If Mascot Daemon cannot connect to your Mascot Server, or if communication
is unreliable, the first thing to try is submitting a Mascot search from
Internet Explorer on the Mascot Daemon PC.
Verify that you can load the Mascot search
form, submit a search, and view the results.
If you cannot submit a search from a web browser:
Try to ping the Mascot server using its IP address.
If this fails, you have a general network problem. Contact your network
administrator. Try to ping the Mascot server using its hostname.
If this fails, there is a DNS problem. Contact your network administrator. Try to load a plain HTML page. In most cases,
entering just the Mascot server hostname into the browser will load a
default page. If this fails, the web server may not be running or there
may be a more general problem with the server. Contact your server administrator. If you can load a web page from the server, but
cannot successfully submit a Mascot search from a web browser, there may
be some problem with Mascot, such as the Monitor service is not running.
Contact your Mascot system administrator.
If submitting a search from a web browser works OK, then try the following,
one at a time:
Verify that Mascot Daemon and the Mascot Server
are the same version (e.g. both 2.1 or both 2.2). If trying to use Mascot Daemon 2.2 with
Mascot Server 2.0, this requires the Mascot Server to be updated by
downloading
file updates from the Mascot support page.
Re-boot the Mascot Daemon PC Make a note of the Mascot server URL in the Preferences dialog.
Use tracert to verify that the route is direct to the Mascot server, and
not going via a proxy server
 What version of Microsoft Internet Explorer is
installed on the Mascot Daemon PC? If a later version is available, it
may be worth upgrading Try setting the Mascot Daemon PC to communicate
using HTTP/1.0. To do this reliably, you need to select HTTP/1.0 in the
Mascot Daemon Preferences dialog
and then exit Mascot Daemon and stop
the Mascot Daemon Service. Exit all instances of Internet Explorer.
Launch Internet Explorer and go to Tools, Internet Options, Advanced.
Clear both checkboxes under HTTP 1.1 settings.
The next two actions sound like acts of desperation, but don't take
long and have been known to fix intractable problems:
Uninstall and re-install Mascot Daemon Re-install Microsoft Internet Explorer
Problems with data import filters
See details for individual filters in the Mascot Daemon on-line help topic:
In Depth; Data Import Filters.
Problems with ODBC drivers
Mascot Daemon requires Microsoft Data Access Components (MDAC) version
2.5 or later. It should only be necessary to update MDAC if the operating
system is Windows NT4. The MDAC 2.5 SP3 setup can be executed
by clicking on this link, mdac_typ.exe,
and choosing Run.
If you experience problems communicating with the Mascot Daemon task
database, one possible cause is a missing, obsolete or damaged driver.
Microsoft provide a utility, the MDAC Component Checker, that will determine
installed version information and diagnose installation issues. This utility,
along with the latest releases of MDAC, can be downloaded from the Microsoft
Data Access Downloads page.
MDAC 2.6 and later releases do not include driver updates for Jet 4.0
(Access 2000). This is the default driver used by Mascot Daemon so, in
addition to repairing or updating MDAC, you may need to apply a service
pack specifically to install or update the Jet 4.0 drivers. Further information
and download links can be found in Microsoft Knowledge Base article 239114.
There are also some useful tips on troubleshooting Access database problems
in Microsoft Knowledge Base article 303528: HOW TO: Keep
a Jet 4.0 Database in Top Working Condition.
Re-installing Mascot Daemon in a different
path
If you un-install Mascot Daemon, and then re-install in a different
path, it will fail to launch correctly and you will get the message "Failed
to start Mascot Daemon Service". This is because the original installation
path is still present in certain registry entries. (Note that you may
not see this message until you next re-boot the PC).
Choose OK, then Cancel, to exit Mascot Daemon.
Ensure the Windows Control Panel Services Applet
is not running. The fix requires a Microsoft utility, sc.exe,
which can be found on your Mascot server, in the mascot/cluster/Windows_NT
directory. It can also be found on the Mascot installation CD, in mascot.tar
(Unix) or \unpacked\cluster\Windows_NT (Windows). Copy this file to the
Daemon PC, and execute it at a command prompt by entering the following:
sc delete MascotDaemonService
It should return [SC] Delete Service SUCCESS. From the Windows Start menu, choose Run, enter
regedit, and choose OK. If the following key exists, then delete it. (It
should not exist, unless the Services Applet was running during the previous
step): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MascotDaemonService
WARNING:
Editing the registry may render your computer unusable.
You should then be able to launch Mascot Daemon and enter the URL of
the local Mascot server.
|