Systemwalker Desktop Keeper Reference Manual

3.5.5 Message Output During Operation

3.5.5.1 Message Output with User Management Command

Incorrect parameter number.

Cause

The specified parameter is incorrect.

Resolution

Specify the correct parameter.

Incorrect format.

Cause

The format of command parameter is incorrect.

Resolution

Specify the command parameter in a correct format.

[IpAddress] is incorrect. Please specify within 1-39 halfwidth characters.

Cause

The length of IP address is incorrect.

Resolution

Enter an IP address of correct length.

The User ID of Management Server [%s] does not exist.

Cause

The user ID of specified Management Server does not exist.

Resolution

Specify the existed user ID of the Management Server.

Failed to delete the user. Please try again after dealing with the cause.

Cause

There is a possibility that the database is not operating.

Resolution

Execute again after confirming whether the database is operating normally.

Failed to access to database. Please try again after dealing with the cause.

Cause

There is a possibility that the database is not operating.

Resolution

Execute again after confirming whether the database is operating normally.

It is not the user of Log Analyzer.

Cause

The specified user name is not the name of the Log Analyzer User.

Resolution

Specify the correct name of the Log Analyzer User.

Not logged in with Log Analyzer User.

Cause

The Log Analyzer User is not used to login to Windows.

Resolution

Use Log Analyzer User to login to Windows.

Failed to change the password of Log Analyzer user.

Cause

Probable causes are as follows:

• The environment is destroyed.

• The authority of the Log Analyzer User is insufficient.

• The database is not operating.

Resolution

Check the following conditions according to the causes, and execute again.

• The environment is not destroyed.

• The authority of the Log Analyzer User is sufficient.

• The database is operating.

Internal exception occurred. Please execute again.

Cause

As the resource is insufficient, the temporary errors occurred due to some causes such as timing error.

Resolution

Execute the operation again.

3.5.5.2 Message Output with Data Import Command

Failed to save log data.

Cause

Failed to save the log data due to some causes such as the operation for saving data has been performed in the process of accessing to database, when a file path exceeding 260 characters is included in the data to be imported.

Resolution

Execute again after confirming whether the database is being accessed.

If the above issue is not resolved, contact Fujitsu technical staff.

Database is not started.

Cause

The database is not started.

Resolution

Start the service "SymfoWARE RDB SWDTLA".

The log data to be saved does not exist.

Cause

The log data of the Management Server does not exist in the specified folder, so the log data cannot be saved.

Resolution

Specify the folder that includes log data.

The specified folder does not exist.

Cause

The specified folder does not exist.

Resolution

Execute again after confirming that the specified folder does exist.

The specified folder is too long. Please specify a path within 70 fullwidth characters, 140 halfwidth characters.

Cause

The folder exceeding 70 fullwidth characters and 140 halfwidth characters has been specified.

Resolution

Check the saving target path of log data and execute again.

The size of the saved data has exceeded the database space.

Cause

The size of data to be saved has exceeded the size of database space.

Resolution

Recreate a database with larger capacity, or reduce the amount of log data to be imported.

Error occurred during night-time Perform night-time batch aggregation.
Perform the batch aggregation processing of error period again at next startup.

Cause

Probable causes are the following:

• The CSV data regarded as aggregation target is not saved in the date folder of aggregation period (in the format of 20060101_20060131).

• Failed to access to the database.

Resolution

According to different causes, take the following resolutions.

• Execute again after saving the CSV data regarded as aggregation target in the date folder.

• Confirm that the service "SymfoWARE RDB SWDTLA" has been started.

Error occurred during night-time Perform night-time batch aggregation.

Cause

Probable causes are the following:

• Failed to access to the database.

Resolution

According to different causes, take the following resolutions.

• Execute again after confirming the environment of database.

The restore during the night batch aggregation failed.

Cause

After an error occurred, failed to restore the data of aggregation results.

Resolution

After confirming that the seven backup data files (CSV files) exist under [Installation Folder of the Log Analyzer Server] \bin\batchnavi, contact Fujitsu technical staff.

Version information is not recorded in trans_end file.

Cause

Probable causes are the following:

• The specified data is data transmitted by Systemwalker Desktop Log Analyzer V12 log linking Adapter.

• The records in the trans_end file are not complete.

Resolution

According to different causes, take the following resolutions.

• Execute again after specifying the data transmitted by using data transmission command.

• Execute again after confirming that the contents recorded in the trans_end file are correct.

The data to be moved is the version out of operation scope [%s].

Cause

The Management Server data of incompatible version will be imported to the Log Analyzer Server.

Resolution

Execute again after specifying the Management Server data of compatible version.

Failed to restore to database.

Cause

The data restoration processing executed when the operation failed. Therefore, the user management information may be damaged.

Resolution

After confirming that there is a file with extension "bkup" in the folders specified by -f option, contact Fujitsu technical staff.

Failed to access to database.

Cause

There is a possibility that the other processes are accessing to the database.

Resolution

After confirming that the other processes are not accessing to the database, contact Fujitsu technical staff.

The period specification folder is out of standard.

Cause

The date folder name of log data does not confirm to the rules.

Resolution

Confirm whether the date folder of log data confirms to the format of "01012006_01312006".

Unable to move in target data.
The operating environment of Log Analyzer Server contains detects.

Cause

Probable causes are the following:

• When transferring the environment of the Management Server to other computer, the transfer executed through data transmission command is not performed normally.

• The user information the Management Server expelling from the operating environment is not deleted from the Log Analyzer Server.

• Part of the Management Server data is not imported.

