3.6 Message Output with Web Console

[%1] %2 Unable to connect to Server. %3

Variable Information

%1 product name
%2 message code
%3 detail message

Cause

Failed to display the Systemwalker Desktop Patrol due to the following causes:

The Web server with Systemwalker Desktop Patrol installed is not started.
The version of Systemwalker Desktop Patrol is not V14.2.0 or later.
The URL of Systemwalker Desktop Patrol is not specified in the environment setting window.

Resolution

Take the following actions:

Confirm whether the Web server with Systemwalker Desktop Patrol installed is operating. If it is not operating, start this server and execute again.
Confirm whether the version of Systemwalker Desktop Patrol is not V14.2.0 or later. If it not the V14.2.0 or later, the linkage cannot be performed.
Set the URL of Systemwalker Desktop Patrol in the environment setting window, and then execute again.

[%1] %2 The User ID or password is specified incorrectly. %3

Variable Information

%1 product name
%2 message code
%3 detail message

Cause

Failed to display the Systemwalker Desktop Patrol due to the following causes.

When logging in to Systemwalker Desktop Patrol, the specified user does not exist.
The user and password recorded in Systemwalker Desktop Patrol are different from the user and password specified during login.

Resolution

Take the following actions:

Confirm whether this user exist in Systemwalker Desktop Patrol. When it does not exist, add, and then execute again.
Execute again after modifying the user and password used during login to Systemwalker Desktop Patrol as the same user and password used during login to Systemwalker Desktop Keeper.

[%1] %2 An exception occurred during login. %3

Variable Information

%1 product name
%2 message code
%3 detail message

Cause

The database of Systemwalker Desktop Patrol may not be operated.

Resolution

Execute again after confirming that the database of Systemwalker Desktop Patrol is operating.

[%1] %2 The authority is insufficient. %3

Variable Information

%1 product name
%2 message code
%3 detail message

Cause

The login user cannot use Systemwalker Desktop Patrol.

Resolution

Confirm the authority of user who logins to Systemwalker Desktop Patrol. If the user does not have authority, grant authority to him, and then execute again.

[%1] %2 An exception occurred on the server. %3

Variable Information

%1 product name
%2 message code
%3 detail message

Cause

An exception occurred on the server of Systemwalker Desktop Keeper or Systemwalker Desktop Patrol.

Resolution

Confirm whether the following servers are operating, and then execute again.

SWLevelControl service of Systemwalker Desktop Keeper
PostgreSQL RDB SWDTK service of Systemwalker Desktop Keeper
SymfoWARE RDB SWDTP service of Systemwalker Desktop Patrol

[%1] %2 Communication error occurred. HTTP error %3

Variable Information

%1 product name
%2 message code
%3 detail message

Cause

A HTTP error occurred.

Resolution

Execute again after confirming whether the following services are operating.

Web server imported by Systemwalker Desktop Keeper
Web server imported by Systemwalker Desktop Patrol

In addition, execute again after confirming whether the network is connected.

[%1] %2 Data does not exist.

Variable Information

%1 product name
%2 message code

Cause

When shifting from the Log Viewer to the assets management window of Systemwalker Desktop Patrol, the Systemwalker Desktop Patrol does not manage this PC.

Resolution

Install the client of Systemwalker Desktop Patrol in this PC.

[Desktop Keeper] Failed to access database. Detailed code: %1

Variable Information

%1: detail error code

Cause

The database of the Management Server may not be started.

Resolution

Execute again after confirming whether the database of the Management Server has been started.

[Desktop Keeper] Internal error occurred. Detailed code: %1

Variable Information

%1: detail error code

Cause

Some temporary errors occurred such as insufficient resource and timing error.

Resolution

Execute again.

[LWCL-ERR001] Failed to communicate with Level Control Service. The processing is cancelled.
The service of Management Server might have been stopped. Please confirm it.

Cause

Probable causes are the following:

The level control services of target servers have been stopped.
An exception occurred in the network environment.
A number of search results is too large; therefore, it takes more time to get the data.
A number of searching targets is too large or the searching conditions are too complex; therefore, searching takes too much time.

Resolution

Take the following actions according to the different causes.

Execute again after starting the level control service of the server to be connected.
Execute again after checking the network environment.
When the searching results are too much, the LWSV SEL001 message will be displayed before this message. Refine the searching conditions and search again.
When the scope of searching targets is too large, refine the searching conditions and search again.

[LWCL-ERR002] Internal error occurred in Level Control Service. The processing is cancelled.

Cause

The system environment or the database of level control service is not complete.

Resolution

Contact Fujitsu technical staff.

[LWCOM-ERR001] Exception occurred in the system. Please contact the system administrator.

Cause

Probable causes are the following:

The Web service of connected target server has been stopped.
The level control service of connected target server has been stopped.
An exception occurred in the network environment.
Failed to get the registry.
Failed to write folder/file.

Resolution

Confirm whether the status of Web service and level control service of connected target server is normal.

When the service has been started, confirm that no exception has occurred in the network environment.

[LWCOM-ERR002] Not logged in.

Cause

Try to open the processing window of Web Console when the login is not performed.

Resolution

