If there is an error, please start your investigation from the error message description.

*Please refer to FAQ No.24348 for how to investigate based off your error message.

 

If no error occurred or you cannot determine the problem from the error, then please make changes to your setting that pertains to the problem and retry the process to isolate the issue.

 

In general, by changing a setting which resolves an ongoing issue and creates a new problem, then most likely that setting is related to the cause. The followings are examples from the past.

 

Also, consider the followings and if there are no issues with the environment or with the connection host, please let us know that the cause of the problem is the product at the inquiry or comment.

 

 

 

We will judge the problematic setting based on the error.

 

For example, error message regarding memory would imply to verify the memory consumption, and error message pertaining to network would imply to check network environment settings.

 

 

 

For problems that have started from a particular point in time, check to see if any change were made in the settings before or after around the similar time frame. The following is an example of such situation.

  Confirm if any change in OS, firewall, and/or security software were made

  Confirm if any change were made on the database and application upon the time of problem

  Confirm if any change were made on the global resources or components of DataSpider Servista

 

If there is such setting, try setting it back to the original to see if that would resolve the issue. If so, that would mean the error was caused by the change in settings.

 

 

 

If error started from a particular point in time, check to see if any change in data and data size were made around the similar time frame.

 

For example, since the starting of the error, check to see if data number has increased or data (including special characters), which in the past not been part of correspondence, has been corresponding.

 

If there is any change in the number of data or the data itself, then try using the data prior to being altered to see if the problem is resolved or not. By doing this, you should be able to determine whether this is the cause or not.

 

 

 

Verify to see whether CPU usage or memory depletion have occurred upon the time of error.

 

For example, if system resource such as CPU, memory, or disk is deficient, then it is possible that process may slow down or even abnormally terminate.

 

If the problem resolves by allocating ample amount of system resources, it is safe to determine that deficiency of resource is the cause.

 

 

 

Verify the processes in order that occurred upon the time of error.

 

For example if it's taking unusually long time to send HTTP request to HTTP trigger, you would be able to isolate the issue by checking the following.

 

 

If a certain problem is occurring due to a process on DataSpider Servista, this can be verified by utilizing alternative options to see if you still encounter the same issue. The following is an example.

For database adapter using JDBC driver for connection, if the problem occurs only on the purpose-specific adapter when testing both purpose-specific adapter and generic adapter separately, then the problem lies in the purpose-specific adapter.

If the issue caused by FTP adapter is fixed upon using other FTP client, FTP process is the cause.