Table of Contents
・Points to check when you want to isolate the problem
・If you want to know the reasons why checking is required
・If you still cannot determine the cause or recover from the problem even after reading this document

Also, if you would like more information related to this inquiry, please check "Reference Information."
 

1. Ports

Check to see if there are any processes using the port(s) that DataSpiderServer uses by utilizing the commands such as "netstat."
* For details, please check the commands of operating system that you are using.

Workaround:
　If there is a process using the port that DataSpiderServer uses, then stop the process and attempt the startup again.

2. License Files

Make sure the license file is placed in the following directory.
$DATASPIDER_HOME/server/lic/
　
Workaround:
　If the license file is not placed, please do so and attempt the startup again.

3. Server Modules

Create an environment applied with the same version, the same service pack, and the same patch as the environment in which the problem is occurring. Also, install the same driver. Then check to make sure the number of modules and their names match up with the problem environment.

If there is a module that is absent only in the environment with problem, it is possible that its absence is the cause for the error's occurrence.

Workaround:
　Return the module to the state it was in before the problem began using one of the following measures.

　-Restore from a backup
　　If you have a backup, return the following directory to the state it was in before the problem began.

　　$DATASPIDER_HOME/server

　　*If you use repository database, please be sure to return them to the same date and time as the module in order to preserve integrity.

　　*Please note that if there are files created via cooperative processing with DataSpider Servista in the above directory, those files will also return to its original state.

　-Reinstallation
　　If you are using version 2.4 or later, reinstall the environment by referring to "Upgrade Guide" of your version, backing up the old environment, installing the new one, and transferring all of the various settings.

 

　　For our customers using a version prior to 2.4, you will not be able to use the above procedure. If this is the case, we ask that you please restore from a backup.

4. Internal Settings File
　Expand the following internal settings file, and check to make sure the file has ended with </projects>.
　$DATASPIDER_HOME/server/etc/projects.xml

Workaround:
　  Handle in same manner as the section 3.

 

DataSpiderServer's startup process is executed in the sequence listed below.
For this reason, DataSpiderServer is unable to start due to process failures in any of the stages below.

(1) Loading of Java modules needed for process of loading module to operate DataSpiderServer

　If there are any module mismatches, an error will occur and the startup will fail.
　This is why we check "3. Server Modules."   

(2) Initialization of the modules loaded in (1)
　Make into a state in which the process can begin by loading the license and settings file, and initializing the loaded modules.

　If the license does not exist or the settings file is not properly configured, the startup will fail.
　This is why we check "2. License File" and "4. Internal Settings File."

(3) Starting of the process using the assigned port
　Using the port assigned in the DataSpiderServer settings or upon installation, start the DataSpiderServer process.

　If the assigned port is being used by another application, the startup will fail.
　This is why we check "1. Ports."

 

If the problem cannot be resolved even by executing all of the contents described in the "Points to Check and Workarounds," it is possible that the successful completion of the startup process is being hindered by the occurrence of an error that has not occurred in the past.

To confirm the situation, please inquire at the support center after checking the following information.

(1) What triggered the issue
　Check whether the problem started directly after installing DataSpiderServer, or if it started occurring suddenly in an environment where there were no problems until then.

　Also, if the problem started occurring, we also ask that you check the date at which you first noticed the occurrence of the issue, and any settings that were changed or work that was done before or after that date.

(2) Frequency of occurrence and existence of workaround
　To determine the impacts on operations, check the frequency of occurrence (every day; every month; etc.) and whether there is a workaround (restart service via "recovery," etc.).

(3) Conditions for occurrence of the issue
　Please let us know if you have noticed any conditions in which the issue occurs (occurs when security software is running, etc.).

(4) Log files
　Please send us the following log files output at the time of issue occurred.

　$DATASPIDER_HOME/server/logs/server.log
　$DATASPIDER_HOME/server/logs/server.log.N （* N is a half-width alphanumeric character)
　$DATASPIDER_HOME/server/logs/server.error.log

A log file in $DATASPIDER_HOME that includes the words "install," or "インストール" ("install" in Japanese), in the file name, and ends with ".log."

(5) Log of when you start up into debug mode from an execution file
　If the log has not been output to server.log at the time of startup, start up DataSpiderServer from the execution file while holding down the "Ctrl" key. Then copy and paste the log output to the console and send it to us. The execution file is located in the following directory.
　$DATASPIDER_HOME/server/bin/DataSpiderServer.exe

(6) Modules
　Send us the following directory containing the pre-recovery backup.
　$DATASPIDER_HOME/server

*If the file size exceeds 5MB after you compress it, please let us know when you make an inquiry, and we will prepare a site to which you can upload it.