Log on in the login window.

[LWCOM-ERR003] The User ID or password is specified incorrectly.

Cause

The user ID or password specified in the login window is incorrect, so the login processing failed.

Resolution

Enter correct user ID and password.

[LWCOM-ERR004] The current password is incorrect. Please enter the correct password.

Cause

The present password specified in the password modifying window is incorrect.

Resolution

Enter the correct present password.

[LWSC-ERR001] The start date of search is later than the end date.
Please enter the start date of search <= Search Date.

Cause

The search start date has exceeded the search end date.

Resolution

Enter according to that the search start date <= search end date.

[LWSC-ERR002] The keyword contains invalid characters. Control characters cannot be specified.

Cause

The limited characters are entered in the keyword of searching conditions.

Resolution

Confirm the value entered in the keyword.

[LWSC-ERR003] The keywords separated by the halfwidth space exceed 10 items. Please enter within 10 items.

Cause

The amount of keywords separated by halfwidth space, regarded as searching conditions, has exceeded 10 items.

Resolution

Confirm the value entered in the keyword.

[LWSC-ERR004] The user name contains invalid characters. Control characters and halfwidth spaces cannot be specified.

Cause

The limited characters and halfwidth space are entered in the user ID of searching conditions.

Resolution

Confirm the value entered in the user ID.

[LWSC-ERR005] The drive type is not selected. Please select more than 1 item.

Cause

The drive type of searching conditions is not selected.

Resolution

At least select one item in the drive type of searching conditions.

[LWSC-ERR008] The characters not allowed are used in page number. Please enter the page number with halfwidth digits.

Cause

The value excluding the halfwidth numerals is entered in the pages of CT operation log list.

Resolution

Confirm the entered value of pages.

[LWSC-ERR009] The characters not allowed are used in log number. Please enter the log number with halfwidth digits.

Cause

The value excluding the halfwidth numerals is entered in the log number of log details window.

Resolution

Confirm the value entered in the log number.

[LWSC-ERR010] The number of days in search range is incorrect.

Cause

In the back trace settings or forward trace settings, the characters excluding the numerals are entered in the "Date Value" item of searching scope.

Resolution

Confirm the entered value and only numerals can be entered in the date value.

[LWSC-ERR012] The date later than the date to search target logs is specified in back trace. Please specify a date that is earlier than the one for searching target logs.

Cause

The input back trace date has exceeded the date of searching target log.

Resolution

Confirm the date of searching target log and specify a date smaller than that date. (The same date can be specified)

[LWSC-ERR013] The date earlier than the date to search target logs is specified in Forward trace. Please specify a date that is later than the one for searching target logs.

Cause

A value (past date) smaller than the date of searching target log is entered in the forward trace date.

Resolution

Confirm the date of searching target log and specify a date larger than that date. (The same date can be specified)

[LWSC-ERR014] The IP address can only contain numbers, letters (A - F, a - f), periods (.) and colons (:).

Cause

In the CT/CT group searching window, the characters other than numerical values, Roman characters (A-F, a-f), full stop (.), and colon (:) are not entered in the IP address.

Resolution

Confirm the value entered in the IP address.

[LWSC-ERR015] The input format of IP address is incorrect.

Cause

In the CT/CT group searching window, the IP address is not entered according to the correct format.

Omit the leading zero before entering the IP address according to the format of "nnn.nnn.nnn.nnn" (n is a number) for IPv4 address.

Enter the IP address according to the format of "xxxx: xxxx: xxxx: xxxx: xxxx: xxxx: xxxx: xxxx" (x is hexadecimal) for IPv6 address. It can be omitted.

Resolution

Confirm the value entered in the IP address.

[LWSC-ERR016] Non-hexadecimal digit and hyphen are not allowed in the MAC address.

Cause

In the CT/CT group searching window, the characters excluding the hexadecimal values and strike are entered in the MAC address.

Resolution

Confirm the value entered in the MAC address.

[LWSC-ERR017] The input format of MAC address is incorrect. 17 characters must be entered.

Cause

In the CT/CT group searching window, the MAC address is not entered according to the format of XX-XX-XX-XX-XX-XX.

Resolution

Confirm the value entered in the MAC address.

[LWSC-ERR018] Non-numeric characters and decimal point are not allowed in CT version.

Cause

In the CT/CT group searching window, the characters excluding the numerals and period are entered in CT version.

Resolution

Confirm the value entered in the CT version.

[LWSC-ERR019] The input format of CT version is incorrect.

Cause

In the CT/CT group searching window, the CT version is not entered in the format of X.X.X.X.

Resolution

Confirm the value entered in the CT version.

[LWSC-ERR020] The input value of last logon date (start) does not exist in the calendar.

Cause

In the CT/CT group searching window, the date that does not exist is entered in last logon date (start).

Resolution

Confirm the value entered in last logon day (start).

[LWSC-ERR021] The input value of last logon date (end) does not exist in the calendar.

Cause

In the CT/CT group searching window, the date that does not exist is entered in last logon date (end).

Resolution

Confirm the value entered in last logon day (end).

[LWSC-ERR022] The input value of client policy update date (start) does not exist in the calendar.

