Cause
The specified parameter is incorrect.
Resolution
Please execute again after modifying it as correct parameter according to the above description.
Cause
The format of command parameter is incorrect.
Resolution
Please execute again after modifying it as correct format according to the above description.
Cause
The length of IP address is incorrect.
Resolution
Please enter an IP address of correct length.
Cause
The specified method of IP address is incorrect.
Resolution
Please specify the IP address correctly.
Cause
The user ID of specified Management Server does not exist.
Resolution
Please specify the existed user ID of the Management Server.
Cause
Failed to delete the data due to some causes such as the database is not operating.
Resolution
Please execute again after confirming whether the database is operating normally.
Cause
Failed to delete the data due to some causes such as the database is not operating.
Resolution
Please execute again after confirming whether the database is operating normally.
Cause
The specified user name is not the name of the Log Analyzer User.
Resolution
Please specify the correct name of the Log Analyzer User.
Cause
The Log Analyzer User is not used to login to Windows.
Resolution
Please use Log Analyzer User to login to Windows.
Cause
The information settings failed.
Resolution
Please confirm whether the environment is destroyed, the authority of the Log Analyzer User is sufficient or the database is operating normally, and then 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.
Cause
In the process of accessing to database, failed to save the log data due to some causes such as the operation for saving data has been performed.
Resolution
Please execute again after confirming whether the database is being accessed.
Cause
As the database is not started, it is unable to save the log data.
As the database is not started, it is unable to delete the log data.
As the database is not started, it is unable to aggregate the data again.
Resolution
Please select [Program]-[Symfoware Enterprise Edition]-[RDB Start/Stop] from the [Start] menu and confirm whether the database is being accessed.
Cause
The log data of the Management Server does not exist in the specified folder, so the log data cannot be saved.
Resolution
Please specify the folder that includes log data.
Cause
The specified folder does not exist.
Resolution
Please execute again after confirming that the specified folder does exist.
Cause
The path of specified folder has exceeded 141 bytes.
Resolution
Please check the saving target path of log data and execute again.
Cause
The size of data to be saved has exceeded the size of database space.
Resolution
Please recreate a database with larger capacity, or reduce the amount of log data to be imported.
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).
Interstage Navigator Server is not started.
Failed to access to the database.
Resolution
According to different causes, take the following resolutions.
Please execute again after saving the CSV data regarded as aggregation target in the date folder.
Please execute again after confirming the environment of Interstage Navigator Server is normal.
Select [Program]-[Symfoware Enterprise Edition]-[RDB Start/Stop] from the [Start] menu and confirm whether the database is operating normally.
Cause
Probable causes are the following:
Interstage Navigator Server is not started.
Failed to access to the database.
Resolution
According to different causes, take the following resolutions.
Please execute again after confirming the environment of Interstage Navigator Server is normal.
Please execute again after confirming the environment of database.
Cause
After an error occurred, failed to restore the data of aggregation results.
Resolution
Please restore the backup data manually.
The backup data is seven CSV files under [Installation Folder of the Log Analyzer Server] \bin\batchnavi.
The method of manual restoration is shown as follows. Please execute for each CSV file respectively.
rdbsloader -mi -i SWDTLA.[DSI Name] -t [Full Path of CSV File]
[DSI Name] is name part of CSV file (excluding the extension).
Example:
rdbsloader -mi -i SWDTLA.LEAKAGE_BASICDSI -t "C:\Program Files\Fujitsu\Systemwalker Desktop Keeper\LogAnalyzer\Server\bin\batchnavi\LEAKAGE_BASICDSI.CSV"
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.
Please execute again after specifying the data transmitted by using data transmission command.
Please execute again after confirming that the contents recorded in the trans_end file are correct.
Cause
The Management Server data of incompatible version will be imported to the Log Analyzer Server.
Resolution
Please execute again after specifying the Management Server data of compatible version.
Cause
The data restoration processing executed when the operation failed failed due to some causes. Therefore, the user management information may be damaged.
Resolution
Please search the file whose extension is “bkup” from the folders specified by -f option, and then restore the data by using “rdbsloader command” of Symfoware.
Cause
Failed to access to the database because other processes are accessing to the database.
Resolution
Please execute again after confirming whether other processes are accessing to the database.
Cause
The date folder name of log data does not confirm to the rules.
Resolution
Please confirm whether the date folder of log data confirms to the format of “01012006_01312006”.
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
Transfer the setting file (TRANS_SETTING.ini) used for data transmission command according to the transferring method of the Management Server.
Open the TRANS_SETTING.ini file transferred based on Step 1 by editor, and copy the 36 bytes string after the "KID=" of [DTKSERVERINFO] keyword.
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
※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 please note that.
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 not abling to 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), please modify it as ordinary IP address.
Cause
Failed to start the service of Interstage Navigator Server.
Resolution
Select [Program]-[Interstage Navigator Server]-[Navigator Server Start/Stop] from the [Start] menu, and then start the service.
Or select [Management Tool]-[Service]-[Interstage Navigator Server]-[Navigator Server Start/Stop] from the [Start] menu to start service.
Cause
Failed to read the required information from the batcherror.ini file.
Resolution
Please confirm whether the batcherror.ini file has been damaged.
Cause
The Log Analyzer User is not used for execution.
Resolution
Please specify the execution user as Log Analyzer User, and then execute again.
Cause
The specified parameter is incorrect.
Resolution
Please execute again after confirming whether the parameter is correct.
Cause
Failed to access to the settings information due to some causes such as the authority is insufficient.
Resolution
Please execute again after confirming whether the execution user is Log Analyzer User.
Cause
Another aggregation processing preparation failed.
Resolution
It is caused because the aggregation results may not match.
Please aggregate again by using -r option.
Cause
Failed to stop the service of Interstage Navigator Server.
Resolution
Select [Program]-[Interstage Navigator Server]-[Navigator Server Start and Stop] from the [Start] menu, and then stop the service.
Or select [Management Tool]-[Service]-[Interstage Navigator Server]-[Navigator Server Start and Stop] from the [Start] menu, and then stop the service.
Cause
The contents in the trans_end file are incorrect.
Resolution
Please execute again after confirming the contents recorded in the trans_end file.
Cause
Failed to transform the log data due to some causes such as the read and write authority of log data are insufficient.
Resolution
Please execute again after confirming whether the execution user is Log Analyzer User.
Cause
Failed to access to the database as other processes are accessing to the database.
Resolution
Please execute again after confirming whether the database is being accessed.
Cause
Failed to access to the database as other processes are accessing to the database.
Resolution
Please execute again after confirming whether the database is being accessed.
Variable Information
%s : folder name
Cause
When the folder in the specified network drive is the folder for saving the log data.
Resolution
Please 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.
Cause
Probable causes are the following:
Interstage Navigator Server is not started.
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:
Please execute again after confirming the environment of Interstage Navigator Server.
Select [Program]-[Symfoware Enterprise Edition]-[RDB Start/Stop] from the [Start] menu, and then confirm whether the database is operating.
In addition, after the processing is finished, please aggregate the aggregation data again by using the second aggregation (-r option).
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
Please according to the different causes, take the following resolutions:
Please execute again after confirming whether the database is being created, or is operating.
Please execute again after confirming that this user has the authority to execute the command.
Please execute again after confirming that problems do not exist in the settings of file’s write/read authority.
Please execute again after guaranteeing sufficient free space of disk.
Please execute the command again after backing up again.