• In the server information settings of Server Settings Tool, the IP address of this node is set to loop back address (127.0.0.1).

Resolution

According to different causes, take the following resolutions:

• The setting file used for data transmission command can be transferred according to the transferring method of the Management Server. After that, in the data transmitted from Management Server in which the environment transfer is executed, the trans_end file can be modified, and the data can be imported again.

  Example) When the Management Server (computer name: SV1) is not transferred normally

  1. Transfer the setting file (TRANS_SETTING.ini) used for data transmission command according to the transferring method of the Management Server.

  2. Open the TRANS_SETTING.ini file transferred based on Step 1 by editor, and copy the 36 characters string after the "KID=" of [DTKSERVERINFO] keyword.

  3. Find out the Management Server data transmitted to Log Analyzer Server, and open the tran_end file in the folder by editor, and then replace the string after "KID=" of [DTK] keyword as the string copied in Step 2. whether it is the target Management Server data or not, it can be determined through the folder name under the 2-level from the shared folder path.

     [The following mentioned is an example when the shared folder is "C:\LASVDATA", the data is Management Server data (computer name: SV1)]

     C:\LASVDATA\20080211\SV1\20080210_20080210
     C:\LASVDATA\20080212\SV1\20080211_20080211
     C:\LASVDATA\20080213\SV1\20080212_20080212

     Note) When the computer name of the Management Server is modified in the operating process, the folder name under the 2-level in the shared folder path will also be modified and note that.

  4. Execute the data import command.

• Use the delete option of user management command to delete the user information of the Management Server expelling from the operating environment, and then import the data again.

• Exclude the causes for Exclude the causes for not being able to import, import, and import the data that cannot be imported to Log Analyzer Server, and then import the data again.

• In the server information settings of Server Settings Tool, when the IP address of this node is set to loop back address (127.0.0.1), modify it as ordinary IP address.

Failed to start Log Analyzer Server.

Cause

Failed to start the service of Interstage Navigator Server.

Resolution

Start the service with Interstage Navigator Server > Navigator Server Start and Stop.

Session reading error in batcherror.ini file. [Key Name]

Cause

Failed to read the required information from the batcherror.ini file.

Resolution

Confirm whether the batcherror.ini file has been damaged.

It is executed by a user that is not Administrator. End the command.

Cause

The Log Analyzer User is not used for execution.

Resolution

Specify the execution user as Log Analyzer User, and then execute again.

Parameter error occurred. [Ret=XX]

Cause

The specified parameter is incorrect.

Resolution

Execute again after confirming whether the parameter is correct.

Failed to access setting information.

Cause

There is a possibility that the log analyzer user has not executed the process.

Resolution

Execute again after confirming whether the execution user is Log Analyzer User.

Session reading error in batcherror.ini file [xxxxx]" or "x [x] WritePrivateProfileString xxxxx Error [xxxxx]

Cause

Another aggregation processing preparation failed.

Resolution

It is caused because the aggregation results may not match.
Aggregate again by using -r option.

Failed to stop Log Analyzer Server.

Cause

Failed to stop the service of Interstage Navigator Server.

Resolution

Stop the service with Interstage Navigator Server > Navigator Server Start and Stop.

Failed to get information from trans_end file.

Cause

The contents in the trans_end file are incorrect.

Resolution

Execute again after confirming the contents recorded in the trans_end file.

Failed to convert log data.

Cause

There is a possibility that the log analyzer user has not executed the process.

Resolution

Execute again after confirming whether the execution user is Log Analyzer User.

Failed to delete old aggregation result.

Cause

There is a possibility that the other processes are accessing to the database.

Resolution

Execute again after confirming that no processes are accessing to the database.

Re-aggregation failed (XX).

Cause

There is a possibility that the other processes are accessing to the database.

Resolution

Execute again after confirming that no processes are accessing to the database.

%s Network drive cannot be specified. Folder name=%s

Variable Information

%s : folder name

Cause

When the folder in the specified network drive is the folder for saving the log data.

Resolution

Execute again after confirming that the folder that does not exist in the network drive is specified as the folder for saving the log data.

Error occurred during night-time Perform night-time batch aggregation.
Inconsistency may occur in the existing aggregation data. Please perform aggregation again.
Perform the batch aggregation processing of error period again at next startup.

Cause

Probable causes are the following:

• Failed to access to the database.

In addition, as an error occurred, the incomplete data may exist in the existed aggregation data.

Resolution

According to different causes, take the following resolutions:

• Confirm that the service "SymfoWARE RDB SWDTLA" has been started.

In addition, after the processing is finished, aggregate the aggregation data again by using the second aggregation (-r option).

The administrator data to be saved does not exist.

Cause

There was no folder to specify the administrator information. Therefore, the administrator information could not be stored.

Resolution

Execute again after specifying the folder containing the administrator information.

3.5.5.3 Messages Output by Backup/Restoration Command of Log Analyzer Settings Information

Error occurred.

Cause

Probable causes are the following:

• The database is not created. Or the database is not started.

• Do not have the authority required for executing the command.

• The problems have existed in the settings of file's write/read authority.

• The free space of disk is insufficient.

• An exception occurred in the backup data. (the file is damaged and missing)

Resolution

According to the different causes, take the following resolutions:

• Execute again after confirming whether the database is being created, or is operating.

• Execute again after confirming that this user has the authority to execute the command.

• Execute again after confirming that problems do not exist in the settings of file's write/read authority.

• Execute again after guaranteeing sufficient free space of disk.

• Execute the command again after backing up again.