Cause

In the CT/CT group searching window, the date that does not exist is entered in the date (start) of updating client policy.

Resolution

Confirm the value entered in the date (start) of updating client policy.

[LWSC-ERR023] The input value of client policy update date (end) does not exist in the calendar.

Cause

In the CT/CT group searching window, the date that does not exist is entered in the date (end) of updating client policy.

Resolution

Confirm the value entered in the date (end) of updating client policy.

[LWSC-ERR024] The last logon date (start) is later than the last logon date (end).
Please enter the last logon date (start) <=Last Logon Date (End).

Cause

In the value entered in CT/CT group searching window, the last logon date (start) > last logon date (end).

Resolution

Confirm the value entered in last logon day (start/end).

[LWSC-ERR025] The client policy update date (start) is later than the client policy update date (end).
Please enter the client policy update date (start) <= Client Policy Update Date (End).

Cause

The value entered in CT/CT group searching window is the date (start) of updating client policy > date (end) of updating client policy.

Resolution

Confirm the value entered in date of updating client policy (start/end).

[LWSC-ERR030] The display target is not selected.

Cause

After the searching configuration change log, the display button is clicked when none of logs is selected in the configuration change log list window.

Resolution

Select at least one log in the configuration change log list window.

[LWSC-ERR032] Specify the owner name using up to 93 halfwidth characters (46 fullwidth characters).

Cause

In the CT/CT group searching window, the string exceeding 93 halfwidth characters (46 fullwidth characters) has been entered in the owner name.

Resolution

Confirm the value entered in the owner name.

[LWSC-ERR033] Specify the name/CT Group name using up to 40 halfwidth characters (20 fullwidth characters).

Cause

In the CT/CT group searching window, the string exceeding 40 halfwidth characters (20 fullwidth characters) has been entered in the name/CT group name.

Resolution

Confirm the value entered in the name/CT group name.

[LWSC-ERR034] Specify the DTPID using up to 41 halfwidth characters (20 fullwidth characters).

Cause

In the CT/CT group searching window, the string exceeding 41 halfwidth characters (20 fullwidth characters) has been entered in the DTPID.

Resolution

Confirm the value entered in the DTPID.

[LWSC-ERR035] Please enter the notes within 128 halfwidth characters (64 fullwidth characters).

Cause

In the CT/CT group searching window, the string exceeding 128 halfwidth characters (64 fullwidth characters) has been entered in the notes.

Resolution

Confirm the value entered in the notes.

[LWSC-ERR036] When specifying the search date, please make sure to specify year.

Cause

In the search date, the month and day has been selected, but the year is not selected.

Resolution

Select the year in the search date.

[LWSC-ERR037] The search start time is later than the search end time.
Please enter the search start time <= Search End Time.

Cause

The search start time has exceeded the search end time.

Resolution

Enter according to the rules that search start time <= search end time.

[LWSC-ERR038] The target group and CT exceed the %1. Please specify the group again.

Variable Information

%1 : limit of target group/CT

Cause

The set number of sets is too much.

Resolution

Specify the value of target group/CT again.

[LWSC-ERR039] Specify the computer name using up to 15 halfwidth characters (7 fullwidth characters).

Cause

In the CT/CT group searching window, the string exceeding 15 halfwidth characters (7 fullwidth characters) has been entered in the computer name.

Resolution

Confirm the value entered in the computer name.

[LWSC-ERR045] When specifying the month of last logon date (start), please make sure to specify the year.

Cause

In the CT/CT group searching window, the input method of last logon day (start) is incorrect. When specifying the value of month, it is required to enter the value of year.

Resolution

Confirm the value entered in the last logon day (start).

[LWSC-ERR046] When specifying the month and day of last logon date (start), please make sure to specify the year.

Cause

In the CT/CT group searching window, the input method of last logon day (start) is incorrect. When specifying the value of month and day, it is required to enter the value of year.

Resolution

Confirm the value entered in the last logon day (start).

[LWSC-ERR047] When specifying the day of last logon date (start), please make sure to specify the month and year.

Cause

In the CT/CT group searching window, the input method of last logon day (start) is incorrect. When specifying the value of day, it is required to enter the value of month and year.

Resolution

Confirm the value entered in the last logon day (start).

[LWSC-ERR048] When specifying the month of last logon date (end), please make sure to specify the year.

Cause

In the CT/CT group searching window, the input method of last logon day (end) is incorrect. When specifying the value of month, it is required to enter the value of year.

Resolution

Confirm the value entered in the last logon day (end).

[LWSC-ERR049] When specifying the month and day of last logon date (end), please make sure to specify the year.

Cause

In the CT/CT group searching window, the input method of last logon day (end) is incorrect. When specifying the value of month and day, it is required to enter the value of year.

Resolution

Confirm the value entered in the last logon day (end).

[LWSC-ERR050] When specifying the day of last logon date (start), please make sure to specify the month and year.

Cause

In the CT/CT group searching window, the input method of last logon day (end) is incorrect. When specifying the value of day, it is required to enter the value of month and year.

Resolution

Confirm the value entered in the last logon day (end).

[LWSC-ERR051] When specifying the month of client policy update date (start), please make sure to specify the year.

Cause

In the CT/CT group searching window, the input method of date (start) of updating client policy is incorrect. When specifying the value of month, it is required to specify the value of year.

Resolution

Confirm the value entered in the date (start) of updating client policy.

[LWSC-ERR052] When specifying the month and day of client policy update date (start), please make sure to specify the year.

Cause

In the CT/CT group searching window, the input method of date (start) of updating client policy is incorrect. When specifying the value of month and day, it is required to enter the value of year.

Resolution

Confirm the value entered in the date (start) of updating client policy.

[LWSC-ERR053] When specifying the day of client policy update date (start), please make sure to specify the month and year.

Cause

In the CT/CT group searching window, the input method of date (start) of updating client policy is incorrect. When specifying the value of day, it is required to enter the value of month and year.

Resolution

Confirm the value entered in the date (start) of updating client policy.

[LWSC-ERR054] When specifying the month of client policy update date (end), please make sure to specify the year.

Cause

In the CT/CT group searching window, the input method of date (end) of updating client policy is incorrect. When specifying the value of month, it is required to enter the value of year.

Resolution

Confirm the value entered in the date (end) of updating client policy.

[LWSC-ERR055] When specifying the month and day of client policy update date (end), please make sure to specify the year.

Cause

In the CT/CT group searching window, the input method of date (end) of updating client policy is incorrect. When specifying the value of month and day, it is required to enter the value of year.

Resolution

Confirm the value entered in the date (end) of updating client policy.

[LWSC-ERR056] When specifying the day of client policy update date (end), please make sure to specify the month and year.

Cause

In the CT/CT group searching window, the input method of date (end) of updating client policy is incorrect. When specifying the value of day, it is required to enter the value of month and year.

Resolution

Confirm the value entered in the date (end) of updating client policy.

[LWSC-ERR057] When specifying the month of search range date (start), please make sure to specify the year.

Cause

The input method of searching scope date (start) in the log searching window is incorrect. When specifying the value of month, it is required to enter the value of year.

Resolution

Confirm the value entered in the searching scope date (start).

[LWSC-ERR058] When specifying the month and day of search range date (start), please make sure to specify the year.

Cause

The input method of searching scope date (start) in the log searching window is incorrect. When specifying the value of month and day, it is required to enter the value of year.

Resolution

Confirm the value entered in the searching scope date (start).

[LWSC-ERR059] When specifying the day of search range date (start), please make sure to specify the month and year.

Cause

The input method of searching scope date (start) in the log searching window is incorrect. When specifying the value of day, it is required to enter the value of month and year.

Resolution

Confirm the value entered in the searching scope date (start).

[LWSC-ERR060] When specifying the month of search range date (end), please make sure to specify the year.

Cause

The input method of searching scope date (end) in the log searching window is incorrect. When specifying the value of month, it is required to enter the value of year.

Resolution

Confirm the value entered in the searching scope date (end).

[LWSC-ERR061] When specifying the month and day of search range date (end), please make sure to specify the year.

Cause

The input method of searching scope date (end) in the log searching window is incorrect. When specifying the value of month and day, it is required to enter the value of year.

Resolution

Confirm the value entered in the searching scope date (end).

[LWSC-ERR062] When specifying the day of search range date (end), please make sure to specify the month and year.

Cause

The input method of searching scope date (end) in the log searching window is incorrect. When specifying the value of day, it is required to enter the value of month and year.

Resolution

Confirm the value entered in the searching scope date (end).

[LWSC-ERR063] When specifying the month of back trace setting and search range date, please make sure to specify the year.

Cause

The input method of back trace settings/searching scope date in the file trace window is incorrect. When specifying the value of month, it is required to enter the value of year.

Resolution

Confirm the value entered in the back trace settings/searching scope.

[LWSC-ERR064] When specifying the month and day of back trace setting and search range date, please make sure to specify the year.

Cause

The input method of back trace settings/searching scope date in the file trace window is incorrect. When specifying the value of month and day, it is required to enter the value of year.

Resolution

Confirm the value entered in the back trace settings/searching scope.

[LWSC-ERR065] When specifying the day of back trace setting and search range date, please make sure to specify the month and year.

Cause

The input method of back trace settings/searching scope date in the file trace window is incorrect. When specifying the value of day, it is required to enter the value of month and year.

Resolution

Confirm the value entered in the back trace settings/searching scope.

[LWSC-ERR066] When specifying the month of forward trace setting and search range date, please make sure to specify the year.

Cause

The input method of forward trace settings/searching scope date in the file trace window is incorrect. When specifying the value of month, it is required to enter the value of year.

Resolution

Confirm the value entered in the forward trace settings/searching scope.

[LWSC-ERR067] When specifying the month and day of forward trace setting and search range date, please make sure to specify the year.

Cause

The input method of forward trace settings/searching scope date in the file trace window is incorrect. When specifying the value of month and day, it is required to enter the value of year.

Resolution

Confirm the value entered in the forward trace settings/searching scope.

[LWSC-ERR068] When specifying the day of forward trace setting and search range date, please make sure to specify the month and year.

Cause

The input method of forward trace settings/searching scope date in the file trace window is incorrect. When specifying the value of day, it is required to enter the value of month and year.

Resolution

Confirm the value entered in the forward trace settings/searching scope.

[LWSC-ERR069] When specifying the month of search range date, please make sure to specify the year.

Cause

The input method of searching scope date (start) in the configuration change log searching window is incorrect. When specifying the value of month, it is required to enter the value of year.

Resolution

Confirm the value entered in the searching scope date (start).

[LWSC-ERR070] When specifying the month and day of search range date (start), please make sure to specify the year.

Cause

The input method of searching scope date (start) in the configuration change log searching window is incorrect. When specifying the value of month and day, it is required to enter the value of year.

Resolution

Confirm the value entered in the searching scope date (start).

[LWSC-ERR071] When specifying day of search range date (start), please make sure to specify the month and year.

Cause

The input method of searching scope date (start) in the configuration change log searching window is incorrect. When specifying the value of day, it is required to enter the value of month and year.

Resolution

Confirm the value entered in the searching scope date (start).

[LWSC-ERR072] When specifying the month of search range date (end), please make sure to specify the year.

Cause

The input method of searching scope date (end) in the configuration change log searching window is incorrect. When specifying the value of month, it is required to enter the value of year.

Resolution

Confirm the value entered in the searching scope date (end).

[LWSC-ERR073] When specifying the month and day of search range date (end), please make sure to specify the year.

Cause

The input method of searching scope date (end) in the configuration change log searching window is incorrect. When specifying the value of month and day, it is required to enter the value of year.

Resolution

Confirm the value entered in the searching scope date (end).

[LWSC-ERR074] When specifying the day of search range date (end), please make sure to specify the month and year.

Cause

The input method of searching scope date (end) in the configuration change log searching window is incorrect. When specifying the value of day, it is required to enter the value of month and year.

Resolution

Confirm the value entered in the searching scope date (end).

[LWSC-ERR075] The log type is not selected. Please select more than 1 item.

Cause

Any log type is not selected. Select at least one log type.

Resolution

Select at least one log type.

[LWSC-ERR076] When specifying the month of specified date, please make sure to specify the year.

Cause

The input method of specified date in the visible column(s) settings window is incorrect. When specifying the value of month, it is required to enter the value of year.

Resolution

Confirm the value entered in the specified date.

[LWSC-ERR077] When specifying the month and day of specified date, please make sure to specify the year.

Cause

The input method of specified date in the visible column(s) settings window is incorrect. When specifying the value of month and day, it is required to enter the value of year.

Resolution

Confirm the value entered in the specified date.

[LWSC-ERR078] When specifying the day of specified date, please make sure to specify the month and year.

Cause

The input method of specified date in the visible column(s) settings window is incorrect. When specifying the value of day, it is required to enter the value of month and year.

Resolution

Confirm the value entered in the specified date.

[LWSC-ERR079] The name of search condition is not entered. Please enter the name of search condition.

Cause

The searching condition name is not entered.

Resolution

Enter a searching condition name.

[LWSC-ERR080] The search condition name contains invalid characters. Control characters cannot be specified.

Cause

The characters not allowed are used in the searching condition name.

Resolution

Enter the characters excluding the limited characters in the searching condition name.

[LWSC-ERR081] The CT group that can perform the log search does not exist. Please shut down the window by closing the button.

Cause

The CT group that can be used by the department administrator does not exist.

Resolution

Close the window.

[LWSC-ERR082] Specify the user name/user group name using up to 40 halfwidth characters (20 fullwidth characters).

Cause

In the user/user group searching window, the string exceeding 40 halfwidth characters (20 fullwidth characters) has been entered in the user name/user group name (searching conditions).

Resolution

Confirm the value entered in the user name/user group name.

[LWSC-ERR083] Emergency procedure requests cannot be issued to V15.1.3 or earlier client (CT) terminals.

Cause

An attempt was made to issue an emergency procedure request to a V15.1.3 or earlier client (CT) terminal.

Resolution

Issue emergency procedure requests only to V15.2.0 or later client (CT) terminals.

[LWSC-ERR084] Specify the user's name using up to 128 halfwidth characters (64 fullwidth characters).

Cause

In the user/user group searching window, the string exceeding 128 halfwidth characters (64 fullwidth characters) has been entered in the user name (searching conditions).

Resolution

Confirm the value entered in the user name.

[LWSC-ERR085] The emergency procedure request failed.

Cause

Possible causes are as follows.

The CT service has been stopped for the emergency procedure request destination client (CT).
The emergency procedure request destination client (CT) does not exist.
An error occurred when communicating with the emergency procedure request destination client (CT).

Resolution

Take the following action depending on the cause:

Start the CT service of the emergency procedure request destination client (CT), and issue the emergency procedure request again.
The client (CT) may have been uninstalled. Contact the client (CT) user, and check the terminal status.
Contact the client (CT) user, start the emergency procedure tool on the client (CT), and then perform the emergency procedure.

[LWSC-ERR086] Specify the employee no. using up to 40 halfwidth characters (20 fullwidth characters).

Cause

In the user/user group searching window, the string exceeding 40 halfwidth characters (20 fullwidth characters) has been entered in the employee number (searching conditions).

Resolution

Confirm the value entered in the employee number.

[LWSC-ERR087] Emergency procedure requests cannot be issued for terminals with the monitoring function of Citrix XenApp.

Cause

There was an attempt to issue an emergency procedure request for a terminal with the monitoring function of Citrix XenApp.

Resolution

Issue emergency procedure requests only for terminals with Systemwalker Desktop Keeper Client.

[LWSC-ERR088] Specify the POST using up to 128 halfwidth characters (64 fullwidth characters).

Cause

In the user/user group searching window, the string exceeding 128 halfwidth characters (64 fullwidth characters) has been entered in the official position (searching conditions).

Resolution

Confirm the value entered in the official position.

[LWSC-ERR089] The emergency procedure request has already been issued.

Cause

An emergency procedure request cannot be issued for terminals for which a procedure is already in progress.

Resolution

A new emergency procedure request can be issued by clearing the Display Status window in the Management Console.

[LWSC-ERR090] Specify the organization using up to 128 halfwidth characters (64 fullwidth characters).

Cause

In the user/user group searching window, the string exceeding 128 halfwidth characters (64 fullwidth characters) has been entered in the department name (searching conditions).

Resolution

Confirm the value entered in the department name.

[LWSC-ERR092] Specify the organization code using up to 40 halfwidth characters (20 fullwidth characters).

Cause

In the user/user group searching window, the string exceeding 40 halfwidth characters (20 fullwidth characters) has been entered in the department code (searching conditions).

Resolution

Confirm the value entered in the department code.

[LWSC-ERR094] Specify the notes using up to 128 halfwidth characters (64 fullwidth characters).

Cause

In the user/user group searching window, the string exceeding 128 halfwidth characters (64 fullwidth characters) has been entered in the notes (searching conditions).

Resolution

Confirm the value entered in the notes.

[LWSC-ERR096] The target number of group users exceeds %1. Review the group specification.

Variable Information

% 1: limit of target group/user

Cause

The set number of users is too large.

Resolution

Specify the value of the target group/user

[LWSC-ERR097] There is no authority to display the CTs directly under the group selected.

Cause

The user does not have authority to display the CTs directly under the selected group.

Resolution

Log in as a system administrator or department administrator with the authority to display CTs directly under the selected group.

[LWSC-ERR098] Emergency procedure requests cannot be issued for a client (CT) terminal that coexists with the Management Server/Master Management Server.

Cause

An attempt was made to issue an emergency procedure request for a client (CT) terminal that coexists with the Management Server/Master Management Server.

Resolution

Issue emergency procedure requests only for client (CT) terminals that do not coexist with the Management Server/Master Management Server.

[LWSC-INF001] The search number is different.
Search number of log viewer: %1 / Aggregation number of log analyzer: %2

Variable Information

%1 : items searched from the Log Viewer

%2 : items aggregated in the Log Analyzer

Cause

After they are aggregated in the Log Analyzer, probably the logs have been deleted.

Resolution

[LWSC-INF002] The emergency procedure request was successful.

Cause

The emergency procedure request was successful.

Resolution

[LWSC-SEL001] Delete the search conditions. Execute?

Cause

Prepare to delete the searching conditions.

Resolution

If it is required to delete, click the [OK] button. If it is required to stop the operation, click the [Cancel] button.

[LWSC-SEL002] An emergency procedure request was issued. Client (CT) terminal operations are restricted as a result.

Cause

An attempt was made to issue an emergency procedure request for a client (CT).

Resolution

Click OK to issue the emergency procedure request, or Cancel to cancel the process.

[LWSET-ERR001] Failed to send data. Please confirm whether the memory of Web Server is insufficient.

Cause

The memory on the Management Server is sufficient.

Resolution

Execute again after finishing the applications that are not used.

[LWSET-ERR002] Failed to read files. [File=%1][Detailed code=%2]

Variable Information

%1: file name
%2: detail error code

Cause

Probable causes are as follows:

The file does not exist.
Do not have the authority to access to the file.
The file is being opened by other applications.

Resolution

Execute again after confirming the following contents.

Whether the file exists.
Whether it has the authority to access to the file.
Whether the file is being opened by other applications.

[LWSET-ERR003] Failed to get configuration value. Please confirm whether the database is running. [Detailed code=%1]

Variable Information

%1: detail error code

Cause

Failed to access to the database.

Resolution

Confirm whether the database of (Master) Management Server is operating.

[LWSET-ERR004] Failed to update configuration value. Please confirm whether the database is running. [Detailed code=%1]

Variable Information

%1: detail error code

Cause

Failed to access to the database.

Resolution

Confirm whether the database of (Master) Management Server is operating.

[LWSET-ERR005] Failed to write file in. [File=%1][Detailed code=%2]

Variable Information

%1: file name
%2: detail error code

Cause

Probable causes are as follows:

The file does not exist.
Do not have the authority to access to the file.
The file is being opened by other applications.

Resolution

Execute again after confirming the following contents.

Whether the file exists.
Whether it has the authority to access to the file.
Whether the file is being opened by other applications.

[LWSV-ERR001] Not logon yet.

Cause

Try to display the windows excluding the login window when the login is not performed.

Resolution

Log on in the login window.

[LWSV-ERR002] Logged off by force due to no operation within a certain amount of time.

Cause

None of operation is executed in a specified time.

Resolution

Log on in the login window.

[LWSV-ERR003] System error occurred on Management Server. Please contact the system administrator.

Cause

The shortcomings have existed in the system environment of Log Viewer.

Resolution

Contact Fujitsu technical staff.

[LWSV-ERR004] Number of logs has exceeded 100,000, so search cannot be performed. Please reset conditions and search again.

Cause

As the searching results items of logs have exceeded 100,000, the searching processing is interrupted.

Resolution

Search again after entering the conditions again.

[LWSV-ERR006] Log searching or processing cancelling. Please execute it later.

Cause

After the searching of CT operation log or configuration change log is cancelled, the searching processing shall be executed immediately.

Resolution

Execute again later.

[LWSV-ERR007] Image data has not been transmitted to the server, failed to display.

Cause

As the image data has not been transmitted to the server, it is unable to display.

Resolution

Execute again after the image data is transmitted to the server. The sending time of screen capture data can be set in [Terminal Operation Settings] of Management Console.

[LWSV-ERR008] Search result has exceeded %d items, interrupt search in the current level.

Variable Information

%d : the maximum value of searching results

Cause

In the searching execution, its results have exceeded 1,000 cases, so the searching processing is interrupted.

Resolution

As the searching scope is too large, search again after modifying the searching conditions. Or execute the searching after resetting the trace target to modify the searching target.

[LWSV-ERR009] Search result has exceeded 10,000 items, the search is interrupted. Search result is partially displayed. Please reset search conditions and search again.

Cause

The searching results have exceeded 10,000 cases, so the searching processing is interrupted.

Resolution

Search after entering the conditions again.

[LWSV-ERR010] Original file has not been transmitted to the server, failed to display.

Cause

Probable causes are as follows:

As the original file has not been transmitted to the server, it is unable to download.
The disk space of server to save the original file may be insufficient.

Resolution

Take the following actions according to the different causes.

Execute again after the original data is transmitted to the server. The sending time of original data can be set in [Terminal Operation Settings] of Management Console.
Increase the disk space of server to save the original file.

[LWSV-ERR011] Processing will be canceled because the number of log data items (%1) was exceeded. Review the conditions.

Variable Information

%1: Searchable items

Cause

During log search, items of searching results have exceeded searchable items.

Resolution

Search again after re-examining the searching conditions.

[LWSV-SEL001] Amount of target data has exceeded %1, so the processing will take some time. Continue? [Number of acquired logs: %2]

Variable Information

%1 : specified upper limit case
%2 : cases of got logs

Cause

The items of logs to be displayed in the Log Viewer have exceeded the specified upper limit case (10,000 cases).

Resolution

If it is required to continue, click the [OK] button. If it is required to stop the processing, click the [Cancel] button.

[LWSV-SEL002] The size of the file has exceeded 10MB, so the processing will take some time. Continue? [Acquired size: %1]

Variable Information

%1 : size of original file backup to be got

Cause

When getting the original file, this will be displayed when the size of this file has exceeded 10MB. %1MB in the message is a numeral displayed in megabytes to show the size of this file, and the numeral is displayed to second after the decimal point.

Resolution

Confirm the size of displayed file. When the size is too large, it will take much more to get the file. When exporting the file, click the [OK] button. When stopping the processing, click the [Cancel] button.

[LWSV-SEL003] A search may not be possible due to the large amount of data targeted for search. Continue processing?

Cause

The estimated searching items exceeded the specified upper limit item; therefore, it takes too much time for searching.

Furthermore, this message is displayed when the items calculated by using the following formula exceed the count of 200000 items.

Search target date (date) x estimated items per CT (1000) x search target CT items (sets)

Resolution

When you continue the search, click OK button. When you re-examine searching conditions, and carry out search again, click Cancel button.

[LWSY-ERR001] Failed to communicate with Level Control Service. The processing is cancelled.
The service of Management Server might have been stopped. Please confirm it.

Cause

Probable causes are as follows:

The level control service of the server to be connected has stopped.
An exception occurred in the network environment.
A number of search results is too large; therefore, it takes more time to get the data.
A number of searching targets is too large or the searching conditions are too complex; therefore, searching takes too much time.

Resolution

Execute again after checking the status of level control service of connected target servers and network environment.
When the items of searching results are too much, the LWSV-SEL001 message will be displayed before this message. Refine the searching conditions and search again.
When the scope of searching targets is too large, refine the searching conditions and search again.

[ERR-DTLAC001] Log Analyzer Server is not constructed. Or, the environment or settings of Log Analyzer Server contains defects.

Cause

Probable causes are as follows:

The information of the Log Analyzer Server logged on the Management Server is incorrect.
Problems have existed in the environment settings of the target Log Analyzer Server. (it is not installed correctly, or the administrator information has not logged on, etc.)
Problems have existed in the status (the server or database stops operating, or it is unable to communicate, etc.) of target Log Analyzer Server.

Resolution

Take the following actions according to the different causes.

Check the information of the Log Analyzer Server logged on the Management Server.
Check the environment settings of target Log Analyzer Server.
Check the status of target Log Analyzer Server.

[ERR-DTLAC002] The environment or configuration of Log Analyzer Server into which the data of Management Server or Master Management Server is moved.

Cause

Probable causes are as follows:

The environment of the Log Analyzer Server that has imported data to Management Server (it is Master Management Server when there are several sets of the Management Server in the system) is not set correctly or the administrator information is not logged on.
The database of the Log Analyzer Server has stopped operating, or it is unable to communicate, etc.
The letters that differ may be entered in the user ID. (The capital and small letters shall be distinguished on the Log Analyzer Server.)
The user ID has duplicated (There are multiple user IDs having the same name belong to the Management Server/Master Management Server).

Resolution

Take the following actions according to the different causes:

Check the information of the Log Analyzer Server logged on the Management Server (it is Master Management Server when there are several sets of the Management Server in the system).
Check the environment settings or status of the target Log Analyzer Server.
Modify the capital and small letters in the user ID as the same as letters used when creating the user ID, and then logon to the Web Console again.
Delete the duplicated user IDs by using the User Management Command.

[ERR-DTLAC099] Error occurred. (Detail Code: %d).

Cause

The operating environment of Web Console or Log Analyzer Server may be destroyed.

Resolution

Confirm whether the Web Console and Log Analyzer Server are installed/set correctly, the database is operating normally, or the communication environment is OK, etc., and if everything goes all right, contact Fujitsu technical staff.

[ERR-DTLAC101] Not logged in.

Cause

When it does not logon to the Web Console, access to the aggregate by objective window

Resolution

Logon to the Web Console.

[ERR-DTLAC102] Another user is performing aggregation processing. Please try again later.

Cause

Probable causes are as follows:

Tried to aggregate in the process when other users are executing the aggregation processing.
There is processing that is not finished.

Resolution

Take the following actions according to the different causes.

Aggregate again after confirming no other users are using the aggregate by objective function.
Aggregate again later.

[ERR-DTLAC103] Another user is performing aggregation, data does not exist. Please try again.

Cause

As other users have executed the aggregation operation, the aggregation results have been given up.

Resolution

Aggregate again after confirming that no other users are using the aggregate by objective function.

[ERR-DTLAC104] Failed to connect to Log Analyzer Server.

Cause

Probable causes are the following:

When the domain account is used for Log Analyzer User, the account with the same name may exist in this location.
Failed to access to Active Directory Server due to some causes the server has stopped operating, or the network is disconnected, etc.
It may be caused because the port used in the Log Analyzer (aggregate by objective) has been blocked by a firewall.

Resolution

Take the following actions according to the different causes:

Reinstall by using the domain name that will be different from accounts existed in this location.
Confirm the Active Directory Server that can be accessed.
Confirm the settings of firewall, and check whether the port used for Log Analyzer (aggregate by objective ) has been opened.

[ERR-DTLAC105] Detailed display failed. Please perform aggregation again.

Cause

A period of time has passed after the aggregation processing is finished, and the connection between Navigator client and server may be overtime.

Resolution

Execute again from the aggregation processing.

[ERR-DTLAC199] Error occurred in processing.

Cause

Probable causes are as follows:

The logs of the Management Server may not be imported.
The space of disk in the path of directory for saving temporary files is insufficient, or the capacity of log data as aggregation target has exceeded the processing scope (2GB).
When the code is 53, IIS may not be set correctly.
Do not have the authority to access the temporary folder.

Resolution

Take the following actions according to the different causes.

Import the log data of the Management Server.
Execute again after the free capacity of disk in the path of Home directory in the environment variable parameter, TMP, is increased to at least 2GB. Or reduce the items of searching results log by shortening the aggregation unit (group > terminal, etc.), or aggregation time frame (7 days > 1 day, etc.) or specifying the keyword to shorten the searching items, etc.
Set IIS correctly by referring to the related contents of "Create Management Server/Master Management Server" of Installation Guide.
When the used Web Server is IIS7.0 or later, [Read of User Property File] in detail settings of application pool ([DefaultAppPool]) is set to False.

[ERR-DTLAC201] The user ID has not been registered to Log Analyzer Server (Detailed Code: n).

Cause

The user ID now logging on the system has not been found on the connected Log Analyzer Server.

Resolution

Import the management information that includes this user ID again, or do not use this user ID.

[ERR-DTLAC202] Failed to connect the database (Detailed Code: n).

Cause

Failed to connect to the database of the Log Analyzer Server.

Resolution

Confirm whether the database of the Log Analyzer Server is operating or the network is OK.

[ERR-DTLAC299] Errors occurred (Detailed Code: n).

Cause

The operating environment of Web Console or Log Analyzer Server may be destroyed.

Resolution

Whether the Web Console or Log Analyzer Server is installed/set correctly, the database is operating, the communication environment is OK. When everything goes all right, contact Fujitsu technical staff.