JP1 Version 13 JP1/IT Desktop Management 2 Messages

3021-3-L78-30(E)

Notices

Relevant program products

For details about the supported operating systems and the service packs or patches that are required by JP1/IT Desktop Management 2, see the Release Notes.

P-2A42-78DL JP1/IT Desktop Management 2 - Manager 13-11

The above product includes the following:

• P-CC2A42-7ADL JP1/IT Desktop Management 2 - Manager (for Windows Server 2022, Windows Server 2019, Windows Server 2016)

• P-CC2A42-7BDL JP1/IT Desktop Management 2 - Agent (for Windows Server 2022, Windows 11, Windows Server 2019, Windows Server 2016, Windows 10, Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008 R2)

• P-CC2A42-7CDL JP1/IT Desktop Management 2 - Network Monitor (for Windows Server 2022, Windows 11, Windows Server 2019, Windows Server 2016, Windows 10, Windows 8.1 Enterprise, Windows 8.1 Pro, Windows 8 Enterprise, Windows 8 Pro, Windows Server 2012, Windows 7 Enterprise, Windows 7 Professional, Windows 7 Ultimate)

• P-CC2A42-7DDL JP1/IT Desktop Management 2 - Asset Console (for Windows Server 2022, Windows Server 2019, Windows Server 2016)

• P-CC2A42-7PDL JP1/IT Desktop Management 2 - Internet Gateway (for Windows Server 2022, Windows Server 2019, Windows Server 2016)

P-2A42-7KDL JP1/IT Desktop Management 2 - Operations Director 13-11

The above product includes the following:

• P-CC2A42-7ADL JP1/IT Desktop Management 2 - Manager (for Windows Server 2022, Windows Server 2019, Windows Server 2016)

• P-CC2A42-7BDL JP1/IT Desktop Management 2 - Agent (for Windows Server 2022, Windows 11, Windows Server 2019, Windows Server 2016, Windows 10, Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008 R2)

• P-CC2A42-7CDL JP1/IT Desktop Management 2 - Network Monitor (for Windows Server 2022, Windows 11, Windows Server 2019, Windows Server 2016, Windows 10, Windows 8.1 Enterprise, Windows 8.1 Pro, Windows 8 Enterprise, Windows 8 Pro, Windows Server 2012, Windows 7 Enterprise, Windows 7 Professional, Windows 7 Ultimate)

• P-CC2A42-7PDL JP1/IT Desktop Management 2 - Internet Gateway (for Windows Server 2022, Windows Server 2019, Windows Server 2016)

Trademarks

BSAFE is a trademark or registered trademark of Dell Inc. in the United States and other countries.

Oracle, Java, and MySQL are registered trademarks of Oracle and/or its affiliates.

Other company and product names mentioned in this document may be the trademarks of their respective owners.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

This product includes software developed by Ben Laurie for use in the Apache-SSL HTTP server project.

Portions of this software were developed at the National Center for Supercomputing Applications (NCSA) at the University of Illinois at Urbana-Champaign.

This product includes software developed by the University of California, Berkeley and its contributors.

This software contains code derived from the RSA Data Security Inc. MD5 Message-Digest Algorithm, including various modifications by Spyglass Inc., Carnegie Mellon University, and Bell Communications Research, Inc (Bellcore).

Regular expression support is provided by the PCRE library package, which is open source software, written by Philip Hazel, and copyright by the University of Cambridge, England. The original software is available from ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre/

This product includes software developed by Ralf S. Engelschall <rse@engelschall.com> for use in the mod_ssl project (http://www.modssl.org/).

This product includes software developed by IAIK of Graz University of Technology.

This product includes software developed by Daisuke Okajima and Kohsuke Kawaguchi (http://relaxngcc.sf.net/).

This product includes software developed by the Java Apache Project for use in the Apache JServ servlet engine project (http://java.apache.org/).

This product includes software developed by Andy Clark.

This product bundles Dell BSAFETM software developed by Dell Inc. in the United States.

Java is a registered trademark of Oracle and/or its affiliates.

Java is a registered trademark of Oracle and/or its affiliates.

1. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)

2. This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)

3. This product includes software written by Tim Hudson (tjh@cryptsoft.com)

4. This product includes the OpenSSL Toolkit software used under OpenSSL License and Original SSLeay License. OpenSSL License and Original SSLeay License are as follow:

LICENSE ISSUES

==============

The OpenSSL toolkit stays under a dual license, i.e. both the conditions of

the OpenSSL License and the original SSLeay license apply to the toolkit.

See below for the actual license texts. Actually both licenses are BSD-style

Open Source licenses. In case of any license issues related to OpenSSL

please contact openssl-core@openssl.org.

OpenSSL License

---------------

/* ====================================================================

* Copyright (c) 1998-2016 The OpenSSL Project. All rights reserved.

*

* Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

*

* 1. Redistributions of source code must retain the above copyright

* notice, this list of conditions and the following disclaimer.

*

* 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in

* the documentation and/or other materials provided with the

* distribution.

*

* 3. All advertising materials mentioning features or use of this

* software must display the following acknowledgment:

* "This product includes software developed by the OpenSSL Project

* for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

*

* 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to

* endorse or promote products derived from this software without

* prior written permission. For written permission, please contact

* openssl-core@openssl.org.

*

* 5. Products derived from this software may not be called "OpenSSL"

* nor may "OpenSSL" appear in their names without prior written

* permission of the OpenSSL Project.

*

* 6. Redistributions of any form whatsoever must retain the following

* acknowledgment:

* "This product includes software developed by the OpenSSL Project

* for use in the OpenSSL Toolkit (http://www.openssl.org/)"

*

* THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY

* EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR

* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR

* ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

* SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT

* NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;

* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,

* STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)

* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED

* OF THE POSSIBILITY OF SUCH DAMAGE.

* ====================================================================

*

* This product includes cryptographic software written by Eric Young

* (eay@cryptsoft.com). This product includes software written by Tim

* Hudson (tjh@cryptsoft.com).

*

*/

Original SSLeay License

-----------------------

/* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)

* All rights reserved.

*

* This package is an SSL implementation written

* by Eric Young (eay@cryptsoft.com).

* The implementation was written so as to conform with Netscapes SSL.

*

* This library is free for commercial and non-commercial use as long as

* the following conditions are aheared to. The following conditions

* apply to all code found in this distribution, be it the RC4, RSA,

* lhash, DES, etc., code; not just the SSL code. The SSL documentation

* included with this distribution is covered by the same copyright terms

* except that the holder is Tim Hudson (tjh@cryptsoft.com).

*

* Copyright remains Eric Young's, and as such any Copyright notices in

* the code are not to be removed.

* If this package is used in a product, Eric Young should be given attribution

* as the author of the parts of the library used.

* This can be in the form of a textual message at program startup or

* in documentation (online or textual) provided with the package.

*

* Redistribution and use in source and binary forms, with or without

* modification, are permitted provided that the following conditions

* are met:

* 1. Redistributions of source code must retain the copyright

* notice, this list of conditions and the following disclaimer.

* 2. Redistributions in binary form must reproduce the above copyright

* notice, this list of conditions and the following disclaimer in the

* documentation and/or other materials provided with the distribution.

* 3. All advertising materials mentioning features or use of this software

* must display the following acknowledgement:

* "This product includes cryptographic software written by

* Eric Young (eay@cryptsoft.com)"

* The word 'cryptographic' can be left out if the rouines from the library

* being used are not cryptographic related :-).

* 4. If you include any Windows specific code (or a derivative thereof) from

* the apps directory (application code) you must include an acknowledgement:

* "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"

*

* THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND

* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE

* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE

* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL

* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS

* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)

* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT

* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY

* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF

* SUCH DAMAGE.

*

* The licence and distribution terms for any publically available version or

* derivative of this code cannot be changed. i.e. this code cannot simply be

* copied and put under another distribution licence

* [including the GNU Public Licence.]

*/

Restrictions

Information in this document is subject to change without notice and does not represent a commitment on the part of Hitachi. The software described in this manual is furnished according to a license agreement with Hitachi. The license agreement contains all of the terms and conditions governing your use of the software and documentation, including all warranty rights, limitations of liability, and disclaimers of warranty.

Material contained in this document may describe Hitachi products not available or features not available in your country.

No part of this material may be reproduced in any form or by any means without permission in writing from the publisher.

Issued

Mar. 2025: 3021-3-L78-30(E)

Copyright

Copyright (C) 2023, 2025, Hitachi, Ltd.

Copyright (C) 2023, 2025, Hitachi Solutions, Ltd.

Colophon

Publisher

Hitachi, Ltd.

6-6, Marunouchi 1-chome, Chiyoda-ku, Tokyo, 100‒8280 Japan

Summary of amendments

The following table lists changes in this manual (3021-3-L78-30(E)) and product changes related to this manual.

Changes

Location

The messages that have the following IDs were added:

KDEX5525-I, KDEX5526-E, KDEX5527-E, KDEX5528-E, KDEX5529-E, KDEX5530-E, KDEX5531-I, KDEX5533-E, KDEX5534-E, KDEX5535-E, KDEX5536-E, KDEX5537-E

1.2

Legend: --: Not applicable

In addition to the above changes, minor editorial corrections were made.

Preface

This manual describes the messages related to JP1/IT Desktop Management 2 - Manager and JP1/IT Desktop Management 2 - Operations Director. Hereafter, JP1/IT Desktop Management 2 - Manager and JP1/IT Desktop Management 2 - Operations Director are abbreviated to JP1/IT Desktop Management 2.

Some functions of JP1/IT Desktop Management 2 - Operations Director are restricted compared to JP1/IT Desktop Management 2 - Manager. For details about functional restrictions, see the description about functional restrictions of JP1/IT Desktop Management 2 - Operations Director in the JP1/IT Desktop Management 2 Overview and System Design Guide.

Intended readers

This manual is intended for use by the following persons:

Administrators who use JP1/IT Desktop Management 2 to manage the security and assets of their organizations

Users who want to learn how to use and perform operations in JP1/IT Desktop Management 2

Organization of this manual

This manual is organized into the following chapters and an appendix:

1. Messages

This chapter describes the messages output by JP1/IT Desktop Management 2.

2. Event Log Messages

This chapter describes the event log messages related to JP1/IT Desktop Management 2.

3. Basic Log Messages

This chapter describes the basic log messages related to JP1/IT Desktop Management 2.

A. Reference Material for This Manual

This appendix provides reference material that might be useful for users of JP1/IT Desktop Management 2.

For reference materials for this manual, see the JP1/IT Desktop Management 2 Overview and System Design Guide.

1 Messages

This chapter lists and describes messages that allow users to check information such as startup and termination of JP1/IT Desktop Management 2, error occurrence, and actions to be taken. These messages are output to JP1/IT Desktop Management 2 - Manager-installation-folder¥log¥JDNMAINn .LOG, JP1/IT Desktop Management 2 - Manager-installation-folder¥log\JDNAUDTn.LOG, JP1/IT Desktop Management 2 - Manager-installation-folder¥log¥JDNSTRCn .LOG or JP1/IT Desktop Management 2 - Manager-installation-folder\mgr\log¥JDNRSTMn.LOG.

1.1 Format of message explanations

JP1/IT Desktop Management 2 messages consist of a message ID, message type, and message text.

The following shows the format of message IDs and message types, and the meanings of the constituent parts of a message.

Format: KDEXpnnn-m

KDEX

Indicate a message output from JP1/IT Desktop Management 2.

p

Indicates the component that output the message. The following table shows the correspondence between the numbers and the components:

Number

Component

1

Installer or setup

2

GUI

3

API

4

Utility

5

Manager service

6

Agent control

7

Agent

8

Site server or internet gateway

9

Relay service for the management server

nnn

Indicates the message number.

m

Indicates the message type. The following are the message types:

Message code

Type

Description

E

Error

Processing could not continue because an error occurred.

W

Warning

A warning was output, and processing continued. See the warning message to determine whether there is a problem.

I

Information

Processing ended successfully.

Q

Query

The system is waiting for a user response.

K

Processing

Processing is currently being performed.

1.2 List of messages

KDEX1001-E

The user does not have Administrative Privileges. Installation is cancelled.

[Cause] The user does not have Administrative Privileges.

[Action] Cancel installation.

[Workaround] Retry installation as a user with Administrative Privileges.

KDEX1002-E

Installation failed. The OS is not supported.

[Cause] The OS is not supported.

[Action] Cancel installation.

[Workaround] Retry the installation on a supported OS.

KDEX1003-E

A newer version of the software is already installed.

Installation is canceled.

[Cause] A newer version of the software is already installed.

[Action] Cancel installation.

[Workaround] Compare the two software versions (between installed and intended to be installed). You can retry installation after uninstalling the installed software.

KDEX1004-W

Insufficient disk space for the database folder.

Free disk space (required): disk-space-required-to-create-database GB

[Cause] The disk space is not sufficient for installation to proceed.

[Action] Return to the main screen and continue installation.

[Workaround] Free the disk space or specify an alternate disk with sufficient space.

KDEX1005-W

No components have been selected.

[Cause] No components are selected for installation.

[Action] Return to the main screen and continue installation.

[Workaround] Select a component to install.

KDEX1006-W

Invalid path. You cannot specify a path exceeding number-of-bytes bytes.

[Cause] The specified path exceeds the maximum path length.

[Action] Return to the main screen and continue installation.

[Workaround] Enter a valid path.

KDEX1008-E

An error occurred during installation/uninstallation.

The operation is canceled.

[Cause] An error occurred during installation/uninstallation.

[Action] Cancel installation/uninstallation.

[Workaround] Retry installation/uninstallation. If the problem persists, contact Support Service.

KDEX1021-W

Could not configure Windows firewall.

[Cause] Could not configure Windows firewall.

[Action] Continue installation.

[Workaround] If Windows firewall is in use, confirm the settings and execute the addfwlist.bat command to enable communication.

KDEX1022-W

Could not restore Windows firewall setting.

[Cause] Could not restore Windows firewall setting.

[Action] Continue uninstallation.

[Workaround] If Windows firewall is in use, confirm the settings and execute the netsh command to disable communication (for the program [Product Name]).

KDEX1024-W

The folder path contains an invalid character ('invalid-character').

[Cause] The folder path contains an invalid character.

[Action] Return to the main screen and continue installation.

[Workaround] Enter a valid folder path.

KDEX1027-E

An installation instance is currently running.

Retry installation after this installation instance ends.

[Cause] An installation instance is running.

[Action] Cancel installation.

[Workaround] Retry installation after the installation instance (current) has ended.

KDEX1030-I

Installation complete.

KDEX1031-W

Please specify the User name and Company name.

[Cause] The User name or Company name is not specified.

[Action] Return to the main screen and continue installation.

[Workaround] Specify User and Company name.

KDEX1032-W

Could not delete the database.

[Cause] The database was not deleted properly during uninstallation.

[Action] Continue uninstallation.

[Workaround] After uninstallation is complete, delete the database and local data folders.

Default database folder: <Application data folder for All Users>\Hitachi\jp1itdmm\Database\db

Default local data folder: <Application data folder for All Users>\Hitachi\jp1itdmm\LocalData

Default operation log database folder: <Application data folder for All Users>\Hitachi\jp1itdmm\Database\oplogdb

KDEX1033-E

Insufficient disk space for the installation folder.

[Cause] The disk space is insufficient for installation to proceed.

[Action] Cancel installation.

[Workaround] Free the disk space or specify an alternate disk with sufficient space. Then, retry installation.

KDEX1034-E

Does not support Silent installation.

Installation is canceled.

[Cause] Silent installation was executed.

[Action] Cancel installation.

[Workaround] Run installation without invalid arguments.

KDEX1035-W

Please specify folder-specified-by-installer on a local disk.

[Cause] A non-local folder was specified.

[Action] Return to the main screen and continue installation.

[Workaround] Specify a local folder.

KDEX1036-W

There is no disk space (sufficient) to upgrade the database.

Free disk space (required): disk-space-required GB, Mount point: mount-point

[Cause] There is no disk space (sufficient) to upgrade the database.

[Action] Return to the main screen and continue installation.

[Workaround] Free disk space or perform custom installation, and then change the database folder (during Setup).

KDEX1037-E

An error occurred during installation.

Might be insufficient disk space for Folder Specified by Setup.

[Cause] Insufficient disk space for installation to proceed.

[Action] Cancel installation.

[Workaround] Either free the disk space, Or perform custom installation, and then change the corresponding folder (during Setup).

KDEX1038-E

An error occurred during installation/uninstallation.

Files or folders in the installation folder may be used by another process.

[Cause] Files or folders in the installation folder are currently in use.

[Action] Cancel installation/uninstallation.

[Workaround] Confirm that files or folders in the installation folder are not used by other processes. Then, retry installation/uninstallation.

KDEX1040-W

Component registration failed.

After installation is complete, from the Start menu, run Component Registration.

[Cause] Component registration failed.

[Action] Continue installation.

[Workaround] After installation is complete, from the Start menu, run Component Registration.

KDEX1043-E

Could not register the license.

Installation is canceled.

[Cause] An error occurred while registering the license.

[Action] Cancel installation.

[Workaround] Retry installation. If the problem persists, contact Customer Support.

KDEX1046-W

Cannot use the folder path specified for folder-specified-by-installer.

A file with a same name as the specified folder already exists in the given path.

[Cause] A file with the same name as the specified folder already exists in the given path. Cannot create a folder with the same name.

[Action] Return to the main screen and continue installation.

[Workaround] Change the name of the existing file, delete the file, or specify a different folder path.

KDEX1047-W

The computer name (computer-name) contains an invalid character.

Valid characters are alphanumerals and hyphen(-).

The first character must be an alphabet and the last character must be an alphabet or a number.

[Cause] The computer name contains an invalid character.

[Action] Return to the main screen and continue installation.

[Workaround] Change the computer name and restart the OS. Then, retry installation.

KDEX1049-E

Failed to proceed installation since Excluded software is currently installed.

[Cause] Excluded software from Product name has been installed in the computer.

[Action] Cancel installation.

[Workaround] Retry installation after uninstalling Excluded software since both the software cannot be used simultaneously.

KDEX1050-Q

Hard disk space might become insufficient later due to large volume of operation logs. Click [OK] to continue.

Required space for database:required-space GB

[Cause] Insufficient hard disk space for folders (in which the database will be created).

[Action] If you want to continue, click [OK]. Clicking [Cancel] will return to the previous screen.

[Workaround] Increase the available disk space for database creation, or specify an alternate hard disk with sufficient space.

KDEX1052-I

Restart the OS after completing "installation" or "uninstallation".

KDEX1053-E

Installation failed. The OS language is not supported.

[Cause] The OS language is not supported.

[Action] Cancel installation.

[Workaround] Retry installation on the OS with supported language.

KDEX1054-E

Service operation failed. Service name=service-name

[Cause] An error occurred while operating the service.

[Action] Cancel installation/uninstallation.

[Workaround] Check the message logs, and take action based on the error logs.

KDEX1055-E

Installation of name-of-product-for-which-installation-was-executed cannot continue.

[Cause] Required software (a prerequisite product name) is not installed in the computer.

[Action] Cancels installation of name-of-product-for-which-installation-was-executed.

[Workaround] Install the required software (a prerequisite product name), and then retry installation of name-of-product-for-which-installation-was-executed.

KDEX1056-E

Installation cannot continue.

[Cause] There is not enough free space on the disk containing the database folder.

Required space: Required space for database GB

[Action] Cancels installation.

[Workaround] Increase the free disk space, or specify a folder on a disk that has enough free space, and then retry installation.

KDEX1057-E

Failed to execute the command. The specified arguments are invalid. Command name=command-name.

[Cause] The specified arguments are invalid.

[Action] Cancel command execution.

[Workaround] Confirm the command arguments, and retry execution.

KDEX1058-E

The troubleshooting information folder is not accessible.

[Cause] The specified troubleshooting information folder does not exist or is not accessible.

[Action] Cancel command execution.

[Workaround] Check if the specified folder exists and is accessible. Then, retry command execution.

KDEX1059-E

Failed to execute the command. You do not have the required permissions. Command name=command-name.

[Cause] The command was executed by a user without Administrator privileges.

[Action] Cancel command execution.

[Workaround] Retry executing the command as a user with Administrator privileges.

KDEX1060-E

Could not collect troubleshooting information.

[Cause] A critical error occurred during command execution.

[Action] Cancel command execution.

[Workaround] Contact Customer Support.

KDEX1061-I

Collected the troubleshooting information.

KDEX1062-W

Could not collect some troubleshooting information.

The following troubleshooting information are not collected.

Folders and files failed to be collected.

[Cause] Insufficient disk space for the troubleshooting information folder.

[Action] Cancel command execution.

[Workaround] Free the disk space, and retry command execution. If the problem persists, get troubleshooting information displayed above individually.

KDEX1063-E

Failed to write to the folder.

Folder path = A folder path

[Cause] The folder is not accessible or an I/O error occurred.

[Action] Cancel command execution.

[Workaround] Check if the specified folder is writable. Then, retry command execution.

KDEX1065-E

Installation cannot continue.

[Cause] There is not enough free space on the disk containing the installation folder.

Required space: Required space for installation MB

[Action] Cancels installation.

[Workaround] Increase the amount of free space on the disk containing the installation folder, and then retry the installation. If you are distributing software by using a package distribution task, edit the site server package, change the installation folder of the install command (the third argument) to a folder on a disk that has enough free space, and then retry the distribution.

KDEX1066-E

Installation cannot continue.

[Cause] A folder that is not on the local disk was specified for the installation folder.

[Action] Cancels installation.

[Workaround] Edit the site server package, specify a local disk for the installation folder of the install command (the third argument), and then retry the distribution.

KDEX1067-W

The database could not be deleted.

[Cause] An error occurred during database deletion.

[Action] Continue uninstallation.

[Workaround] After uninstallation is complete, delete the database folder.

Default database folder: <application-folder-for-All-Users>\Hitachi\jp1itdms\Database\db

KDEX1068-E

The trial version cannot be installed because the actual product is already installed.

[Cause] A user attempted to install a trial version in an environment where the product was already installed.

[Action] Cancels installation of the trial version.

[Workaround] If necessary, uninstall the product, and then install the trial version.

KDEX1069-E

Installation cannot continue.

[Cause] A path that exceeds maximum-number-of-bytes-of-path bytes is specified for the parameter-specified-for-jdn_manager_setup.conf parameter.

[Action] Cancels installation.

[Workaround] Check the path specified for the parameter-specified-for-jdn_manager_setup.conf parameter of the jdn_manager_setup.conf file, and then re-create the package for distributing site server programs.

KDEX1070-E

Installation cannot continue.

[Cause] The path specified for the parameter-specified-for-jdn_manager_setup.conf parameter contains an invalid character (invalid-character).

[Action] Cancels installation.

[Workaround] Check the path specified for the parameter-specified-for-jdn_manager_setup.conf parameter of the jdn_manager_setup.conf file, and then re-create the package for distributing site server programs.

KDEX1071-E

Installation cannot continue.

[Cause] Either a folder that is not on the local disk or an invalid path is specified for the parameter-specified-for-jdn_manager_setup.conf parameter.

[Action] Cancels installation.

[Workaround] Check the path specified for the parameter-specified-for-jdn_manager_setup.conf parameter of the jdn_manager_setup.conf file, and then re-create the package for distributing site server programs.

KDEX1072-E

Installation cannot continue.

[Cause] The value specified for the parameter-specified-for-jdn_manager_setup.conf parameter is outside the valid range. Valid range: valid-range

[Action] Cancels installation.

[Workaround] Check the value specified for the parameter-specified-for-jdn_manager_setup.conf parameter of the jdn_manager_setup.conf file, and then re-create the package for distributing site server programs.

KDEX1073-E

Installation cannot continue.

[Cause] The folders specified for the parameter1-specified-for-jdn_manager_setup.conf and parameter2-specified-for-jdn_manager_setup.conf parameters are the same folder, or one is a subfolder of the other.

[Action] Cancels installation.

[Workaround] Check the paths specified for the parameter1-specified-for-jdn_manager_setup.conf and parameter2-specified-for-jdn_manager_setup.conf parameters of the jdn_manager_setup.conf file, and then re-create the package for distributing site server programs.

KDEX1074-E

Installation cannot continue.

[Cause] A path exceeding maximum-number-of-bytes-of-path bytes is specified for the installation folder.

[Action] Cancels installation.

[Workaround] Edit the site server package, change the specification of the installation folder of the install command (the third argument), and then retry the distribution.

KDEX1075-E

Installation cannot continue.

[Cause] The path for the installation folder contains an invalid character (invalid-character).

[Action] Cancels installation.

[Workaround] Edit the site server package, change the specification of the installation folder of the install command (the third argument), and then retry the distribution.

KDEX1076-E

The full-product version cannot be installed because the trial version is installed.

[Cause] An attempt was made to install the full-product version in an environment in which the trial version was installed.

[Action] Cancels installation of the full-product version.

[Workaround] Remove the trial version, and then try to install the full-product version again.

KDEX1077-E

Failed to write to the data folder shared between servers.

(data folder shared between servers = pass-of-data-folder-shared-between-servers)

[Cause] You do not have permission to access the data folder shared between servers, or an I/O error occurred.

[Action] Cancels installation.

[Workaround] Verify that you are able to write to the data folder shared between servers, and then retry installation.

KDEX1078-W

Failed to delete the ODBC data source.

[Cause] An error occurred during deletion of the ODBC data source.

[Action] Continues removal.

[Workaround] After the product has been removed, start the 32-bit version of ODBC Data Source Administrator, and then delete the system data source (JDN_HIRDB).

KDEX1079-W

If you want to install Manager, also install Remote Install Manager.

[Cause] Remote Install Manager will not be installed.

[Action] Returns to the previous window to continue the installation.

[Workaround] Install both Manager and Remote Install Manager.

KDEX1080-W

Enter the information (user ID and password) required to use the database.

[Cause] The User ID or password is not entered.

[Action] Returns to the previous window to continue the installation.

[Workaround] Enter the user ID and password.

KDEX1081-W

The value specified for input-item-name is invalid. The valid value is valid-value.

[Cause] An invalid value is specified for input-item-name.

[Action] Returns to the previous window to continue the installation.

[Workaround] Specify a valid value.

KDEX1082-W

The entered passwords do not match.

[Cause] The character strings entered in the password field and the password confirmation field are different.

[Action] Returns to the previous window to continue the installation.

[Workaround] Enter the same character strings in the password field and the password confirmation field.

KDEX1083-W

The character string entered in the user ID field cannot be used.

[Cause] A reserved keyword of the database is entered as the user ID.

[Action] Returns to the previous window to continue the installation.

[Workaround] Enter another character string in the user ID field.

KDEX1084-E

Failed to proceed installation/uninstallation since name-of-product-that-must-be-uninstalled is currently installed.

[Cause] name-of-product-that-must-be-uninstalled has been installed on the computer.

[Action] Cancel installation/uninstallation.

[Workaround] Retry installation/uninstallation after uninstalling name-of-product-that-must-be-uninstalled.

KDEX1086-E

Files or folders in the installation folder may be used by another process.

[Cause] Files or folders in the installation folder are currently in use.

[Action] Cancel installation/uninstallation.

[Workaround]

(1) Confirm that files or folders in the installation folder are not used by other processes. Then, retry installation/uninstallation.

(2) If the following service is running, stop the service, and then perform the installation/uninstallation again.

- World Wide Web Publishing Service

KDEX1501-E

Failed to start Setup.

[Cause] Installation was terminated abnormally.

[Action] Cancel Setup.

[Workaround] Perform re-installation.

KDEX1502-W

Could not find the import file.

[Cause] The import file does not exist.

[Action] Return to the main screen and continue Setup.

[Workaround] Specify a valid and existing import file.

KDEX1503-E

An error occurred during Setup.

Setup is canceled.

[Cause] An error occurred during Setup.

[Action] Cancel Setup.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX1504-E

Failed to initialize the database.

[Cause] An error occurred while initializing the database.

[Action] Cancel Setup.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX1505-E

Failed to delete the database or the ODBC data source.

[Cause] The possible causes are as follows:

(1) You do not have permission to access the database folder, the operation log database folder, or the local data folder.

(2) An attempt was made to access the database from Remote Install Manager or IT Desktop Management 2 - Asset Console.

(3) An I/O error occurred.

[Action] Cancels setup.

[Workaround] Perform the following checks, and then retry the setup:

(1) Verify that you have permission to access the database folder, the operation log database folder, and the local data folder.

(2) Stop Remote Install Manager, and then make sure that the commands for the distribution function that uses Remote Install Manager are not being executed. Also, make sure that management information on IT Desktop Management 2 - Asset Console is not being acquired. If there is a cnctusrinf file in the mgr\db\SPOOL folder under the installation folder, use the IP addresses shown in the "C-IP" item of the cnctusrinf file to identify the computers that are accessing the database.

(3) Make sure that no disk failures occurred.

If the problem persists, collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX1506-E

Failed to create the database or the ODBC data source.

[Cause] The possible causes are as follows:

(1) You do not have permission to access the database folder, the operation log database folder, or the local data folder.

(2) An attempt was made to access the database from Remote Install Manager or IT Desktop Management 2 - Asset Console.

(3) An I/O error occurred.

[Action] Cancels setup.

[Workaround] Perform the following checks, and then retry the setup:

(1) Verify that you have permission to access the database folder, the operation log database folder, and the local data folder.

(2) Stop Remote Install Manager, and then make sure that the commands for the distribution function that uses Remote Install Manager are not being executed. Also, make sure that management information on IT Desktop Management 2 - Asset Console is not being acquired. If there is a cnctusrinf file in the mgr\db\SPOOL folder under the installation folder, use the IP addresses shown in the "C-IP" item of the cnctusrinf file to identify the computers that are accessing the database.

(3) Make sure that no disk failures occurred.

If the problem persists, collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX1508-E

The database folder could not be changed.

[Cause] An error occurred while changing the database folder. The possible reasons are:

(1) Improper access privileges to the database folder, the operation log database folder, the operation log backup folder, or the database extraction folder.

(2) An attempt was made to access the database from Remote Install Manager or IT Desktop Management 2 - Asset Console.

(3) An I/O error occurred.

[Action] Cancel Setup.

[Workaround] Perform the following checks, and then retry the setup:

(1) Confirm the access rights of the database folder, the operation log database folder, the operation log backup folder, and the database extraction folder.

(2) Stop Remote Install Manager, and then make sure that the commands for the distribution function that uses Remote Install Manager are not being executed. Also, make sure that management information on IT Desktop Management 2 - Asset Console is not being acquired. If there is a dbconbackup.inf file in the mgr\temp folder under the installation folder, use the IP addresses shown in the "C-ADDR" item of the dbconbackup.inf file to identify the computers that are accessing the database.

(3) Make sure that no disk failures occurred.

If the problem persists, Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX1509-E

An error occurred during Setup.

Setup is canceled.

[Cause] An error occurred during Setup.

[Action] Cancel Setup.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX1510-W

The specified value for Input item name (ex. Logical IP Address) is invalid (out of valid range: Valid range).

[Cause] An invalid value for Input item name (ex. Logical IP Address) was specified.

[Action] Return to the main screen and continue Setup.

[Workaround] Specify a value within the valid range.

KDEX1511-E

The user does not have Administrative Privileges.

[Cause] The user doest not have Administrative Privileges.

[Action] Cancel Setup.

[Workaround] Retry Setup as a user with Administrative Privileges.

KDEX1512-E

Currently, another Setup instance is running.

[Cause] Another Setup instance is currently running.

[Action] Cancel the new Setup.

[Workaround] Continue running the existing Setup instance.

KDEX1513-E

Could not find the setting file for Setup or the file may be corrupted.

[Cause] The setting file (Setup) does not exist or is corrupted.

[Action] Cancel Setup.

[Workaround] Retry installation after uninstalling the program.

KDEX1514-E

Could not upgrade the database.

[Cause] An error occurred while upgrading the database. The possible reasons are:

(1) Improper access privileges to database folder, local data folder, or database extraction folder.

(2) An attempt was made to access the database from Remote Install Manager or IT Desktop Management 2 - Asset Console.

(3) An I/O error occurred.

[Action] Cancel Setup.

[Workaround] Perform the following checks, and then retry the setup:

(1) Confirm the access rights of database folder, local data folder, and database extraction folder.

(2) Stop Remote Install Manager, and then make sure that the commands for the distribution function that uses Remote Install Manager are not being executed. Also, make sure that management information on IT Desktop Management 2 - Asset Console is not being acquired. If there is a cnctusrinf file in the mgr\db\SPOOL folder under the installation folder, use the IP addresses shown in the "C-IP" item of the cnctusrinf file to identify the computers that are accessing the database. If there is a dbconbackup.inf file in the mgr\temp folder under the installation folder, use the IP addresses shown in the "C-ADDR" item of the dbconbackup.inf file to identify the computers that are accessing the database.

(3) Make sure that no disk failures occurred.

If the problem persists, Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX1516-E

Could not stop the service. Service name=service-name.

Setup is canceled.

[Cause] An error occurred while stopping the service.

[Action] Cancel Setup.

[Workaround] Check the message logs and take action based on the errors in the logs.

KDEX1517-E

Could not start the service. Service name=service-name.

Setup is canceled.

[Cause] An error occurred while starting the service.

[Action] Cancel Setup.

[Workaround] Check the message logs, and take action based on the error logs.

KDEX1518-E

Could not chage the startup service type. Service name=service-name.

Setup is being canceled.

[Cause] An error occurred while changing the startup service type.

[Action] Cancel Setup.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX1519-Q

To continue Setup, JP1/IT Desktop Management 2 - Manager services must be stopped. Do you want to stop the service? The service will start automatically when the Setup is complete.

KDEX1520-Q

To continue Setup, set the cluster resources associated with the following services offline. Then, click OK to resume Setup.

Set the cluster resources online after the Setup is completed.

(service = service-name)

KDEX1521-Q

To continue Setup, set the cluster resources associated with the following services offline. Then, click OK to resume Setup.

(service = service-name)

KDEX1524-W

Insufficient disk space. Required free disk space: required-free-disk-space GB, Mount point: mount-point.

[Cause] Insufficient disk space.

[Action] Return to the main screen and continue Setup.

[Workaround] Free the disk space or specify an alternate disk with sufficient space.

KDEX1525-W

Invalid cluster configuration content.

The cluster resource status is either offline or another node is set as the resource owner.

[Cause] Either the cluster resource status is offline or another node is set as the resource owner.

[Action] Return to the main screen and continue Setup.

[Workaround] Confirm the status and ownership of the cluster resource.

KDEX1526-I

(JP1_ITDM2_Web Container) service has started.

KDEX1527-I

(JP1_ITDM2_Web Container) service has stopped.

KDEX1528-E

Could not start (JP1_ITDM2_Web Container) service.

[Cause] An error occurred while starting the service.

[Action] Cancel the service initiation.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX1529-E

(JP1_ITDM2_Web Container) service has terminated abnormally due to an unexpected cause.

[Cause] An unrecoverable error occurred in the service.

[Action] Stop the service.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX1530-E

Could not start (JP1_ITDM2_Web Container) service since JP1/IT Desktop Management 2 - Manager Setup was not complete.

[Cause] The service was started before the JP1/IT Desktop Management 2 - Manager Setup was complete.

[Action] Cancel (JP1_ITDM2_Web Container) service initiation.

[Workaround] Complete the JP1/IT Desktop Management 2 - Manager Setup first and then start the service.

KDEX1531-I

Setup successful.

KDEX1532-E

Setup failed.

KDEX1533-W

Could not create login shortcut for JP1/IT Desktop Management 2 - Manager.

To log in JP1/IT Desktop Management 2 - Manager, use the URL:

URL-to-log-in-to-JP1/IT Desktop Management 2 - Manager

To launch from a shortcut, create an internet shortcut of the above URL in the following file:

full-path-of-<installation folder>\mgr\conf\jdn_login.url

[Cause] An error occurred while creating a login shortcut for JP1/IT Desktop Management 2 - Manager.

[Action] Continue Setup.

[Workaround] To log in JP1/IT Desktop Management 2 - Manager, access the URL provided in this message.

To launch from a shortcut, create an internet shortcut as directed.

KDEX1534-W

The folder specified for the Folder Specified by Setup is unusable.

[Cause] Among the following folders that were specified during the current or previous setup, at least two folders are identical or have a parent-child relationship:

- Database folder

- Data folder

- Local data folder

- Database backup folder

[Action] Return to the previous window and continue the setup.

[Workaround] For the following folders that were specified during the current or previous setup, specify a unique folder that does not have a parent-child relationship with another:

- Database folder

- Data folder

- Local data folder

- Database backup folder

KDEX1535-W

Specify folder-specified-by-setup on a local disk.

[Cause] folder-specified-by-setup is not on the local disk, or the path is invalid.

[Action] Return to the main screen and continue Setup.

[Workaround] Specify a folder on the local disk for folder types like database, data, local data, and database extraction.

KDEX1536-E

An error occurred during Setup.

Insufficient disk space for folder-specified-by-setup.

[Cause] Not enough disk space for the specified folders.

[Action] Cancel Setup.

[Workaround] Free the disk space and retry Setup or specify a folder on a disk with sufficient free space.

KDEX1537-W

Invalid content in import file.

[Cause] An invalid import file was specified.

[Action] Return to the main screen and continue Setup.

[Workaround] Specify a correct import file. If the specified import file is not correct, try copying the import file from the primary server.

KDEX1538-E

An error occurred during Setup.

Insufficient disk space.

Required free disk space=required-free-disk-space GB, Mount point=mount-point

[Cause] Insufficient disk space to complete Setup.

[Action] Cancel Setup.

[Workaround] Free the disk space and retry Setup or specify a folder on a disk with sufficient free space.

KDEX1539-W

Insufficient disk space to upgrade the database.

Required free disk space=required-free-disk-space MB, Mount point=mount-point.

[Cause] Insufficient disk space to complete Setup.

[Action] Return to the main screen and continue Setup.

[Workaround] Free the disk space and retry Setup or specify a folder on a disk with sufficient free space.

KDEX1543-E

The license could not be registered.

License registration is being canceled.

[Cause] An error occurred while registering the license.

[Action] Cancel Setup.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX1545-E

Could not launch Setup. Database Manager or a command is running.

[Cause] Setup was launched when the Database Manager or a command was running.

[Action] Cancel Setup launch.

[Workaround] Wait until the executing process (Database Manager or command) ends, and then retry Setup.

KDEX1546-W

You cannot specify a path that exceeds The number of bytes bytes for Folder Specified by Setup.

[Cause] The specified path for Folder Specified by Setup exceeds the maximum path length.

[Action] Return to the main screen and continue setup.

[Workaround] Enter a valid path.

KDEX1547-E

Could not start (JP1_ITDM2_Web Container) service. An executing process (Setup, Database Manager, or a command) might be running.

[Cause] Started the (JP1_ITDM2_Web Container) service when an executing process (Setup, Database Manager, or a command) was running.

[Action] Cancel the (JP1_ITDM2_Web Container) service initiation.

[Workaround] Wait until the executing process (Setup, Database Manager, or command) ends, and retry starting (JP1_ITDM2_Web Container) service.

KDEX1548-W

Invalid cluster configuration content.

[Cause] Secondary server option was not selected.

[Action] Return to the main screen and continue Setup.

[Workaround] Select the secondary server option, and continue Setup.

KDEX1550-W

The specified logical IP address for the cluster configuration is invalid.

[Cause] The specified logical IP address does not exist as a cluster resource.

[Action] Return to the main screen and continue Setup.

[Workaround] If on the primary server, check the specified logical IP address. If on the secondary server, check if the import file is correct.

KDEX1551-W

Cannot use the specified folder for folder-specified-by-setup.

A file with a same name as the specified folder already exists in the folder path.

[Cause] Cannot create a folder with this name in the folder path. Since the folder already contains a file with the same name.

[Action] Return to the main screen and continue Setup.

[Workaround] Change the name of the existing file, delete the file, or specify a different folder path.

KDEX1552-E

The computer name (computer-name) contains an invalid character.

Valid characters are alphanumerals and hyphen(-).

The first character must be an alphabet and the last character must be an alphabet or a number.

[Cause] The computer name contains an invalid character.

[Action] Cancel Setup.

[Workaround] Change the computer name and restart the OS. Then, retry Setup.

KDEX1555-W

Failed to connect operation-log-backup-folder.

[Cause] An error occurred while connecting to the specified network resource.

[Action] Return to the main screen and continue Setup.

[Workaround] Create a folder on a valid network or specify a folder on a local disk.

KDEX1556-W

Please specify folders on the network in UNC format.

[Cause] A network drive was specified.

[Action] Return to the main screen and continue Setup.

[Workaround] Set the folder in UNC format.

KDEX1557-W

The folder specified for Folder Specified by Setup is unusable.

[Cause] Among the following folders that were specified during the current or previous setup, at least two folders are identical or have a parent-child relationship:

- Folder specified in the Folder Settings window

- Operation log database folder

- Operation log storage folder

- Output folder for saving the revision history

[Action] Return to the previous window and continue the setup.

[Workaround] For the following folders that were specified during the current or previous setup, specify a unique folder that does not have a parent-child relationship with another:

- Folder specified in the Folder Settings screen

- Operation log database folder

- Operation log storage folder

- Output folder for saving the revision history

KDEX1558-W

The specified Username or Password is invalid.

[Cause] The Username or Password used for connecting to the network resource was invalid.

[Action] Return to the main screen and continue Setup.

[Workaround] Specify a valid Username and Password.

KDEX1559-E

An error occurred during setup.

Insufficient disk space for folder-specified-in-Folder-Settings-window or operation-log-storage-location.

[Cause] Insufficient disk space for the specified folder.

[Action] Cancel Setup.

[Workaround] Free the disk space and retry Setup or specify a folder on a disk with sufficient free space.

KDEX1560-E

An error occurred during Setup.

Failed to connect operation-log-backup-folder.

[Cause] An error occurred while connecting to the specified network resource.

[Action] Cancel Setup.

[Workaround] Specify a folder on a valid network or specify a folder on a local disk. Then retry Setup.

KDEX1561-E

An error occurred during Setup.

The Username or Password used for connecting to operation-log-backup-folder is invalid.

[Cause] The Username or Password specified for connecting to the network resource was invalid.

[Action] Cancel Setup.

[Workaround] Confirm that the Username and Password are valid, and then retry Setup.

KDEX1562-I

Username and Password has been set successfully to connect to the operation log backup folder.

KDEX1563-W

Specify operation-log-storage-area on a local disk.

[Cause] operation-log-storage-area is not on the local disk, or the path is invalid.

[Action] Return to the main screen and continue Setup.

[Workaround] Specify a folder on a local disk.

KDEX1564-Q

If the operation logs backup setting is off, the operations logs will be deleted. If you want to keep operations logs, change the automatic backup settings to on.

Click OK to start. Click Cancel to review.

KDEX1565-W

Invalid folder path for operation-log-storage-area.

[Cause] An invalid folder path is specified for operation-log-storage-area.

[Action] Return to the main screen and continue Setup.

[Workaround] Specify a valid folder path for operation-log-storage-area.

KDEX1566-W

The specified folder-specified-by-setup is not accessible.

[Cause] The possible reasons are:

(1) Either the cluster resource status is offline or another node is set as the resource owner.

(2) An I/O error occurred.

[Action] Return to the main screen and continue Setup.

[Workaround] Confirm the specified folder is accessible. If you are specifying the cluster shared disk, confirm the status and ownership of the disk resource.

KDEX1567-W

Component registration failed.

After setup is complete, from the Start menu, run Component Registration.

[Cause] Component registration failed.

[Action] Continue setup.

[Workaround] After setup is complete, from the Start menu, run Component Registration.

KDEX1568-W

Failed to start the service. Service name=service-name.

[Cause] An error occurred while starting the service.

[Action] Continue Setup.

[Workaround] Check the message logs, and take action based on the error logs.

KDEX1569-I

Restart the OS after completing Setup.

KDEX1570-Q

The settings will be modified so that operation logs are not collected. This will delete already collected operation logs.

(To obtain already collected operation logs and reference these logs in an environment where a site server is used and the operation logs are distributed, specify the settings so that operation logs are collected.)

Do you want to continue?

KDEX1571-E

The configuration file specified for setup is invalid.

[Cause] An invalid file was specified for the configuration file specified for setup.

[Action] Cancels setup.

[Workaround] Perform installation again. If the problem persists, use the troubleshooting information collection command to collect troubleshooting information, and contact Customer Support.

KDEX1572-E

The folder specified for the folder-specified-by-the-configuration-file is not usable.

[Cause] The specified folder is a database folder, data folder, or operation log data folder, or has a parent-child relationship with such a folder.

[Action] Cancels setup.

[Workaround] Specify a folder that is not a database folder, data folder, or operation log data folder, and does not have a parent-child relationship with such a folder.

KDEX1573-E

The path specified for the folder-specified-by-the-configuration-file is not usable.

[Cause] An invalid path or a path to a non-local disk was specified for folder-specified-by-the-configuration-file.

[Action] Cancels setup.

[Workaround] Specify a path on a local disk.

KDEX1574-E

The folder path specified for the folder-specified-by-the-configuration-file is not usable. An existing file has the same name as the path folder.

[Cause] The folder cannot be created because an existing file has the same name as the path folder.

[Action] Cancels setup.

[Workaround] Change the name of the existing file, delete the file, or specify a different folder path.

KDEX1575-E

The disk containing the folder specified for the folder-specified-by-the-configuration-file cannot be accessed.

[Cause] A disk failure occurred.

[Action] Cancels setup.

[Workaround] Make sure the disk containing the specified folder can be accessed.

KDEX1576-W

The folder specified for folder-specified-by-setup is unusable.

[Cause] Among the following folders that were specified during the current or previous setup, at least two folders are identical or have a parent-child relationship:

- Database folder

- Data folder

- Operation log data folder

[Action] Return to the previous window and continue the setup.

[Workaround] For the following folders that were specified during the current or previous setup, specify a unique folder that does not have a parent-child relationship with another:

- Database folder

- Data folder

- Operation log data folder

KDEX1577-E

Setup cannot start because a command is executing.

[Cause] Setup was executed while a command was executing.

[Action] Cancels the start of setup.

[Workaround] Wait until the command finishes, and then re-execute setup.

KDEX1578-W

The port number specified for specified-reserved-port-number cannot be used.

[Cause] A reserved port number was specified for specified-reserved-port-number.

[Action] Return to the main screen and continue Setup.

[Workaround] Specify another port number, and then retry Setup.

KDEX1579-E

An attempt to stop the service failed.

[Cause] Setup was executed during processing to start or stop the service used by JP1/IT Desktop Management 2 - Manager.

[Action] Cancels setup.

[Workaround] Wait a while, and then re-execute Setup.

KDEX1580-E

An attempt to start the service failed (service name = service-name). Setup will be canceled.

[Cause] Setup was executed during processing to start or stop the service.

[Action] Cancels setup.

[Workaround] Wait a while, and then re-execute Setup.

KDEX1581-E

The service (Web-Container-service-name) cannot be started from a type-of-server. Service startup will be canceled.

[Cause] The service was started on a server other than the management server.

[Action] Cancels startup of the service.

[Workaround] Start the service (Web-Container-service-name) from the management server.

KDEX1582-W

Failed to connect to data-folder-of-database-server.

[Cause] The data folder shared between servers that was specified in the folder settings window cannot be connected to.

[Action] Returns to the previous window and continues setup.

[Workaround] Verify that the path of the specified data folder shared between servers is correct, and then check whether there are any problems in the network.

KDEX1583-W

Failed to read files from the database server.

[Cause] Possible causes are as follows:

(1) The path specified for the data folder shared between servers is incorrect.

(2) Database server setup is incomplete.

(3) You do not have permission to access the data folder shared between servers.

(4) An I/O error occurred.

[Action] Returns to the previous window and continues setup.

[Workaround]

(1) Specify the same path for both of the following:

- The path specified for the data folder in the folder settings window during database setup

- The path specified for the data folder shared between servers

(2) Verify that database server setup is complete.

(3) Verify that you have permission to both read from and write to the data folder shared between servers.

(4) Verify that no disks have failed.

KDEX1584-E

An error occurred during setup.

[Cause] The management-server is accessing the database.

[Action] Cancels setup.

[Workaround] Stop the service given below, which is used by JP1/IT Desktop Management 2 - Manager on the management-server, and then retry setup.

(service = service-name)

KDEX1587-Q

From the management server, stop the service given below, which is used by JP1/IT Desktop Management 2 - Manager. If you continue while this service is running, setup might not finish properly.

(service = service-name-of-management-server)

The database server service will stop automatically. The database server service that is stopped in this way will start automatically after setup is complete.

Are you sure you want to stop the database server service?

KDEX1588-Q

From the management server, stop the service given below, which is used by JP1/IT Desktop Management 2 - Manager. If you continue while this service is running, setup might not finish properly.

(service = service-name-of-management-server)

Take offline the cluster resources associated with the service given below. After doing so, click [OK] to continue setup.

After setup is complete, bring the cluster resources back online.

(service = service-name-of-database-server)

KDEX1589-Q

From the management server, stop the service given below, which is used by JP1/IT Desktop Management 2 - Manager. If you continue while this service is running, setup might not finish properly.

(service = service-name-of-management-server)

Take offline the cluster resources associated with the service given below. After doing so, click [OK] to continue setup.

(service = service-name-of-database-server)

KDEX1590-E

Failed to write to the data folder shared between servers.

(data folder shared between servers = pass-of-data-folder-shared-between-servers)

[Cause] Possible causes are as follows:

(1) You do not have permission to access the data folder shared between servers.

(2) An I/O error occurred.

[Action] Cancels setup.

[Workaround] Check the following, and then retry setup.

(1) Verify that you have permission to write to the data folder shared between servers.

(2) Verify that no disks have failed.

KDEX1591-W

A folder that cannot be used is specified for the folder-specified-by-Setup.

[Cause] The same folder as the installation folder was specified for the folder-specified-by-Setup.

[Action] Returns to the previous window and continues setup.

[Workaround] For the folder-specified-by-Setup, specify a folder other than the installation folder.

KDEX1592-E

An error occurred during setup processing.

[Cause] Possible causes are as follows:

(1) The IP address specified in the database connection settings window during setup is invalid.

(2) An I/O error occurred.

[Action] Cancels setup.

[Workaround] Check the following, and then retry setup.

(1) Verify that the IP address specified in the database connection settings window during setup is valid.

(2) Verify that no disks have failed.

If the problem persists, collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX1593-E

Failed to connect to the database.

[Cause] Possible causes are as follows:

(1) In the database connection settings window during setup, an IP address was specified that does not exist in the segment that includes the management server.

(2) In the cluster environment settings window for the database server, the IP address specified for the logical IP address does not exist in the segment that includes the management server.

(3) The database is not running.

[Action] Cancels setup.

[Workaround] Check the following, and then retry setup.

(1) Verify that the IP address specified in the database connection settings window during setup exists in the segment that includes the management server.

(2) Verify that the logical IP address specified in the cluster environment settings window for the database server is an IP address that exists in the management server segment.

(3) Verify that the database server service (service-of-database-server) is running.

KDEX1594-E

Failed to create the folder for storing operation logs.

[Cause] Possible causes are as follows:

(1) You do not have permission to access the folder for storing operation logs.

(2) An I/O error occurred.

[Action] Cancels setup.

[Workaround] Check the following, and then retry setup.

(1) Verify that you have permission to access the folder for storing operation logs.

(2) Verify that no disks have failed.

KDEX1595-I

The user name and password for connecting to the output folder for saving the revision history were specified.

KDEX1597-E

Failed to create the output folder for saving the revision history.

[Cause] Possible causes include the following:

(1) You do not have access rights for the output folder.

(2) An I/O error occurred.

[Action] Cancels setup.

[Workaround] Verify the following, and then retry setup.

(1) Verify that you have access rights for the output folder.

(2) Verify that no disk failure has occurred.

KDEX1598-E

Failed to upgrade the database.

[Cause] An error occurred in an attempt to upgrade the database. Possible causes are as follows:

(1) You do not have permission to access the database folder, the local data folder, or the database backup folder.

(2) An I/O error occurred.

(3) The management server is accessing the database.

[Action] Cancels setup.

[Workaround]

(1) Verify that you have permission to access the database folder, the local data folder, or the database backup folder.

(2) Make sure that no disk failure has occurred.

(3) Stop the following services that are being used by JP1/IT Desktop Management 2 on the management server, and then re-execute setup:

service-name

If the problem persists, collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX1599-E

The setup is canceled.

The setup is interrupted.

[Cause] The setup of the distribution function that uses Remote Installation Manager is canceled.

[Action] Cancels the setup.

[Workaround] Retry the setup.

KDEX1600-Q

If you are using Remote Installation Manager or IT Desktop Management 2 - Asset Console, perform the checks below. If you continuously use Remote Installation Manager or IT Desktop Management 2 - Asset Console without performing the checks, the setup might not have successfully completed.

- Stop Remote Installation Manager, and then make sure that the commands for the distribution function that uses Remote Installation Manager are not being executed.

- Make sure that management information on IT Desktop Management 2 - Asset Console is not being acquired.

To continue the setup, you must stop the services used by product-name.

Click [OK] to display the setup window of the distribution function that uses Remote Installation Manager.

Are you sure you want to stop these services?

Stopped services will start automatically when the setup is complete.

KDEX1601-Q

If you are using Remote Installation Manager or IT Desktop Management 2 - Asset Console, perform the checks below. If you continuously use Remote Installation Manager or IT Desktop Management 2 - Asset Console without performing the checks, setup might not successfully complete.

- Stop Remote Installation Manager, and then make sure that the commands for the distribution function that uses Remote Installation Manager are not being executed.

- Make sure that management information on IT Desktop Management 2 - Asset Console is not being acquired.

In addition, to continue the setup, take the cluster resources that are associated with the service shown below offline.

After taking the cluster resources offline, click [OK]. The setup window of the distribution function that uses Remote Installation Manager appears.

After the setup, bring the cluster resources online.

list-of-corresponding-JP1/IT Desktop Management 2-services

KDEX1602-Q

If you are using Remote Installation Manager or IT Desktop Management 2 - Asset Console, perform the checks below. If you continuously use Remote Installation Manager or IT Desktop Management 2 - Asset Console without performing the checks, the setup might not successfully complete.

- Stop Remote Installation Manager, and then make sure that the commands for the distribution function that uses Remote Installation Manager are not being executed.

- Make sure that management information on IT Desktop Management 2 - Asset Console is not being acquired.

In addition, to continue the setup, take the cluster resources that are associated with the service shown below offline. After taking the cluster resources offline, click [OK]. The setup continues.

list-of-corresponding-JP1/IT Desktop Management 2-services

KDEX1603-E

An error occurred during the setup.

The setup will be interrupted.

[Cause] An error occurred during the setup.

[Action] Cancels the setup.

[Workaround] Use the troubleshooting information acquisition command to acquire troubleshooting information, and then contact the support service.

KDEX1604-W

The character string entered in the user ID field cannot be used.

[Cause] A reserved keyword of the database is entered as the user ID.

[Action] Returns to the previous window to continue the setup.

[Workaround] Enter another character string, and then perform the setup again.

KDEX1605-W

The character string entered in the current password field is invalid.

[Cause] The entered character string is different from the current password that was specified.

[Action] Returns to the previous window to continue the setup.

[Workaround] Enter a valid password.

KDEX1606-W

The passwords that you entered are inconsistent.

[Cause] The passwords entered in Password or New password and Confirm new password are different.

[Action] Returns to the previous window to continue the setup.

[Workaround] Enter the same character strings in Password and Confirm password.

KDEX1607-Q

The server configuration is set to "multi-server configuration".

If you set the configuration to "multi-server configuration", you cannot change it to "single-server configuration". Do you want to continue?

KDEX1608-W

The specified value for "control-name" is invalid. You cannot set "specified-invalid-value" for "control-name".

[Cause] An invalid value is specified for "control-name".

[Action] Returns to the previous screen, and continues the setup.

[Workaround] Specify a valid value.

KDEX1609-W

The specified value for "control-name" is invalid. The name "control-name" is already specified.

[Cause] The name "control-name" is already specified.

[Action] Returns to the previous screen, and continues the setup.

[Workaround] Specify a name that is different from "control-name".

KDEX1700-E

Because reorganize the database is incomplete, startup of the (service display name) service failed.

[Cause] Because reorganize the database is incomplete, the (service display name) service could not be started.

[Cause] Because reorganize the database is incomplete, the (service display name) service could not be started.

[Action] Stops the (service display name) service.

KDEX2002-E

Could not import device information.

KDEX2003-I

Exported device information successfully.

KDEX2004-E

Could not export device information.

KDEX2005-I

Imported asset information successfully.

KDEX2006-E

Could not import asset information.

KDEX2007-I

Exported asset information successfully.

KDEX2008-E

Could not export asset information.

KDEX2009-I

Imported network connection information successfully.

KDEX2010-E

Could not import network connection information.

KDEX2011-I

Exported network connection information successfully.

KDEX2012-E

Could not export network connection information.

KDEX2013-I

The API request was accepted. URL = URL, User ID = user-id, Request number = request-number

Note: This message is output to JP1/IT Desktop Management 2 - Manager-installation-folder\log\JDNSTRMn.LOG.

KDEX2014-I

The API response was returned. Request number = request-number, Status code = status-code, Status code text = status-code-text

Note: This message is output to JP1/IT Desktop Management 2 - Manager-installation-folder\log\JDNSTRMn.LOG.

KDEX2015-W

Failed to operate part of the API. Request number = request-number, Status code = status-code, Status code text = status-code-text, Cause of error = cause-of-error

Note: This message is output to JP1/IT Desktop Management 2 - Manager-installation-folder\log\JDNSTRMn.LOG.

KDEX2016-E

Failed to authenticate the API user. Request number = request-number, Status code = status-code, Status code text = status-code-text, Cause of error = cause-of-error

Note: This message is output to JP1/IT Desktop Management 2 - Manager-installation-folder\log\JDNSTRMn.LOG.

KDEX2017-E

The API request is incorrect. Request number = request-number, Status code = status-code, Status code text = status-code-text, Cause of error = cause-of-error

Note: This message is output to JP1/IT Desktop Management 2 - Manager-installation-folder\log\JDNSTRMn.LOG.

KDEX2018-E

Failed to run the API. Request number = request-number, Status code = status-code, Status code text = status-code-text, Cause of error = cause-of-error

[Cause] Possibly one of the following:

(1) There was not enough free space on the disk of either the data folder or the installation folder.

(2) An error occurred on the management server.

[Processing] Execution will be terminated.

[Action] Take the following steps.

(1) Increase the amount of free space on the disk of the data folder and the installation folder.

(2) If an error occurs repeatedly, collect information needed for troubleshooting by using the relevant command, and then contact the support service.

Note: This message is output to JP1/IT Desktop Management 2 - Manager-installation-folder\log\JDNSTRMn.LOG.

KDEX2019-E

The specified message body for the API request is invalid. Request number = request-number, Detail = detailed-information

Note: This message is output to JP1/IT Desktop Management 2 - Manager-installation-folder\log\JDNSTRMn.LOG.

Supplementary information

detailed-information is output in format 1 when an incorrect item can be identified, or in format 2 when an incorrect item cannot be identified.

Format 1

sequence-number:item-name:error-message

Format 2

error-message

sequence-number: Sequence number (starting from 1) specified in JSON format and assigned to device information

item-name: Name of the incorrect item specified for the device information in question

error-message: Error message

For example, if the character string specified for the DeviceID item for the 10th registered device exceeds the maximum length allowed, the following detailed information is output:

10:DeviceID:Specify a character string not exceeding 1024 characters.

KDEX2020-E

Login is not possible with an API user account. User ID = user-ID

KDEX3004-I

Logon succeeded. UserID=user-ID.

KDEX3005-E

Failed to log in. The specified User ID or Password is invalid. User ID=user-ID.

[Cause] The specified User ID or Password is invalid.

[Action] Cancel login.

[Workaround] Log in using a valid User ID and Password.

KDEX3006-E

Logon failed. UserID=user-ID (or null if not obtainable), cause message=cause-message

[Cause]Database error or Expiration of Usage period.

[Action] Cancel Logon.

[Workaround] For expiration of usage period, purchase a license. For other reasons, collect troubleshooting information from troubleshooting collection information command and contact support service.

KDEX3007-I

Logoff successful UserID=user-ID

KDEX3027-E

Logon failed. User account is locked. UserID=user-ID

KDEX3029-E

Lock user account. UserID=user-ID

KDEX3030-I

Unlock user account. UserID=user-ID

KDEX3200-I

User is registered. User ID=user-ID, Permissions list=permissions-list

KDEX3201-I

User is deleted. User ID=user-ID

KDEX3202-I

User's permission is changed. User ID=user-ID, Permissions list=permissions-list

KDEX3203-I

The security policy has been updated. Policy name=policy-name, Policy ID=policy-ID, Update type=update-type

KDEX3204-W

The security policy could not be updated. (policy name = policy-name, policy ID = policy-ID, update type = update-type, cause of failure = cause-of-failure)

[Cause] If the cause of failure is "application error" and the update type is "update", security policy names are duplicated. If the cause of failure is "application error" and the update type is "delete", an attempt was made to delete a security policy associated with a device or group. In other cases, an error occurred in the database.

[Action] Cancels the update of the security policy.

[Workaround] If the cause of failure is "application error" and the update type is "update", specify a security policy name that does not conflict with another. If the cause of failure is "application error" and the update type is "delete", remove all associations, and then delete the security policy. In other cases, collect troubleshooting information by using the troubleshooting information collection command, and then contact customer support.

KDEX3205-I

Agent setting is updated. agent_setting_name=agent-setting-name, setting_ID=setting-ID, update_type=update-type

KDEX3206-W

An agent setting could not be updated. (agent setting name = agent-setting-name, setting ID = setting-ID, update type = update-type, cause of failure = cause-of-failure)

[Cause] If the cause of failure is "application error" and the update type is "update", agent setting names are duplicated. If the cause of failure is "application error" and the update type is "delete", an attempt was made to delete an agent setting associated with a device or group. In other cases, an error occurred in the database.

[Action] Cancels the update of the agent setting.

[Workaround] If the cause of failure is "application error" and the update type is "update", specify an agent setting name that does not conflict with another. If the cause of failure is "application error" and the update type is "delete", remove all associations, and then delete the agent setting. In other cases, collect troubleshooting information by using the troubleshooting information collection command, and then contact customer support.

KDEX3238-I

Successful license file registration.

KDEX3239-W

Error in license file registration.

KDEX3240-I

Updated login credentials or proxy login credentials in support service site setting. userId=user-ID, proxyUserId=proxy-user-ID, proxyIPAddress=proxy-IP-address, proxyPortno=proxy-port-number

KDEX3241-W

Login credentials or proxy login credentials in support service site setting failed. userId=user-ID, proxyUserId=proxy-user-ID, proxyIPAddress=proxy-IP-address, proxyPortno=proxy-port-number

KDEX3242-I

Updated login credentials in discovery settings. credentialName=credential-name, credentialKind=credential-kind, userName or communityName =user-name or community-name

KDEX3243-W

Login credentials update in discovery setting failed. credentialName=credential-name, credentialKind=credential-kind, userName or communityName =user-name or community-name

KDEX3244-I

Updated login credentails for AMT settings. userId=user-ID

KDEX3245-W

Login credential update for AMT setting failed. userId=user-ID

KDEX3246-I

Updated login credentials for AD setting. userId=user-ID, hostname=host-name, portno=port-number, domainName=domain-name

KDEX3247-W

Login credential update for AD setting failed. userId=user-ID, hostname=host-name, portno=port-number, domainName=domain-name

KDEX3248-I

Updated login credentials for mail server connection settings. userId=user-ID, hostname=host-name, portno=port-number

KDEX3249-W

Login credential update for mail server connection setting failed. userId=user-ID, hostname=host-name, portno=port-number

KDEX3252-I

The mandatory software will be distributed based on the security policy settings. You can view the task progress status in the ITDM-compatible distribution screen. Task name=task-name

KDEX3253-I

The unauthorized software will be uninstalled based on the security policy settings. You can view the task progress status in the ITDM-compatible distribution screen. Task name=task-name

KDEX3254-I

Task started on schedule execution-start-time. Task name=task-name

KDEX3255-I

This on demand task has been executed some time ago. It is deleted now. Task name=task-name

KDEX3265-I

The credential ID or Password in the discovery setting was deleted. discoveryCredentialInformationID=discovery-credential-information-ID, discoveryCredentialInformationName=discovery-credential-information-name

KDEX3266-I

The administrator permissions password for the AMT settings was updated.

KDEX3267-W

An attempt to update the administrator permissions password for the AMT settings failed.

KDEX3299-I

An MDM setting was added. (setting ID = setting-ID, MDM setting name = MDM-setting-name)

KDEX3300-E

Failed to add an MDM setting. (setting ID = setting-ID, MDM setting name = MDM-setting-name)

KDEX3301-I

The user ID or password of an MDM server or proxy server was updated. (setting ID = setting-ID, MDM setting name = MDM-setting-name)

KDEX3302-E

Failed to update the user ID or password of an MDM server or proxy server. (setting ID = setting-ID, MDM setting name = MDM-setting-name)

KDEX3303-I

An MDM setting was deleted. (setting ID = setting-ID, MDM setting name = MDM-setting-name)

KDEX3304-E

Failed to delete an MDM setting. (setting ID = setting-ID, MDM setting name = MDM-setting-name)

KDEX3308-I

The revision history settings were changed.

KDEX3309-E

Failed to change the revision history settings.

KDEX3319-I

The auto update settings of the network filter list were changed.

KDEX3320-E

Failed to change the auto update settings of the network filter list.

KDEX3321-I

Changed the JP1/NETM/NM - Manager linkage settings.

KDEX3322-E

Failed to change the JP1/NETM/NM - Manager linkage settings.

KDEX3333-I

The settings for the Operation Log Settings in the Settings window were changed.

KDEX3334-E

Failed to change the settings for the Operation Log Settings in the Settings window.

KDEX3338-I

The operation permission settings for the USB device were changed.

KDEX3340-I

The authentication information for logging in to Remote Install Manager or Packager was successfully obtained. UserID=user-ID

KDEX3341-E

Failed to obtain the authentication information required for logging in to Remote Install Manager or Packager. The specified User ID or Password is invalid. User ID=user-ID.

[Cause] The specified User ID or Password is invalid.

[Action] Cancel login.

[Workaround] Log in using a valid User ID and Password.

KDEX3342-E

Failed to obtain the authentication information required for logging in to Remote Install Manager or Packager. UserID=user-ID (or null if not obtainable), cause message=cause-message

[Cause]Database error or Expiration of Usage period.

[Action] Cancel Logon.

[Workaround] For expiration of usage period, purchase a product license. For other reasons, collect troubleshooting information from troubleshooting collection information command and contact support service.

KDEX3343-E

Failed to obtain the authentication information required for logging in to Remote Install Manager or Packager. The user account is locked. UserID=user-ID.

[Cause] The user account is locked.

[Action] Cancels the login.

[Workaround] Unlock the user account.

KDEX3344-I

The settings for the [Network Filter Settings] - [Range of targets subject to automatic updates of the Network Filter List] in the Settings window were changed.

KDEX3345-E

Failed to change the settings for the [Network Filter Settings] - [Range of targets subject to automatic updates of the Network Filter List] in the Settings window.

KDEX3356-I

The settings for the [Windows Agent Deployment] - [Settings of the Components of the Agents to Be Deployed] in the Settings window were changed.

KDEX3357-E

Failed to change the settings for the [Windows Agent Deployment] - [Settings of the Components of the Agents to Be Deployed] in the Settings window.

KDEX3358-I

Detection conditions for device maintenance is updated. (detection condition name=detection condition name, setting_ID=setting ID, update_type=update type)

KDEX3359-E

Detection conditions for device maintenance could not be updated. (detection condition name=detection condition name, setting_ID=setting ID, update_type=update type)

KDEX3362-I

The settings for the [Assets] - [Asset Status Settings of Hardware Assets Associated with Deleted Devices] in the Settings window were changed.

KDEX3363-E

Failed to change the settings for the [Assets] - [Asset Status Settings of Hardware Assets Associated with Deleted Devices] in the Settings window.

KDEX3369-I

Logon succeeded. JP1 user name=JP1-user-name.

KDEX3370-I

Logoff successful JP1 user name=JP1-user-name

KDEX3371-E

Failed to log in. The specified JP1 user name or Password is invalid. JP1 user name=JP1-user-name.

[Cause] The specified JP1 user name or Password is invalid.

[Action] Cancel login.

[Workaround] Log in using a valid JP1 user name and Password.

KDEX3372-E

Logon failed. JP1 user name=JP1-user-name (or null if not obtainable), cause message=cause-message

[Cause] Database error or Expiration of Usage period.

[Action] Cancel Logon.

[Workaround] For expiration of usage period, purchase a license. For other reasons, collect troubleshooting information from troubleshooting collection information command and contact support service.

KDEX3374-I

The email notification destination was registered. (email address=email-address)

KDEX3375-I

The email notification destination was removed. (email address=email-address)

KDEX3377-I

The authentication information for logging in to Remote Install Manager or Packager was successfully obtained. JP1 user name=JP1-user-name

KDEX3378-E

Failed to obtain the authentication information required for logging in to Remote Install Manager or Packager. The specified JP1 user name or Password is invalid. JP1 user name=JP1-user-name.

[Cause] The specified User ID or Password is invalid.

[Action] Cancel login.

[Workaround] Log in using a valid JP1 user name and Password.

KDEX3379-E

Failed to obtain the authentication information required for logging in to Remote Install Manager or Packager. JP1 user name=JP1-user-name (or null if not obtainable), cause message=cause-message

[Cause] Database error or Expiration of Usage period.

[Action] Cancel Logon.

[Workaround] For expiration of usage period, purchase a product license. For other reasons, collect troubleshooting information from troubleshooting collection information command and contact support service.

KDEX3381-E

Authentication of the network control command failed. The specified user ID or password is incorrect. User ID = user-ID

Reason: The specified user ID or password is incorrect.

System processing: Stops execution of the network control command.

Corrective measure: Execute the network control command with the correct user ID and password specified.

KDEX3382-E

Authentication of the network control command failed. User ID = user-ID, cause message = cause-message

Reason: The product license has expired, or an error occurred in the database.

System processing: Stops execution of the network control command.

Corrective measure: If the product license has expired, purchase another product license and authenticate the license. If the product license has not expired, execute the command to obtain troubleshooting information, and then contact the customer support center.

KDEX3383-E

Authentication of the network control command failed. The user account is locked. User ID = user-ID

Reason: The user account is locked.

System processing: Stops execution of the network control command.

Corrective measure: Unlock the user account.

KDEX3384-I

Authentication of the network control command was successful. JP1 user name = JP1-user-name

KDEX3385-E

Authentication of the network control command failed. The specified user ID or password is incorrect. JP1 user name = JP1-user-name

Reason: The specified JP1 user name or password is incorrect.

System processing: Stops execution of the network control command.

Corrective measure: Use a valid JP1 user name and password to execute the network control command.

KDEX3386-E

Authentication of the network control command failed. JP1 user name = JP1-user-name, cause message = cause-message

Reason: The product license is expired, or an error occurred in the database.

System processing: Stops execution of the network control command.

Corrective measure: If the product license is expired, purchase another product license and authenticate the license. If the product license is not expired, execute the command to obtain troubleshooting information, and then contact the customer support center.

KDEX3389-I

Authentication of the network control command was successful. User ID = user-ID

KDEX3390-I

The settings for the [Security] - [Security Judgment Settings for Update Programs] in the Settings window were changed.

KDEX3391-E

Failed to change the settings for the [Security] - [Security Judgment Settings for Update Programs] in the Settings window.

KDEX3392-I

Authentication of the API user account was successful. User ID = user-ID

KDEX3394-I

Authentication of the API user account was successful. JP1 user name = JP1-user-name

KDEX3396-E

Authentication of the API user account has failed. The specified user ID or password is incorrect. User ID = user-ID

Reason: The specified user ID or password is incorrect.

System processing: API execution is stopped.

Corrective measure: Execute the operation using the correct user ID and password.

KDEX3397-E

Authentication of the API user account has failed. The specified JP1 user name or password is incorrect. JP1 user name = JP1-user-name

Reason: The specified JP1 user name or password is incorrect.

System processing: API execution is stopped.

Corrective measure: Execute the operation using the correct JP1 user name and password.

KDEX3398-E

Authentication of the API user account has failed. User ID = user-ID, Cause message = cause-message

Reason: The license for this product has not been authenticated (registration).

System processing: API execution is stopped.

Corrective measure: Authenticate (register) the license for this product.

KDEX3399-E

Authentication of the API user account has failed. JP1 user name = JP1-user-name, Cause message = cause-message

Reason: The license for this product has not been authenticated (registration).

System processing: API execution is stopped.

Corrective measure: Authenticate (register) the license for this product.

KDEX3400-E

Authentication of the API user account has failed. The user account is locked. User ID = user-ID

Reason: The user account is locked.

System processing: API execution is stopped.

Corrective measure: Unlock the user account.

KDEX4000-E

Failed to execute the command. The specified arguments are invalid. Command name=command-name.

[Cause] The specified arguments are invalid.

[Action] Cancel command execution.

[Workaround] Confirm the command arguments, and retry execution.

KDEX4001-E

Failed to execute the command. You do not have the required permissions. Command name=command-name.

[Cause] The command was executed by a user without Administrator privileges.

[Action] Cancel command execution.

[Workaround] Retry executing the command as a user with Administrator privileges.

KDEX4002-E

Failed to execute the command. An executing process (Setup, Database Manager, or a command) might be running. Command name=command-name

[Cause] The command was executed when either Setup, Database Manager, or a command was running.

[Action] Cancel command execution.

[Workaround] Wait until the executing process (Setup, Database Manager, or a command) ends, and then retry command execution.

KDEX4003-E

Failed to execute the command. Setup has not completed. Command name=command-name

[Cause] The JP1/IT Desktop Management 2 - Manager Setup has not completed.

[Action] Cancel command execution.

[Workaround] Retry executing the command, after JP1/IT Desktop Management 2 - Manager Setup.

KDEX4009-E

Failed to execute the command. Command name=command-name, Error code=error-code (maintenance-code).

[Cause] A critical error has occurred while executing the command.

[Action] Cancel command execution.

[Workaround] Use the troubleshooting information collection command to collect troubleshooting information and contact support service.

KDEX4010-E

Failed to execute the command. Cannot execute in a cluster environment. Command name=command-name.

[Cause] The start / stop command was executed in a cluster environment.

[Action] Cancel command execution.

[Workaround] Use the cluster software utility to start/stop JP1/IT Desktop Management 2 - Manager.

KDEX4011-I

JP1/IT Desktop Management 2 - Manager is stopped. Command name=command-name.

KDEX4012-I

JP1/IT Desktop Management 2 - Manager is forced to stop. Command name=command-name.

KDEX4013-E

Failed to execute the command. Command name=command-name, Error code=error-code (maintenance-code).

[Cause] A critical error occurred during command execution.

[Action] Cancel command execution.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX4014-W

JP1/IT Desktop Management 2 - Manager is stopped. Command name=command-name.

[Cause] Executed stop command (when JP1/IT Desktop Management 2 - Manager was stopped).

[Action] Cancel stop command execution.

[Workaround] None.

KDEX4015-I

JP1/IT Desktop Management 2 - Manager is started. Command name=command-name.

KDEX4016-E

Failed to execute the command. Command name=command-name, Error code=error-code (maintenance-code)

[Cause] A critical error occurred during command execution.

[Action] Cancel command execution.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX4017-W

JP1/IT Desktop Management 2 - Manager is started. Command name=command-name.

[Cause] Executed the start command (when JP1/IT Desktop Management 2 - Manager was launched).

[Action] Cancel command execution.

[Workaround] None.

KDEX4020-E

Command execution failed. JP1/IT Desktop Management 2 - Manager is not stopped. (command name = command-name)

[Cause] The command was executed without stopping JP1/IT Desktop Management 2 - Manager on the management server or database server.

[Action] Cancels command execution.

[Workaround] Stop JP1/IT Desktop Management 2 - Manager, and then re-execute the command.

KDEX4021-E

Failed to execute the command. Could not stop JP1/IT Desktop Management 2 - Manager. Command name=command-name, Error code=error-code (maintenance-code).

[Cause] A critical error occurred during command execution.

[Action] Cancel command execution.

[Workaround] Use the troubleshooting information collection command to collect troubleshooting information and contact support service.

KDEX4022-W

Database reorganization successful. But, an error occurred while starting JP1/IT Desktop Management 2 - Manager. Command name=command-name, Error code=error-code (maintenance-code).

[Cause] A critical error occurred during command execution.

[Action] Cancel command execution.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX4023-E

Failed to execute the command. The -s option cannot be specified in a cluster environment. (command name = command-name)

[Cause] The -s option is specified in a cluster environment.

[Action] Cancels command execution.

[Workaround] Stop JP1/IT Desktop Management 2 - Manager by using the cluster software functionality. Then, execute the command again without specifying the -s option.

KDEX4024-I

The database reorganization was successful. Command name=command-name.

KDEX4025-E

Failed to execute the command. Command name=command-name, Error code=error-code (maintenance-code).

[Cause] Failed to execute the command. The following are possible causes:

(1) You do not have permission to access the operation folder.

(2) An attempt was made to access the database from Remote Install Manager or IT Desktop Management 2 - Asset Console.

(3) An I/O error occurred.

[Action] Cancels the reconfiguration.

[Workaround] Perform the following checks, and then execute the command again.

(1) Check whether you have permission to access the operation folder.

(2) Stop Remote Install Manager, and then make sure that the commands for the distribution function that uses Remote Install Manager are not being executed. Also, make sure that management information on IT Desktop Management 2 - Asset Console is not being acquired. If there is a dbconreorg.inf file in the mgr\temp folder under the installation folder, use the IP addresses shown in the "C-ADDR" item of the dbconreorg.inf file to identify the computers that are accessing the database.

(3) Make sure that no disk failures occurred. If the problem still persists, use the troubleshooting information acquisition command to acquire troubleshooting information, and then contact Customer Support.

KDEX4026-E

Failed to execute the command. The backup folder is invalid or does not exist. Command name=command-name.

[Cause] The specified backup folder is invalid or does not exist.

[Action] Cancel command execution.

[Workaround] Check if the specified folder exists and is accessible. Then, retry command execution.

KDEX4027-E

Failed to execute the command. A backup folder with an identical timestamp already exists. Command name=command-name.

[Cause] The command could not create the backup folder since a folder with the same name (a string indicating the date and time) already exists.

[Action] Cancel command execution.

[Workaround] retry command execution.

KDEX4028-I

The database backup was successful. Command name=command-name, Backup folder=backup-folder.

KDEX4029-E

Failed to execute the command. Command name=command-name, Error code=error-code (maintenance-code).

[Cause] Failed to execute the command. The following are possible causes:

(1) You do not have permission to access the backup folder or the data folder.

(2) An attempt was made to access the database from Remote Install Manager or IT Desktop Management 2 - Asset Console.

(3) An I/O error occurred.

[Action] Cancels the backup.

[Workaround] Perform the following checks, and then execute the command again.

(1) Check whether you have permission to access the backup folder and the data folder.

(2) Stop Remote Install Manager, and then make sure that the commands for the distribution function that uses Remote Install Manager are not being executed. Also, make sure that management information on IT Desktop Management 2 - Asset Console is not being acquired. If there is a dbconbackup.inf file in the mgr\temp folder under the installation folder, use the IP addresses shown in the "C-ADDR" item of the dbconbackup.inf file to identify the computers that are accessing the database.

(3) Make sure that no disk failures occurred. If the problem still persists, use the troubleshooting information acquisition command to acquire troubleshooting information, and then contact Customer Support.

KDEX4030-E

Failed to execute the command. The data folder is either invalid or does not exist. Command name=command-name.

[Cause] The specified data folder is either invalid or does not exist.

[Action] Cancel command execution.

[Workaround] Check if the specified folder exists and is accessible. Then, try executing the command.

KDEX4031-I

The database restoration was successful. Command name=command-name, Data folder=data-folder.

KDEX4032-E

Failed to execute the command. Command name=command-name, Error code=error-code (maintenance-code).

[Cause] Failed to execute the command. The following are possible causes:

(1) You do not have permission to access the data storage folder, the operation folder, or the data folder.

(2) An attempt was made to access the database from Remote Install Manager or IT Desktop Management 2 - Asset Console.

(3) An I/O error occurred.

[Action] Cancels the execution of the command.

[Workaround] Perform the following checks, and then execute the command again:

(1) Check whether you have permission to access the data storage folder, the operation folder, and the data folder.

(2) Stop Remote Install Manager, and then make sure that the commands for the distribution function that uses Remote Install Manager are not being executed. Also, make sure that management information on IT Desktop Management 2 - Asset Console is not being acquired. If there is a dbconrestore.inf file in the mgr\temp folder under the installation folder, use the IP addresses shown in the "C-ADDR" item of the dbconrestore.inf file to identify the computers that are accessing the database.

(3) Make sure that no disk failures occurred. If the problem still persists, use the troubleshooting information acquisition command to acquire troubleshooting information, and then contact Customer Support.

KDEX4033-E

Failed to execute the command. Insufficient disk space for the backup folder. Command name=command-name.

[Cause] Insufficient disk space for the backup folder.

[Action] Cancel command execution.

[Workaround] Free the disk space, and then try executing the command.

KDEX4034-E

Failed to execute the command. Insufficient disk space for the temporary folder. Command name=command-name.

[Cause] Insufficient disk space for the temporary folder.

[Action] Cancel command execution.

[Workaround] Free the disk space, and then try executing the command.

KDEX4035-E

Failed to execute the command. The temporary folder is either invalid or does not exist. Command name=command-name.

[Cause] The specified temporary folder is either invalid or does not exist.

[Action] Cancel command execution.

[Workaround] Check if the temporary folder exists and is accessible. Then, try executing the command.

KDEX4036-E

Failed to execute the command. Could not start the database. Command name =command-name .

[Cause] Insufficient disk space to start the database.

[Action] Cancel command execution.

[Workaround] Free the space on the disk where you have the installation folder, and retry command execution. If the problem persists, Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX4037-E

The database reorganization failed. Command name=command-name, Error code=error-code (maintenance-code).

KDEX4038-E

The database backup failed. Command name=command-name, Error code=error-code (maintenance-code).

KDEX4039-E

The database restoration failed. Command name=command-name, Error code=error-code (maintenance-code).

KDEX4040-I

Collected the troubleshooting information.

KDEX4041-E

Could not collect troubleshooting information.

[Cause] Insufficient disk space for the troubleshooting information folder.

[Action] Cancel command execution.

[Workaround] Free the disk space, and retry command execution. If the problem persists, contact Customer Support.

KDEX4042-I

Canceled the troubleshooting information collection.

KDEX4043-W

Could not collect some troubleshooting information.

[Cause] Failed to collect some of the troubleshooting information.

[Action] Cancel command execution.

[Workaround] Retain the partially collected troubleshooting information file, and retry command execution. If the problem persists, contact Customer Support with the retained troubleshooting information.

KDEX4044-E

The troubleshooting information folder is either invalid or does not exist.

[Cause] The specified troubleshooting information folder is either invalid or does not exist.

[Action] Cancel command execution.

[Workaround] Check if the specified folder exists and is accessible. Then, retry command execution.

KDEX4050-E

Failed to execute the command. Could not use the default backup folder. Command name=command-name

[Cause] The installation folder name contains characters that cannot be used in the backup folder name.

[Action] Cancel command execution.

[Workaround] Retry executing the command with option -b.

KDEX4051-E

Failed to execute the command. Could not use the default data folder and temporary folder. Command name=command-name.

[Cause] The installation folder name contains characters that cannot be used in the data folder name and temporary folder name.

[Action] Cancel command execution.

[Workaround] Retry executing the command with option -b and option -w.

KDEX4052-E

Failed to execute the command. Could not use the default temporary folder. Command name=command-name.

[Cause] The installation folder name contains invalid characters that cannot be used as temporary folder name.

[Action] Cancel command execution.

[Workaround] Retry executing the command with option -w.

KDEX4053-W

The database backup was successful. But, an error occurred while starting JP1/IT Desktop Management 2 - Manager. Command name=command-name, Error code=error-code (maintenance-code), Backup folder=backup-folder.

[Cause] A critical error occurred during command execution.

[Action] Cancel command execution.

[Workaround] Start JP1/IT Desktop Management 2 - Manager using the start command. If the problem persists, Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX4054-W

The database restoration was successful. But, an error occurred while starting JP1/IT Desktop Management 2 - Manager. Command name=command-name, Error code=error-code (maintenance-code), Data folder=data-folder.

[Cause] A critical error occurred during command execution.

[Action] Cancel command execution.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX4055-E

Failed to execute the command. Command name=command-name, Data folder=data-folder.

[Cause] The specified data folder does not contain backup files.

[Action] Cancel command execution.

[Workaround] Confirm that the specified folder is correct. Then, retry command execution.

KDEX4056-E

Failed to execute the command. The temporary folder is either invalid or does not exist. Command name=command-name.

[Cause] The specified temporary folder is either invalid or does not exist.

[Action] Cancel command execution.

[Workaround] Check if the specified folder exists and is accessible. Then, retry command execution.

KDEX4057-E

Failed to execute the command. Insufficient disk space for the temporary folder. Command name=command-name.

[Cause] Insufficient disk space for the temporary folder.

[Action] Cancel command execution.

[Workaround] Free the disk space, and retry command execution.

KDEX4058-E

Failed to execute the command. The old version couldn't be backed up. Command name=command-name, Backup folder=backup-folder.

[Cause] The specified backup was obtained from a version older than the current version.

[Action] Cancel command execution.

[Workaround] Backup the current version and retry command execution.

KDEX4061-E

Failed to execute the command. Could not establish connection to access operation logs for backup destination folder. Command name=command-name

[Cause] The backup destination folder does not exist. Or could not establish connection to the backup destination folder.

[Action] Cancel command execution.

[Workaround] Check if the backup destination folder (specified for operation logs during the Setup) exists, and then reestablish the connection.

KDEX4062-E

Failed to execute the command. Could not establish connection to access operation logs for backup destination folder. Command name=command-name

[Cause] The User name or Password authentication for the backup destination folder has failed.

[Action] Cancel command execution.

[Workaround] Check the Username or Password that was specified during the Setup.

KDEX4063-E

Failed to execute the command. Command name=command-name

[Cause] Insufficient backup space for the local data folder or the operation logs.

[Action] Cancel command execution.

[Workaround] Change the backup destination for the local data folder or the operation logs. Or, free hard disk space.

KDEX4064-E

Failed to execute the command. The operation logs backup has failed. Command name=command-name

[Cause] A critical error occurred during command execution.

[Action] Cancel command execution.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX4065-E

Failed to execute the command. Could not start [JP1/IT Desktop Management 2 - Manager]. Command name =command-name

[Cause] The possible reasons are given below:

(1) The license is not registered.

(2) The license has expired.

(3) The license information is invalid.

[Action] Cancel command execution.

[Workaround]

(1) Register a valid license.

(2) Purchase a valid license.

(3) Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX4070-E

Failed to execute the command. Command name=command-name.

[Cause] The specified support information file is either invalid or does not exist.

[Action] Cancel command execution.

[Workaround] Check if the specified file exists and is correct. Then, retry command execution.

KDEX4071-E

Failed to execute the command. Command name=command-name.

[Cause] Executed the command without starting JP1/IT Desktop Management 2 - Manager.

[Action] Cancel command execution.

[Workaround] Start JP1/IT Desktop Management 2 - Manager, then retry command execution.

KDEX4072-E

Failed to execute the command. Failed to update all or part of information for JP1/IT Desktop Management 2 - Manager. Command name=command-name, Not updated information=information-that-could-not-be-updated (Windows updates, antivirus software, definition files for Manager behavior, Agent)

[Cause] The possible reasons are given below:

(1) An update for another function is running.

(2) Insufficient space in the installation folder or the database folder.

(3) Improper access privileges to the installation folder or the database folder.

(4) An I/O error has occurred.

[Action] Cancel command execution.

[Workaround]

(1) Retry command execution after a while.

(2) Free the disk space.

(3) Confirm the access rights.

(4) Confirm that a disk failure has not occurred.

KDEX4073-I

Updated JP1/IT Desktop Management 2 - Manager.

Command name=command-name

KDEX4080-E

Failed to execute the command. The file path is invalid. Command name=command-name, Subcommand name=subcommand-name, File path=file-path.

[Cause] The possible reasons are:

(1) The folder in the specified path does not exist, or the specified file path is incorrect.

(2) The specified path exceeds the maximum path length.

(3) You do not have file access permission for the specified file.

(4) Insufficient disk space for the specified file.

(5) An I/O error occurred.

[Action] Cancel command execution.

[Workaround]

(1) Make sure the folder in the specified path exists and the specified path is correct.

(2) Check the path length.

(3) Make sure you have file access permission.

(4) Free the disk space for the specified file or specify another file which has sufficient space.

(5) Confirm that a disk failure has not occurred.

After these are confirmed, retry command execution.

KDEX4081-E

Failed to execute the command. The patch group is invalid. Command name=command-name, Subcommand name=subcommand-name, Update group name=update-group-name.

[Cause] The specified update group is does not exist.

[Action] Cancel command execution.

[Workaround] Make sure the specified update group exists and retry command execution.

KDEX4082-E

Failed to execute the command. The filter cannot be used. Command name=command-name, Subcommand name=subcommand-name.

[Cause] The specified filter is invalid or does not exist.

[Action] Cancel command execution.

[Workaround] Make sure the specified filter exists and the type of the filter is correct. Then, retry command execution.

KDEX4083-E

Failed to execute the command. Database access error occurred. Detailed information=DBMS-message, Command name =command-name, Subcommand name=subcommand-name.

[Cause] JP1/IT Desktop Management 2 - Manager stopped or the displayed error occurred.

[Action] Cancel command execution.

[Workaround] Start JP1/IT Desktop Management 2 - Manager or resolve the displayed error and retry command execution. If the problem persists, execute troubleshooting information collection command to collect troubleshooting information and contact customer support.

KDEX4084-E

Failed to execute the command. Cannot export. Command name=command-name, Subcommand name=subcommand-name.

[Cause] The possible reasons are:

(1) Insufficient disk space for the export folder.

(2) You do not have file access permission for the specified export file.

(3) An I/O error occurred.

[Action] Cancel command execution.

[Workaround]

(1) Free the disk space for the export folder or specify another file which has sufficient space.

(2) Make sure you have file access permission for the specified export file.

(3) Confirm that a disk failure has not occurred.

After these are confirmed, retry command execution.

KDEX4085-I

expanded-inventory-name export successful.

Management Item Name = One of the following is displayed.

- Asset

- Custom field

- Template

- Filter

- Security policy

- Operations log

- Update group

- Devices

- Devices (details)

- Common management fields and additional management fields

- Windows Update

- Asset association information

Command name=command-name, Subcommand name=subcommand-name.

KDEX4086-E

Failed to execute the command. Command name=command-name, Subcommand name=subcommand-name, Error code=error-code (maintenance-code).

[Cause] Insufficient memory for the command execution environment. Or a critical error occurred during command execution.

[Action] Cancel command execution.

[Workaround] Make sure there is sufficient memory for the command execution environment, and retry command execution. If the problem persists, use the troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX4087-I

Export or Import is canceled. Command name=command-name, Subcommand name=subcommand-name.

KDEX4088-E

Failed to execute the command. Cannot use the template. Command name=command-name, Subcommand name=subcommand-name.

[Cause] The specified template is invalid or does not exist.

[Action] Cancel command execution.

[Workaround] Make sure the specified template exists and the type of the template is correct. Then, retry command execution.

KDEX4089-E

Failed to execute the command. Cannot import the specified file. Command name=command-name, Subcommand name=subcommand-name.

[Cause] Invalid file format.

[Action] Cancel command execution.

[Workaround] Make sure the specified import file is correct and retry command execution.

KDEX4090-E

Failed to execute the command. Cannot import the specified file. Command name=command-name, Subcommand name=subcommand-name.

[Cause] The template and specified import file do not match.

[Action] Cancel command execution.

[Workaround] Make sure the specified import file is correct and retry command execution.

KDEX4091-I

Successfully imported the asset. Type of asset=asset-type, add=number-of-information-items, update=number-of-information-items, error=number-of-information-items.

Type of asset = One of the following is displayed.

- Hardware asset information

- Software license information

- Managed software information

- Contract information

- Contract vendor list

KDEX4092-I

expanded-inventory-name import successful.

Management Item Name = One of the following is displayed.

- Custom field

- Template

- Filter

- Security policy

- Update group

- Common management fields and additional management fields

- Windows Update

- External log

Command name=command-name, Subcommand name=subcommand-name.

KDEX4093-E

Failed to execute the command. The specified template name is invalid. Command name=command-name, Subcommand name=subcommand-name.

[Cause]The specified template name has an invalid character.

[Action] Cancel command execution.

[Workaround] Make sure the specified template name is correct and retry command execution.

KDEX4094-E

Failed to execute the command. Cannot use the Security Policy. Command name=command-name, Subcommand name=subcommand-name.

[Cause] The specified security policy does not exist.

[Action] Cancel command execution.

[Workaround] Make sure the specified security policy exists and retry command execution.

KDEX4095-E

Failed to execute the command. The specified security policy name is invalid. Command name=command-name, Subcommand name=subcommand-name.

[Cause] The specified security policy name has an invalid character.

[Action] Cancel command execution.

[Workaround] Make sure the specified security policy name is correct and retry command execution.

KDEX4096-E

Failed to execute the command. The specified filter name is invalid. Command name=command-name, Subcommand name=subcommand-name.

[Cause] The filter name length is invalid or the filter name has an invalid character.

[Action] Cancel command execution.

[Workaround] Make sure the specified filter name is correct and retry command execution.

KDEX4097-E

Failed to execute the command. The specified update group name is invalid. Command name=command-name, Subcommand name=subcommand-name.

[Cause] The specified update group name has an invalid character.

[Action] Cancel command execution.

[Workaround] Make sure the specified update group name is correct and retry command execution.

KDEX4098-E

Failed to execute the command. Cannot import the specified file. Command name=command-name, Subcommand name=subcommand-name.

[Cause] The additional custom fields in the import file doesn't exist.

[Action] Cancel command execution.

[Workaround] Make sure you specify the additional custom fields and retry command execution.

KDEX4099-W

Although the command ended successfully, there are some updates that cannot be assigned to the update group. Command name=command-name, Subcommand name=subcommand-name.

[Cause] The update information does not exist.

[Action] Ends the command successfully.

[Workaround] Subscribe to the support service, update the update information to its latest state, and then re-execute the command. If you have imported a manually registered update to an update group, import the update, and then re-execute the command.

KDEX4100-E

The export of expanded-inventory-name failed.

Management Item Name = One of the following is displayed.

- Asset

- Custom field

- Template

- Filter

- Security policy

- Operations log

- Update group

- Devices

- Devices (details)

- Common management fields and additional management fields

- Windows Update

- Asset association information

Command name=command-name, Subcommand name=subcommand-name.

KDEX4101-E

The import of expanded-inventory-name failed.

Management Item Name = One of the following is displayed.

- Asset

- Custom field

- Template

- Filter

- Security policy

- Update group

- Common management fields and additional management fields

- Windows Update

- Asset association information

- External log

Command name=command-name, Subcommand name=subcommand-name.

KDEX4102-E

Failed to execute the command. Cannot export the specified security policy. Command name=command-name, Subcommand name=subcommand-name.

[Cause] This security policy is part of mandatory (auto-enforce) software installation package.

[Action] Cancel command execution.

[Workaround]Delete this security policy from auto-enforce settings and retry executing the command.

KDEX4103-E

Failed to execute the command. Cannot export the specified filter. Command name=command-name, Subcommand name=subcommand-name.

[Cause] Following might be the possible causes:

(1) The specified user definition already exists in the filter.

(2) The specified location or department already exists in the filter.

[Action] Cancel command execution.

[Workaround]

(1) Make sure this user definition already exists in the filter, delete this definition and retry command execution.

(2) Make sure this department or location already exists in the filter and delete the specified location or department and retry executing the command.

KDEX4104-E

Failed to execute the command. JP1/IT Desktop Management 2 - Manager cannot be started or stopped. Command name =command-name

[Cause] A command was executed during processing to start or stop JP1/IT Desktop Management 2 - Manager.

[Action] Cancel command execution.

[Workaround] Retry command execution after a while.

KDEX4105-E

Failed to execute the command. Could not stop JP1/IT Desktop Management 2 - Manager. Command name =command-name

[Cause] A command was executed during processing to start JP1/IT Desktop Management 2 - Manager.

[Action] Cancel command execution.

[Workaround] Retry command execution after a while.

KDEX4106-E

Failed to execute the command. Could not start the database. Command name =command-name

[Cause] A command was executed during processing to stop the database.

[Action] Cancel command execution.

[Workaround] Retry command execution after a while.

KDEX4120-I

Deletion of the product license ended normally. (command name = command-name)

KDEX4121-I

The product license was not found or has already been deleted. (command name = command-name)

KDEX4122-E

Command execution failed. JP1/IT Desktop Management 2 - Manager has not stopped. (command name = command-name)

[Cause] JP1/IT Desktop Management 2 - Manager has not stopped.

[Action] Cancels command execution.

[Workaround] Stop JP1/IT Desktop Management 2 - Manager, and then retry command execution.

KDEX4123-E

Command execution failed. The product license cannot be deleted. (command name = command-name)

[Cause] You do not have the necessary administrator access rights for the database folder or files and folders in the local data folder.

[Action] Cancels command execution.

[Workaround] Verify your access rights for the database folder or files and folders in the local data folder, and then retry command execution.

KDEX4124-E

Failed to delete the product license. (command name = command-name)

KDEX4125-I

A network segment in which no device exists has been deleted from the device list (network). (command name = command-name)

KDEX4126-W

Custom fields was imported normally, but some services have not started. (command name = command-name, subcommand name = subcommand-name)

[Cause] Some services have not started.

[Action] Ends the command normally.

[Workaround] Check whether all services have started. If they have not, start the services.

KDEX4127-E

Execution of the command failed. The settings or the environment is incorrect. (command name = command-name, subcommand name = subcommand-name)

[Cause] Possible causes include the following:

(1) The setting to acquire the operations log, in the settings for the setup operations log, is disabled.

(2) The command cannot access the folder storing the operations log.

[Action] Execution of the command stops.

[Workaround] Take the following actions, as appropriate, and then re-execute the command:

(1) In the settings for the setup operation log, enable the setting to acquire the operations log.

(2) Make sure the command can access the folder storing the operations log.

Important:

When the HibunLogImport value in the configuration file for the external log import command is 0, change the value to 1.

KDEX4128-I

The file was imported. (file name = import-file-name)

KDEX4129-W

The import processing was skipped because the file types are different. (file name = import-file-name)

[Cause] An attempt was made to import a log file of a different type.

[Action] The file was skipped, and importing continues.

[Workaround] Make sure the file to be imported matches the type of log specified in the command argument, and then import it again.

KDEX4130-W

The invalid rows were skipped. (file name = import-file-name, line number = line-number)

[Cause] A line has an invalid format.

[Action] The line with the invalid format is skipped, and importing continues.

[Workaround] Remake the file to be imported, and then import it again.

KDEX4131-E

An error occurred in the command ioutils importexlog.

[Cause] An error occurred in the command ioutils importexlog.

[Action] Execution of the command stops.

[Workaround] Check the error message displayed for the preceding command ioutils importexlog.

KKDEX4132-W

Part of the log import processing by the command ioutils importexlog was skipped.

[Cause] The file to be imported contains invalid data.

[Action] Execution of the command continues.

[Workaround] Check the message output to the standard output of the command ioutils importexlog.

KDEX4133-E

Command execution failed. External log files could not be saved to the operation logs folder or to the data folder. (command name = command-name, subcommand name = subcommand-name)

[Cause] Possible causes include the following:

(1) The folder storing the operations log or the data folder does not have sufficient free space.

(2) You do not have permission to access the operation logs folder or the data folder.

(3) An input/output error occurred when the operation logs folder or the data folder was accessed.

[Action] Cancels the execution of the command.

[Workaround] Perform the appropriate steps below (the numbers below correspond to the numbers above), and then retry the command.

(1) Increase the free space on the hard disk that contains The folder storing the operations log or the data folder.

(2) Make sure you have permission to access The folder storing the operations log or the data folder.

(3) Check whether a disk failure occurred in the hard disk that contains The folder storing the operations log or the data folder. If a disk failure has occurred, recover the disk.

KDEX4134-I

Deletion of packages ended normally. (command name = command-name)

KDEX4200-E

Setup is not complete.

[Cause] Since the setup is not complete, could not start the database manager.

[Action] Cancel launching the Database Manager.

[Workaround] Retry starting the Database Manager after Setup ends.

KDEX4202-E

Database Manager can be started only from the database server.

[Cause] An attempt was made to start Database Manager on a server other than the database server.

[Action] Cancels startup of Database Manager.

[Workaround] Start Database Manager from the database server.

KDEX4203-E

Could not start Database Manager.

[Cause] Could not start the Database Manager due to an unknown error.

[Action] Cancel launching the Database Manager.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX4204-E

Please start (JP1_ITDM2_DB Service).

[Cause] The (JP1_ITDM2_DB Service) was stopped, so could not start the Database Manager.

[Action] Cancel launching the Database Manager.

[Workaround] Retry launching the Database Manager after starting (JP1_ITDM2_DB Service).

KDEX4205-E

The user does not have Administrator privileges.

[Cause] The user does not have Administrator privileges.

[Action] Cancel launching the Database Manager.

[Workaround] Retry launching the Database Manager as a user with Administrator privileges.

KDEX4206-E

Could not start the Database Manager because either Setup or a command is running.

[Cause] Started the Database Manager while either Setup or a command was executing.

[Action] Cancel launching Database Manager.

[Workaround] Wait until the executing process (Setup or command) ends, and then retry launching the Database Manager.

KDEX4207-E

The Database Manager has already started.

[Cause] The Database Manager was already started.

[Action] Cancel launching the Database Manager.

[Workaround] Continue operation with the Database Manager started already.

KDEX4208-E

An error occurred in the Database Manager.

[Cause] An error occurred in the Database Manager.

[Action] Cancel the execution of Database Manager.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX4210-Q

If you are using Remote Install Manager or IT Desktop Management 2 - Asset Console, perform the checks below. If you continuously use Remote Install Manager or IT Desktop Management 2 - Asset Console without performing the checks, the processing might not successfully complete.

- Stop Remote Install Manager, and then make sure that the commands for the distribution function that uses Remote Install Manager are not being executed.

- Make sure that management information on IT Desktop Management 2 - Asset Console is not being acquired.

To continue operation, JP1/IT Desktop Management 2 - Manager service must be stopped. Would you like to stop the service?

The service will automatically start when the process ends.

KDEX4211-Q

If you are using Remote Install Manager or IT Desktop Management 2 - Asset Console, perform the checks below. If you continuously use Remote Install Manager or IT Desktop Management 2 - Asset Console without performing the checks, the processing might not successfully complete.

- Stop Remote Install Manager, and then make sure that the commands for the distribution function that uses Remote Install Manager are not being executed.

- Make sure that management information on IT Desktop Management 2 - Asset Console is not being acquired.

Take the cluster resources that are associated with the service below offline. After taking the cluster resources offline, click [OK] to continue the operation.

When the processing is complete, bring the cluster resources online.

service-name

KDEX4212-E

Database is in maintenance, so cannot continue the process.

[Cause] Could not continue the process since the database is in maintenance.

[Action] Cancel the execution of Database Manager.

[Workaround] Retry execution after database maintenance ends.

KDEX4213-E

Cannot use the folder path specified for folder-specified-by-Database-Manager.

A file with a same name as the specified folder already exists in the given path.

[Cause] A file with the same name as the specified folder already exists in the given path.

[Action] Cancel the execution.

[Workaround] To resume execution, either change or delete the duplicate filename, or specify an alternate folder path.

KDEX4214-E

Failed to acquire server ID authentication. Authentication server ID file is invalid.

[Cause] Invalid file for server ID authentication.

[Action] Cancel Database Manager execution.

[Workaround] Make sure the authentication server ID file is valid and restart Database Manager.

KDEX4215-Q

From the management server, stop the service given below. If you continue while this service is running, processing might not finish properly.

(service = service-name-of-management-server)

The database server service will stop automatically. The database server service that is stopped in this way will start automatically after processing is complete.

Are you sure you want to stop the database server service?

KDEX4216-Q

From the management server, stop the service given below. If you continue while this service is running, processing might not finish properly.

(service = service-name-of-management-server)

Take offline the cluster resources associated with the service given below. After doing so, click OK to continue processing. After processing is complete, bring the cluster resources back online.

(service = service-name-of-database-server)

KDEX4220-E

Failed to start the database.

[Cause] Failed to start the database. Possible causes are as follows:

(1) The disk containing the installation folder does not have enough free space to start the database (required space = required-space MB).

(2) (JP1_ITDM2_DB Service) has stopped.

[Action] Cancels database startup.

[Workaround]

(1) Free the disk space in the installation folder, and restart the service (JP1_ITDM2_DB Service).

(2) Start (JP1_ITDM2_DB Service).

If the problem persists, collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX4221-E

A database failure occurred.

[Cause] A database failure occurred because there was not enough hard disk space for a database extension.

[Action] Cancels database extension.

[Workaround] Use Setup to re-create the database. If a backup of the database exists, after re-creating the database, restore the backup by using Database Manager.

KDEX4230-E

Could not start the service. Service name=service-name.

[Cause] An error occurred while starting the service.

[Action] Cancel the service.

[Workaround] Check the message logs and take action based on the errors in the logs.

KDEX4231-E

Could not stop the service. Service name=service-name.

[Cause] An error occurred while stopping the service.

[Action] Cancel the service.

[Workaround] Check the message logs and take action based on the errors in the logs.

KDEX4232-E

An attempt to stop the service failed.

[Cause] Processing was executed during processing to start or stop the service used by JP1/IT Desktop Management 2 - Manager.

[Action] Cancel the execution of Database Manager.

[Workaround] Wait a while, and then retry the operation.

KDEX4233-E

Database backup, restoration, or reorganization processing failed.

[Cause] The database is being accessed from the management server.

[Action] Cancels database backup, restoration, or reorganization processing.

[Workaround] From the management server, stop the service given below, and then retry the database backup, restoration, or reorganization.

(service = service-name-of-management-server)

KDEX4270-I

The database is backed up.

KDEX4271-E

An error occurred while backing up the database. Backup has been canceled.

[Cause] Backup failed due to the following possible reasons:

(1) Improper access privileges for the backup folder or data folder.

(2) An attempt was made to access the database from Remote Install Manager or IT Desktop Management 2 - Asset Console.

(3) An I/O error occurred.

[Action] Cancel backup.

[Workaround] Perform the following checks, and then perform the backup again.

(1) Confirm the access rights of the backup folder and data folder.

(2) Stop Remote Install Manager, and then make sure that the commands for the distribution function that uses Remote Install Manager are not being executed. Also, make sure that management information on IT Desktop Management 2 - Asset Console is not being acquired. If there is a dbconbackup.inf file in the mgr\temp folder under the installation folder, use the IP addresses shown in the "C-ADDR" item of the dbconbackup.inf file to identify the computers that are accessing the database.

(3) Make sure that no disk failures occurred.

If the problem persists, Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX4272-E

The backup folder is not specified.

[Cause] The backup folder is not specified.

[Action] Cancel backup.

[Workaround] Specify a backup folder, and then retry backup .

KDEX4273-E

The backup folder path contains invalid characters. Valid characters are alphanumeric, #, @, \, period(.), space, and round brackets ().

[Cause] The backup folder path contains invalid characters.

[Action] Cancel backup.

[Workaround] Specify a valid backup folder path, and then retry backup.

KDEX4275-Q

The specified backup folder already exists.

To overwrite the existing backup folder, click OK.

KDEX4276-E

Backup failed.

[Cause] The backup folder is either on a non-local disk or the path is invalid.

[Action] Cancel backup.

[Workaround] Specify a backup folder on a local disk, and then retry backup.

KDEX4277-E

An error occurred during database backup. Canceled backup. The disk space may be insufficient for the backup folder.

[Cause] Insufficient disk space for the backup folder.

[Action] Cancel backup.

[Workaround] Free the disk space or specify another backup folder, and then retry backup.

KDEX4278-E

The backup folder path should not exceed number-of-bytes bytes.

[Cause] The backup folder path exceeds the maximum path length.

[Action] Cancel backup.

[Workaround] Check the path length, and then retry backup.

KDEX4280-I

Restored the database.

KDEX4281-E

An error occurred while restoring the database. Restoration is canceled.

[Cause] Restore failed due to the following possible reasons:

(1) Improper access privileges for the temporary or the data folder.

(2) An attempt was made to access the database from Remote Install Manager or IT Desktop Management 2 - Asset Console.

(3) An I/O error occurred.

[Action] Cancel restoration.

[Workaround] Perform the following checks, and then perform the restoration again.

(1) Confirm the access rights of the temporary and data folders.

(2) Stop Remote Install Manager, and then make sure that the commands for the distribution function that uses Remote Install Manager are not being executed. Also, make sure that management information on IT Desktop Management 2 - Asset Console is not being acquired. If there is a dbconrestore.inf file in the mgr\temp folder under the installation folder, use the IP addresses shown in the "C-ADDR" item of the dbconrestore.inf file to identify the computers that are accessing the database.

(3) Make sure that no disk failures occurred.

If the problem persists, Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX4282-E

The data folder (folder-path-specified-by-user) does not exist. Please check the data folder.

[Cause] The data folder does not exist.

[Action] Cancel restoration.

[Workaround] Specify a valid data folder, and then retry restoration.

KDEX4283-E

The data folder is not specified.

[Cause] The data folder was not specified.

[Action] Cancel restoration.

[Workaround] Specify a data folder, and then retry restoration.

KDEX4284-E

The data folder path contains invalid characters. Valid characters are alphanumeric, #, @, \, period(.), space, and round brackets ().

[Cause] The data folder path contains invalid characters.

[Action] Cancel restoration.

[Workaround] Specify a valid data folder path, and then retry restoration.

KDEX4285-E

The data folder does not contain the required files for restoration.

[Cause] The data folder does not contain the required files.

[Action] Cancel restoration.

[Workaround] Specify a valid data folder, and then retry restoration.

KDEX4286-E

An error occurred while restoring the database. Restoration is canceled. The disk space may be insufficient for the temporary folder.

[Cause] Insufficient disk space for the temporary folder.

[Action] Cancel restoration.

[Workaround] Free the disk space or specify another temporary folder, and then retry restoration.

KDEX4287-E

Failed to restore the backup of an older version. Folder=specified-folder-path

[Cause] An older version was backed up than the current version.

[Action] Cancel restoration.

[Workaround] Backup the current version.

KDEX4288-E

Restoration failed.

[Cause] The data folder is either on a non-local disk or the path is invalid.

[Action] Cancel restoration.

[Workaround] Specify a data folder on a local disk, and then retry restoration.

KDEX4289-E

The data folder path should not exceed number-of-bytes bytes.

[Cause] The data folder path exceeds the maximum path length.

[Action] Cancel restoration.

[Workaround] Check the path length of the data folder, and retry restoration.

KDEX4290-I

Reorganized the database.

KDEX4291-E

An error occurred while reorganizing the database. Reorganization has been canceled.

[Cause] Reorganization failed due to the following possible reasons:

(1) Insufficient privileges to access the temporary folder.

(2) An attempt was made to access the database from Remote Install Manager or IT Desktop Management 2 - Asset Console.

(3) An I/O error occurred.

[Action] Cancel reorganization.

[Workaround] Perform the following checks, and then perform the reorganization again.

(1) Confirm the access rights of the temporary folder.

(2) Stop Remote Install Manager, and then make sure that the commands for the distribution function that uses Remote Install Manager are not being executed. Also, make sure that management information on IT Desktop Management 2 - Asset Console is not being acquired. If there is a dbconreorg.inf file in the mgr\temp folder under the installation folder, use the IP addresses shown in the "C-ADDR" item of the dbconreorg.inf file to identify the computers that are accessing the database.

(3) Make sure that no disk failures occurred.

If the problem persists, Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX4292-E

The reorganization parameters are not specified.

[Cause] The reorganization parameters were not specified.

[Action] Cancel reorganization.

[Workaround] Retry executing reorganization by specifying the parameters.

KDEX4293-E

A temporary folder is not specified.

[Cause] A temporary folder was not specified.

[Action] Cancel reorganization.

[Workaround] Specify a temporary folder, and then retry reorganization.

KDEX4294-E

The temporary folder path contains invalid characters. Valid characters are alphanumeric, #, @, \, period(.), space, and round brackets ().

[Cause] The temporary folder path contains invalid characters.

[Action] Cancel reorganization.

[Workaround] Specify a valid temporary folder path, and then retry reorganization.

KDEX4295-E

Reorganization failed.

[Cause] The temporary folder is either on a non-local disk or the path is invalid.

[Action] Cancel reorganization.

[Workaround] Specify a temporary folder on a local disk, and then retry reorganization.

KDEX4296-E

An error occurred while reorganizing the database. Reorganization has being canceled. The disk space may be insufficient for the temporary folder.

[Cause] Insufficient disk space for the temporary folder.

[Action] Cancel reorganization.

[Workaround] Free the disk space or specify another temporary folder, and then retry reorganization.

KDEX4297-E

You cannot specify a temporary folder path exceeding number-of-bytes bytes.

[Cause] The temporary folder path exceeds the maximum path length.

[Action] Cancel reorganization.

[Workaround] Check the path length of the temporary folder, and retry reorganization.

KDEX4300-E

A temporary folder is not specified.

[Cause] A temporary folder was not specified.

[Action] Cancel restoration.

[Workaround] Specify a temporary folder, and then retry restoration.

KDEX4301-E

The temporary folder path contains invalid characters. Valid characters are alphanumeric, #, @, \, period(.), space, and round brackets ().

[Cause] The temporary folder path contains invalid characters.

[Action] Cancel restoration.

[Workaround] Specify a valid temporary folder path, and then retry restoration.

KDEX4302-E

You cannot specify a temporary folder path exceeding number-of-bytes bytes.

[Cause] The temporary folder path exceeds the maximum path length.

[Action] Cancel restoration.

[Workaround] Check the path length of the temporary folder, and retry restoration.

KDEX4303-E

Restoration failed.

[Cause] The temporary folder is either on a non-local disk or the path is invalid.

[Action] Cancel restoration.

[Workaround] Specify a temporary folder on a local disk, and then retry restoration.

KDEX4354-I

The database backup was successful.

KDEX4355-E

The database backup failed.

KDEX4356-I

The database restoration was successful.

KDEX4357-E

The database restoration failed.

KDEX4358-I

The database reorganization was successful.

KDEX4359-E

The database reorganization failed.

KDEX4360-E

Backup for data other than operations logs successful. But, operation logs backup failed. So the backup process will stop now.

[Cause] An internal error occurred.

[Action] Cancel backup.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX4361-E

Backup for data other than operations logs successful. But, operation logs backup failed. So the backup process will stop now.

[Cause] Insufficient space for local-data-folder or operation-log-storage-area for data backup.

[Action] Cancel operation logs backup.

[Workaround] Change operation-log-storage-area or free the disk space.

KDEX4362-E

Backup for data other than operations logs successful. But, operation logs backup failed. Could not establish the connection to the operation log backup folder. So the backup process will stop now.

[Cause] Either the operation log backup folder does not exist, Or could not establish the connection to the network drive.

[Action] Cancel operation logs backup.

[Workaround] Check if the operation log backup folder (specified for operation logs during the Setup) exists, and then reestablish the connection.

KDEX4363-E

Backup for data other than operations logs successful. But, operation logs backup failed. Could not establish the connection to the operation log backup folder. So the backup process will stop now.

[Cause] The Username or Password authentication used for accessing the operation log backup folder has failed.

[Action] Cancel operation logs backup.

[Workaround] Check the Username or Password that was specified during Setup.

KDEX4364-E

Failed to restore the database. Restoration will be stopped. Insufficient disk space.

[Cause] Insufficient hard disk space for local-data-folder.

[Action] Restoration will be stopped.

[Workaround] Change local-data-folder, or increase hard disk space.

KDEX4365-E

Database restoration failed. Restoration will be stopped.

Could not establish the connection to the operation log backup folder.

[Cause] Either the operation log backup folder does not exist, Or, could not establish the connection to a network drive.

[Action] Cancel restoration.

[Workaround] Check that the operation log backup folder exists, and reestablish the connection.

KDEX4366-E

Database restoration failed. Restoration will be stopped.

Could not establish the connection to the operation log backup folder.

[Cause] The Username or Password authentication has failed for the operation log backup folder.

[Action] Cancel restoration.

[Workaround] Check the Username or Password specified during Setup.

KDEX4367-E

Automatic operation logs backup failed.

[Cause] An internal error occurred.

[Action] Cancel the operation logs backup.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX4368-E

Automatic operation logs backup failed.

An I/O error has occurred.

[Cause] Insufficient hard disk space for local-data-folder-oroperation-log-backup-folder.

[Action] Cancel the operation logs backup.

[Workaround] Change local-data-folder-oroperation-log-backup-folder, or increase hard disk space.

KDEX4369-E

Automatic operation logs backup failed.

Could not establish the connection to the operation log backup folder.

[Cause] Either the operation log backup folder does not exist, Or, could not establish the connection to a network drive.

[Action] Cancel the operation logs backup.

[Workaround] Check that the operation log backup folder exists, and reestablish the connection.

KDEX4370-E

Operation log backup failed. Could not establish the connection to the operation log backup folder.

[Cause] The Username or Password authentication has failed for the operation log backup folder.

[Action] Cancel the operation logs backup.

[Workaround] Check the Username or Password specified during Setup.

KDEX4371-E

Restore operation logs failed.

[Cause] An internal error has occurred.

[Action] Cancel restoration.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX4372-E

Restore operation logs failed.

An I/O error has occurred.

[Cause] Insufficient hard disk space for local-data-folder.

[Action] Cancel restoration.

[Workaround] Change local-data-folder, or increase hard disk space.

KDEX4373-E

Restore operation logs failed.

Could not establish the connection to the operation log backup folder.

[Cause] Either the operation log backup folder does not exist, Or could not establish the connection to the network drive.

[Action] Cancel restoration.

[Workaround] Check that the operation log backup folder (specified during Setup) exists, and reestablish the connection.

KDEX4374-E

Restore operation logs failed. Could not establish the connection to the operation log backup folder.

[Cause] The Username or Password authentication has failed for the operation log backup folder.

[Action] Cancel restoration.

[Workaround] Check the Username or Password specified during the Setup.

KDEX4375-W

Skipped some operation logs data during restoration.

Skip time:skip-time

[Cause] Backup file (operation logs) for the specified day does not exists in the operation log backup folder.

[Action] Continue operation logs restoration.

[Workaround] If the backup data for the specified day has been moved to any other folder, then copy the data to the operation log backup folder. Restore the operation logs again.

KDEX4376-E

Restore operation logs failed.

[Cause] The backup files do not exists in the operation log backup folder.

[Action] Cancel restoration.

[Workaround] If the backup files has been moved to any other folder, then copy the files to the operation log backup folder. Restore the operation logs again.

KDEX4377-E

Restore operation logs failed.

[Cause] Improper backup files. In the operation log backup folder there is no catalog file(OPR_CATALOG_YYYYMMDD.csv), which has the same date of the backup file(OPR_DATA_YYYYMMDD.zip).

[Action] Cancel restoration.

[Workaround] If the backup files has been moved to any other folder, then restore the files and try restoration. Else you can remove the backup files and the improper catalog file, and then try operation logs restoration.

KDEX4378-Q

If automatic operation logs backup setting is disabled, the operations logs will not be backed up. Enable the automatic backup setting to store the logs.

Click OK to resume. Click Cancel to review.

KDEX4379-E

An error occurred while restoring the database. Restoration has been canceled.

[Cause] The backup data version is different from the current version.

[Action] Cancel restoration.

[Workaround] Specify backup data whose version is same as the current version.

KDEX4380-E

Restore operation logs failed.

[Cause] Operation log backup folder was not specified during Setup.

[Action] Cancel restoration.

[Workaround] Check if the operation log backup folder was specified during Setup.

KDEX4381-E

Failed to backup the operation logs.

Connection to the operation log backup folder could not be established.

[Cause] Anonymous access to shared folders is restricted on the management server.

[Action] Cancel the operation logs backup.

[Workaround] Create a user account in the management server with Username and Password specified during Setup.

KDEX4382-E

Restore operation logs failed.

Could not establish the connection to the operation log backup folder.

[Cause] Anonymous access to shared folders is restricted on the management server.

[Action] Cancel restoration.

[Workaround] Create a user account in the management server with Username and Password specified during Setup.

KDEX4383-Q

You are trying to restore the backup data collected from "backed-up-server" to "current-server". Do you want to continue?

Click the [OK] button to continue with the restoration.

KDEX4384-Q

You are trying to restore backup data collected from a different management server. Do you want to continue?

To restore to a different management server, the settings of the management server need to be changed before the restoration is performed. For details about this procedure, see the description of migrating environments in the manual.

Click the [OK] button to continue with the restoration.

KDEX4387-E

Command execution failed. The specified file cannot be imported. (command name = command-name, subcommand name = subcommand-name, import file = import-file-name, line number at which import check error occurred = line-number-at-which-imported-CSV-file-error-occurred, item at which import check error occurred = name-of-the-item-for-which-imported-CSV-file-error-occurred)

[Cause] Possible causes (of invalid character input) include the following:

(1) The format of the import file is invalid.

(2) An ASCII control character was specified in the import file.

(3) A surrogate pair was specified in the import file.

(4) The character encoding of the import file does not match the character encoding specified by the -encoding option.

[Action] Cancels command execution.

[Workaround] Revise the specified import file, and then retry command execution.

KDEX4388-E

Command execution failed. The specified file cannot be imported. (command name = command-name, subcommand name = subcommand-name, import file = import-file-name, line number at which import check error occurred = line-number-at-which-imported-CSV-file-error-occurred, item at which import check error occurred = name-of-the-item-for-which-imported-CSV-file-error-occurred)

[Cause] Possible causes (of invalid update or deletion targets) include the following:

(1) A higher-level value that does not exist was specified for a post-change value. (For example, /A/B is specified for the post-change value, but /A does not exist.)

(2) An attempt was made in the import file to update or delete a value that did not exist before importing the file.

(3) An attempt was made in the import file to delete a value multiple times.

(4) An attempt was made in the import file to delete a value that was added in the same import file.

(5) An attempt was made in the import file to update or delete a management field that did not exist before importing the file. Alternatively, the management field for which an update or deletion attempt was made is not selectable or hierarchical data.

(6) An attempt was made in the import file to delete all values.

(7) A lower-level value that does not exist was specified for the post-change values. (For example, /A/B is specified for the pre-change values and /A/B/C is specified for the post-change values, but because /B will become /C after the change, /B is considered to be nonexistent.)

(8) The update category is D, and no value exists before changing the default language.

(9) The default selection for a management field (asset status, asset type, license status, license type, contract status, contract type) was changed.

(10) The default selection for a management field (asset status, asset type, license status, license type, contract status, contract type) was deleted.

(11) An attempt was made to update the department data applied from data collected from Active Directory.

(12) The character encoding of the import file does not match the character encoding specified by the -encoding option.

[Action] Cancels command execution.

[Workaround] Revise the specified import file, and then retry command execution.

KDEX4389-E

Command execution failed. The specified file cannot be imported. (command name = command-name, subcommand name = subcommand-name, import file = import-file-name, line number at which import check error occurred = line-number-at-which-imported-CSV-file-error-occurred, item at which import check error occurred = name-of-the-item-for-which-imported-CSV-file-error-occurred)

[Cause] Possible causes (of invalid deletion targets) include the following:

(1) An attempt was made to delete a hierarchical level that contains sublevels.

(2) The character encoding of the import file does not match the character encoding specified by the -encoding option.

[Action] Cancels command execution.

[Workaround] Revise the specified import file, and then retry command execution.

KDEX4390-E

Command execution failed. The specified file cannot be imported. (command name = command-name, subcommand name = subcommand-name, import file = import-file-name, line number at which import check error occurred = line-number-at-which-imported-CSV-file-error-occurred, item at which import check error occurred = name-of-the-item-for-which-imported-CSV-file-error-occurred)

[Cause] Possible causes (of invalid content input for an item) include the following:

(1) The contents of the import file specified for the command are invalid.

(2) The header of the import file is invalid.

(3) A value that cannot be specified in the import file is specified.

(4) The same language is specified in the multilingual settings.

(5) The number of characters that can be specified exceeded the limit.

(6) The character encoding of the import file does not match the character encoding specified by the -encoding option.

[Action] Cancels command execution.

[Workaround] Revise the specified import file, and then retry command execution.

KDEX4391-E

Command execution failed. The specified file cannot be imported. (command name = command-name, subcommand name = subcommand-name, import file = import-file-name, line number at which import check error occurred = line-number-at-which-imported-CSV-file-error-occurred, item at which import check error occurred = name-of-the-item-for-which-imported-CSV-file-error-occurred)

[Cause] Possible causes (of an invalid combination) include the following:

(1) The hierarchy settings among multiple languages do not match.

(2) The number of columns separated by commas is insufficient in the header or data of the import file.

(3) For update category U, only the explanation was changed, without changing the set value.

(4) The multilingual settings were changed for a custom item, an additional license item, or an additional contract item.

(5) The multilingual settings do not match among identical management fields.

(6) All pre-change languages were deleted.

(7) For update category A, a pre-change value has been input.

(8) An explanation has been input for a hierarchical item.

(9) For update category U, a pre-change value has been input for a newly added language.

(10) The character encoding of the import file does not match the character encoding specified by the -encoding option.

[Action] Cancels command execution.

[Workaround] Revise the specified import file, and then retry command execution.

KDEX4392-E

Command execution failed. The specified file cannot be imported. (command name = command-name, subcommand name = subcommand-name, import file = import-file-name, line number at which import check error occurred = line-number-at-which-imported-CSV-file-error-occurred, item at which import check error occurred = name-of-the-item-for-which-imported-CSV-file-error-occurred)

[Cause] Possible causes (of data duplication) include the following:

(1) Multiple lines that add the same selection exist in the import file.

(2) A selection was added that was set before the import of the file.

(3) A selection is specified that was set before the import of the file and that has the same name as a post-change selection.

(4) A line prior to the import file is adding the same selection as after the change.

(5) A line prior to the import file is changing the same selection as after the change.

(6) The character encoding of the import file does not match the character encoding specified by the -encoding option.

[Action] Cancels command execution.

[Workaround] Revise the specified import file, and then retry command execution.

KDEX4393-E

Command execution failed. The specified file cannot be imported. (command name = command-name, subcommand name = subcommand-name, import file = import-file-name, line number at which import check error occurred = line-number-at-which-imported-CSV-file-error-occurred, item at which import check error occurred = name-of-the-item-for-which-imported-CSV-file-error-occurred)

[Cause] In the import file specified for the command, /unknown is specified for the root of hierarchical or selectable data.

[Action] Cancels command execution.

[Workaround] Verify that the specified import file is correct, and then retry command execution.

KDEX4394-E

Command execution failed. The specified file cannot be imported. (command name = command-name, subcommand name = subcommand-name, import file = import-file-name, line number at which import check error occurred = line-number-at-which-imported-CSV-file-error-occurred, item at which import check error occurred = name-of-the-item-for-which-imported-CSV-file-error-occurred)

[Cause] Possible causes (of required items that have not been entered) include the following:

(1) No value is set for a required item.

(2) The multilingual value is set, but no languages corresponding to the multilingual settings are specified.

(3) The character encoding of the import file does not match the character encoding specified by the -encoding option.

[Action] Cancels command execution.

[Workaround] Revise the specified import file, and then retry command execution.

KDEX4395-E

Command execution failed. The specified file cannot be imported. (command name = command-name, subcommand name = subcommand-name, import file = import-file-name, line number at which import check error occurred = line-number-at-which-imported-CSV-file-error-occurred, item at which import check error occurred = name-of-the-item-for-which-imported-CSV-file-error-occurred)

[Cause] Possible causes (of hierarchical levels exceeding the upper limit) include the following:

(1) In the hierarchical data in the import file specified for the command, the specified data exceeds 40 levels.

(2) The character encoding of the import file does not match the character encoding specified by the -encoding option.

[Action] Cancels command execution.

[Workaround] Verify that the specified import file is correct, and then retry command execution.

KDEX4396-E

Command execution failed. Processing to apply the import data failed. The data is not reflected in the database. (command name = command-name, subcommand name = subcommand-name, import file = import-file-name, line number at which import check error occurred = line-number-at-which-imported-CSV-file-error-occurred, item at which import check error occurred = name-of-the-item-for-which-imported-CSV-file-error-occurred)

[Cause] Possible causes include the following:

(1) While the command was being executed, settings for an asset management field were edited from the operations window.

(2) The management server is temporarily experiencing a heavy load.

(3) The character encoding of the import file does not match the character encoding specified by the -encoding option.

[Action] Cancels command execution.

[Workaround]

(1) Retry command execution, and check the input from the import file.

(2) Wait a while, and then retry command execution.

(3) Ensure that the character encoding of the import file matches the character encoding specified by the -encoding option, and then retry command execution.

If the problem persists, collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX4397-E

Command execution failed. The specified file cannot be imported. (command name = command-name, subcommand name = subcommand-name, import file = import-file-name, line number at which import check error occurred = line-number-at-which-imported-CSV-file-error-occurred, item at which import check error occurred = name-of-the-item-for-which-imported-CSV-file-error-occurred)

[Cause] An attempt was made to update the additional management items specified for the following information, by using the import file specified for the command:

(1) User-specified security setup items

(2) User-specified group conditions

(3) Automatic maintenance policies

[Action] Cancels command execution.

[Workaround] Check whether the specified import file is correct. Also, specify the settings so that the additional management items specified for the following items cannot be updated by executing a command, and then execute the command again:

(1) User-specified security setup items

(2) User-specified group conditions

(3) Automatic maintenance policies

KDEX4398-W

After the common management fields and additional management fields was successfully imported, an attempt to restart the service failed. (command name = command-name, subcommand name = subcommand-name, service name = service-name)

[Cause] Possible causes include the following:

(1) Processing to link with the service failed.

(2) An error occurred while the service was being restarted.

[Action] Cancels stopping or starting of the service.

[Workaround] Check the public message log file, and follow the instructions in the message output by the service that failed to be restarted. If no such message has been output, try restarting the service again.

KDEX4399-I

The common management fields and additional management fields was successfully imported. On the management server, restart the service indicated in parentheses at the end of this message. (command name = command-name, subcommand name = subcommand-name, service name = service-name)

KDEX4400-E

Import log file output failed. The data is not reflected in the database. (log file name = import-log-file-name)

[Cause] Failed to write the log file.

[Action] Cancels processing.

[Workaround] Complete the following steps, and then retry command execution.

(1) Assign write permissions to the folder in which the import file is stored.

(2) Ensure that there is enough free space on the disk on which the import file is stored.

(3) Delete any log files in the folder in which the import file is stored (import-file-name.log).

KDEX4401-E

Command execution failed. The specified file cannot be imported. The data is not reflected in the database. (command name = command-name, subcommand name = subcommand-name, import file = import-file-name, management field name = name-of-common-management-field-or-additional-management-field, selection = selection-set-as-a-common-management-field-or-additional-management-field)

[Cause] Possible causes include the following:

(1) A selection that is set as an additional management field of hardware asset information was updated or deleted.

(2) A selection that is set as an additional management field of software license information was updated or deleted.

(3) A selection that is set as an additional management field of contract information was updated or deleted.

[Action] Cancels command execution.

[Workaround]

(1) From the hardware asset information, delete the selection that is set as the additional management field of hardware asset information, and then retry command execution.

(2) From the software license information, delete the selection that is set as the additional management field of software license information, and then retry command execution.

(3) From the contract information, delete the selection that is set as the additional management field of contract information, and then retry command execution.

KDEX4402-E

Command execution failed. The specified file cannot be imported. The data is not reflected in the database. (command name = command-name, subcommand name = subcommand-name, import file = import-file-name, management field name = name-of-common-management-field-or-additional-management-field, selection = selection-set-as-a-common-management-field-or-additional-management-field, filter name = filter-name)

[Cause] A selection of an additional management field that is set as a filter condition was updated or deleted.

[Action] Cancels command execution.

[Workaround] Delete the additional management field that is set as a filter condition from the conditions, and then retry command execution.

KDEX4403-E

Failed to execute the command. An attempt to apply the import data failed. The data is not reflected in the database. (command name = command-name, subcommand name = subcommand-name, import file = import-file-name)

[Cause] Possible causes include the following:

(1) The service (JP1_ITDM2_DB Service) is stopped.

(2) A network failure occurred.

(3) The authentication information for connecting to the data folder shared between servers is incorrect.

(4) The management server is temporarily experiencing a heavy load.

[Action] Cancels command execution.

[Workaround]

(1) Start the service (JP1_ITDM2_DB Service), and then execute the command again.

(2) Resolve the cause of the network failure, and then retry command execution.

(3) Verify that the user name and password for connecting to the data folder shared between servers are correct, and then retry command execution.

(4) Wait a while, and then retry command execution.

If the problem persists, collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX4404-I

number-of-managed-nodes

KDEX4405-E

Acquisition of the number of managed nodes failed.

The processing of the command will stop.

KDEX4406-E

A command argument is incorrect.

The processing of the command will stop.

Specify the correct argument, and then re-execute the command.

KDEX4407-E

An internal error occurred.

The processing of the command will stop.

Extract data by using a data extraction tool, and then contact a system administrator.

KDEX4408-I

The license distribution command finished successfully, and processing based on the command settings has started. (command name = command-name)

KDEX4409-I

The distribution of licenses and the permissions required to register licenses for lower-level management servers, including the initialization of settings, were successfully completed.

KDEX4410-E

Failed to execute the command. This command can only be executed on the primary management server. (command name = command-name)

[Cause] The command was executed on a management relay server or a management server in a single-server configuration.

[Action] Cancels the execution of the command.

[Workaround] Execute the command again on the primary management server.

KDEX4411-E

Failed to execute the command. The specified file could not be read. (command name = command-name, file-path = file-path, row number corresponding to the error = row-number-corresponding-to-error, item for which the error occurred = item-for-which-the-error-occurred)

[Cause] The format of the CSV file specified in the command is invalid.

[Action] Cancels the execution of the command.

[Workaround] Make sure that the specified CSV file is correct, and then execute the command again.

KDEX4412-E

Failed to execute the command. The specified file could not be read. (command name = command-name, file path = file-path, row number corresponding to the error = row-number-corresponding-to-error )

[Cause] The host name of the management relay server specified in the CSV file is invalid.

[Action] Cancels the execution of the command.

[Workaround] Make sure that the host name is correct, and then execute the command again.

KDEX4413-E

Failed to execute the command. The specified file could not be read. (command name = command-name, file path = file-path, row number corresponding to the error = row-number-corresponding-to-error)

[Cause] The same host name is specified multiple times in the CSV file.

[Action] Cancels the execution of the command.

[Workaround] Make sure that the host name is correct, and then execute the command again.

KDEX4414-E

Failed to execute the command. The specified file could not be read. (command name = command-name, file path = file-path)

[Cause] The total number of licenses specified in the CSV file exceeds the total number of licenses for the primary management server.

[Action] Cancels the execution of the command.

[Workaround] Revise the total number of licenses so that it is less than the total number of licenses for the primary management server, and then execute the command again.

KDEX4415-E

Failed to execute the command. The specified file could not be read. (command name = command-name, file path = file-path, row number corresponding to the error = row-number-corresponding-to-error)

[Cause] The CSV file is trying to distribute licenses for a management relay server (for which license registration is permitted) to a lower-level management server.

[Action] Cancels the execution of the command.

[Workaround] Make sure that the distribution destination for licenses is correct, and then execute the command again.

KDEX4416-E

Failed to execute the command. The license could not be distributed. (command name = command-name)

[Cause] The following are possible causes:

(1) The license for this product was not authenticated (registered).

(2) The license for this product has expired.

(3) The license information for this product is invalid.

[Action] Cancels the execution of the command.

[Workaround]

(1) Authenticate (register) the license for this product.

(2) Purchase a license for this product.

(3) Collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX4417-E

Failed to execute the license distribution command. (command name = command-name)

KDEX4418-E

Failed to execute the command. The file path is invalid. Command name=command-name File path=file-path

[Cause] The possible reasons are:

(1) The folder in the specified path does not exist, or the specified file path is incorrect.

(2) The specified path exceeds the maximum path length.

(3) You do not have access permission for the specified file.

(4) Insufficient disk space for the specified file.

(5) An I/O error occurred.

[Action] Cancel command execution.

[Workaround]

(1) Make sure the folder in the specified path exists and the specified path is correct.

(2) Check the path length.

(3) Make sure you have file access permission.

(4) Free the disk space for the specified file or specify another file which has sufficient space.

(5) Confirm that a disk failure has not occurred.

After these are confirmed, retry command execution.

KDEX4419-E

Failed to execute the command. Command name=command-name, Error code=error-code (maintenance-code).

[Cause] Insufficient memory for the command execution environment. Or a critical error occurred during command execution.

[Action] Cancel command execution.

[Workaround] Make sure there is sufficient memory for the command execution environment, and retry command execution. If the problem still persists, use the troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX4420-E

Failed to execute the command. Database access error occurred. Detailed information=detailed-information, Command name =command-name.

[Cause] JP1/IT Desktop Management 2 - Manager stopped or the displayed error occurred.

[Action] Cancel command execution.

[Workaround] Start JP1/IT Desktop Management 2 - Manager or resolve the displayed error and retry command execution. If the problem persists, execute troubleshooting information collection command to collect troubleshooting information and contact customer support.

KDEX4421-E

Command execution was canceled. (command name = command-name)

KDEX4430-E

Failed to execute the command. The specified file could not be imported. (command name = command-name, subcommand name = subcommand-name, import file = import-file-name, line number at which import check error occurred = line-number-at-which-imported-CSV-file-error-occurred, item for which import check error occurred = name-of-the-item-for-which-imported-CSV-file-error-occurred)

[Cause] An attempt was made to update the custom field value of hardware asset information applied by a higher-level management server.

[Action] Cancel the command execution.

[Workaround] Make sure the specified import file is correct, and then try again.

KDEX4440-I

The command ended normally. (command name = command name)

KDEX4441-E

Failed to execute the command. The specified arguments are invalid. (command name = command name)

[Cause] The specified arguments are invalid. Or the specified file path is invalid.

[Action] Cancels execution of the command.

[Workaround] Confirm the command arguments or file path, and then try again.

KDEX4442-E

Failed to execute the command. The input file could not be read. (command name = command name)

[Cause] Possible causes are as follows:

(1) You do not have the necessary permissions to access the input file.

(2) An I/O error occurred.

(3) The input file is currently being used.

[Action] Cancel command execution.

[Workaround]

(1) Make sure you have the necessary permissions to access the input file.

(2) Check whether a disk failure occurred.

(3) Check whether the input file is currently being used.

After these are confirmed, re-execute the command.

KDEX4443-E

Failed to execute the command. The file name of the input file is invalid. (file name = file name, command name = command name)

[Cause] There is a mistake in the file name of the settings file to be input.

[Action] Cancel command execution.

[Workaround] Revise the file name of the settings file, and then re-execute the command.

KDEX4445-E

The format of the input file is invalid. (line number = invalid line number)

KDEX4446-E

The format of the input file is invalid. The same section is specified more than once. (line number = invalid line number)

KDEX4447-E

The format of the input file is invalid. Specify both the ITDM section and the DM section.

KDEX4448-E

Failed to execute the command. The format of the input file is invalid. (command name = command name)

[Cause] The format of the specified input file is invalid.

[Action] Cancel command execution.

[Workaround] Check the format of the input file, and then re-execute the command.

KDEX4449-E

Failed to execute the command. (command name = command name).

[Cause] Insufficient memory space.

[Action] Cancels execution of the command.

[Workaround] Free the memory space, and then try again.

KDEX4450-E

Failed to execute the command. (command name = command name).

[Cause] Failed to execute the command.

[Action] Cancels execution of command.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact the support service.

KDEX4451-E

Invalid content in import file. (command name = command name, line number of the line that caused the error = line-number)

KDEX4452-E

The format of the input file is invalid. Specify section-name section.

KDEX4460-I

The command was executed. (command name = command name , command argument = command-argument, version = version)

Note:

This is the message concerning the network control command. For details about the location to which the messages are output, see "Output format of the network control command message file" in "jdnrnetctrl (controlling network access)" in the manual JP1/IT Desktop Management 2 Administration Guide.

KDEX4461-I

The command ended normally.

Note:

This is the message concerning the network control command. For details about the location to which the messages are output, see "Output format of the network control command message file" in "jdnrnetctrl (controlling network access)" in the manual JP1/IT Desktop Management 2 Administration Guide.

KDEX4462-W

The command ended normally. However, an invalid line was found in the specified network connection control file.

[Cause] An invalid line was found in the network connection control file.

[Action] The command ended normally.

[Workaround] Implement the workaround specified for KDEX4465-W that is displayed immediately before this message.

Note:

This is the message concerning the network control command. For details about the location to which the messages are output, see "Output format of the network control command message file" in "jdnrnetctrl (controlling network access)" in the manual JP1/IT Desktop Management 2 Administration Guide.

KDEX4463-E

Failed to execute the command. The specified arguments are invalid.

[Cause]The specified arguments are invalid.

[Action]Cancel command execution.

[Workaround]Confirm the command arguments, and retry execution.

Note:

This is the message concerning the network control command. For details about the location to which the messages are output, see "Output format of the network control command message file" in "jdnrnetctrl (controlling network access)" in the manual JP1/IT Desktop Management 2 Administration Guide.

KDEX4464-E

Failed to execute the command. The file path is invalid.

[Cause] The possible causes are as follows:

(1) The folder does not exist at the specified path, or the specified path is invalid.

(2) The length of the specified path is invalid.

(3) You do not have the permission to access the specified file.

(4) An I/O error occurred.

(5) The file format of the network control command setting file is invalid.

[Action] Cancel command execution.

[Workaround]

(1) Check whether the folder exists at the specified path and that the specified path is valid.

(2) Check the length of the specified path.

(3) Check whether you have the permission to access the specified file.

(4) Check whether a disk failure has occurred.

(5) Check the network control command setting file.

After performing these checks, re-execute the command.

Note:

This is the message concerning the network control command. For details about the location to which the messages are output, see "Output format of the network control command message file" in "jdnrnetctrl (controlling network access)" in the manual JP1/IT Desktop Management 2 Administration Guide.

KDEX4465-W

An invalid line was found in the network connection control file. Execution of the command continues. Line number of the invalid line = line-number-of-the-invalid-line

[Cause] An invalid line was found in the network connection control file.

[Action] Continues execution of the command.

[Workaround] Review the invalid line in the network connection control file, and then re-execute the command as necessary.

Note:

This is the message concerning the network control command. For details about the location to which the messages are output, see "Output format of the network control command message file" in "jdnrnetctrl (controlling network access)" in the manual JP1/IT Desktop Management 2 Administration Guide.

KDEX4466-E

Failed to execute the command. Failed to connect to the management server.

[Cause] The possible causes are as follows:

(1) The host name (IP address) or port number set in the network control command configuration file is invalid.

(2) The set firewall or other communication environment does not allow the computer to communicate with the management server by using the information set in the network control command configuration file.

(3) The management server is not up and running.

(4) A network failure has occurred.

[Action] Cancel command execution.

[Workaround]

(1) Specify the correct host name (IP address) and the port number in the network control command configuration file.

(2) Set the firewall or other communication environment so that it allows the computer to communicate with the management server by using the information set in the network control command configuration file.

(3) Start the management server.

(4) Resolve the network failure.

After performing these checks, re-execute the command.

Note:

This is the message concerning the network control command. For details about the location to which the messages are output, see "Output format of the network control command message file" in "jdnrnetctrl (controlling network access)" in the manual JP1/IT Desktop Management 2 Administration Guide.

KDEX4467-E

Failed to execute the command. Authentication failed on the management server. Cause or workaround number = cause-or-workaround-number

[Cause] The possible causes are as follows:

(3) You do not have the necessary permission to execute the command.

(10) The following reasons are possible:

- The user ID or password is incorrect. (The user ID and password are case-sensitive.)

- The user account is locked.

(11) The trial license has expired.

(12) The product license has expired, or an error occurred in the database.

(13) JP1/IT Desktop Management 2 is starting up.

[Action] Cancel command execution.

[Workaround]

(3) Confirm whether the specified user has the account that grants the necessary permission to the user.

After performing these checks, re-execute the command.

(10) Set the correct user ID and password. Contact the administrator to find out whether your account has been locked.

(11) If you want to continue using the product, purchase a product edition license.

(12) If the product license has expired, purchase a product license. If the product license has not expired, execute the command to obtain troubleshooting information from the management server, and then contact the support service.

(13) Wait for a while and then re-execute the command. If this message is repeatedly displayed, confirm whether the server on which JP1/IT Desktop Management 2 is installed is up and running, and whether a network failure has not occurred.

Note:

This is the message concerning the network control command. For details about the location to which the messages are output, see "Output format of the network control command message file" in "jdnrnetctrl (controlling network access)" in the manual JP1/IT Desktop Management 2 Administration Guide.

KDEX4468-E

Failed to execute the command. Another command is being executed.

[Cause] The command was executed while another command was being executed.

[Action] Cancel command execution.

[Workaround] Re-execute the command after the current command ends.

Note:

This is the message concerning the network control command. For details about the location to which the messages are output, see "Output format of the network control command message file" in "jdnrnetctrl (controlling network access)" in the manual JP1/IT Desktop Management 2 Administration Guide.

KDEX4469-E

Failed to execute the command. You do not have the permission to execute the command.

[Cause] The user executing the command did not have the Administrator permission.

[Action] Cancel command execution.

[Workaround] The user having the Administrator permission re-executes the command.

Note:

This is the message concerning the network control command. For details about the location to which the messages are output, see "Output format of the network control command message file" in "jdnrnetctrl (controlling network access)" in the manual JP1/IT Desktop Management 2 Administration Guide.

KDEX4470-E

Failed to execute the command.

[Cause] The possible causes are as follows:

- The user ID or password is incorrect. (The user ID and password are case-sensitive.)

- The user account is locked.

- The password has expired.

[Action] Cancel command execution.

[Workaround] Set the correct user ID and password. Contact the administrator to find out whether your account has been locked or whether your password has expired.

After performing these checks, re-execute the command.

Note:

This is the message concerning the network control command. For details about the location to which the messages are output, see "Output format of the network control command message file" in "jdnrnetctrl (controlling network access)" in the manual JP1/IT Desktop Management 2 Administration Guide.

KDEX4471-E

Command execution failed. (JP1_ITDM2_Service) service has not stopped. (command name = command-name, subcommand name = subcommand-name)

[Cause] (JP1_ITDM2_Service) service has not stopped.

[Action] Cancels command execution.

[Workaround] Stop (JP1_ITDM2_Service) service, and then retry command execution.

KDEX4472-I

Command executed successfully. (Command name=command-name, Subcommand name=subcommand-name.)

KDEX4473-I

Successfully imported the asset. Type of asset=asset-type, add=number-of-information-items, update=number-of-information-items, error=number-of-information-items, skipped=number-of-information-items.

KDEX4474-I

Content in the file to be imported was skipped. Command name=command-name, subcommand name=subcommand-name, line number of skipped content=line-number.

KDEX4475-W

The export of Devices (details) ended normally, but information other than the host ID cannot be output for one or more devices. Command name = ioutils, Subcommand name = exportdevicedetail

[Cause] The possible reasons are:

(1) A temporary error occurred during data processing.

(2) The detailed information of a device contains invalid information.

[Action] Ends the command normally.

[Workaround] Perform the workaround in the following orde, and retry execution.

(a) Refer to the content of the exported file and check which of the host IDs correspond to devices whose rows (for columns other than that of the host ID) are all empty.

(b) If, in the specified template, Host ID is not specified as a column to be exported, from the [Device List] in the device window, display the Select Export Columns dialog box. In the dialog box, select Host ID and export the file again, and then check which of the host IDs correspond to devices whose rows (for columns other than that of the host ID) are all empty.

(c) From the device window, in the [Device List], execute the action Update Device Details for the devices to which the host IDs correspond. If the problem still persists, collect troubleshooting information for the management server and for the agents to which the host IDs correspond, and then contact Customer Support.

KDEX4476-W

Invalid data was detected while the asset information or asset association information was being imported. command name = command-name, subcommand name = subcommand-name, file path = file-path, row number = row-number, item = item, value = value

[Cause] Data that cannot be set on the management server is specified.

[Action] Skip the illegal data and continue the import.

[Workaround]

When importing asset information:

Refer the formats in imported CSV files of asset information described in the manual JP1/IT Desktop Management 2 Overview and System Design Guide, correct the CSV files, and retry execution.

When importing asset association information:

Specify the information registered on JP1/IT Desktop Management 2. Or, refer the formats in imported CSV files of asset association information described in the manual JP1/IT Desktop Management 2 Overview and System Design Guide, correct the CSV files, and retry execution.

KDEX4477-W

A row could not be updated due to an error that occurred while the asset information or asset association information was being imported. command name = command-name, subcommand name = subcommand-name, file path = file-path, list of row numbers = list-of-row-numbers

[Cause] Data that cannot be set on the management server is specified.

[Action] The command finished normally.

[Workaround] Refer the description of KDEX4476-W, correct the CSV files, and retry execution.

KDEX4478-I

The asset association information was imported. asset association information = asset-association-information, update = update, error = error

KDEX4600-I

An internet connection was successfully set. Command name=command-name

KDEX4601-I

Internet connection settings were successfully output. Command name=command-name

KDEX4602-E

Failed to set the internet connection. Command name=command-name

KDEX4603-E

Failed to output the internet connection settings. Command name=command-name

KDEX4604-W

The internet connection settings were successfully applied. However, an attempt to restart the service failed. Command name=command-name

[Cause] An error occurred while restarting the service.

[Action] Cancel starting of the service.

[Workaround] Check the public message log file, and follow the instructions in the message output by the service that failed to restart. Run the startservice command to restart the service. If JP1_ITDM2_Agent Service has not started, please restart the service.

KDEX4605-E

Failed to execute the command. You cannot access the file. Command name=command-name, File path=file-path

[Cause] The possible causes are as follows:

(1) The folder or file with the specified file path does not exist.

(2) You do not have permissions to access the specified file.

(3) An I/O error occurred.

[Action] Cancel command execution.

[Workaround]

(1) Check whether the folder or file with the specified file path exists.

(2) Check the access permissions for the specified file.

(3) Make sure that no disk failure has occurred. After checking the above, re-execute the command.

KDEX4606-E

Failed to execute the command. You cannot write to the internet connection settings file. Command name=command-name, File path=file-path

[Cause] The possible causes are as follows:

(1) The folder with the specified file path does not exist.

(2) You do not have permissions to access the file to which you want to write.

(3) The hard disk to which data is to be written does not have sufficient space.

(4) An I/O error occurred.

[Action] Cancel command execution.

[Workaround]

(1) Check whether the folder with the specified file path exists and whether it is a specifiable folder.

(2) Check the access permissions for the folder and file to which you want to write.

(3) Increase the space on the hard disk to which you want to write. Alternatively, specify the file path of a disk with sufficient space.

(4) Make sure that no disk failure has occurred. After checking the above, re-execute the command.

KDEX4607-E

Failed to execute the command. The command can be executed on a management relay server. Command name=command-name

[Cause] The command was executed on a management server rather than the management relay server.

[Action] Cancel command execution.

[Workaround] Re-execute the command on the management relay server.

KDEX4608-E

Failed to execute the command. A mistake exists in the settings in the internet connection settings file. Command name=command-name, File=file, Section=section, Key=key

[Cause] The possible causes are as follows:

(1) A required value is not set.

(2) An invalid value is set.

[Action] Cancel command execution.

[Workaround] Review the contents of the settings file, specify the correct file for the command argument, and then re-execute the command.

KDEX4609-E

Failed to execute the command. Command name=command-name

[Cause] The command execution environment does not have sufficient memory.

[Action] Cancel command execution.

[Workaround] Make sure that the command execution environment has sufficient memory, and then re-execute the command. If the problem persists, restart the OS, and then re-execute the command.

KDEX4610-E

Failed to execute the command. Failed to stop the service. Command name=command-name

[Cause] An error occurred while stopping the service.

[Action] Cancel command execution.

[Workaround] Check the public message log file, and then take action according to the message output by the service that failed to stop. Re-execute the command.

KDEX5000-I

Starting discovery from IP address range.

KDEX5001-I

IP address range discovery complete.

KDEX5002-I

Searching the range (Start IP address=start-IP-address, End IP address=end-IP-address).

KDEX5003-I

Completed the search for range (Start IP address=start-IP-address, End IP address=end-IP-address).

KDEX5004-I

Discovered a new network device and sent an e-mail to the administrator.

KDEX5005-I

Searching the node (IP address=IP-address, MAC address=MAC-address).

KDEX5006-I

Search for (IP address=IP-address, MAC address=MAC-address) is complete.

KDEX5007-W

User authentication failed during discovery for this device. IP address=IP-address

[Cause] Authentication information is either not set or is not valid.

[Action] Continue the process.

[Workaround] Check if you can log into the target computer as an Administrator with the Windows authentication information specified for discovery. Confirm administrative share is enabled in the target computer, and then retry discovery.

KDEX5008-W

Failed to access the administrative share. IP address=IP-address

[Cause] Failed to connect to the administrative share in the target computer.

[Action] Continue the process.

[Workaround] If the power is switched off in target computer, turn it on. If the firewall is enabled, confirm the port for shared files are open and retry discovery.

KDEX5009-E

Failed to access the administrative share. IP address=IP-address, Error code=error-code (maintenance-code)

[Cause] An error occurred while accessing the administrative share. The error is caused by a factor other than connection, communication, and authentication.

[Action] Continue the process.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX5010-W

Failed to discover this device because it is processing another request. (IP address = IP-address)

[Cause] Possible causes include the following:

(1) Discovery was executed on a device that was responding to a request from another management server.

(2) Discovery was executed on a device that was responding to a request from the same management server.

[Action] Continues processing.

[Workaround]

(1) Revise the discovery range, and then retry discovery.

(2) Wait a while, and then retry discovery.

If the problem persists, restart the device, and then retry discovery.

KDEX5011-W

Failed to obtain detailed information from the administrative share. IP address=IP-address

[Cause] Failed to retrieve detailed information in time, from the administrative share.

[Action] Continue the process.

[Workaround] Check the status of the computer, and retry discovery.

KDEX5012-E

An error occurred while accessing the administrative share in the target computer. IP address=IP-address, Error code=error-code (maintenance-code)

[Cause] An error occurred while accessing the administrative share in the target computer.

[Action] Continue the process.

[Workaround] Check the operational status of the target computer, and retry discovery. Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX5013-E

An error occurred during discovery. Error code=error-code (maintenance-code)

[Cause] A critical error occurred during discovery.

[Action] Cancel the process.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX5014-W

Failed to update a node due to a brief server error during discovery.

[Cause] (JP1_ITDM2_Agent Control) service was either not started or was busy during discovery.

[Action] Continue the process.

[Workaround] Make sure (JP1_ITDM2_Agent Control) service is running, and then retry discovery.

KDEX5015-I

Searching for the nodes discovered by Network Access Control.

KDEX5016-I

Search for nodes discovered by Network Access Control is complete.

KDEX5020-I

Collecting device data from agentless devices.

KDEX5021-I

Device data collection from agentless devices is complete.

KDEX5027-W

User authentication failed while collecting device data. IP address=IP-address

[Cause] Authentication information is either not set or is invalid.

[Action] Continue the process.

[Workaround] Check if you can log into the target computer as an Administrator with the Windows authentication information specified for discovery. Confirm administrative share is enabled in the target compute, and then retry discovery.

KDEX5040-I

Collecting on-demand device data from agentless devices.

KDEX5041-I

On-demand device data collection from agentless devices is complete.

KDEX5043-I

Collected on-demand device data. IP address=IP-address

KDEX5047-W

User authentication failed while collecting on-demand device data. IP address=IP-address

[Cause] Authentication information is either not set or is invalid.

[Action] Continue the process.

[Workaround] Check if you can log into the target computer as an Administrator with the Windows authentication information specified for discovery. Confirm administrative share is enabled in the target compute, and then retry discovery.

KDEX5060-I

Delivering agent.

KDEX5061-I

Agent delivery complete.

KDEX5063-I

The agent installer has been started. Access point=access-point (host-name or IP-address), Model name=model-name, Version=version

KDEX5064-W

Agent delivery failed. The agent is not registered.

[Cause] The agent is not registered.

[Action] Continue the process.

[Workaround] Go to Start>Programs>JP1_IT Desktop Management 2 - Manager>Tools>Component Registration to register the agent. Then, retry agent delivery.

KDEX5065-E

An error occurred during agent delivery. Error code=error-code (maintenance-code)

[Cause] A critical error occurred during agent delivery.

[Action] Cancel the process.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX5067-W

Agent deployment failed because user authentication failed. (access point = access-point (host-name or IP-address))

[Cause] Possible causes are as follows:

(1) No credentials are specified, or the specified credentials are invalid.

(2) The discovery range for when the computer was discovered has been deleted.

[Action] Continues processing.

[Workaround]

(1) Check whether you are able to log on to the access point as an administrator by using the Windows credentials specified for agent deployment, and then retry agent deployment.

(2) Increase the discovery range, and then specify credentials. Perform discovery again, and then retry agent deployment.

KDEX5068-W

Agent delivery failed. Connection failure to the administrative share. Access point=access-point (host-name or IP-address)

[Cause] Failed to access the administrative share using the authentication information.

[Action] Continue the process.

[Workaround] Check if the administrative share (ADMIN$) is enabled in the target computer. Check if you can log into the target computer as an Administrator with the Windows authentication information specified for agent delivery. After confirming the settings, retry agent delivery.

KDEX5069-W

An error occurred during agent installation. Access point=access-point (host-name or IP-address), Error code=error-code (maintenance-code)

[Cause] A critical error occurred during agent installation.

[Action] Continue the process.

[Workaround] Check if the target computer is prepared for agent installation, and then retry agent delivery. If the problem persists, Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX5070-W

Started Agent delivery. But Failed to connect to the computer. Access point=access-point (host-name or IP-address)

[Cause] Failed to connect to the administrative shared folder in target computer.

[Action] Continue the process.

[Workaround] Turn the power on, if the power of the target computer is switched off. If the firewall is enabled, confirm the port for shared files are open and retry discovery.

KDEX5071-W

A communication error occurred during agent delivery. Access point = access-point (host-name or IP-address)

[Cause] Possible causes include the following:

(1) There is a problem in the status of the network between the management server and the computer to which the agent is to be delivered.

(2) The IP address of the computer to which the agent is to be delivered does not exist in the device information.

[Action] Continues processing.

[Workaround]

(1) Verify that there are no problems in the status of the network, and then retry agent delivery.

(2) From the device window, in the [Device List], specify the IP address in the computer device information, and then retry agent delivery.

KDEX5072-E

An error occurred during agent delivery. Access point=access-point (host-name or IP-address), Error code=error-code (maintenance-code)

[Cause] An error occurred during agent delivery. The error is caused by a factor other than connection, communication, and authentication.

[Action] Continue the process.

[Workaround] Use the troubleshooting information collection command to collect troubleshooting information and contact support service.

KDEX5073-E

An error occurred on the target computer during agent delivery. Access point=access-point (host-name or IP-address), Error code=error-code (maintenance-code)

[Cause] An error occurred on the target computer during agent delivery.

[Action] Continue the process.

[Workaround] Retry agent delivery. If the problem persists, execute troubleshooting information collection command to collect troubleshooting information and contact customer support.

KDEX5074-W

Unabble to deliver agent since the MAC address of the computer differs from the registered MAC address.

[Cause] On agent delivery, the MAC address of the target computer, and that managed by the management server are different. The system had connected to a different computer from the one discovered. Access point=access-point (host-name or IP-address), Registered MAC address=registered-MAC-address

[Action] Continue the process.

[Workaround] This may be caused by out-of-date discovery information. Retry agent delivery after re-executing discovery.

KDEX5075-W

Agent delivery was not performed because an agent is already installed. (access point = access-point (host-name or IP-address))

[Cause] An agent is already installed on the target computer.

[Action] Continues processing.

[Workaround] Agent delivery is not required because an agent is already installed on the target computer.

KDEX5076-W

Agent is installed but no communication from the agent. Access point=access-point (host-name or IP-address)

[Cause] The management server has not received any confirmation message from the installed agent.

[Action] Continue the process.

[Workaround] Check the operational status of the network between the management server and the target computer, and confirm whether the agent is installed. If the agent is not installed, retry agent delivery. If the problem persists, Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX5077-W

Failed to deliver agent. Could not resolve management server host name management-server-host-name on the target computer. Access point=access-point (host-name or IP-address)

[Cause] Could not resolve the management server's host name on the target computer.

[Action] Continue the process.

[Workaround] Configure the agent setting to enable host name resolution on the target computer, if the setting Connecting management server is set to the default host name. Or, you can set the IP address instead of host name, and then retry agent delivery.

KDEX5078-W

Credentials required for agent deployment have not been specified. (access point = access-point (host-name or IP-address))

[Cause] Possible causes are as follows:

(1) You cannot log on to the access point because no Windows credentials have been specified for agent deployment.

(2) The discovery range for when the computer was discovered has been deleted.

[Action] Continues processing.

[Workaround]

(1) Specify Windows credentials to enable logon to the access point as an administrator, and then retry agent deployment.

(2) Increase the discovery range, and then specify credentials. Perform discovery again, and then retry agent deployment.

KDEX5079-E

An error occurred while creating the agent media used for agent delivery. Error code=error-code (maintenance-code)

[Cause] A critical error occurred while creating the agent media used for agent delivery.

[Action] Cancel the process.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX5080-I

Agent delivery started (retry).

KDEX5081-I

Agent delivery complete (retry).

KDEX5082-W

Failed to deliver agent since the agent is being installed. Access point=access-point (host-name or IP-address)

[Cause] Delivered agent to a computer while it was processing another agent delivery.

[Action] Continue the process.

[Workaround] Another agent delivery is in process, so agent delivery is not required.

KDEX5083-W

Failed to complete agent installation within elapsed-time-in-minutes minutes. Access point=access-point (host-name or IP-address)

[Cause] Failed to complete agent installation within the given time.

[Action] Continue the process.

[Workaround] If the agent is installed after this message display, agent will work normally, no action required. If the agent failed to install for a while, retry agent delivery.

KDEX5084-W

Failed to deliver the agent. User authentication has failed. Access Point=access-point (host-name or IP-address).

[Cause] Authentication information is either not set or is invalid.

[Action] Continue the process.

[Workaround] Check if you can log into the target device as an Administrator with the Active Directory information specified for agent delivery.Then, retry agent delivery.

KDEX5085-W

Failed to deliver the agent. Administrative share connection failure. Access point=access-point (host-name or IP-address)

[Cause] Failed to access the administrative share using the authentication information.

[Action] Continue the process.

[Workaround] Check if the administrative share (ADMIN$) is enabled in the target computer. Check if you can log into the target device as an Administrator with the Active Directory information specified for agent delivery. After confirming the settings, retry agent delivery.

KDEX5086-W

Authentication information required for agent delivery is not specified. Access point=access-point (host-name or IP-address)

[Cause] Login has failed because the Active Directory information required for agent delivery was not specified.

[Action] Continue the process.

[Workaround] Specify one or more Active Directory information to log in the target computer with Administrator privileges. Retry agent delivery.

KDEX5100-I

Agentless processing was started on the site server.

Access point=access-point-IP-address, Operation type=agentless-operation-type.

KDEX5101-E

Agentless processing could not be started on the site server.

Access point=access-point-IP-address, Operation type=agentless-operation-type.

[Cause] The site server service (site-server-service-name) has not been started.

[Action] Cancel the process.

[Workaround] Confirm that the site server process (site-server-service-name) has been started, and then retry the operation.

KDEX5102-I

Agentless processing on the site server is complete.

Access point=access-point-IP-address, Operation type=agentless-operation-type.

KDEX5103-E

A request for agentless processing could not be sent to the site server.

Access point=access-point-IP-address, Operation type=agentless-operation-type.

[Cause] Possible causes are as follows:

(1) The site server service (site-server-service-name) has not been started.

(2) The load on the site server has increased.

(3) An error has occurred on the network.

[Action] Cancel processing.

[Workaround] Check whether an error has occurred on the network, and then check whether the site server service (site-server-service-name) has been started. To perform discovery, collection of the latest device data, or agent delivery, wait a while, and then retry the operation.

KDEX5104-I

Starting discovery from IP address range. (n time around)

KDEX5199-E

A system error has occurred.

[Cause] A critical internal error has occurred in the system.

[Action] Cancel discovery or agent delivery.

[Workaround] Confirm whether configuration environment of the management server is valid and is operating properly. If the problem persists, Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX5301-I

Connected to Active Directory.

KDEX5302-E

Active Directory connection failed.

KDEX5305-I

A connection to JP1/NETM/NM - Manager was successfully established.

KDEX5306-E

Failed to connect JP1/NETM/NM - Manager.

KDEX5307-I

Successfully connected to the Support Service site.

KDEX5308-E

Failed to connect the Support Service site.

KDEX5309-I

Updated the security policy.

KDEX5310-E

Failed to update the security policy.

KDEX5311-I

Determined the security status. Performed date=security-judgment-data, Safe=number-of-safe-PCs, Caution=number-of-caution-PCs, Warning=number-of-warning-PCs, Danger=number-of-danger-PCs, Unknown=number-of-unknown-PCs, Out of Target=number-of-out-of-target-PCs

KDEX5314-I

Network connection denied. Performed date=performed-date, Number of target computers=number-of-target-computers

KDEX5315-I

Network connection successful. Performed date=performed-date, Number of target computers=number-of-target-computers

KDEX5316-E

An error occurred in (JP1_ITDM2_Service). Error code=error-code (maintenance-code)

[Cause] A critical error occurred in the (JP1_ITDM2_Service).

[Action] Stop the (JP1_ITDM2_Service).

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX5317-E

Improper security status result. Host name=host-name-or-IP-address

[Cause] The computer does not have an agent installed.

[Action] Cancel the process for determining security status.

[Workaround] Install an agent on the computer indicated by the host name.

KDEX5319-E

An error occurred while sending e-mail notification to the system administrator. Failed to reach the mail server. Mail server host name=mail-server-host-name, Mail server port number=mail-server-port-number

[Cause] The host name or port number specified in the settings screen of the mail server is either invalid or the mail server is not in operation.

[Action] Cancel e-mail notification.

[Workaround] Check the host name and port number of the mail server, in the settings screen. Also check the operational status of the mail server. To check the mail server connectivity, send a test mail.

KDEX5320-E

An error occurred while sending e-mail notification to the system administrato. Invalid SMTP authentication information. Mail server host name=mail-server-host-name, Mail server port number=mail-server-port-number

[Cause] Incorrect SMTP authentication information in the mail server settings screen.

[Action] Cancel e-mail notification.

[Workaround] Check the SMTP authentication information specified in the settings screen of the mail server. To check the mail server connectivity, send a test mail.

KDEX5326-E

Failed to start the (JP1_ITDM2_Service). The port number is already in use. Error code=error-code (maintenance-code), Port number=port-number

[Cause] The port number is already in use.

[Action] Stop the(JP1_ITDM2_Service).

[Workaround] Change the port number and start the service (JP1_ITDM2_Service).

KDEX5335-W

Failed to retrieve added device information from the Active Directory server. An irretrievable Active Directory attribute is specified. List of attribute names=list-of-attribute-names

[Cause] An irretrievable Active Directory attribute is specified.

[Action] Cancel information retrieval from the added devices.

[Workaround] Check the settings for the added device information.

KDEX5336-I

Started the (JP1_ITDM2_Service).

KDEX5337-E

Failed to start the (JP1_ITDM2_Service).

KDEX5338-E

Failed to start the (JP1_ITDM2_Service). Setup is not complete.

[Cause] JP1/IT Desktop Management 2 - Manager Setup is not complete.

[Action] Cancel starting the(JP1_ITDM2_Service).

[Workaround] Retry starting the (JP1_ITDM2_Service) after the JP1/IT Desktop Management 2 - Manager Setup is completed.

KDEX5339-E

Failed to start the (JP1_ITDM2_Service). Error code=error-code (maintenance-code)

[Cause] A critical error has occurred in the service (JP1_ITDM2_Service).

[Action] Cancel the launch of the service (JP1_ITDM2_Service).

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX5340-I

Stopped the (JP1_ITDM2_Service).

KDEX5341-E

An error occurred in the (JP1_ITDM2_Service). Stopped the (JP1_ITDM2_Service).

KDEX5342-E

An error occurred in the (JP1_ITDM2_Service). Error code=error-code (maintenance-code)

[Cause] A critical error occurred in the (JP1_ITDM2_Service).

[Action] Stop the (JP1_ITDM2_Service).

[Workaround] Determine the cause of the error and use appropriate workarounds to solve the problem, and restart the (JP1_ITDM2_Service). Or, use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX5343-W

An error occurred while sending a user notification message. Agent is not installed in the computer. Host name=host-name-or-IP-address

[Cause] Agent is not installed in the computer.

[Action] Cancel the notification.

[Workaround] Install an agent to the computer indicated by the host name.

KDEX5344-W

An error occurred while controlling network connection. The computer does not have a network interface card. Host name=host-name-or-IP-address

[Cause] The computer does not have a network interface card.

[Action] Cancel the control of network connection.

[Workaround] Install a network interface card on the computer indicated by the host name.

KDEX5346-E

Failed to start the service(JP1_ITDM2_Service). The license has expired.

[Cause] Failed to start the service(JP1_ITDM2_Service) because the license has expired.

[Action] Cancel starting the service(JP1_ITDM2_Service).

[Workaround] Purchase a valid license.

KDEX5347-E

Failed to start the (JP1_ITDM2_Service). Setup, the database manager, or a command is in execution.

[Cause] The service (JP1_ITDM2_Service) was started while setup, the database manager, or a command was in execution.

[Action] Cancel starting the (JP1_ITDM2_Service).

[Workaround] Wait until the executing process (Setup, Database Manager, or command) ends, and then restart the (JP1_ITDM2_Service).

KDEX5352-E

An error occurred during e-mail notification to the administrator. The encrypted communication failed. Mail server host name=mail-server-host-name, Mail server port number=mail-server-port-number

[Cause] The following are possible causes:

(1) The mail certificate is not installed on the mail server.

(2) Incorrect authentication method settings for the mail server.

[Action] Cancel e-mail notification.

[Workaround]

(1) Install the mail certificate on the mail server.

(2) Check the authentication method settings for the mail server.

To check the mail server connectivity, send a test mail.

KDEX5353-I

The system is connected to the mail server.

KDEX5354-E

Failed to connect the system to the mail server.

KDEX5355-E

Failed to e-mail the Administrators.

[Cause] A critical error occurred during e-mail notification.

[Action] Cancel e-mail notification.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX5359-W

Failed to perform Automatic Windows Update. Agent is not installed. Host name=host-name-or-IP-address

[Cause] Agent is not installed.

[Action] Cancel automatic Windows Update.

[Workaround] Install Agent on the computer indicated in the above Host name.

KDEX5360-E

An error occurred in JP1_ITDM2_Service.

[Cause] An error occurred in the database.

[Action] Stop JP1_ITDM2_Service.

[Workaround] Set up JP1/IT Desktop Management 2 - Manager again.

KDEX5361-E

Failed to connect to the Active Directory server. A connection error has occurred. Error code=error-code, Host name=Active-Directory-server-host-name, Port number=port-number, Connection account=user-ID, Route path for information acquisition=root-OU

[Cause] The possible causes are given below:

(1) The specified host name is incorrect.

(2) The specified port number is incorrect.

(3) The Active Directory server is not running.

[Action] Cancel the acquisition of device and organizational information.

[Workaround]

(1) Check the specified host name in the Active Directory settings.

(2) Check the specified port number in the Active Directory settings.

(3) Check whether the Active Directory server is running.

To check the Active Directory server connectivity, test the connection to it.

KDEX5362-E

Failed to connect to the Active Directory server. Connection authentication has failed. Error code=error-code, Host name=Active-Directory-server-host-name, Port number=port-number, Connection account=user-ID, Route path for information acquisition=root-OU

[Cause] The specified account or password is incorrect.

[Action] Cancel the acquisition of device and organizational information.

[Workaround] Check the specified account and password in the Active Directory settings. To check the Active Directory server connectivity, test the connection.

KDEX5363-E

Failed to connect to the Active Directory server.

Could not find the specified domain. Error code=error-code, Host name=Active-Directory-server-host-name, Port number=port-number, Connection account=user-ID, Route path for information acquisition=root-OU

[Cause] The specified domain in the route path for acquiring Active Directory information is incorrect.

[Action] Cancel the acquisition of device and organizational information.

[Workaround] Check the specified domain in the Active Directory settings. To check the Active Directory server connectivity, test the connection.

KDEX5364-E

Failed to connect to the Active Directory server.

The specified route path for acquiring Active Directory information could not be found. Error code=error-code, Host name=Active-Directory-server-host-name, Port number=port-number, Connection account=user-ID, Route path for information acquisition=root-OU

[Cause] The specified OU in the route path for acquiring Active Directory information is incorrect.

[Action] Cancel the acquisition of device and organizational information.

[Workaround] Check the specified OU in the Active Directory settings. To check the Active Directory server connectivity, test the connection to it.

KDEX5365-E

Failed to connect to the Active Directory server. Could not establish encrypted communication.

Error code=error-code, Host name=Active-Directory-server-host-name, Port number=port-number, Connection account=user-ID, Route path for information acquisition=root-OU

[Cause] The possible causes are given below:

(1) The specified port number is incorrect.

(2) The certificate is not installed in the Active Directory server.

[Action] Cancel the acquisition of device and organizational information.

[Workaround]

(1) Check the specified port number in the Active Directory settings.

(2) Check whether the certificate is installed in the Active Directory server.

To check the Active Directory server connectivity, test the connection.

KDEX5366-I

Synchronization between JP1/IT Desktop Management 2 - Manager and Active Directory is complete.

KDEX5367-E

Failed to connect to Product Update. The Product Update URL or The proxy server settings is incorrect. Error code=error-code (maintenance-code)

[Cause] The specified Product Update URL or The proxy server settings is incorrect.

[Action] Cancel the Product Update connection.

[Workaround] Check the specified URL or The proxy server settings in the Product Update settings. To check the Product Update connectivity, test the connection to it.

KDEX5368-E

Failed to connect toProduct Update. The user ID or password is incorrect. Error code=error-code (maintenance-code)

[Cause] The specified user ID or password is incorrect.

[Action] Cancel the Product Update connection.

[Workaround] Check the specified user ID or password in the Product Update settings.

To check the Product Update connectivity, test the connection.

KDEX5369-E

Failed to connect to Product Update. Error code=error-code (maintenance-code)

[Cause] The proxy server settings has an error.

[Action] Cancel the connection to Product Update.

[Workaround] Check the specified proxy server settings. To check the Product Update connectivity, test the connection.

KDEX5370-E

The service(JP1_ITDM2_Service) will be terminated. The license has either expired or is invalid.

[Cause] The possible causes are given below:

(1) The license has expired.

(2) The license information is invalid.

[Action] Terminate the service(JP1_ITDM2_Service).

[Workaround]

(1) Purchase a valid license.

(2) Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX5371-I

Added update programs.

KDEX5372-E

Failed to add update program details.

KDEX5373-I

Added antivirus software information.

KDEX5374-E

Failed to add antivirus software information.

KDEX5375-I

Updated the definition file of Manager behavior.

KDEX5376-E

Failed to update the definition file of Manager behavior.

KDEX5377-I

Updated the agent version.

KDEX5378-E

Failed to update the agent version.

KDEX5379-I

Connected to the Microsoft site successfully.

KDEX5380-E

Failed to connect the Microsoft site.

KDEX5381-I

Based on the settings in securit policy settings, the mandatory Windows Update will be distributed. You can view the task progress status on the ITDM-compatible distribution screen. Task name=task-name

KDEX5382-E

Windows Update distribution task is terminated abnormally. Task name=task-name

[Cause] The possible causes are given below:

(1) The Windows Update File download failed.

(2) Windows Update File was not registered when you added Windows Update manually.

[Action] Cancel installation.

[Workaround]

(1) Check the proxy server settings of Product Update in Settings window and network connection status. Execute task again.

(2) Register Windows Update File. Execute task again.

KDEX5383-I

The definition file of Agent behavior was updated.

KDEX5384-E

Failed to update the definition file of Agent behavior.

KDEX5385-I

The JP1_ITDM_Remote Site Service started.

KDEX5386-E

The JP1_ITDM_Remote Site Service failed to start.

KDEX5387-E

The JP1_ITDM_Remote Site Service failed to start. Setup is not complete.

[Cause] Setup of JP1/IT Desktop Management - Manager is not complete.

[Action] Cancel startup of the JP1_ITDM_Remote Site Service.

[Workaround] After setup of JP1/IT Desktop Management - Manager is complete, restart the JP1_ITDM_Remote Site Service.

KDEX5388-E

The JP1_ITDM_Remote Site Service failed to start. (error code = error-code (maintenance-code))

[Cause] A critical error occurred in the JP1_ITDM_Remote Site Service.

[Action] Cancel startup of the JP1_ITDM_Remote Site Service.

[Workaround] Collect troubleshooting information, and contact Customer Support.

KDEX5389-I

The JP1_ITDM_Remote Site Service stopped.

KDEX5390-E

An error occurred in the JP1_ITDM_Remote Site Service. The JP1_ITDM_Remote Site Service will now stop.

KDEX5391-E

An error occurred in the JP1_ITDM_Remote Site Service. (error code = error-code (maintenance-code))

[Cause] A critical error occurred in the JP1_ITDM_Remote Site Service.

[Action] Stop the JP1_ITDM_Remote Site Service.

[Workaround] Following the instructions in the messages output before this message, remove the cause of the error, and then restart the JP1_ITDM_Remote Site Service. If the problem persists, use the troubleshooting information collection command to collect troubleshooting information, and contact Customer Support.

KDEX5392-E

An error occurred in the JP1_ITDM_Remote Site Service. (error code = error-code (maintenance-code))

[Cause] A critical error occurred in the JP1_ITDM_Remote Site Service.

[Action] Stop the JP1_ITDM_Remote Site Service.

[Workaround] Collect troubleshooting information, and contact Customer Support.

KDEX5393-E

The JP1_ITDM_Remote Site Service failed to start. The port number is already in use. (error code = error-code (maintenance-code), port number = port-number)

[Cause] The port number is already in use.

[Action] Stop the JP1_ITDM_Remote Site Service.

[Workaround] Change the port number, and then start the JP1_ITDM_Remote Site Service.

KDEX5394-E

The JP1_ITDM_Remote Site Service failed to start. Setup is in progress, or a command is executing.

[Cause] The JP1_ITDM_Remote Site Service started while setup was in progress or a command was executing.

[Action] Cancel startup of the JP1_ITDM_Remote Site Service.

[Workaround] Wait until setup or the command ends, and then restart the JP1_ITDM_Remote Site Service.

KDEX5395-E

Failed to start the service (JP1_ITDM2_Service). The license for this product has not been authenticated (registered).

[Cause] The service (JP1_ITDM2_Service) could not be started because the license for this product is not registered.

[Action] Cancels startup of the service (JP1_ITDM2_Service).

[Workaround] Authenticate (register) the license for this product.

KDEX5396-I

A connection to an MDM server was established. (MDM setting = MDM-setting-name)

KDEX5397-E

Failed to connect to an MDM server. (MDM setting = MDM-setting-name)

KDEX5399-E

Failed to start the service (JP1_ITDM2_Service). The data folder shared between servers cannot be accessed.

[Cause] Possible causes include the following:

(1) The database server is stopped.

(2) A network error occurred.

[Action] Cancels startup of the service (JP1_ITDM2_Service).

[Workaround]

(1) Start the database server, and then start the service (JP1_ITDM2_Service).

(2) Resolve the cause of the network failure, and then start the service (JP1_ITDM2_Service).

KDEX5400-E

Failed to start the service (JP1_ITDM2_Service). The data folder shared between servers cannot be accessed.

[Cause] The user name or password for connecting to the data folder shared between servers is incorrect.

[Action] Cancels startup of the service (JP1_ITDM2_Service).

[Workaround] Verify that the user name and password for connecting to the data folder shared between servers are correct. (This user name and password were specified during management server setup.) Then, start the service (JP1_ITDM2_Service).

KDEX5401-E

Failed to collect device information and organization information from the Active Directory server. (error code = error-code)

[Cause] An error occurred during collection of device information and organization information from the Active Directory server.

[Action] Cancels collection of device information and organization information.

[Workaround] Use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX5402-I

A smart device will be locked.

KDEX5403-E

Failed to lock a smart device.

KDEX5404-E

Failed to lock a smart device. (error code = error-code, MDM server host name = MDM-server-host-name, MDM server port number = MDM-server-port-number, proxy server IP address = proxy-server-IP-address, proxy server port number = proxy-server-port-number)

[Cause] Possible causes include the following:

(1) Connection to the MDM server failed.

(2) Connection to the proxy server failed.

(3) The MDM server is not running.

[Action] Cancels locking of the smart device.

[Workaround]

(1) Check the host name and port number of the MDM server that were set in the settings window for MDM linkage.

(2) Check the IP address and port number of the proxy server that were set in the settings window for MDM linkage.

(3) Check whether the MDM server is running.

KDEX5405-E

Failed to lock a smart device. (error code = error-code, MDM server user ID = MDM-server-user-ID)

[Cause] Authentication for connection to the MDM server failed.

[Action] Cancels locking of the smart device.

[Workaround] Check the user ID and password for the MDM server that were set in the settings window for MDM linkage.

KDEX5406-E

Failed to lock a smart device. (error code = error-code, proxy server IP address = proxy-server-IP-address, proxy server port number = proxy-server-port-number, proxy server user ID = proxy-server-user-ID)

[Cause] Authentication for connection to the proxy server failed.

[Action] Cancels locking of the smart device.

[Workaround] Check the IP address, port number, user ID, and password for the proxy server that were set in the settings window for MDM linkage.

KDEX5407-E

Failed to lock a smart device. (error code = error-code)

[Cause] Possible causes include the following:

(1) The applicable smart device is not being managed by the MDM system.

(2) The profile of the MDM system has been deleted from the smart device.

[Action] Cancels the locking of the smart device.

[Workaround] Verify the following, and then try collecting smart device information from the MDM server again.

(1) Has the smart device been specified as a managed device of the MDM system?

(2) Has the profile of the MDM system been installed on the smart device?

KDEX5409-E

Failed to lock a smart device. (error code = error-code)

[Cause] An MDM linkage error occurred.

[Action] Cancels locking of the smart device.

[Workaround] Collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX5410-I

The password of a smart device will be reset.

KDEX5411-E

Failed to reset the password of a smart device.

KDEX5412-E

Failed to reset the password of a smart device. (error code = error-code, MDM server host name = MDM-server-host-name, MDM server port number = MDM-server-port-number, proxy server IP address = proxy-server-IP-address, proxy server port number = proxy-server-port-number)

[Cause] Possible causes include the following:

(1) Connection to the MDM server failed.

(2) Connection to the proxy server failed.

(3) The MDM server is not running.

[Action] Cancels the reset of the smart device password.

[Workaround]

(1) Check the host name and port number of the MDM server that were set in the settings window for MDM linkage.

(2) Check the IP address and port number of the proxy server that were set in the settings window for MDM linkage.

(3) Check whether the MDM server is running.

KDEX5413-E

Failed to reset the password of a smart device. (error code = error-code, MDM server user ID = MDM-server-user-ID)

[Cause] Authentication for the MDM server failed.

[Action] Cancels the reset of the smart device password.

[Workaround] Check the user ID and password for the MDM server that were set in the settings window for MDM linkage.

KDEX5414-E

Failed to reset the passcode of a smart device. (error code = error-code, proxy server IP address = proxy-server-IP-address, proxy server port number = proxy-server-port-number, proxy server user ID = proxy-server-user-ID)

[Cause] Authentication for connection to the proxy server failed.

[Action] Cancels the reset of the smart device passcode.

[Workaround] Check the IP address, port number, user ID, and password for the proxy server that were set in the settings window for MDM linkage.

KDEX5415-E

Failed to reset the password of a smart device. (error code = error-code)

[Cause] The target smart device is not managed by the MDM system.

[Action] Cancels the reset of the smart device password.

[Workaround] Obtain device information from the MDM server.

KDEX5417-E

Failed to reset the password of a smart device. (error code = error-code)

[Cause] An MDM linkage error occurred.

[Action] Cancels the reset of the smart device password.

[Workaround] Collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX5418-I

A smart device will be initialized.

KDEX5419-E

Failed to initialize a smart device.

KDEX5420-E

Failed to initialize a smart device. (error code = error-code, MDM server host name = MDM-server-host-name, MDM server port number = MDM-server-port-number, proxy server IP address = proxy-server-IP-address, proxy server port number = proxy-server-port-number)

[Cause] Possible causes include the following:

(1) Connection to the MDM server failed.

(2) Connection to the proxy server failed.

(3) The MDM server is not running.

[Action] Cancels initialization of the smart device.

[Workaround]

(1) Check the host name and port number of the MDM server that were set in the settings window for MDM linkage.

(2) Check the IP address and port number of the proxy server that were set in the settings window for MDM linkage.

(3) Check whether the MDM server is running.

KDEX5421-E

Failed to initialize a smart device. (error code = error-code, MDM server user ID = MDM-server-user-ID)

[Cause] Authentication for connection to the MDM server failed.

[Action] Cancels initialization of the smart device.

[Workaround] Check the user ID and password for the MDM server that were set in the settings window for MDM linkage.

KDEX5422-E

Failed to initialize a smart device. (error code = error-code, proxy server IP address = proxy-server-IP-address, proxy server port number = proxy-server-port-number, proxy server user ID = proxy-server-user-ID)

[Cause] Authentication for connection to the proxy server failed.

[Action] Cancels initialization of the smart device.

[Workaround] Check the IP address, port number, user ID, and password for the proxy server that were set in the settings window for MDM linkage.

KDEX5423-E

Failed to initialize a smart device. (error code = error-code)

[Cause] Possible causes include the following:

(1) The applicable smart device is not being managed by the MDM system.

(2) The profile of the MDM system has been deleted from the smart device.

[Action] Cancels initialization of the smart device.

[Workaround] Verify the following, and then try collecting smart device information from the MDM server again.

(1) Has the smart device been specified as a managed device of the MDM system?

(2) Has the profile of the MDM system been installed on the smart device?

KDEX5425-E

Failed to initialize a smart device. (error code = error-code)

[Cause] An MDM linkage error occurred.

[Action] Cancels initialization of the smart device.

[Workaround] Collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX5426-E

Failed to synchronize device information with the MDM system. (MDM setting name = MDM-setting-name, error code = error-code, MDM server host name = MDM-server-host-name, MDM server port number = MDM-server-port-number, proxy server IP address = proxy-server-IP-address, proxy server port number = proxy-server-port-number)

[Cause] Possible causes include the following:

(1) Connection to the MDM server failed.

(2) Connection to the proxy server failed.

(3) The MDM server is not running.

[Action] Cancels synchronization of device information with the MDM system.

[Workaround]

(1) Check the host name and port number of the MDM server that were specified in the settings window for MDM linkage.

(2) Check the IP address and port number of the proxy server that were specified in the settings window for MDM linkage.

(3) Check whether the MDM server is running.

KDEX5427-E

Failed to synchronize device information with the MDM system. (MDM setting name = MDM-setting-name, error code = error-code, MDM server user ID = MDM-server-user-ID)

[Cause] Authentication for connection to the MDM server failed.

[Action] Cancels synchronization of device information with the MDM system.

[Workaround] Check the user ID and password for the MDM server that were specified in the settings window for MDM linkage.

KDEX5428-E

Failed to synchronize device information with the MDM system. (MDM setting name = MDM-setting-name, error code = error-code, proxy server IP address = proxy-server-IP-address, proxy server port number = proxy-server-port-number, proxy server user ID = proxy-server-user-ID)

[Cause] Authentication for connection to the proxy server failed.

[Action] Cancels synchronization of device information with the MDM system.

[Workaround] Check the IP address, port number, user ID, and password for the proxy server that were set in the settings window for MDM linkage.

KDEX5430-E

Failed to synchronize device information with the MDM system. (error code = error-code)

[Cause] An MDM linkage error occurred.

[Action] Cancels synchronization of device information with the MDM system.

[Workaround] Collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX5431-I

Synchronization of device information with the MDM system was completed. (MDM setting name = MDM-setting-name)

KDEX5432-I

Synchronization of device information with the MDM system will now start. (MDM setting name = MDM-setting-name)

KDEX5433-E

Failed to start the service (JP1_ITDM_Remote Site Service). The command for deleting operation log data (deletelog) is not finished.

[Cause] The command for deleting operation log data is not finished or has failed.

[Action] Cancels the start of the service (JP1_ITDM_Remote Site Service).

[Workaround] After the command for deleting operation log data ends normally, start the service (JP1_ITDM_Remote Site Service).

KDEX5434-E

Failed to delete a smart device. (host name = host-name, error code = error-code)

[Cause] A database access error might have occurred.

[Action] Cancels the deletion of the smart device.

[Workaround] In the settings window, select [Discover Devices], and [Managed Devices]. Then, select the devices that you want to delete, and delete them.

KDEX5435-E

An error occurred in the service (JP1_ITDM2_Service). The data folder shared between servers cannot be accessed.

[Cause] Possible causes include the following:

(1) The database server is not running.

(2) A network failure occurred.

[Action] Continues processing of the service (JP1_ITDM2_Service).

[Workaround] If the error occurs repeatedly, take the following actions:

(1) Start the database server.

(2) Resolve the cause of the network failure.

KDEX5436-E

An error occurred in the service (JP1_ITDM2_Service). The data folder shared between servers cannot be accessed.

[Cause] The user name or password for connecting to the data folder shared between servers is incorrect.

[Action] Continues processing of the service (JP1_ITDM2_Service).

[Workaround] If the error occurs repeatedly, verify that the user name and password for connecting to the data folder shared between servers are correct. (This user name and password were specified during management server setup.)

KDEX5437-I

The SAMAC software dictionary was updated.

KDEX5438-E

Failed to update the SAMAC software dictionary.

KDEX5440-E

Failed to synchronize device information with the MDM system. (MDM setting name = MDM-setting-name, error code = error-code)

[Cause] An MDM linkage error occurred.

[Action] Cancels synchronization of device information with the MDM system.

[Workaround] Collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX5450-E

Failed to lock a smart device.

[Cause] The server certificate of the MDM server is invalid.

[Action] Cancels the locking of the smart device.

[Workaround] Execute the keytool command to check whether the server certificate has been imported. If it has not, execute the keytool command to import the server certificate. For details about the keytool command, see the relevant documentation.

KDEX5451-E

Failed to lock a smart device. (error code = error-code)

[Cause] The applicable smart device is excluded from management by the MDM system.

[Action] Cancels the locking of the smart device.

[Workaround] From the MDM system, specify the applicable smart device as a managed device.

KDEX5452-E

Failed to unlock the pass code of a smart device.

[Cause] The server certificate of the MDM server is invalid.

[Action] Cancels the unlocking of the pass code of the smart device.

[Workaround] Execute the keytool command to check whether the server certificate has been imported. If it has not, execute the keytool command to import the server certificate. For details about the keytool command, see the relevant documentation.

KDEX5453-E

Failed to unlock the pass code of a smart device. (error code = error-code)

[Cause] The applicable smart device is excluded from management by the MDM system.

[Action] Cancels the unlocking of the pass code of the smart device.

[Workaround] From the MDM system, specify the applicable smart device as a managed device.

KDEX5454-E

Failed to initialize a smart device.

[Cause] The server certificate of the MDM server is invalid.

[Action] Cancels initialization of the smart device.

[Workaround] Execute the keytool command to check whether the server certificate has been imported. If it has not, execute the keytool command to import the server certificate. For details about the keytool command, see the relevant documentation.

KDEX5455-E

Failed to initialize a smart device. (error code = error-code)

[Cause] The applicable smart device is excluded from management by the MDM system.

[Action] Cancels initialization of the smart device.

[Workaround] From the MDM system, specify the applicable smart device as a managed device.

KDEX5456-E

Failed to synchronize device information with the MDM system. (MDM setting name = MDM-setting-name)

[Cause] The server certificate of the MDM server is invalid.

[Action] Cancels synchronization of device information with the MDM system.

[Workaround] Execute the keytool command to check whether the server certificate has been imported. If it has not, execute the keytool command to import the server certificate. For details about the keytool command, see the relevant documentation.

KDEX5457-E

An error occurred during the attempt to access the sdm_import.properties definition file.

[Cause] Possible causes include the following:

(1) You do not have the necessary permissions to access the sdm_import.properties definition file.

(2) An I/O error occurred.

(3) The content of the sdm_import.properties definition file is invalid.

[Action] Continues processing without loading software information.

[Workaround]

(1) Make sure you have the necessary permissions to access the sdm_import.properties definition file.

(2) Verify that no disk failure has occurred.

(3) Check the content of the sdm_import.properties definition file.

If the problem persists, collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX5458-E

An error occurred during the attempt to access the database of the MDM-setting-name server.

[Cause] Possible causes are as follows:

(1) The instance of JP1/ITDM2 - Smart Device Manager to be linked is not running.

(2) The host whose host name is specified in the sdm_import.properties definition file cannot be accessed from the management server.

[Action] Continues processing without loading software information.

[Workaround]

(1) Start the instance of JP1/ITDM2 - Smart Device Manager to be linked.

(2) Check the host name that is specified in the sdm_import.properties definition file.

If the problem persists, collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX5460-I

Collection of the revision history started.

KDEX5461-I

Collection of the revision history ended.

KDEX5462-E

Collection of the revision history failed.

[Cause] A fatal error occurred during collection of the revision history.

[Action] Cancels collection of the revision history.

[Workaround] Collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX5463-E

Failed to output the file for saving the revision history.

[Cause] Possible causes include the following:

(1) You do not have access rights for the output folder for saving the revision history.

(2) An I/O error occurred.

[Action] Cancels output of the file for saving the revision history.

[Workaround]

(1) Verify that you have access rights for the output folder for saving the revision history.

(2) Verify that no disk failure has occurred.

If the problem persists, collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX5464-I

A request to allow connections to the network was sent to JP1/NETM/NM - Manager.

KDEX5465-I

A request to reject connections to the network was sent to JP1/NETM/NM - Manager.

KDEX5466-E

The request to JP1/NETM/NM - Manager to allow connections to the network failed.

[Cause] The JP1/NETM/NM - Manager service has not been started on the management server.

[Action] Stops allowing connections to the network.

[Workaround] Start the JP1/NETM/NM - Manager service on the management server.

KDEX5467-E

The request to JP1/NETM/NM - Manager to reject connections to the network failed.

[Cause] The JP1/NETM/NM - Manager service has not been started on the management server.

[Action] Stops rejecting connections to the network.

[Workaround] Start the JP1/NETM/NM - Manager service on the management server.

KDEX5468-E

The request to JP1/NETM/NM - Manager to allow connections to the network failed.

[Cause] JP1/NETM/NM - Manager has not been installed on the management server.

[Action] Stops allowing connections to the network.

[Workaround] Install JP1/NETM/NM - Manager on the management server.

KDEX5469-E

The request to JP1/NETM/NM - Manager to reject connections to the network failed.

[Cause] JP1/NETM/NM - Manager has not been installed on the management server.

[Action] Stops rejecting connections to the network.

[Workaround] Install JP1/NETM/NM - Manager on the management server.

KDEX5470-E

The request to JP1/NETM/NM - Manager to allow connections to the network failed. (error code = error-code (maintenance-code))

[Cause] A fatal error occurred while connections to the network were being allowed.

[Action] Stops allowing connections to the network.

[Workaround] If this error occurs repeatedly, collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX5471-E

The request to JP1/NETM/NM - Manager to reject connections to the network failed. (error code = error-code (maintenance-code))

[Cause] A fatal error occurred while connections to the network were being rejected.

[Action] Stops rejecting connections to the network.

[Workaround] If this error occurs repeatedly, collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX5472-I

Operation log data was successfully stored.

KDEX5473-E

Failed to store operation log data. (cause and workaround number = cause and workaround number)

[Cause] The possible causes are as follows:

(1) A temporary error occurred during data processing.

(2) An I/O error occurred in the data folder or a local data folder.

(3) A connection to the operation log storage folder could not be established.

(4) Authentication to the operation log storage folder failed.

(5) An I/O error occurred in the operation log storage folder.

(6) The operation log storage folder is not specified.

(7) A connection to the operation log storage folder could not be established because anonymous access to shared folders is restricted on the management server.

[Action] Cancels the storage of the operation log data.

[Workaround]

(1) If the error occurs repeatedly, use the troubleshooting information acquisition command to acquire troubleshooting information, and then contact the support service.

(2) Check whether the data folder or the local folder is accessible, and whether the disk space is sufficient. If the disk does not have enough free space, increase the free disk space, or specify (during setup) a folder on a disk that has enough free space, and then restart the management server.

(3) Check whether the operation log storage folder specified during setup exists, and whether a connection can be established.

(4) Check whether a connection to the operation log storage folder can be established by using the user ID and password specified during setup.

(5) Check whether the operation log storage folder is accessible, and whether the disk space is sufficient.

(6) Check whether the operation log storage folder was specified during setup.

(7) On the management server, create a user account with the username and password that were specified during setup for connections to the operation log storage folder.

KDEX5474-I

Operation log data was successfully acquired manually.

KDEX5475-E

An error occurred while manually acquiring operation log data. (cause and workaround number = cause and workaround number, detailed information = detailed information)

[Cause] The possible causes are as follows:

(1) A temporary error occurred during data processing.

(2) An I/O error occurred in the data folder or a local data folder.

(3) A connection to the operation log storage folder could not be established.

(4) Authentication to the operation log storage folder failed.

(5) An I/O error occurred in the operation log storage folder.

(6) Stored files do not exist in the operation log storage folder.

(7) The operation log storage folder is not specified.

(8) A connection to the operation log storage folder could not be established because anonymous access to shared folders is restricted on the management server.

(9) The operation log file cannot be added to the database because the operation log file shown in detailed information is corrupt.

(10) The disk capacity required to expand the database was insufficient.

(11) The total number of dates of automatically-acquired operation logs and dates of manually-acquired operation logs exceeded the maximum value that can be specified for the number of dates to be stored in the operation log database.

[Action] Cancels the manual acquisition of operation log data.

[Workaround]

(1) If the error occurs repeatedly, use the troubleshooting information acquisition command to acquire troubleshooting information, and then contact the support service.

(2) Check whether the data folder or the local folder is accessible, and whether the disk space is sufficient. If the disk does not have enough free space, increase the free disk space, or specify (during setup) a folder on a disk that has enough free space, and then restart the management server.

(3) Check whether the operation log storage folder specified during setup exists, and whether a connection can be established.

(4) Check whether a connection to the operation log storage folder can be established by using the user ID and password specified during setup.

(5) Check whether the operation log storage folder is accessible, and whether the disk space is sufficient.

(6) If the stored files were moved to another folder, restore the files saved in the operation log storage folder, and then acquire the operations log data again.

(7) Check whether the operation log storage folder was specified during setup.

(8) On the management server, create a user account with the username and password that were specified during setup for connections to the operation log storage folder.

(9) Delete the operation log file shown in detailed information.

(10) In the settings window, reconfigure the server, and then restore the database by using the database manager.

(11) In the list of operation logs in the security window, delete any unnecessary operation logs that were manually acquired.

KDEX5477-I

The processing to periodically export operation log data was successfully completed.

KDEX5478-E

An error occurred during the processing to periodically export operation log data. (cause and workaround number = cause and workaround number)

[Cause] The possible causes are as follows:

(1) A temporary error occurred during data processing.

(2) An I/O error occurred in the data folder or a local data folder.

(3) A connection to the operation log storage folder could not be established.

(4) Authentication to the operation log storage folder failed.

(5) An I/O error occurred in the operation log storage folder.

(6) The operation log storage folder is not specified.

(7) A connection to the operation log storage folder could not be established because anonymous access to shared folders is restricted on the management server.

[Action] Cancels the processing to periodically export operation log data.

[Workaround]

(1) If the error occurs repeatedly, use the troubleshooting information acquisition command to acquire troubleshooting information, and then contact the support service.

(2) Check whether the data folder or the local folder is accessible, and whether the disk space is sufficient. If the disk does not have enough free space, increase the free disk space, or specify (during setup) a folder on a disk that has enough free space.

(3) Check whether the operation log storage folder specified during setup exists, and whether a connection can be established.

(4) Check whether a connection to the operation log storage folder can be established by using the user ID and password specified during setup.

(5) Check whether the operation log storage folder is accessible, and whether the disk space is sufficient.

(6) Check whether the operation log storage folder was specified during setup.

(7) On the management server, create a user account with the username and password that were specified during setup for connection to the operation log storage folder.

KDEX5479-E

An error occurred while automatically acquiring operation log data. (cause and workaround number = cause and workaround number)

[Cause] The possible causes are as follows:

(1) A temporary error occurred during data processing.

(2) An I/O error occurred in the data folder or a local data folder.

(3) A connection to the operation log storage folder could not be established.

(4) Authentication to the operation log storage folder failed.

(5) An I/O error occurred in the operation log storage folder.

(6) The operation log storage folder is not specified.

(7) A connection to the operation log storage folder could not be established because anonymous access to shared folders is restricted on the management server.

(8) The disk capacity required to expand the database was insufficient.

(9) The total number of dates of automatically-acquired operation logs and dates of manually-acquired operation logs exceeded the maximum value that can be specified for the number of dates to be stored in the operation log database.

[Action] Cancels the processing to automatically acquire operation log data.

[Workaround]

(1) If the error occurs repeatedly, use the troubleshooting information acquisition command to acquire troubleshooting information, and then contact the support service.

(2) Check whether the data folder or the local folder is accessible, and whether the disk space is sufficient. If the disk does not have enough free space, increase the free disk space, or specify (during setup) a folder on a disk that has enough free space.

(3) Check whether the operation log storage folder specified during setup exists, and whether a connection can be established.

(4) Check whether a connection to the operation log storage folder can be established by using the user ID and password specified during setup.

(5) Check whether the operation log storage folder is accessible, and whether the disk space is sufficient.

(6) Check whether the operation log storage folder was specified during setup.

(7) On the management server, create a user account with the username and password that were specified during setup for connection to the operation log storage folder.

(8) In the settings window, reconfigure the server, and then restore the database by using the database manager.

(9) In the list of operation logs in the security window, delete any unnecessary operation logs that were manually acquired.

KDEX5480-E

An error occurred while updating operation log date information. (cause and workaround number = cause and workaround number)

[Cause] The possible causes are as follows:

(1) A temporary error occurred during data processing.

(2) An I/O error occurred in the data folder or the local data folder.

(3) A connection to the operation log storage folder could not be established.

(4) Authentication to the operation log storage folder failed.

(5) An I/O error occurred in the operation log storage folder.

(6) The operation log storage folder is not specified.

(7) A connection to the operation log storage folder could not be established because anonymous access to shared folders is restricted on the management server.

[Action] Cancels the update of operation log date information.

[Workaround]

(1) If the error occurs repeatedly, use the troubleshooting information acquisition command to acquire troubleshooting information, and then contact the support service.

(2) Check whether the data folder or the local folder is accessible, and whether the disk space is sufficient. If the disk does not have enough free space, increase the free disk space, or specify (during setup) a folder on a disk that has enough free space.

(3) Check whether the operation log storage folder specified during setup exists, and whether a connection can be established.

(4) Check whether a connection to the operation log storage folder can be established by using the user ID and password specified during setup.

(5) Check whether the operation log storage folder is accessible, and whether the disk space is sufficient.

(6) Check whether the operation log storage folder was specified during setup.

(7) On the management server, create a user account with the username and password that were specified during setup for connection to the operation log storage folder.

KDEX5481-E

Failed to expand the operation log database.

[Cause] No free space for the operation log database exists.

[Action] Cancels the expansion of the operation log database.

[Workaround] Free up space, and then restart the service of management servers. If free space is sufficient and the error occurs repeatedly, use the troubleshooting information acquisition command to acquire troubleshooting information, and then contact the support service.

KDEX5482-I

The deletion of the operation logs that exceeded the storage period from the operation log database, and the recreation of the index information of the operation log database started. The multi-tenant management server does not perform re-creation of the index information.

KDEX5483-I

The deletion of the operation logs that exceeded the storage period from the operation log database, and the recreation of the index information of the operation log database finished. The multi-tenant management server does not perform re-creation of the index information.

KDEX5484-E

Errors occurred during the deletion of the operation logs that exceeded the storage period from the operation log database, and the recreation of the index information of the operation log database. The multi-tenant management server does not perform re-creation of the index information. (cause and workaround number = cause and workaround number)

[Cause] The possible causes are as follows:

(1) A temporary error occurred during data processing.

(2) An I/O error occurred in a local data folder.

(3) An error occurred in the operation log database.

[Action] Cancels the deletion of the operation logs that exceeded the storage period from the operation log database, and the recreation of the index information of the operation log database.

[Workaround]

(1) If the error occurs repeatedly, use the troubleshooting information acquisition command to acquire troubleshooting information, and then contact the support service.

(2) Check whether the data folder or the local folder is accessible, and whether the disk space is sufficient. If the disk does not have enough free space, increase the free space on the disk, or specify (during setup) a folder on a disk that has enough free space, and then restart management server.

(3) Use Setup to rebuild the server, then use Database Manager to restore the database.

KDEX5501-I

Database maintenance started.

KDEX5502-I

Database maintenance finished.

KDEX5503-I

The aggregation processing to create a report started. (aggregation processing target = aggregation-processing-target)

KDEX5504-I

The aggregation processing to create a report finished. (aggregation processing target = aggregation-processing-target)

KDEX5505-I

The automatic maintenance of devices has started.

KDEX5506-I

The automatic maintenance of devices is complete.

KDEX5507-E

An error occurred during the automatic maintenance of devices.

[Cause] The system clock of the server is incorrect.

[Action] Cancels the automatic maintenance of devices.

[Workaround] Set the correct time for the system clock of the server. If the problem persists, collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX5508-I

Device information was deleted during the automatic maintenance of devices. (type of detection condition = type of detection condition, detection condition name = detection condition name, device type = device type, host name = host name, IP address = IP address, host ID = host ID, MAC address = MAC address, user name = user name, last alive confirmation date/time = last alive confirmation date/time, host ID of duplicate devices = host ID of duplicate devices)

KDEX5509-I

During the processing to evaluate the security status of update programs, The article ID of the modified rollup updates (the update program released on released date to address issues in The article ID of the flawed rollup updates) was added to the list of update programs whose security status is subject to evaluation. (exclusion setting of the update program The article ID of the flawed rollup updates = Exclusion setting)

KDEX5510-I

No changes were made to the list of update programs whose security status is subject to evaluation.

KDEX5511-I

Security judgment started.

Note: Output for a management server with the large-scale management option enabled.

KDEX5512-I

Security judgment finished.

Note: Output for a management server with the large-scale management option enabled.

KDEX5513-E

Failed to lock smart device. (MDM setting name = MDM-setting-name, error code = error-code, application (client) ID = application-(client)-ID, directory (tenant) ID = directory-(tenant)-ID)

[Cause] Authentication for connection to Microsoft Intune failed.

[Action] Cancel smart devices locking.

[Workaround] Review the following configuration information, or the certificate file.

- Application (client) ID

- Directory (tenant) ID

- Client secret value

If the problem is not found above, please review the API permission settings of the app registered on Microsoft Entra ID.

KDEX5514-E

Failed to lock smart device. (MDM setting name = MDM-setting-name, error code = error-code, MDM server host name = MDM-server-host-name, MDM server port number = MDM-server-port-number, proxy server IP address = proxy-server-IP-address, proxy server port number = proxy-server-port-number, proxy server user ID = proxy-server-user-ID)

[Cause] Possible causes are as follow.

(1) Connection to Microsoft Intune failed.

(2) Connection to proxy server failed.

(3) Microsoft Intune's server certificate is invalid.

(4) An unsupported operation was performed in Microsoft Intune.

[Action] Cancel smart devices locking.

[Workaround] Review the following setting information set on the MDM linkage setting screen, or the certificate file.

- MDM server host name

- MDM server port number

- Proxy server settings

If the issue is not found above, please run the keytool command to check if the required server certificate has been imported. If it has not been imported, run the keytool command to import the server certificate.

If the problem is not found above, review configuration item of MDM server information and access permission setting of API of app registered with Microsoft Entra ID.

For cause (4), you cannot perform operations that are not supported by Microsoft Intune.

KDEX5515-E

Failed to lock smart device. (MDM setting name = MDM-setting-name, error code = error-code)

[Cause] An error occurred in Microsoft Intune.

[Action] Cancel smart devices locking.

[Workaround] Check if there is a problem with Microsoft Intune.

KDEX5516-E

Failed to lock smart device. (MDM setting name = MDM-setting-name, error code = error-code)

[Cause] Certificate file not found.

[Action] Cancel smart devices locking.

[Workaround] Store the certificate file (IntuneCert.pem) in the mgr\temp folder under the installation folder. For a multi-tenant management server, store the certificate file in the mgr\tenant\tenant-name\mgr\temp folder.

KDEX5517-E

Failed to initialize smart device. (MDM setting name = MDM-setting-name, error code = error-code, application (client) ID = application-(client)-ID, directory (tenant) ID = directory-(tenant)-ID)

[Cause] Authentication for connection to Microsoft Intune failed.

[Action] Cancels initialization of the smart device.

[Workaround] Review the following setting information set on the MDM linkage setting screen, or the certificate file.

- Application (client) ID

- Directory (tenant) ID

- Client secret value

If the problem is not found above, please review the API permission settings of the app registered on Microsoft Entra ID.

KDEX5518-E

Failed to initialize smart device. (MDM setting name = MDM-setting-name, error code = error-code, MDM server host name = MDM-server-host-name, MDM server port number = MDM-server-port-number, proxy server IP address = proxy-server-IP-address, proxy server port number = proxy-server-port-number, proxy server user ID = proxy-server-user-ID)

[Cause] Possible causes are as follow.

(1) Connection to Microsoft Intune failed.

(2) Connection to proxy server failed.

(3) Microsoft Intune's server certificate is invalid.

[Action] Cancels initialization of the smart device.

[Workaround] Review the following setting information set on the MDM linkage setting screen, or the certificate file.

- MDM server host name

- MDM server port number

- Proxy server settings

If the issue is not found above, please run the keytool command to check if the required server certificate has been imported. If it has not been imported, run the keytool command to import the server certificate.

If the problem is not found above, review configuration item of MDM server information and access permission setting of API of app registered with Microsoft Entra ID.

KDEX5519-E

Failed to initialize smart device. (MDM setting name = MDM-setting-name, error code = error-code)

[Cause] An error occurred in Microsoft Intune.

[Action] Cancels initialization of the smart device.

[Workaround] Check if there is a problem with Microsoft Intune.

KDEX5520-E

Failed to initialize smart device. (MDM setting name = MDM-setting-name, error code = error-code)

[Cause] Certificate file not found.

[Action] Cancels initialization of the smart device.

[Workaround] Store the certificate file (IntuneCert.pem) in the mgr\temp folder under the installation folder. For a multi-tenant management server, store the certificate file in the mgr\tenant\tenant-name\mgr\temp folder.

KDEX5521-E

Failed to synch smart device with MDM system. (MDM setting name = MDM-setting-name, error code = error-code, application (client) ID = application-(client)-ID, directory (tenant) ID = directory-(tenant)-ID)

[Cause] Authentication for connection to Microsoft Intune failed.

[Action] Cancels synchronization of device information with the MDM system.

[Workaround] Review the following setting information set on the MDM linkage setting screen, or the certificate file.

- Application (client) ID

- Directory (tenant) ID

- Client secret value

If the problem is not found above, please review the API permission settings of the app registered on Microsoft Entra ID.

KDEX5522-E

Failed to synch smart device with MDM system. (MDM setting name = MDM-setting-name, error code = error-code, MDM server host name = MDM-server-host-name, MDM server port number = MDM-server-port-number, proxy server IP address = proxy-server-IP-address, proxy server port number = proxy-server-port-number, proxy server user ID = proxy-server-user-ID)

[Cause] Possible causes are as follow.

(1) Connection to Microsoft Intune failed.

(2) Connection to proxy server failed.

(3) Microsoft Intune's server certificate is invalid.

[Action] Cancels synchronization of device information with the MDM system.

[Workaround] Review the following setting information set on the MDM linkage setting screen, or the certificate file.

- MDM server host name

- MDM server port number

- Proxy server settings

If the issue is not found above, please run the keytool command to check if the required server certificate has been imported. If it has not been imported, run the keytool command to import the server certificate.

If the problem is not found above, review configuration item of MDM server information and access permission setting of API of app registered with Microsoft Entra ID.

KDEX5523-E

Failed to synch smart device with MDM system. (MDM setting name = MDM-setting-name, error code = error-code)

[Cause] An error occurred in Microsoft Intune.

[Action] Cancels synchronization of device information with the MDM system.

[Workaround] Check if there is a problem with Microsoft Intune.

KDEX5524-E

Failed to synch smart device with MDM system. (MDM setting name = MDM-setting-name, error code = error-code)

[Cause] Certificate file not found.

[Action] Cancels synchronization of device information with the MDM system.

[Workaround] Store the certificate file (IntuneCert.pem) in the mgr\temp folder under the installation folder. For a multi-tenant management server, store the certificate file in the mgr\tenant\tenant-name\mgr\temp folder.

KDEX5525-I

Retrieves malware infection information. MDM setting name = MDM-setting-name

KDEX5526-E

Failed to retrieve malware infection information. MDM setting name = MDM-setting-name, error code = error-code, application (client) ID = (client) ID, directory (tenant) ID = (tenant) ID

[Cause] Authentication for connection to Microsoft Intune failed.

[Action] Cancels retrieval of malware infection information.

[Workaround] Review the following setting information set on the MDM linkage setting screen:

- Application (client) ID

- Directory (tenant) ID

- Client secret value

If no issues are found above, review the access permission setting of the API of the app registered with Microsoft Entra ID.

KDEX5527-E

Failed to retrieve malware infection information. MDM setting name = MDM-setting-name, error code = error-code, MDM server host name = MDM-server-host-name, MDM server port number = MDM-server-port-number, proxy server IP address = proxy-server-IP-address, proxy server port number = proxy-server-port-number, proxy server user ID = proxy-server-user-ID

[Cause] Possible causes are as follows:

(1) Connection to Microsoft Intune failed.

(2) Connection to the proxy server failed.

(3) Microsoft Intune's server certificate is invalid.

[Action] Cancels retrieval of malware infection information.

[Workaround] Review the following setting information set on the MDM linkage setting screen, or the certificate file:

- MDM server host name

- MDM server port number

- Proxy server settings

If the issue is not found above, please run the keytool command to check if the server certificate has been imported. If it has not been imported, run the keytool command to import the server certificate.

In addition, if no issues are found above, review the configuration items of MDM server information and the access permission setting of the API of the app registered with Microsoft Entra ID.

KDEX5528-E

Failed to retrieve malware infection information. MDM setting name = MDM-setting-name, error code = error-code)

[Cause] An error occurred in Microsoft Intune.

[Action] Cancels retrieval of malware infection information.

[Workaround] Check if there is an issue with Microsoft Intune.

KDEX5529-E

Failed to retrieve malware infection information. MDM setting name = MDM-setting-name, error code = error-code)

[Cause] Certificate file not found.

[Action] Cancels retrieval of malware infection information.

[Workaround] Store the certificate file (IntuneCert.pem) in the mgr\temp folder under the installation folder. For a multi-tenant management server, store the certificate file in the mgr\tenant\tenant name\mgr\temp folder.

KDEX5530-E

An error occurred during malware-infected device control. MDM setting name = MDM-setting-name, error code = error-code

[Cause] An error occurred during malware-infected device control.

[Action] Cancels malware-infected device control.

[Workaround] Collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX5531-I

Retrieval of malware infection information completed. MDM setting name = MDM-setting-name

KDEX5533-E

Failed to synchronize device information with the MDM system. MDM setting name = MDM-setting-name, error code = error-code

[Cause] Authentication for connection to Google Workspace failed.

(1) The secret key file is invalid.

(2) The service account that created the secret key is disabled.

(3) Proof of domain ownership for Google Workspace is incomplete.

[Action] Cancels synchronization of device information with the MDM system.

[Workaround] Register the correct secret key file. If no issues are found with the secret key file, review the settings for Google Workspace.

KDEX5534-E

Failed to synchronize device information with the MDM system. MDM setting name = MDM-setting-name, error code = error-code, proxy server IP address = proxy-server-IP-address, proxy server port number = proxy-server-port-number, proxy server user ID = proxy-server-user-ID

[Cause] Possible causes are as follows:

(1) Connection to Google Workspace failed.

(2) Connection to the proxy server failed.

(3) Google Workspace's server certificate is invalid.

[Action] Cancels synchronization of device information with the MDM system.

[Workaround] Review the following setting information set on the MDM linkage setting screen:

- GWS administrator user

- Secret key file

- Import organization

- Proxy server settings

If the issue is not found above, please run the keytool command to check if the server certificate has been imported. If it has not been imported, run the keytool command to import the server certificate.

In addition, if no issues are found above, review the settings for Google Workspace.

KDEX5535-E

Failed to synchronize device information with the MDM system. (MDM setting name = MDM-setting-name, error code = error-code)

[Cause] Possible causes are as follows:

(1) Exceeded the request limit per user.

(2) Reached the simultaneous request limit.

[Action] Cancels synchronization of device information with the MDM system.

[Workaround] Wait for a while and try again. If the error keeps recurring, do the following:

(1) Check if there is an issue with Google Workspace.

If the problem still persists, use the troubleshooting information acquisition command to acquire troubleshooting information, and then contact the support service.

KDEX5536-E

Failed to synchronize device information with the MDM system. MDM setting name = MDM-setting-name, error code = error-code

[Cause] Secret key file not found.

[Action] Cancels synchronization of device information with the MDM system.

[Workaround] Re-register the secret key file.

KDEX5537-E

Failed to synchronize device information with the MDM system. MDM setting name = MDM-setting-name, error code = error-code

[Cause] An error occurred in Google Workspace.

[Action] Cancels synchronization of device information with the MDM system.

[Workaround] Check if there is a problem with Google Workspace.

KDEX5700-W

Insufficient hard disk space for Database, Data, Operation Log Database, or Operation Log Backup.

[Cause] Insufficient hard disk space for Database, Data, Operation Log Database, or Operation Log Backup.

[Action] None.

[Workaround] Increase hard disk space, or specify any other path for Database, Data, Operation Log Database, or Operation Log Backup on a hard disk with sufficient space.

KDEX5701-W

Insufficient hard disk space for Database, Data, Operation Log Database, or Operation Log Backup. A database failure might occur.

[Cause] Insufficient hard disk space for Database, Data, Operation Log Database, or Operation Log Backup.

[Action] None.

[Workaround] Increase hard disk space, or specify any other path for Database, Data, Operation Log Database, or Operation Log Backup on a hard disk with sufficient space.

KDEX6110-I

The (JP1_ITDM2_Agent Control) service will be started.

KDEX6111-E

Failed to start the (JP1_ITDM2_Agent Control) service.

KDEX6112-E

Failed to start the (JP1_ITDM2_Agent Control) service.

[Cause] Failed to start the (JP1_ITDM2_Agent Control) service.

[Action] Stop the (JP1_ITDM2_Agent Control) service.

[Workaround] Start the (JP1_ITDM2_Agent Control) service again. If the problem persists, use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX6113-E

Because JP1/IT Desktop Management 2 - Manager setup is incomplete, startup of the (JP1_ITDM2_Agent Control) service failed.

[Cause] Because JP1/IT Desktop Management 2 - Manager setup is incomplete, the (JP1_ITDM2_Agent Control) service could not be started.

[Action] Stops the (JP1_ITDM2_Agent Control) service.

[Workaround] After JP1/IT Desktop Management 2 - Manager setup is complete, start the (JP1_ITDM2_Agent Control) service.

KDEX6114-E

Failed to start the (JP1_ITDM2_Agent Control) service. The license has expired.

[Cause] Failed to start the (JP1_ITDM2_Agent Control) service because the license has expired.

[Action] Cancels starting the (JP1_ITDM2_Agent Control) service.

[Workaround] Purchase a valid license.

KDEX6115-E

Failed to start the (JP1_ITDM2_Agent Control) service. Setup, the database manager, or a command is in execution.

[Cause] The (JP1_ITDM2_Agent Control) service was started while setup, the database manager, or a command was in execution.

[Action] Cancel starting the (JP1_ITDM2_Agent Control) service.

[Workaround] Wait until the executing process (Setup, Database Manager, or command) ends, and then restart the (JP1_ITDM2_Agent Control) service.

KDEX6116-E

Service (JP1_ITDM2_Agent Control) error occurred.

[Cause] The RD area has blocked the service.

[Action] Service (JP1_ITDM2_Agent Control) has stopped.

[Workaround] JP1_ITDM2_Agent Control has been set up again.

KDEX6117-E

The (JP1_ITDM2_Agent Control) service will be terminated. The license has either expired or is invalid.

[Cause] Possible causes include the following:

(1) The license has expired.

(2) The license information is invalid.

[Action] Stops the (JP1_ITDM2_Agent Control) service.

[Workaround]

(1) If the license has expired, purchase a valid license.

(2) If the license information is invalid, collect troubleshooting information by using troubleshooting information collection command, and then contact customer support.

KDEX6118-E

Failed to start the JP1_ITDM2_Agent Control) service. The license is not registered.

[Cause] Failed to start the (JP1_ITDM2_Agent Control) service because the license is not registered.

[Action] Cancels starting the (JP1_ITDM2_Agent Control) service.

[Workaround] Register a valid license.

KDEX6119-E

Failed to start the service (JP1_ITDM2_Agent Control).

[Cause] An attempt was made to start the service (JP1_ITDM2_Agent Control) on the database server.

[Action] Cancels startup of the service (JP1_ITDM2_Agent Control).

[Workaround] Check whether the service (JP1_ITDM2_Agent Control) is running on the management server. If it is not, start the service on the management server.

KDEX6120-I

The (JP1_ITDM2_Agent Control) service is complete.

KDEX6121-E

Failed to stop the (JP1_ITDM2_Agent Control) service.

KDEX6122-E

Failed to stop the (JP1_ITDM2_Agent Control) service.

[Cause] Failed to stop (JP1_ITDM2_Agent Control) service due to an error.

[Action] Stop the (JP1_ITDM2_Agent Control) service.

[Workaround] If the service fails to stop after a while, use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX6131-E

(JP1_ITDM2_Agent Control) service has stopped abnormally.

KDEX6132-E

(JP1_ITDM2_Agent Control) service has stopped abnormally.

[Cause] Due to a failure, (JP1_ITDM2_Agent Control) service has stopped abnormally.

[Action] Stop the (JP1_ITDM2_Agent Control) service.

[Workaround] Restart the service (JP1_ITDM2_Agent Control). If the problem persists, use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX6140-I

Notified the user with a message. Performed date=performed-date, Notification destination=notification-destination-host-name

KDEX6141-I

The database was expanded because of capacity shortage in the operation log storage area.

KDEX6151-E

Failed to start the service (JP1_ITDM2_Agent Control). The data folder shared between servers cannot be accessed.

[Cause] Possible causes include the following:

(1) The database server is stopped.

(2) A network failure occurred.

[Action] Cancels startup of the service (JP1_ITDM2_Agent Control).

[Workaround]

(1) Start the database server, and then start the service (JP1_ITDM2_Agent Control).

(2) Resolve the cause of the network failure, and then start the service (JP1_ITDM2_Agent Control).

KDEX6152-E

Failed to start the service (JP1_ITDM2_Agent Control). The data folder shared between servers cannot be accessed.

[Cause] The user name or password for connecting to the data folder shared between servers is incorrect.

[Action] Cancels startup of the service (JP1_ITDM2_Agent Control).

[Workaround] Verify that the user name and password for connecting to the data folder shared between servers are correct. (This user name and password were specified during management server setup.) Then, start the service (JP1_ITDM2_Agent Control).

KDEX6153-E

A service (JP1_ITDM2_Agent Control) failed to start. The port number is already being used. (error code = error-code (Windows Sockets), port number = port-number)

[Cause] The port number is already being used.

[Action] Stops the processing to start the service (JP1_ITDM2_Agent Control).

[Workaround] Change the port number, and then restart the service (JP1_ITDM2_Agent Control).

KDEX6154-E

Failed to start the service (JP1_ITDM2_Agent Control). Invalid configuration file settings. (property=property)

[Cause] The properties set in the configuration file are not set correctly.

[Action] Cancels startup of the service (JP1_ITDM2_Agent Control).

[Workaround] Review property settings and restart service (JP1_ITDM2_Agent Control).

KDEX6211-E

An error occurred while initializing audit logs of the (JP1_ITDM2_Agent Control) service.

[Cause] Due to a failure, an error occurred while initializing audit logs of the (JP1_ITDM2_Agent Control) service.

[Action] None.

[Workaround] Restart the (JP1_ITDM2_Agent Control) service. If the problem persists, use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX6221-E

An error occurred while processing the audit logs of the (JP1_ITDM2_Agent Control) service.

[Cause] Due to a failure, an error occurred during the output processing of audit logs of the (JP1_ITDM2_Agent Control) service.

[Action] None.

[Workaround] Restart the (JP1_ITDM2_Agent Control) service. If the problem persists, use troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX6411-I

The on-demand task is complete. (task name = task-name, number of error nodes = number-of-error-nodes)

KDEX6412-E

The installation task was terminated because of an error. Target computer name=target-computer-name, Task name=task-name

[Cause] cause-of-error

[Action] Cancel installation.

[Workaround] workaround

KDEX6413-E

The uninstallation task was terminated because of an error. Target computer name=target-computer-name, Task name=task-name

[Cause] cause-of-error

[Action] Cancel uninstallation.

[Workaround] workaround

KDEX6511-E

An error occurred during event notification to JP1/IM. (error code = error-code)

[Cause] A database access error occurred.

[Action] Cancels event notification to JP1/IM.

[Workaround] Check whether the service (JP1_ITDM2_DB Service) is running. If it is not, start it. If the problem persists, collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX6512-I

RegDelayQueue=unprocessed-number Interval=performance-log-display-interval (min.) AGI=number-of-reports-processed OPI=number-of-operation-Log-and-suspicious-operation-information-processed URI=number-of-USB-related-information-processed SD=number-of-security-measure-information-processed Operation=number-of-operation-log-information-processed-(number-of-operation-logs-included-in-the-number-of-processed-reports) CD=number-of-on-demand-received-results-processed TD=number-of-results-of-distributed-task-executions-processed VD=number-of-network-monitor-agent-status-notifications-processed SE=number-of-event-notifications-processed ON=number-of-site-management-node-lists-processed

Note:

This message is output to JP1/IT Desktop Management 2 - Manager-installation-folder\log\JDNAGCQn.LOG.

KDEX6513-I

RegDelayQueue=unprocessed-number R=number-of-data-reported-by-the-management-relay-server Interval=performance-log-display-interval (min.) AGI=number-of-reports-processed R=number-of-data-reported-by-the-management-relay-server OPI=number-of-operation-Log-and-suspicious-operation-information-processed R=number-of-data-reported-by-the-management-relay-server URI=number-of-USB-related-information-processed R=number-of-data-reported-by-the-management-relay-server SD=number-of-security-measure-information-processed Operation=number-of-operation-log-information-processed-(number-of-operation-logs-included-in-the-number-of-processed-reports) R=number-of-data-reported-by-the-management-relay-server CD=number-of-on-demand-received-results-processed TD=number-of-results-of-distributed-task-executions-processed VD=number-of-network-monitor-agent-status-notifications-processed SE=number-of-event-notifications-processed ON=number-of-site-management-node-lists-processed DEI=number-of-processed-device-information-(GUI-and-command)-(information-from-the-managed-relay-server) DSI=number-of-processed-device-information-(management-state)-(information-from-the-management-relay-server) NSI=number-of-processed-network-connection-states-(information-from-the-management-relay-server)

Note:

This message is output to JP1/IT Desktop Management 2 - Manager-installation-folder\log\JDNAGCQn.LOG.

KDEX7000-I

The command will be started.

KDEX7001-I

The command ended normally.

KDEX7002-E

Failed to execute the command. The specified arguments are invalid.

[Cause] The specified argument is incorrect.

[Action] Cancel command execution.

[Workaround] Review the argument and then re-execute the command.

KDEX7003-I

Usage:

softwaresearch /START

/START Specify when performing a software search.

KDEX7004-E

Failed to execute the command. The software search condition file does not exist or software search conditions are not defined.

[Cause] The software search conditions file does not exist. Or, the software search conditions are not defined.

[Action] Cancel command execution.

[Workaround] Check if the file is saved in the folder for saving the software search conditions file. If the software search conditions file is saved, check if the search conditions are defined in the software search conditions file.

KDEX7005-E

An invalid line was detected in the software search condition file. line number = line-number

[Cause] The software search conditions file contains an invalid row.

[Action] Cancel command execution.

[Workaround] Review the invalid row and then re-execute the command.

KDEX7006-E

Unable to read the software search condition file.

[Cause] The following causes are possible.

(1) The software search condition file does not have a read attribute or you do not have access permissions.

(2) The software search condition file is an invalid file. [Action] Cancel command execution.

[Action] Cancel command execution.

[Workaround]

(1) Set the read permission for the software search condition file and then re-execute the command.

(2) Check if the software search condition file is created in UTF-8 and then re-execute the command.

KDEX7007-E

The command is already running.

[Cause] The command is already being executed.

[Action] Cancel command execution.

[Workaround] Re-execute the command once the command being executed is terminated.

KDEX7008-E

Command execution failed. You do not have the required permissions.

[Cause] You do not have permissions to execute the command.

[Action] Cancel command execution.

[Workaround] Re-execute the command with administrator privileges.

KDEX7009-E

Command execution failed. error code = error-code

[Cause] A fatal error occurred in the command.

[Action] Cancel command execution.

[Workaround] Restart the target computer, and then execute the command again. If the problem still persists, use the troubleshooting information collection command to collect troubleshooting information and contact Customer Support.

KDEX7010-W

The software information detected by the command has exceeded the upper limit.

[Cause] The number of software information hits detected by the software search exceeded the upper limit of 64.

[Action] Terminate command execution. Software information exceeding the upper limit will not be detected.

[Workaround] Review the conditions defined in the software search conditions file and then re-execute the command.

KDEX7011-E

The search conditions defined in the software search condition file exceeds the upper limit.

[Cause] There are 501 or more search conditions defined in the software search conditions file.

[Action] Cancel command execution.

[Workaround] Set the search conditions defined in the software search conditions file to within 500 and then re-execute the command.

KDEX8000-E

Failed to execute the command. The specified arguments are invalid. (command name = command-name)

[Cause] The specified arguments are invalid.

[Action] Cancel command execution.

[Workaround] Confirm the command arguments, and retry execution.

KDEX8001-E

Failed to execute the command. You do not have the required permissions. (command name = command-name)

[Cause] The command was executed by a user without Administrator permissions.

[Action] Cancel command execution.

[Workaround] Re-execute the command as a user with Administrator permissions.

KDEX8002-E

Failed to execute the command. Setup is in progress, or a command is executing. (command name = command-name)

[Cause] The command was executed while setup was in progress or a command was executing.

[Action] Cancel command execution.

[Workaround] Wait until the process or command ends, and then re-execute the command.

KDEX8003-I

Re-creation of the operation log database has started.

KDEX8004-E

Failed to execute the command. Setup is not complete. (command name = command-name)

[Cause] Setup of JP1/IT Desktop Management - Remote Site Server is not complete.

[Action] Cancel command execution.

[Workaround] Complete setup of JP1/IT Desktop Management - Remote Site Server, and then re-execute the command.

KDEX8005-E

Failed to execute the command. (command name = command-name, error code = error-code (maintenance-code))

[Cause] A critical error occurred during command execution.

[Action] Cancel command execution.

[Workaround] Use the troubleshooting information collection command to collect troubleshooting information, and contact Customer Support.

KDEX8006-E

Failed to execute the command. A database access error occurred. (details = DBMS-message, command name = command-name)

[Cause] The service (JP1_ITDM2_DB Service) has stopped, or the error described in "details" occurred.

[Action] Cancels command execution.

[Workaround] Start the service (JP1_ITDM2_DB Service) or resolve the error described in "details", and then re-execute the command. If the problem persists, collect troubleshooting information on the site server by using the troubleshooting information collection command, and then contact Customer Support.

KDEX8007-I

The operation log was moved successfully.

KDEX8008-E

Failed to execute the command. A file access error occurred. (command name = command-name)

[Cause] Possible causes include the following:

(1) You do not have access permission for the specified folder.

(2) There is not enough free disk space for the specified folder.

(3) An I/O error occurred.

[Action] Cancel command execution.

[Workaround]

(1) Make sure you have access permission for the specified folder.

(2) Make sure there is enough free disk space for the specified folder.

(3) Make sure that a disk error did not occur.

If the problem persists, use the troubleshooting information collection command to collect troubleshooting information, and contact Customer Support.

KDEX8009-E

Failed to execute the command. The specified folder is invalid. (command name = command-name)

[Cause] Possible causes include the following:

(1) The operation log folder currently in use or a folder that does not contain an operation log is specified for the migration-source folder.

(2) The migration-destination folder is not empty.

[Action] Cancels command execution.

[Workaround] Make sure the specified folder is correct, and then re-execute the command. If the problem persists, collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX8010-I

Storage of the operation logs is complete.

KDEX8011-W

Free space on the disk containing the operation log backup folder has become scarce. Increase the free disk space, or change to a disk that has enough free disk.

KDEX8012-W

Storage of the operations logs stopped because there is almost no free space on the disk containing the operation log backup folder. Increase the free disk space, or change to a disk that has enough free disk.

KDEX8013-W

Free space on the disk containing the operation log database has become scarce.

KDEX8014-W

Storage of the operation logs stopped because there is almost no free disk space for the operation log database.

KDEX8015-I

The operation log database was expanded because its capacity was insufficient.

KDEX8016-I

Command execution was canceled. (command name = command-name)

KDEX8017-W

Free space on the disk containing the folder that stores content has become scarce. Increase the free disk space, or change to a disk that has enough free space.

KDEX8018-W

Downloading of content to the site server was stopped because there is almost no free space on the disk containing the folder that stores content. Increase the free disk space, or change to a disk that has enough free space.

KDEX8019-E

Failed to execute the command. The JP1_ITDM_Remote Site Service service failed to stop. (command name = command-name)

[Cause] The command was executed during processing to start or stop the JP1_ITDM_Remote Site Service service.

[Action] Cancels command execution.

[Workaround] Collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX8020-E

Failed to execute the command. Failed to connect to the management server. (command name = command-name)

[Cause] Possible causes are as follows:

(1) The management server service is not running.

(2) A failure occurred on the network of the management server.

[Action] Cancels command execution.

[Workaround]

(1) Execute the startservice command to start the management server service, and then re-execute the command.

(2) Eliminate the cause of the network failure, and then re-execute the command.

KDEX8021-I

The list of agents managing operation logs was reported to the managing server.

KDEX8022-W

Re-creation of the operation log database started normally, but the JP1_ITDM_Remote Site Service service could not start. (command name = command-name)

[Cause] A critical error occurred during command execution.

[Action] Cancels command execution.

[Workaround] Collect troubleshooting information on the site server by using the troubleshooting information collection command, and then contact Customer Support.

KDEX8023-W

The operation log was moved successfully, but deletion of the move-source folder failed. (command name = command-name)

[Cause] A file in the move-source folder is being used.

[Action] Cancels command execution.

[Workaround] Stop any application using the move-source folder, and then delete the folder.

KDEX8024-W

The operation log was moved successfully, but the service (JP1_ITDM_Remote Site Service) could not be started. (command name = command-name)

[Cause] A fatal error occurred in the command.

[Action] Cancel command execution.

[Workaround] Collect troubleshooting information on the site server by using the troubleshooting information collection command, and then contact Customer Support.

KDEX8025-I

The communication service of the site server was started.

KDEX8026-E

An attempt to start the communication service of the site server failed.

KDEX8027-I

The communication service of the site server was stopped.

KDEX8028-E

A database access error occurred in the communication service of the site server. (details = DBMS-message)

[Cause] The service (JP1_ITDM2_DB Service) has not started, or the error described in "details" occurred.

[Action] Restart the communication service of the site server.

[Workaround] Start the service (JP1_ITDM2_DB Service), or resolve the error described in "details" and restart the service (JP1_ITDM_Remote Site Service). If the problem persists, collect troubleshooting information on the site server by using the troubleshooting information collection command, and then contact Customer Support.

KDEX8029-E

An error occurred in the communication service of the site server. (error code = internal-error-code)

[Cause] An internal error occurred.

[Action] Restart the communication service of the site server.

[Workaround] Collect troubleshooting information on the site server by using the troubleshooting information collection command, and then contact Customer Support.

KDEX8030-E

Re-creation of the operation log database has failed.

KDEX8031-I

Deletion of operation log data ended normally. (number of operation log items before deletion = number-of-operation-log-items, number of operation log items after deletion = number-of-operation-log-items)

KDEX8032-W

Deletion of operation log data ended normally, but the service (JP1_ITDM_Remote Site Service) could not be started. (command name = command-name)

[Cause] A fatal error occurred in the command.

[Action] Cancels execution of the command.

[Workaround] Collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX8033-E

Command execution failed. There is not enough free space in the work folder. (command name = command-name, required space = required-space)

[Cause] Possible causes include the following:

(1) There is not enough free space on the disk that contains the specified folder.

(2) If no work folder has been specified, there is not enough free space on the disk that contains the data folder.

[Action] Cancels execution of the command.

[Workaround] Increase the free space on the disk or specify a folder on a disk that has enough free space, and then re-execute the command. If the problem persists, collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX8034-E

Deletion of operation log data failed.

KDEX8035-W

Operation log data to be deleted does not exist.

KDEX8036-E

Command execution failed. The specified date is invalid. (command name = command-name)

[Cause] A date that does not exist was specified.

[Action] Cancels execution of the command.

[Workaround] Check the specified date, and then re-execute the command. If the problem persists, collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX8037-E

Command execution failed. The specified folder is invalid. (command name = command-name)

[Cause] Possible causes include the following:

(1) The folder is not specified using an absolute path.

(2) A path exceeding 120 bytes is specified for the folder.

(3) The folder contains characters that cannot be entered. Characters that can be entered are halfwidth spaces and the following halfwidth characters:

A-Z a-z 0-9 # @ \ : . ( )

(4) A folder that is not on a local disk is specified.

[Action] Cancels execution of the command.

[Workaround] Check the specified folder, and then re-execute the command. If the problem persists, collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX8038-E

Command execution failed. The site server was unable to notify the management server of the list of agents managing operation logs. (command name = command-name)

[Cause] Possible causes include the following:

(1) The management server service has not started.

(2) A failure has occurred on the network connection to the management server.

[Action] Cancels execution of the command.

[Workaround]

(1) Execute the startservice command to start the management server service, and then re-execute the command.

(2) Remove the cause of the network failure, and then re-execute the command.

If the problem persists, collect troubleshooting information by using the appropriate command, and then contact customer support.

KDEX8039-E

Command execution failed. (command name = command-name)

[Cause] The command for deleting operation log data is not finished or has failed.

[Action] Cancels execution of the command.

[Workaround] After the command for deleting operation log data ends normally, re-execute the command.

KDEX8100-I

A connection to a higher-level system was successfully established. (higher-level system = higher-level-system, host name or IP address = host-name-or-IP-address, port number = port-number)

Note:

This is the message concerning the internet gateway. This message is output to Internet-gateway-installation-folder\log\JDNGWMAINn.LOG.

KDEX8101-E

The attempt to connect to a higher-level system failed. (higher-level system = higher-level-system, host name or IP address = host-name-or-IP-address, port number = port-number)

[Cause] Possible causes include the following:

(1) The connection destination specified in the Internet gateway setup is incorrect.

(2) The connection was blocked by the firewall between the Internet gateway and the higher system.

(3) The higher system is down.

(4) A network failure has occurred.

[Action] Cancel the connection with a higher system.

[Workaround]

(1) Review the connection destination setting in the Internet gateway setup.

(2) Review the firewall setting between the Internet gateway and the higher system.

(3) Confirm that the higher system is up and running.

(4) Confirm that no network failure has occurred.

Note:

This is the message concerning the internet gateway. This message is output to Internet-gateway-installation-folder\log\JDNGWMAINn.LOG.

KDEX9000-I

The (JP1_ITDM2_Relay Manager) service will be started.

KDEX9001-I

The (JP1_ITDM2_Relay Manager) service is complete.

KDEX9002-E

Failed to start the service (JP1_ITDM2_Relay Manager). The port number is already being used. (error code = error-code, port number =port-number)

[Cause] The port number is already being used.

[Action] Stops the processing to start the service (JP1_ITDM2_Relay Manager).

[Workaround] Change the port number, and then restart the service (JP1_ITDM2_Relay Manager).

KDEX9003-E

Failed to start the (JP1_ITDM2_Relay Manager) service. (error code = error-code)

[Cause] Failed to start the (JP1_ITDM2_Relay Manager) service.

[Action] Stops the (JP1_ITDM2_Relay Manager) service.

[Workaround] If the (JP1_ITDM2_Relay Manager) service is stopped after the management server starts, start the (JP1_ITDM2_Relay Manager) service again. If the problem persists, use troubleshooting information collection command to collect troubleshooting information and contact the support service.

KDEX9004-E

The (JP1_ITDM2_Relay Manager) service has stopped abnormally.

[Cause] Due to a failure, the (JP1_ITDM2_Relay Manager) service has stopped abnormally.

[Action] Stops the (JP1_ITDM2_Relay Manager Service) service.

[Workaround] If the (JP1_ITDM2_Relay Manager) service is stopped after the management server starts, start the (JP1_ITDM2_Relay Manager) service again. If the problem persists, use troubleshooting information collection command to collect troubleshooting information and contact the support service.

KDEX9005-E

Failed to start the (JP1_ITDM2_Relay Manager) service.

KDEX9006-E

Because JP1/IT Desktop Management 2 - Manager setup is incomplete, startup of the (JP1_ITDM2_Relay Manager) service failed.

[Cause] Because JP1/IT Desktop Management 2 - Manager setup is incomplete, the (JP1_ITDM2_Relay Manager) service could not be started.

[Action] Stops the (JP1_ITDM2_Relay Manager) service.

[Workaround] After JP1/IT Desktop Management 2 - Manager setup is complete, start the (JP1_ITDM2_Relay Manager) service.

KDEX9007-E

Failed to start the (JP1_ITDM2_Relay Manager) service. Setup, the database manager, or a command is in execution.

[Cause] The (JP1_ITDM2_Relay Manager) service was started while setup, the database manager, or a command was in execution.

[Action] Cancel starting the (JP1_ITDM2_Relay Manager) service.

[Workaround] Wait until the executing process (Setup, Database Manager, or command) ends, and then restart the (JP1_ITDM2_Relay Manager) service.

KDEX9008-E

The (JP1_ITDM2_Relay Manager) service has stopped abnormally.

KDEX9100-I

The route between a device and a managing device was updated. If the route information of the device with the same Host ID is repeatedly updated, it might be because several management servers specify the same discovery settings or MDM linkage settings.

host ID = host-ID, route pre-change = route-before-change, route post-change = route-after-change

Note: This message is output to JP1/IT Desktop Management 2 - Manager-installation-folder\log\JDNSTRCn.LOG.

2 Event Log Messages

This chapter lists and describes event log messages. Event log messages are output to the Windows Event Viewer by JP1/IT Desktop Management 2. In the Event Viewer, messages for which the Source column displays JP1ITDM2 (DMM), JP1ITDM2 (DMU), or JP1ITDM2 (DMC) are messages output by JP1/IT Desktop Management 2.

2.1 Format of message explanations

Each event log message output by JP1/IT Desktop Management 2 consists of a message ID, message type, and message text. In this manual, the description of each event log message consists of the following elements:

event-ID <including type>, message-text, cause, and action

The meaning of each element is as follows:

Event ID

The ID that identifies the event log message.

Type

The type of information reported by the message. One of the following types is output:

Information

Warning

Error

Message text

The body of the message that is output.

Cause

Describes the reason why the message was output, and the variables used in the message.

Action

Describes the action to be taken when the message is output.

The following table describes the common variables used in the following sections:

Variable

Meaning

bb

Any character string

mm

n1

n2

nn

xx

yy

op

Command option

path

Command execution path

yyyyyy

Alert message

YYYYMMDDhhmmss

Date and time

zz

Attribute of the JP1 event to be issued

2.2 List of event log messages output by the management server

0 <Error>

Windows NT API error occurred. Request: xx, Error yy

1 <Error>

No input file. Error message from path op.

2 <Error>

An attempt to create the package or a file in the package failed. Check the JP1/ITDM2 log files. Check the specified path of the file or directory to be packaged, or reduce the number of files or directories to be packaged. Error message from path op.Detail:xx.

3 <Error>

Invalid input data. Error message from xx.

4 <Error>

Error in reading the file. Error message from path op.

5 <Error>

Error in server connection. Error message from path op.

6 <Error>

Error in file transfer. Error message from xx.

7 <Error>

Error in writing file. Error message from path op.

10 <Error>

Storage completed. Error message from xx.

11 <Error>

Connector Error. Error message from xx.

12 <Error>

Invalid Environment. Error message from path op.

13 <Error>

System Error. Error message from path op.

98 <Error>

The maximum number of registrations (path op) was exceeded, or there was an inconsistency in the internal processing.

99 <Error>

Exception error - xx. Error message from path op.

100 <Error>

Failed to update input file for new version/generation: path op.

101 <Error>

Failed to melt xx.

102 <Error>

Valid path to file(s) to be collected not found. Error message from path op.

103 <Error>

An environment is injustice. Error message from path op.

104 <Error>

Matching record not found in database. Error message from path op.

105 <Error>

Loading of DLL to extract package contents failed. Error message from path op.

106 <Error>

The package contents could not be output. Make sure that the administration file of the package is correct, and that there is enough memory and free space in the HD. Error message from path op.

107 <Error>

ODBC environment not initialized. Error message from path op.

108 <Error>

Local manager version not supported. Error message from path op.

109 <Error>

Failed to create query. Error message from path op.

112 <Error>

Too much data satisfies the constraint, output was not done. Error message from path op.

113 <Error>

The registry information could not be obtained. Error message from path op.

114 <Error>

The temporary file could not be opened. Error message from path op.

115 <Error>

Insufficient command argument. Check the command format. Error message from path op.

116 <Error>

Two /par arguments are specified. Check the command format. Error message from path op.

117 <Error>

Two /csv arguments are specified. Check the command format. Error message from path op.

118 <Error>

Two /o arguments are specified. Check the command format. Error message from path op.

119 <Error>

The file name of the output file is invalid. Check the command format. Error message from path op.

120 <Error>

Two /i arguments are specified. Check the command format. Error message from path op.

121 <Error>

The parameter file name is invalid. Check the command format. Error message from path op.

122 <Error>

Two template keys are specified or an invalid command argument is specified. Check the command format. Error message from path op.

123 <Error>

The template key is invalid or an invalid command argument is specified. Check the command format. Error message from path op.

124 <Error>

The file name of the output file is too long. Check the command format. Error message from path op.

125 <Error>

The parameter file name is too long. Check the command format. Error message from path op.

126 <Error>

The specified template key cannot be used when the /par argument is specified. Check the command format. Error message from path op.

127 <Error>

No Output file name is specified. Check the command format. Error message from path op.

128 <Error>

No file name is specified for the output file. Check the command format. Error message from path op.

129 <Error>

No parameter file name is specified. Check the command format. Error message from path op.

130 <Error>

No parameter file name is specified. Check the command format. Error message from path op.

131 <Error>

Package xx restoration failed. Error message from path op.

132 <Error>

Item xx import failed. Error message from path op.

133 <Error>

Package / Cabinet xx backup failed. Error message from path op.

134 <Error>

One of xx.pkg, xx.xml, xx.dpf file is not available for restoration. Error message from path op.

135 <Error>

Unable to execute external program xx. Error message from path op.

136 <Error>

Maximum execution period for the command expired. xx Job not ended. Error message from path op.

137 <Error>

xx is invalid input value. Error message from path op.

138 <Error>

Error in backing up package xx. Error Message From path op.

139 <Error>

Label of Item name (xx) which is specified in Parameter file is being used on entered another item.

140 <Error>

Existing Higher Server or Local and higher servers of item name (xx) which is specified in Parameter file will be updated. High Server or Local and higher servers cannot be updated.

141 <Error>

Though Insert parameter of Item name (xx) in Parameter file is specified, Select parameter is not specified. If Insert parameter is specified, Select parameter is required to be specified together.

142 <Error>

This Parameter is duplicated. Or parameter is specified out of brackets: xx.

143 <Error>

Unusable characters(\ / * " ' : ; , & tab) are specified in Parameter(item) of Item name. Or specifiable characters exceed 64 characters. Specified value: xx.

144 <Error>

Unusable characters(\ / * " ' : ; , & tab) are specified in Parameter(label) of Label. Or specifiable characters exceed 64 characters. Specified value: xx.

145 <Error>

Unusable characters(\ / * " ' : ; , & tab) are specified in Parameter(comment) of Comment. Or specifiable characters exceed 255 characters. Specified value: xx.

146 <Error>

Unusable characters (except Y (y) or N (n)) are specified in Parameter (require) of required item. Or specification is incorrectly. Specified value: xx.

147 <Error>

Unusable characters (except Y (y) or N (n)) are specified in Parameter (insert) of List or List (Text is possible). Or specification is incorrectly. Specified value: xx.

148 <Error>

Parameter is specified incorrectly. : xx.

149 <Error>

Parameter (select) of List is specified out of brackets: xx.

150 <Error>

Unusable characters(\ / * " ' : ; , & tab) are specified to parameter(select) of List on Item name (xx) which is specified in parameter file. Or specification is incorrectly.

151 <Error>

Parameter (select) of List which exceeds 201 characters is specified to Item name (xx) in parameter file.

152 <Error>

A specified selection item exceeds the max size for the parameter specified for selection items that have the item name (xx), specified in the parameter file. (For "select", the max size is 51,254 bytes. For "selectable", the total value with "upper_select" is 102,509 bytes.)

153 <Error>

Duplicated parameter (select) of List is specified to Item name (xx) in parameter file.

154 <Error>

Format of Parameter file is invalid. Check whether the format is correctly on [L. line number] or upon lines. : xx.

155 <Error>

Item name (item) is not specified in parameter file. Item name is required to specify. : xx.

156 <Error>

Item name (item) is not specified in parameter file. Check whether the input value is specified correctly on [L. line number] or upon lines. Item name is required to specify. : xx.

157 <Error>

Number of items is achieved the upper limit 255. Check existing number of items. If items do not achieve 255, parameter in the item is incorrectly. Check the contents. Item name of failed to addition: xx.

158 <Error>

Duplicate USER_INVENTORY tags are specified. USER_INVENTORY tag can be specified in Parameter file only once. : xx.

159 <Error>

File cannot be opened. Check the file. : xx.

160 <Error>

File cannot be read. Check the file. : xx.

161 <Error>

File cannot be written. Check the file. : xx.

162 <Error>

path op The CSV file contains invalid data. Check the information specified on [L. line number]: xx

163 <Error>

path op The CSV file format is invalid: xx

166 <Error>

Nothing has been specified for the parameter (upper_item). Item name: xx

167 <Error>

path op The specified policy could not be found: xx

168 <Error>

An item other than those enabled for text input has been specified as a hierarchical item. The selected item must be a hierarchical item specified for input. Item name: xx

169 <Error>

An incorrect value has been specified for the relation parameters (upper_select or selectable). Check the information specified on [L. line number]: xx

170 <Error>

Invalid characters (\ / * " ' : ; , & tab) have been specified in the relation parameters (upper_select or selectable). Specified value: xx

171 <Error>

The value specified for the relation parameters (upper_select or selectable) exceeds 200 characters. Item name: xx

172 <Error>

The number of items exceeds 255. Item name: xx

173 <Error>

Duplicate values have been specified for the relation parameters (upper_select or selectable). Item name: xx

175 <Error>

xx The CSV file header data is invalid: yy

176 <Error>

The valid selection items parameter (selectable) has been set in an invalid location. Check the information specified on [L. line number]: xx

177 <Error>

Either invalid characters (\ / * " ' : ; , & tab) have been specified in the relation parameters (upper_select or selectable), or the value of these parameters exceeds 64 characters. Specified value: xx

178 <Error>

Either the parameter (select, upper_select, or selectable) has not been specified. Item name: xx

179 <Error>

A value not specified in the selection item parameter (select) has been specified in the valid selection items parameter (selectable). Item name: xx

180 <Error>

An attempt to add a lower item relationship to upper item xx failed because it already has a lower item.

181 <Error>

The maximum number of items (255) or hierarchy levels (10) has been exceeded. Check the existing number of items and hierarchy levels, and if the maximum limit has not been reached, a parameter in the item is most likely specified incorrectly. Item name: xx

183 <Error>

A value specified in requirement parameter (require) does not match the value of the higher item. Item name: xx

184 <Error>

An attempt to add or modify a selection values in a top-level or mid-level item has failed, since these actions are not allowed via import. Check the value of the parameter (select). Item name: xx

185 <Error>

An attempt to add a related lower item to a relationless upper item or a nonexistent selection item has failed. Check the value of the parameter (upper_select). Item name: xx

186 <Error>

An attempt to change a relationship on a top-level or mid-level item has failed. Relationships on these levels can not be changed. Item name: xx

187 <Error>

An attempt to change a relationship in a top-level or mid-level item has failed, since this is not allowed via import. Check the value of the parameter (select or upper_select). Item name: xx

188 <Error>

Unable to monitor ID job. Error message from path op.

189 <Error>

DM database is under renewal by other process. Wait and re-execute. Error message from path op.

190 <Error>

Specified job [xx] does not exist. Error message from path op.

191 <Error>

Error type specification is invalid for Basic Database environment. Error message from path op.

192 <Error>

Monitor Interval Time is greater than the time out period. Error message from path op.

195 <Error>

xx You are trying to change items set as policy conditions for automatic maintenance. First delete the user inventory item set in the policy. (item name = yy)

1000 <Error>

Control file not found on server. Error message from path op.

1003 <Error>

API Parameter is invalid (Handle value specification). Error message from path op.

1004 <Error>

Other process is using file. Error message from path op.

1006 <Error>

API parameter is invalid (Unspecified parameter error). Error message from path op.

1007 <Error>

API parameter is invalid (Name syntax check error). Error message from path op.

1008 <Error>

Already exists. Error message from path op.

1009 <Error>

Job creation continues. Error message from path op.

1010 <Error>

No search items or search ended specified information does not exist. Error message from path op.

1011 <Error>

Not enough space on disk. Error message from path op.

1014 <Error>

Fatal error occurred (internal error detection). Error message from path op.

1016 <Error>

System call error occurred due to API. Error message from path op.

1017 <Error>

API cannot continue transaction. Error message from path op.

1018 <Error>

Service name does not exist. Error message from path op.

1019 <Error>

Host name does not exist. Error message from path op.

1020 <Error>

Appears insufficient memory. Error message from path op.

1021 <Error>

Service is motive yet. Error message from path op.

1024 <Error>

Failed to connect. Error message from path op.

1025 <Error>

Discrepancy about protocol version of server & its API. Error message from path op.

1026 <Error>

Not match in environment of server with environment of remote install manager. Error message from path op.

1032 <Error>

Destination not specified (job definition creation/edit error). Error message from path op.

1033 <Error>

Package specification does not exist (Job definition creation / edit error). Error message from path op.

1035 <Error>

Unusable node exists. Error message from path op.

1036 <Error>

Usable node not found. Error message from path op.

1037 <Error>

Unusable package exists. Error message from path op.

1038 <Error>

Usable package not found. Error message from path op.

1040 <Error>

Retry object not found. Error message from path op.

1045 <Error>

Unusable node and package exists. Error message from path op.

1048 <Error>

System definition does not exists. Error message from path op.

1051 <Error>

Modification/deletion item does not exists. Error message from path op.

1052 <Error>

Cabinet is full. Error message from path op.

1053 <Error>

DM database is under renewal by other process. Error message from path op.

1054 <Error>

No. of connections to RDB server exceeded max simultaneous connections. Error message from path op.

1055 <Error>

An error occurred during the accessing RDB server. Error message from path op.

1056 <Error>

Invalid Password. Error message from xx.

1057 <Error>

RDB server name invalid or RDB server is under suspension. Error message from path op.

1058 <Error>

Database does not exists, darabase has not been created or may be corrupted. Error message from path op.

1060 <Error>

Connection with RDB server is removed. Error message from path op.

1061 <Error>

Specified manager ID does not have permission to get access to the database. Error message from path op.

1063 <Error>

Login name or password is incorrect. Error message from path op.

1064 <Error>

Specified version of ODBC driver is inapplicable. Error message from path op.

1067 <Error>

path op There are no settings for storing the software operation monitoring history into the database.

1068 <Error>

path op The specified storage directory does not exist or access is denied: storage directory name

1069 <Error>

path op The specified directory is not a storage directory or access is denied: storage directory name

1070 <Information>

path op Command processing completed normally.

1071 <Warning>

xx Command processing was interrupted because the server received a stop request.

1072 <Warning>

path op Command processing was interrupted because the release request was received.

1073 <Error>

path op Computer group was neither created nor inherited.

1074 <Error>

path op The specified group does not exist, an invalid character is included in the specified character string, or the specified character string exceeds the maximum length.

1086 <Error>

path op Input processing for the offline machine information file (xx) was skipped because another process is in progress.

1500 <Error>

Specified job does not exists xx. Error message from yy.

2001 <Error>

Memory allocation failure. Error message from path op.

2002 <Error>

Parameter file xx is invalid. Error message from path op.

2003 <Error>

Parameter file contains invalid value xx. Error message from path op.

2004 <Error>

Server connect error. Error message from path op.

2005 <Error>

Output file open error. Error message from path op.

2006 <Error>

Invalid command line argument. Error message from path op.

2007 <Error>

path op is invalid argument. Error message from xx.

2008 <Error>

path op An error occurred in analyzing the parameter file or the map file.:xx

2009 <Error>

path op The processing will now stop because the command has been started twice.:xx

2014 <Error>

path op System Error: xx

2016 <Error>

path op The process has stopped because a change of the assignment key was detected.

2021 <Error>

path op Processing ended because the user logged off. : xx.

2022 <Error>

The size of the file to be split is below the split size. File name=file name

Cause

The value specified for the /splitfilesize option is larger than the size of the file to be split.

Action

Specify a split size smaller than the size of the file to be split.

2023 <Error>

An error occurred during the output of a split file. File name=file name

Cause

An error occurred while split files were being output.

Action

Check if the folder specified in the /tempdir argument exists, is accessible, and has sufficient free space.

5007 <Error>

RDB access error during DB transfer.

7018 <Error>

The length of local hostname was too long.

Cause

The local host name is coded in 65 or more characters.

Action

Code the local host name in 64 or fewer characters.

10000 <Error>

RDBMS is connected up to the maximum connection.

10004 <Error>

The communication between RDBMS erred.

10007 <Error>

An access timing error to RDBMS.

10008 <Error>

Database format unmatched.

10009 <Error>

Login to RDBMS failed.

10010 <Error>

DataSourceName is invalid.

10011 <Error>

An access error to RDBMS, because transaction log full.

10012 <Error>

An access error to RDBMS, because capacity of database over.

10101 <Error>

System error occurred.

10106 <Error>

File close error.

11002 <Error>

System error occurred in the file transfer server.

11003 <Error>

Processing contradiction occurred in the file transfer server.

11004 <Error>

The processing sequence to the file transfer server is improper.

11005 <Error>

Processing request to a file transfer server is improper.

11006 <Error>

While starting the Software Distribution server,a memory shortage had occurred.

Cause

The system might be unstable because of a memory shortage.

Action

Solve the memory shortage problem, and then restart the JP1_ITDM2_Agent Control service.

11007 <Error>

It failed in creation of a directory in the file transfer server.

11010 <Error>

Interruption occurred.

11011 <Error>

The specified file does not exist.

11012 <Error>

The specified file is improper.

11017 <Error>

File error occurred in the management file.

11020 <Error>

Setting of an operation environment is improper.

Cause

The settings specified during setup might be incorrect.

Action

From the Setup dialog box for the management server, open the Setup for Distribution by Using Remote Install Manager dialog box, and then check the settings displayed on the Server Customization Options page.

11022 <Error>

Resource hangar is destroyed.

Cause

The package storage directory of JP1/IT Desktop Management 2 might be corrupted.

Action

Start the maintenance wizard, select Repair and re-install JP1/IT Desktop Management 2. The package storage directory will then be repaired and initialized.

11023 <Error>

An illegal difference instruction file received from xx.

11024 <Error>

An illegal status notification file received from xx.

11025 <Error>

An illegal inventory file received from xx.

11026 <Warning>

A file(yy) of the agent (xx) is illegal.

11027 <Warning>

The yy file to which an illegal host name was set was received from xx.

11028 <Warning>

There was a connection request from xx of illegal host name.

11030 <Warning>

The destination host (host: xx, type: yy) cannot be found in the system configuration so that the result cannot be applied to the system configuration.

11031 <Warning>

An error was returned to a request for uploading a file (file name: yy, size: nn bytes) from a lower-level system (xx). The lower-level system will send the file again.

One of the following character strings is set as the file name:

CD000000: Job execution status information

N0000000: System configuration information

IDxxxxxx: ID information

Fxxxxxxx: Remote collection job information

Gxxxxxxx: Remote collection files

S0000000: Installation package information

IV000000: System information

11032 <Warning>

The processing to send the result of a request for uploading a file (file name: yy, size: nn bytes) from a lower-level system (xx) failed. The lower-level system will send the file again.

One of the following character strings is set as the file name:

CD000000: Job execution status information

N0000000: System configuration information

IDxxxxxx: ID information

Fxxxxxxx: Remote collection job information

Gxxxxxxx: Remote collection files

S0000000: Installation package information

IV000000: System information

12013 <Error>

Environment for the resource management file access server is destroyed.

Cause

The cabinet information storage directory of JP1/IT Desktop Management 2 might be corrupted.

Action

Start the maintenance wizard, select Repair and re-install JP1/IT Desktop Management 2. The cabinet information storage directory will then be repaired and initialized.

12014 <Error>

Environment for the resource attribute file access server is destroyed.

Cause

The package information storage directory of JP1/IT Desktop Management 2 might be corrupted.

Action

Start the maintenance wizard, select Repair and re-install JP1/IT Desktop Management 2. The package information storage directory will then be repaired and initialized.

12015 <Error>

Environment for the execution management file access server is destroyed.

Cause

The job details information storage directory of JP1/IT Desktop Management 2 might be corrupted.

Action

Start the maintenance wizard, select Repair and re-install JP1/IT Desktop Management 2. The job details information storage directory will then be repaired and initialized.

12016 <Error>

Environment for the resource state file access server is destroyed.

Cause

The installed-package information storage directory of JP1/IT Desktop Management 2 might be corrupted.

Action

Start the maintenance wizard, select Repair and re-install JP1/IT Desktop Management 2. The installed-package information storage directory will then be repaired and initialized.

12017 <Error>

It failed in generation of an environment that a resource management file access server operates.

Cause

The system might be unstable because of memory shortage.

Action

Solve the memory shortage problem, and then restart the JP1_ITDM2_Agent Control service.

12018 <Error>

Generation of an environment for the resource attribute file access server failed.

Cause

The system might unstable because of memory shortage.

Action

Solve the memory shortage problem, and then restart the JP1_ITDM2_Agent Control service.

12019 <Error>

Generation of an environment for the execution management file access server failed.

Cause

The system might be unstable because of memory shortage.

Action

Solve the memory shortage problem, and then restart the JP1_ITDM2_Agent Control service.

12020 <Error>

Generation of an environment for the resource state file access server failed.

Cause

The system might be unstable because of memory shortage.

Action

Solve the memory shortage problem, and then restart the JP1_ITDM2_Agent Control service.

12032 <Error>

No space left on management file,no more space for writing is available.

12033 <Error>

It failed in creating an index of the management file.

12034 <Error>

It failed in creating an alternation index of the management file.

12035 <Error>

It failed in putting on the record key into index of a management file.

12036 <Error>

It failed in putting on the letter into index of a management file.

12037 <Error>

It failed in dividing index of a management file.

12038 <Information>

System is suspended. Download request is denied.

13003 <Information>

Software Distribution server was started.

13004 <Information>

Software Distribution server was terminated.

14004 <Error>

System error occurred during start.

Cause

The system might be unstable because of memory shortage.

Action

Solve the memory shortage problem, and then restart the JP1_ITDM2_Agent Control service.

14010 <Error>

Connection request to the Software Distribution Manager is improper.

14018 <Error>

The hostname of connection destination is not set.

14033 <Information>

Request of connection is denied,because server is refuse condition.

14035 <Information>

server will be made to be connectable condition.

14036 <Information>

Symbol of OpenView NNM Add Failed (Node=xx, Label=yy).

14037 <Error>

The JP1/ITDM2 - Manager process is down.

Cause

JP1/IT Desktop Management 2 detected an abnormal state. A JP1/IT Desktop Management 2 - Manager service (JP1_ITDM2_Agent Control) might not be running.

Action

Restart the JP1_ITDM2_Agent Control service.

14039 <Error>

JP1/IM Server or Agent is not installed.

14040 <Error>

A notice of event to the JP1/IM Event Server failed.

14081 <Error>

An error occurred during output of the audit logs.

14082 <Information>

A new audit log file was generated successfully.

16001 <Warning>

There is no device information that matches the specified conditions.

16002 <Error>

An error occurred during the search for device information.

16003 <Error>

The device information of xx is incorrect.

16004 <Information>

Processing to update the device information of xx will now be stopped.

16005 <Error>

A system error occurred during the processing of device information.

16006 <Error>

System error occurred.

18000 <Error>

netmdmclt/udp service was not definition.

18001 <Error>

Local host name is not defined.

18002 <Error>

Socket error occurred.

18003 <Error>

xx was unknown client address.

18004 <Error>

Call to xx for distribution job failed.

18005 <Error>

Fail in start rtcp server.

18006 <Error>

Error rtcp before process (host:xx).

18008 <Information>

Client request server started.

18010 <Error>

Message size error.

18011 <Error>

netmdmclt/tcp service was not definition.

19001 <Information>

Job schedule server was started.

19002 <Information>

Job schedule server was terminated.

19003 <Warning>

The schedule information was deleted because the xx required for schedule execution does not exist. (job definition name: yy, job number: nn, schedule execution date: mm)

19100 <Information>

Flow control for the distribution function that uses Remote Install Manager is enabled.

Note: If the relay system has enabled flow control for the distribution function using the Remote Install Manager, this message is output in the relay system's public log (MAIN.LOG).

19101 <Information>

Flow control for the distribution function that uses Remote Install Manager is disabled.

Cause

Possible causes are as follows:

Failed to open the configuration file (jdn_rim_distr_bwc.conf).

The BandwidthCtrl section was not found in the configuration file.

The Function key was not found in the BandwidthCtrl section.

The Function key was not enabled for the BandwidthCtrl section.

There is no valid SettingN section.

Action

Make sure that the configuration file exists.

Make sure that the BandwidthCtrl section exists in the configuration file, and that the Function key is enabled.

Make sure that a valid SettingN section is present.

Note: If the relay system has enabled flow control for the distribution function using the Remote Install Manager, this message is output in the relay system's public log (MAIN.LOG). For relay system, replace "SettingN section" with "Setting section".

19102 <Information>

Flow control setting: Section=section-name, MinIP=value-of-MinIP, MaxIP=value-of-MaxIP, MaxTransSpeedKbps=value-of-MaxTransSpeedKbps

Cause

Information about valid flow control settings is displayed. If information about the specified SettingN section is not displayed, possible causes are as follows:

The SettingN section that is not displayed was not found in the configuration file (jdn_rim_distr_bwc.conf).

One of the following was not found in the SettingN section that is not displayed: the MinIP key, MaxIP key, or MaxTransSpeedKbps key.

The value of the MinIP key or MaxIP key of the SettingN section that is not displayed is not in the range from 0.0.0.0 to 255.255.255.255.

The SettingN section that is not displayed does not satisfy the following condition: the value of the MinIP key ≤ the value of the MaxIP key.

The MaxTransSpeedKbps key of the SettingN section that is not displayed is not in the range from 32 to 8,388,608.

Action

Make sure that the SettingN section that is not displayed exists in the configuration file.

Make sure that the MinIP key, MaxIP key, and MaxTransSpeedKbps key all exist in the SettingN section that is not displayed.

Make sure that the values of the MinIP key and MaxIP key of the SettingN section that is not displayed are in the range from 0.0.0.0 to 255.255.255.255, and that the value of the MinIP key ≤ the value of the MaxIP key.

Make sure that the value of the MaxTransSpeedKbps key of the SettingN section that is not displayed is in the range from 32 to 8,388,608.

Note 1: section-name is displayed in the following format: SettingN.

Note 2: If the relay system has enabled flow control for the distribution function using the Remote Install Manager, this message is output in the relay system's public log (MAIN.LOG). For relay system, replace "SettingN section" with "Setting section". In the case of a relay system, only the MaxTransSpeedKbps key settings in the configuration file Setting section are output.

19200 <Error>

JP1 authentication failed for a communication error or an invalid environment. (code=error-code [process-or-function])

Cause

Possible causes are as follows:

An attempt to connect to the authentication server failed, because communication between the management server and the authentication server failed.

An attempt to load DLL for the JP1/Base API failed. (This sometimes occurs when JP1/Base is not installed or setup on the management server.)

The name of the logical host of the cluster environment specified during setup of the management server is incorrect.

Action

Make sure that the authentication server is running, that no network failure has occurred, and that the authentication server is correctly configured on the management server. After the error has been resolved, try to log in again.

Make sure that version of JP1/Base installed on the management server is supported.

Make sure that the name of the logical host of the cluster environment that was specified during setup of the management server is correct.

Note: The values displayed for error-code and process-or-function are as follows.

When a communication error occurs:

error-code: JP1/Base API error code

process-or-function: Name of the JP1/Base API function

When an attempt to load DLL for JP1/Base fails:

error-code: Error code obtained by the GetLastError function of WINAPI

process-or-function: LoadLibrary

20000 <Error>

Error occured. Error xx, Info: yy.

Cause

Either the network environment is invalid or it is possible that a communication failure occurred.

xx: Socket error code

yy: Name of the function in which the error occurred

Action

Solve the network environment or communication setting problem, and then restart the JP1_ITDM2_Agent Control service.

3 Basic Log Messages

This chapter lists and describes basic log messages. Basic log messages are fundamental log messages related to Agent behavior. For agents, these messages are output to JP1/IT-Desktop-Management-2-Agent-installation-folder\log\USER_CLT.LOG. For agents for management relay server, these messages are output to JP1/IT-Desktop-Management-2-Manager-installation-folder\mgr\log\USER_CLT.LOG and JP1/IT-Desktop-Management-2-Manager-installation-folder\mgr\LOG_S\USER_CLT.LOG.

3.1 Format of the basic log (USER_CLT.LOG file)

The following figure shows the format of the USER_CLT.LOG file, to which basic log messages are output.

In the USER_CLT.LOG file, the number of the line on which the newest message is recorded is output to the first line. Messages are output to the second and following lines. You can track the operations of Agent from the date, time, message ID, or message text of each message. On the second and following lines, fixed items are output at fixed positions (columns). The following shows the location of each item:

Windows Server 2003 or Windows XP

Line number: Columns 0 to 3

Date: Columns 6 to 15

Time (hour:minute:second:millisecond): Columns 17 to 28

Thread ID: Columns 30 to 41

Function type: Columns 43 to 50

Processing: Columns 52 to 67

Message ID: Columns 69 to 78

Message text: Columns 80 to 189

Windows Server 2019, Windows Server 2016, Windows 10, Windows 8.1, Windows 8, Windows Server 2012, Windows 7, Windows Server 2008, or Windows Vista

Line number: Columns 0 to 3

Date: Columns 5 to 14

Time (hour:minute:second:millisecond): Columns 16 to 27

Thread ID: Columns 29 to 52

Function type: Columns 54 to 61

Processing: Columns 63 to 78

Message ID: Columns 80 to 89

Message text: Columns 91 to 189

3.2 Format of message explanations

In this manual, the description of each basic log message consists of the following elements:

basic-log-message-ID, message-text, cause, and action

The meaning of each element is as follows:

Basic log message ID

The ID that identifies the basic log message. The alphabetic character at the end of the ID indicates the type of information reported by the message. One of the following types is output:

I (information)

W (warning)

E (error)

Message text

The body of the message that is output. For items that are enclosed by curly brackets ({ }) and separated by a vertical bar (|), only one of the items is output. Items that are enclosed by square brackets ([ ]) are output depending on the condition.

Cause

Describes the reason why the message was output, and the variables used in the message.

The instruction number in a message is a unique number assigned to identify the job process as a more fine-grained processing unit. Messages logged with the same instruction number pertain to the same process. For example, if a single job is used to distribute two packages, messages indicating job reception, success, and other events are output for each package. In this case, the job numbers in these messages are the same, but the instruction numbers are different for each package. To track the events for a specific package, see the messages that contain the instruction number for that package.

The maintenance code in a message is necessary only when the user inquires about the message. The user does not need to know the meaning of the maintenance code.

Action

Describes the action to be taken when the message is output. This element does not exist for messages that require no action.

3.3 List of basic log messages output by Agents

KDSF0001-I

xxxxxxxx version=vvrrss started. OS=oooooooo, Resident client=YES, Run without Administrator permissions=YES

Cause

The product indicated by xxxxxxxx started. The details of the product are as follows:

xxxxxxxx: Product name

vvrrss: Version number and the revision number

oooooooo: OS name and version

KDSF0003-E

A process pppppppp failed to start in xxxxxxxx version=vvrrss. OS=oooooooo, {Win32|Socket|Runtime} error, Code=mm[: nnnnnn][, zzzzzzzz]

Cause

Startup of a process failed.

pppppppp: Name of the process that could not be started

xxxxxxxx: Product name

vvrrss: Version

oooooooo: OS name and version

{Win32|Socket|Runtime}: Type of error

Win32: Win32 API error

Socket: Socket error

Runtime: C runtime error

mm: Error code

nnnnnn: Explanation of the error code indicated by mm

zzzzzzzz: Maintenance information

Action

Restart the computer.

KDSF0010-I

uuuuuuuu(SessionID=sss) logged on. User permission={Administrator|Ordinary user}

Cause

A user logged on.

uuuuuuuu: Name of the logged-on user

sss: Session ID (output if the OS is Windows Vista or later)

{Administrator|Ordinary user}: Permission of the logged-on user

Administrator: Administrator permissions

Ordinary user: Non-administrator user permissions

KDSF0020-I

A {logoff|shutdown} request was issued from OS[,SessionID=sss].

Cause

The OS issued a logoff or shutdown request.

{logoff|shutdown}: Type of request from the OS

logoff: A logoff request was issued.

shutdown: A shutdown request was issued.

sss: Session ID (output if the OS is Windows Vista or later)

Note that if the OS is Windows Server 2019, Windows Server 2016, Windows 10, Windows 8.1, Windows 8, or Windows Server 2012, this message is not output when a shutdown request is issued.

KDSF0030-I

xxxxxxxx terminated normally.

Cause

The product indicated by xxxxxxxx terminated normally.

xxxxxxxx: Product name

KDSF0031-W

A process down was detected in xxxxxxxx. Process name=pppppppp

Cause

A process failure was detected.

xxxxxxxx: Product name

pppppppp: Relevant process name

Action

Restart the computer.

If this event occurs frequently, contact the system administrator.

KDSF0032-W

The process pppppppp was forcibly terminated by a timeout.

Cause

Because a process did not terminate within a certain length of time during termination of a product, the process was terminated forcibly.

pppppppp: Relevant process name

KDSF0040-I

Ready to receive jobs. Protocol=TCP, Port number=yyyyyyyy

Cause

Preparation for job reception was completed.

yyyyyyyy: Number of port to be used (decimal number)

KDSF0041-E

Preparation for receiving jobs failed. {Win32|Socket|Runtime} error, Code=mm[: nnnnnn][, zzzzzzzz]

Cause

Preparation for job reception failed.

{Win32|Socket|Runtime}: Type of error

Win32: Win32 API error

Socket: Socket error

Runtime: C runtime error

mm: Error code

nnnnnn: Explanation of the error code indicated by mm

zzzzzzzz: Maintenance information

Action

Restart the computer. If the same failure occurs again after the computer has been restarted, review the environment settings after referring to the explanation of the error code.

KDSF0042-I

A job execution request was received from xxxxxxxx (yyy.yyy.yyy.yyy, zzzzzz). Protocol=TCP, ID key for operations=0xnn

Cause

A job execution request was received from a higher-level system. The details are as follows:

xxxxxxxx: Host name of the higher-level system

yyy.yyy.yyy.yyy: IP address of the higher-level system

zzzzzz: Product type of the higher-level system

netmdm: Manager

netmdmw: Relay system

0xnn: Operation key for the higher-level system

0x01: Host name

0x02: IP address

KDSF0050-I

Polling to xxxxxxxx (yyyyyyyy) started.

Cause

Polling started.

xxxxxxxx: Host name or IP address of the polling-destination device.

When connecting via Internet Gateway, use local hostname.

yyyyyyyy: Product type of the polling-destination device

netmdm: Manager

netmdmw: Relay system

netmgw: Connecting via Internet Gateway

KDSF0051-I

Polling to xxxxxxxx (yyyyyyyy) from hhhhhhhh (iii.iii.iii.iii, dddddddd) is completed. ID key for operations=0xnn

Cause

Polling was completed.

xxxxxxxx: Host name or IP address of the polling-destination device.

When connecting via Internet Gateway, use local hostname.

yyyyyyyy: Product type of the polling-destination device

netmdm: Manager

netmdmw: Relay system

netmgw: Connecting via Internet Gateway

hhhhhhhh: Local host name

iii.iii.iii.iii: IP address of the local host

dddddddd: Host ID of the local host

0xnn: Operation key for the higher-level system

0x03: Host name

0x04: IP address

0xff: The operation key information is invalid.

KDSF0052-W

Polling to xxxxxxxx (yyyyyyyy) from hhhhhhhh (iii.iii.iii.iii, dddddddd) failed. ID key for operations=0xnn, {Win32|Socket|Runtime|Protocol} error, Code=mm[: nnnnnn][, zzzzzzzz]

Cause

Polling failed due to an error. (The error might be a temporary error.)

xxxxxxxx: Host name or IP address of the polling-destination device.

When connecting via Internet Gateway, use local hostname.

yyyyyyyy: Product type of the polling-destination device

netmdm: Manager

netmdmw: Relay system

netmgw: Connecting via Internet Gateway

hhhhhhhh: Local host name

iii.iii.iii.iii: IP address of the local host

dddddddd: Host ID of the local host

0xnn: Operation key for the higher-level system

0x03: Host name

0x04: IP address

0xff: The operation key information is invalid.

{Win32|Socket|Runtime|Protocol}: Type of error

Win32: Win32 API error

Socket: Socket error

Runtime: C runtime error

Protocol: Protocol error

mm: Error code

nnnnnn: Explanation of the error code indicated by mm

zzzzzzzz: Maintenance information

Action

Check whether the host name (or IP address) and the product type of the polling-destination device are correct. If these settings are correct, make sure that the higher-level system of the polling-destination device is running.

When connecting via Internet Gateway, check KDSF0350-I, KDSF0351-I and KDSF0352-I message.

KDSF0053-I

Searching the local host for a package to be installed started. Cause={BOOT|SCHEDULE}

Cause

The system started a search for the packages that have been downloaded and are ready for installation on the local host.

Cause={BOOT|SCHEDULE}: When a search is performed

BOOT: When the system starts, it searches for the packages that are set to be installed at startup.

SCHEDULE: If the system has already received packages for which the installation date and time has been specified, the system searches for those packages at the specified date and time.

KDSF0054-I

Searching the local host for a package to be installed was completed.

Cause

The system completed a search for the packages that have been downloaded and are ready for installation on the local host.

KDSF0055-W

A fatal error occurred during job processing.

Cause

A fatal error occurred during job processing.

Action

Restart the OS.

KDSF0060-I

A job was received. Job type=yyyyyyyy, Job number=jjjjjjjj, Instruction number=cccccccc, Installation timing=zzzzzzzz (0xaa+0xbb), Replace existing package={YES|NO}, Installation date/time=tttttttttttt {, Installation mode={BG|GUI}, Package information=d.cc.pppppp.vvvv.ssss, Package name=nnnnnnnn, ffffffff|Software to be Searched=ssssssss[, File system to be Searched=xxxxxxxx]}

Cause

This message is output when a job was received. This message is also output when the managing server deletes a job that is running on the Agent and the Agent receives a job deletion request.

yyyyyyyy: Job type

Install package: Install package job

Get system information from computer (UNIX): Get system information from computer (UNIX) job

Get software information from computer (UNIX): Get software information from computer (UNIX) job

Collect files from client: Collect files from agent job

Send package, allow client to choose: Send package, allow client users to choose job

Delete job: Job deletion request (A job deletion request sent to the client when the managing server deletes a job. This job deletion request is not a job.)

jjjjjjjj: Job number

cccccccc: Instruction number

zzzzzzzz: When the package is installed

Normal installation: The package is installed immediately.

Install when the system starts: The package is installed when the system starts.

Install when system stops: The package is installed when the system stops.

0xaa+0xbb: Maintenance information about the execution timing

Replace existing package={YES|NO}: Whether to replace the same already existing package

YES: Replaces the same package.

NO: Does not replace the same package.

tttttttttttt: Installation date and time (YYYYMMDDhhmm)

The following information is output for an Install package job or Send package, allow client users to choose job only:

{BG|GUI}: Installation mode

BG: Background installation mode

GUI: GUI installation mode

d.cc.pppppp.vvvv.ssss: Package information

- d: Packager type

C: Package registered from a UNIX packager (Packager)

D: Package registered from a Windows packager

- cc: Cabinet ID

- pppppp: Package ID

- vvvv: Version number and the revision number

- ssss: Generation number

nnnnnnnn: Package name

ffffffff: Package maintenance information

The following information is output for the Get system information from computer (UNIX) job:

ssssssss: Software to be searched

- Software installed by remote install: In case of search for software installed by remote install

- All software: In case of search for all software

When Software to be searched is All software, the following information is output:

xxxxxxxx: File system to be searched

- Local file systems: In case of search for local file systems

- Local file systems and Network file systems: In case of search for local file systems and network file systems

KDSF0061-I

The local host reported to the managing server that the status of a job on the local host has changed. Instruction number=cccccccc, Maintenance code=kkkkkkkkkkkkkk[: ssssssss]

Cause

The status of a job on the local host changed, and the change was reported to the managing server.

cccccccc: Instruction number

kkkkkkkkkkkkkk: Maintenance code (same code as for Remote Install Manager)

ssssssss: Explanation of the maintenance code

KDSF0070-I

Downloading a file by unicasting was started. ffffffff, Unicasting from hhhhhhhh

Cause

Downloading of a file that was delivered by unicast started.

ffffffff: Maintenance information

hhhhhhhh: Host name or IP address of the higher-level system (unicast source).

When connecting via Internet Gateway, use local hostname.

KDSF0071-I

Downloading a file by multicasting was started. ffffffff, Multicasting from hhhhhhhh (multicast address=iii.iii.iii.iii)

Cause

Downloading of a file that was delivered by multicast started.

ffffffff: Maintenance information

hhhhhhhh: Host name or IP address of the higher-level system (multicast source)

iii.iii.iii.iii: Multicast address set in the higher-level system (multicast source)

KDSF0072-I

The file was normally downloaded by unicasting. ffffffff, Size=yyyyyyyy bytes, Unicasting from hhhhhhhh

Cause

A file delivered by unicast was downloaded successfully.

ffffffff: Maintenance information

yyyyyyyy: Size of the downloaded file (bytes)

hhhhhhhh: Host name or IP address of the higher-level system (unicast source).

When connecting via Internet Gateway, use local hostname.

KDSF0073-I

The file was normally downloaded by multicasting. ffffffff, Size=yyyyyyyy bytes, Multicasting from hhhhhhhh (multicast address=iii.iii.iii.iii)

Cause

A file delivered by multicast was downloaded successfully.

ffffffff: Maintenance information

yyyyyyyy: Size of the downloaded file (bytes)

hhhhhhhh: Host name or IP address of the higher-level system (multicast source)

iii.iii.iii.iii: Multicast address set in the higher-level system (multicast source)

KDSF0074-W

An error occurred in downloading a file by unicasting. ffffffff, Unicasting from hhhhhhhh, {Win32|Socket|Runtime|Protocol} error, Code=mm[: nnnnnn][, zzzzzzzz]

Cause

A file delivered by unicast could not be downloaded.

ffffffff: Maintenance information

hhhhhhhh: Host name or IP address of the higher-level system (unicast source).

When connecting via Internet Gateway, use local hostname.

{Win32|Socket|Runtime|Protocol}: Type of error

Win32: Win32 API error

Socket: Socket error

Runtime: C runtime error

Protocol: Protocol error

mm: Error code

nnnnnn: Explanation of the error code indicated by mm

zzzzzzzz: Maintenance information

Action

Normally, no user needs to take action. For the management relay server, a retry is automatically performed five times at 5-second intervals. For the relay system and agents, a retry is automatically performed according to the information specified by selecting Communication settings and then Settings to Perform Retries when an Error Occurs in the Agent Configuration window.

Note, however, that if this symptom frequently occurs early after deployment of the product, the network environment might have a problem. In this case, review the network environment settings.

KDSF0075-W

An error occurred in downloading a file by multicasting. {Win32|Socket|Runtime|Protocol} error, Code=mm[: nnnnnn][, zzzzzzzz]

Cause

A file delivered by multicast could not be downloaded.

{Win32|Socket|Runtime|Protocol}: Type of error

Win32: Win32 API error

Socket: Socket error

Runtime: C runtime error

Protocol: JP1/Software Distribution protocol error

mm: Error code

nnnnnn: Explanation of the error code indicated by mm

zzzzzzzz: Maintenance information

Action

Normally, no user needs to take action. A retry is attempted automatically. If the number of retry attempts reaches the preset maximum, downloading will be retried by unicast.

Note, however, that if this symptom frequently occurs early after deployment of the product, the network environment might have a problem. In this case, review the network environment settings.

KDSF0076-W

Downloading by multicasting terminated abnormally. This package will be downloaded by unicasting. ffffffff, Multicasting from hhhhhhhh (multicast address=iii.iii.iii.iii)

Cause

A package delivered by multicast could not be downloaded normally. This package will be downloaded by unicast.

ffffffff: Maintenance information

hhhhhhhh: Host name or IP address of the higher-level system (multicast source)

iii.iii.iii.iii: Multicast address set in the higher-level system (multicast source)

Action

If this message is frequently output on multiple agents, decrease the job packet size in the settings on the multicast-source host.

KDSF0077-W

The multicast address does not match between the higher system and client. This package will be downloaded by unicasting. Multcasting from hhhhhhhh, Local multicast address=lll.lll.lll.lll

Cause

The multicast address set on the local host is different from the multicast address set in the higher-level system (multicast source). This package will be downloaded by unicast.

hhhhhhhh: Host name or IP address of the higher-level system (multicast source)

lll.lll.lll.lll: Multicast address set on the local host

Action

In a multi-polling environment, if the multicast source is not the higher-level system that is set as the default connection destination, ignore this message. If the multicast source is the higher-level system that is set as the default connection destination, set the same multicast address for the agent and higher-level system.

KDSF0080-I

Uploading to hhhhhhhh was started. ffffffff, Size=yyyyyyyy bytes

Cause

Uploading of a file started.

hhhhhhhh: Host name or IP address of the upload destination.

When connecting via Internet Gateway, use local hostname.

ffffffff: Maintenance information

yyyyyyyy: Size of the file being uploaded (bytes)

KDSF0081-I

The file was normally uploaded to hhhhhhhh. ffffffff, Size=yyyyyyyy bytes

Cause

A file was uploaded successfully.

hhhhhhhh: Host name or IP address of the upload destination.

When connecting via Internet Gateway, use local hostname.

ffffffff: Maintenance information

yyyyyyyy: Size of the uploaded file (bytes)

KDSF0082-W

An error occurred in uploading to hhhhhhhh. ffffffff, {Win32|Socket|Runtime|Protocol} error, Code=mm[: nnnnnn][, zzzzzzzz]

Cause

A file could not be uploaded.

hhhhhhhh: Host name or IP address of the upload destination.

When connecting via Internet Gateway, use local hostname.

ffffffff: Maintenance information

{Win32|Socket|Runtime|Protocol}: Type of error

Win32: Win32 API error

Socket: Socket error

Runtime: C runtime error

Protocol: Protocol error

mm: Error code

nnnnnn: Explanation of the error code indicated by mm

zzzzzzzz: Maintenance information

Action

Normally, no user needs to take action. For the management relay server, a retry is automatically performed ten times at 300-second intervals. For the relay system and agents, a retry is automatically performed according to the information specified by selecting Communication settings and then Non-transmitted Processing Result Files in the Agent Configuration window.

Note, however, that if this symptom frequently occurs early after deployment of the product, the network environment might have a problem. In this case, review the network environment settings.

KDSF0090-I

A job started. Job type=jjjjjjjj, Job number=xxxxxxxx, Instruction number=yyyyyyyy, Package information=d.cc.pppppp.vvvv.ssss, Package name=nnnnnnnn, ffffffff

Cause

Execution of a job started.

jjjjjjjj: Job type

Install package: Install package job

Collect files from client: Collect files from agent job

Send package, allow client to choose: Send package, allow client users to choose job

xxxxxxxx: Job number

yyyyyyyy: Instruction number

The following information is output for an Install package job or Send package, allow client users to choose job only:

d.cc.pppppp.vvvv.ssss: Package information

d: Packager type

C: Package registered from a UNIX packager (Packager)

D: Package registered from a Windows packager

cc: Cabinet ID

pppppp: Package ID

vvvv: Version number and the revision number

ssss: Generation number

nnnnnnnn: Package name

ffffffff: Package maintenance information

KDSF0091-I

The job is completed. Job type=jjjjjjjj, Job Number=xxxxxxxx, Instruction number=yyyyyyyy[, Package information=d.cc.pppppp.vvvv.ssss, Package name=nnnnnnnn, ffffffff, Installation path=zzzzzzzz]

Cause

A job was executed successfully.

jjjjjjjj: Job type

Install package: Install package job

Collect files from client: Collect files from agent job

Send package, allow client to choose: Send package, allow client users to choose job

xxxxxxxx: Job number

yyyyyyyy: Instruction number

The following information output for an Install package job or Send package, allow client users to choose job only:

d.cc.pppppp.vvvv.ssss: Package information

- d: Packager type

C: Package registered from a UNIX packager (Packager)

D: Package registered from a Windows packager

- cc: Cabinet ID

- pppppp: Package ID

- vvvv: Version number and the revision number

- ssss: Generation number

nnnnnnnn: Package name

ffffffff: Package maintenance information

zzzzzzzz: Installation destination path name (Note: If a Hitachi program product is installed at the default installation destination, the correct value is not displayed.)

KDSF0092-E

An error occurred in a job. Job type=jjjjjjjj, Job number=xxxxxxxx, Instruction number=yyyyyyyy, [Package information=d.cc.pppppp.vvvv.ssss, Package name=nnnnnnnn, ffffffff, Installation path=iiiiiiii, ]Cause={The installer cccccccc, Code=0xdd, zzzzzzzz|An external program aaaaaaaa, Code=0xdd, zzzzzzzz|An error occurred in unarchiving or archiving a file, eeeeeeee error, Code=mm[: nnnnnn][, zzzzzzzz]|An installation conditions error occurred: pppppppp, zzzzzzzz}. Maintenance code=kkkkkkkkkkkkkk[: ssssssss]

Cause

A job could not be executed.

jjjjjjjj: Job type

Install package: Install package job

Collect files from client: Collect files from agent job

Send package, allow client to choose: Send package, allow client users to choose job

xxxxxxxx: Job number

yyyyyyyy: Instruction number

[Package information=d.cc.pppppp.vvvv.ssss, Package name=nnnnnnnn, ffffffff, Installation path=iiiiiiii, ]

This information is output for an Install package job or Send package, allow client users to choose job only.

d.cc.pppppp.vvvv.ssss: Package information

- d: Packager type

C: Package registered from a UNIX packager (Packager)

D: Package registered from a Windows packager

- cc: Cabinet ID

- pppppp: Package ID

- vvvv: Version number and the revision number

- ssss: Generation number

nnnnnnnn: Package name

ffffffff: Package maintenance information

iiiiiiii: Installation destination path name (Note: If a Hitachi program product is installed at the default installation destination, the correct value is not displayed.)

Cause: The cause of the error. Information is output with one of the following four patterns:

1) The installer cccccccc, Code=0xdd, zzzzzzzz

Job execution failed because of a problem with the installer of a Hitachi program product or another company's software.

cccccccc: What happened in the installer:

- was not started because of an error

- resulted in an error

- terminated by a timeout

0xdd: Error code

zzzzzzzz: Maintenance information

2) An external program aaaaaaaa, Code=0xdd, zzzzzzzz

Job execution failed because of a problem with an external program.

aaaaaaaa: What happened in the external program:

- was not started because of an error

- resulted in an error

- terminated by a timeout

0xdd: Error code

zzzzzzzz: Maintenance information

3) An error occurred in unarchiving or archiving a file, eeeeeeee error, Code=mm[: nnnnnn][, zzzzzzzz]

Job execution failed because an error occurred while a file was being unarchived or archived.

eeeeeeee: Error type

Win32: Win32 API error

Socket: Socket error

Runtime: C runtime error

mm: Error code

nnnnnn: Explanation of the error code indicated by mm

zzzzzzzz: Maintenance information

4) An installation conditions error occurred: pppppppp, zzzzzzzz

Job execution failed because of an installation condition error.

pppppppp: Installation condition (system or software condition) that caused the error

zzzzzzzz: Maintenance information

kkkkkkkkkkkkkk: Maintenance code (same code as for Remote Install Manager)

ssssssss: Explanation of the maintenance code

Action

Take action after referring to the maintenance code's explanation output at ssssssss. In addition, take action according to the cause indicated in the message as shown below:

Cause=The installer cccccccc, Code=0xdd, zzzzzzzz

If no explanation is output at ssssssss, determine why Code=0xdd is returned, by referring to the documentation for the relevant program product or software.

Cause=An external program aaaaaaaa, Code=0xdd, zzzzzzzz

If no explanation is output at ssssssss, determine why Code=0xdd is returned, by referring to the documentation for the external program or by contacting the vendor of the external program.

Cause=An error occurred in unarchiving or archiving a file, eeeeeeee error, Code=mm[: nnnnnn][, zzzzzzzz]

Take action by referring to the error code's explanation output at nnnnnn.

Cause=An installation conditions error occurred: pppppppp, zzzzzzzz

Verify that the installation condition output at pppppppp is appropriate.

KDSF0093-I

Job number=xxxxxxxx, Instruction number=yyyyyyyy, Program path=zzzzzzzz. The installer started. Package information=d.cc.pppppp.vvvv.ssss, Package name=nnnnnnnn, Timeout=mm

Cause

An installer started.

xxxxxxxx: Job number

yyyyyyyy: Instruction number

zzzzzzzz: Path name of the started program

d.cc.pppppp.vvvv.ssss: Package information

d: Packager type

C: Package registered from a UNIX packager (Packager)

D: Package registered from a Windows packager

cc: Cabinet ID

pppppp: Package ID

vvvv: Version number and the revision number

ssss: Generation number

nnnnnnnn: Package name

mm: Timeout value (seconds). The timeout value of 0 means that a timeout never occurs.

KDSF0094-I

Job number=xxxxxxxx, Instruction number=yyyyyyyy, Program path=zzzzzzzz. The external program started. Timing=tttttttt, Monitor=wwwwwwww, Result notification=eeeeeeee, Error action={Abort|Continue}, Timeout=mm

Cause

An external program started.

xxxxxxxx: Job number

yyyyyyyy: Instruction number

zzzzzzzz: Path name of the started program

tttttttt: When the external program started

Before installation: The external program started immediately before installation.

After installation: The external program started immediately after installation.

Installation error: The external program started when an installation error occurred.

wwwwwwww: Timeout-related behavior

No timeout: The system waits for the external program to respond indefinitely. No timeout occurs.

Error after timeout: The system treats the timeout as an error.

Continue after timeout: The system does not treat the timeout as an error.

eeeeeeee: Notification method for the external program processing result

Windows: The Windows message for the external program is used for notification.

Return code: The exit code for the external program is used for notification.

{Abort|Continue}: How the system behaves if the processing result is an error

Abort: The system stops processing, assuming an error.

Continue: The system continues processing without assuming an error.

mm: Timeout value for the external program (seconds). The timeout value of 0 means that a timeout never occurs.

KDSF0095-I

Job number=xxxxxxxx, Instruction number=yyyyyyyy, Program path=zzzzzzzz. The {installer|external program} terminated normally.

Cause

An installer or external program terminated normally.

xxxxxxxx: Job number

yyyyyyyy: Instruction number

zzzzzzzz: Path name of the program that terminated normally

{installer|external program}: Type of program that terminated normally

installer: The program is an installer.

external program: The program is an external program.

KDSF0096-W

Job number=xxxxxxxx, Instruction number=yyyyyyyy, Program path=pppppppp. The {installer|external program} {was not started because of an error. eeeeeeee error, Code=mm[: nnnnnn][, zzzzzzzz]|resulted in an error. Return code=0xzz, Extend return code=0xcccccccc|terminated by a timeout}.

Cause

An installer or external program terminated abnormally or timed out.

xxxxxxxx: Job number

yyyyyyyy: Instruction number

pppppppp: Path name of the external program

{installer|external program}: Type of terminated program

installer: The program is an installer.

external program: The program is an external program.

{was not started because of an error. eeeeeeee error, Code=mm[: nnnnnn][, zzzzzzzz]|resulted in an error. Return code=0xzz|, Extend return code=0xcccccccc|terminated by a timeout}: The cause of termination. Information is output with one of the following three patterns:

was not started because of an error. eeeeeeee error, Code=mm[: nnnnnn][, zzzzzzzz]

The program failed to start.

eeeeeeee: Error type

Win32: Win32 API error

Socket: Socket error

Runtime: C runtime error

Protocol: Protocol error

mm: Error code

nnnnnn: Explanation of the error code indicated by mm

zzzzzzzz: Maintenance information

resulted in an error. Return code=0xzz, Extend return code=0xcccccccc

The program terminated because of an error.

0xzz: Return code returned by the external program (one-byte format)

0xcccccccc: Return code returned by the external program (four-byte format)

terminated by a timeout

The program terminated because of a timeout.

Action

Take action according to the cause of termination as shown below:

If the cause is that the program failed to start

Check whether the path name of the external program is correct.

If the cause is that an error occurred

Check the conditions specified by the return code.

If the cause is that a timeout occurred

Make sure that the timeout settings are correct. In addition, determine why the external program did not terminate before a timeout occurred.

KDSF0100-I

The automatic registration of hhhhhhhh (iii.iii.iii.iii, dddddddd) to the managing server started. Old managing server: vvvvvvvv -> New managing server: xxxxxxxx

Cause

Automatic registration of the local host to the system configuration information managed by the managing server started.

hhhhhhhh: Local host name

iii.iii.iii.iii: IP address of the local host

dddddddd: Host identifier of the local host

vvvvvvvv: Host name or IP address of the (old) managing server on which the local host is currently registered#. If the local host has never been registered, an asterisk (*) is output here.

xxxxxxxx: Host name or IP address of the (new) managing server on which the local host is being registered#1.

When connecting via Internet Gateway, use local hostname.

#

This message is also output when the IP address or host name of the local host is changed, even if the managing server is not changed. In this case, the same value is output as the old and new managing server names.

KDSF0101-I

The automatic registration of hhhhhhhh (iii.iii.iii.iii, dddddddd) to the managing server was completed. Old managing server: vvvvvvvv -> New managing server: xxxxxxxx

Cause

Automatic registration of the local host to the system configuration information managed by the managing server finished.

hhhhhhhh: Local host name

iii.iii.iii.iii: IP address of the local host

dddddddd: Host identifier of the local host

vvvvvvvv: Host name or IP address of the (old) managing server on which the local host was previously registered#. If the local host has never been registered, an asterisk (*) is output here.

xxxxxxxx: Host name or IP address of the (new) managing server on which the local host is currently registered#.

When connecting via Internet Gateway, use local hostname.

#

This message is also output when the IP address or host name of the local host is changed, even if the managing server is not changed. In this case, the same value is output as the old and new managing server names.

KDSF0102-W

The automatic registration of hhhhhhhh (iii.iii.iii.iii, dddddddd) to the managing server failed. Old managing server: vvvvvvvv -> New managing server: xxxxxxxx, {Win32|Socket|Runtime|Protocol} error, Code=mm[: nnnnnn][, zzzzzzzz]

Cause

Automatic registration of the local host to the system configuration information managed by the managing server failed.

hhhhhhhh: Local host name

iii.iii.iii.iii: IP address of the local host

dddddddd: Host identifier of the local host

vvvvvvvv: Host name or IP address of the (old) managing server on which the local host is currently registered#. If the local host has never been registered, an asterisk (*) is output here.

xxxxxxxx: Host name or IP address of the (new) managing server on which registration of the local host failed#.

When connecting via Internet Gateway, use local hostname.

{Win32|Socket|Runtime|Protocol}: Type of error

Win32: Win32 API error

Socket: Socket error

Runtime: C runtime error

Protocol: Protocol error

mm: Error code

nnnnnn: Explanation of the error code indicated by mm

zzzzzzzz: Maintenance information

#

This message is also output when the IP address or host name of the local host is changed, even if the managing server is not changed. In this case, the same value is output as the old and new managing server names.

Action

Automatic registration is retried at the next polling. If polling is triggered by system startup, restart the OS.

If a retry of automatic registration fails, check the explanation of the error code.

When connecting via Internet Gateway, check KDSF0350-I, KDSF0351-I and KDSF0352-I message.

KDSF0103-I

Inventory information was reported because a system modification was detected.

Cause

Inventory information was reported because a system modification was detected.

KDSF0110-I

ID group processing started. ID group=xxxxxxxx, Operation={ADD|EXECUTE|DELETE}, ID-management relay computer=hhhhhhhh (iiiiiiii)

Cause

A process related to ID groups started.

xxxxxxxx: Target ID group name

{ADD|EXECUTE|DELETE}: Processing type

ADD: The started process is the addition of the local host to the target ID group.

EXECUTE: The started process is a request to execute the ID group job submitted to the target ID group. (When the local host is registered to an ID group, this process automatically takes place to request the execution of the ID group job that has already been saved on the ID-management relay computer.)

DELETE: The started process is the deletion of the local host from the target ID group.

hhhhhhhh : ID-management relay computer.

When connecting via Internet Gateway, use local hostname.

iiiiiiii : Product type of the ID-management relay computer

netmdm: Manager

netmdmw: Relay system

KDSF0111-I

ID group processing was completed. ID group=xxxxxxxx, Operation={ADD|EXECUTE|DELETE}, ID-management relay computer=hhhhhhhh (iiiiiiii)

Cause

A process related to ID groups finished.

xxxxxxxx: Target ID group name

{ADD|EXECUTE|DELETE}: Processing type

ADD: The finished process is the addition of the local host to the target ID group.

EXECUTE: The finished process is a request to execute the ID group job submitted to the target ID group. (When the local host is registered to an ID group, this process automatically takes place to request the execution of the ID group job that has already been saved on the ID-management relay computer.)

DELETE: The finished processing is deletion of the local host from the target ID group.

hhhhhhhh : ID-management relay computer.

When connecting via Internet Gateway, use local hostname.

iiiiiiii : Product type of the ID-management relay computer

netmdm: Manager

netmdmw: Relay system

KDSF0112-E

An error occurred in IP group processing. ID group=xxxxxxxx, Operation={ADD|EXECUTE|DELETE}, ID-management relay computer=hhhhhhhh (iiiiiiii), {Win32|Socket|Runtime|Protocol} error, Code=mm[: nnnnnn][, zzzzzzzz]

Cause

A process related to ID groups failed.

xxxxxxxx: Target ID group name

{ADD|EXECUTE|DELETE}: Processing type

ADD: The failed process is the addition of the local host to the target ID group.

EXECUTE: The failed process is a request to execute the ID group job submitted to the target ID group. (When the local host is registered to an ID group, this process automatically takes place to request the execution of the ID group job that has already been saved on the ID-management relay computer.)

DELETE: The failed process is the deletion of the local host from the target ID group.

hhhhhhhh : ID-management relay computer.

When connecting via Internet Gateway, use local hostname.

iiiiiiii : Product type of the ID-management relay computer

netmdm: Manager

netmdmw: Relay system

{Win32|Socket|Runtime|Protocol}: Type of the error

Win32: Win32 API error

Socket: Socket error

Runtime: C runtime error

Protocol: Protocol error

mm: Error code

nnnnnn: Explanation of the error code indicated by mm

zzzzzzzz: Maintenance information

Action

By referring to the explanation of the error code, make sure that the ID-management relay computer is specified correctly and no communication errors occurred.

When connecting via Internet Gateway, check KDSF0350-I, KDSF0351-I and KDSF0352-I message.

KDSF0120-I

Packaging started. Package information=D.cc.pppppppp.vvvv.ssss, Save to=hhhhhhhh (iiiiiiii)

Cause

Packaging started.

D.cc.pppppp.vvvv.ssss: Package information

- D: Type of Packager. D indicates that the package was registered from Windows Packager. D is always output as the type of Packager.

- cc: Cabinet ID

- pppppp: Package ID

- vvvv: Version number and the revision number

- ssss: Generation number

hhhhhhhh: Host name or IP address of the managing server in which to register the package

iiiiiiii: Product type of the managing server in which to register the package

netmdm: Manager

netmdmw: Relay system

KDSF0121-I

Packaging terminated normally. Package information=D.cc.pppppppp.vvvv.ssss, Save to=hhhhhhhh (iiiiiiii)

Cause

Packaging finished successfully.

D.cc.pppppp.vvvv.ssss: Package information

- D: Type of Packager. D indicates that the package was registered from Windows Packager. D is always output as the type of Packager.

- cc: Cabinet ID

- pppppp: Package ID

- vvvv: Version number and the revision number

- ssss: Generation number

hhhhhhhh: Host name or IP address of the managing server in which to register the package

iiiiiiii: Product type of the managing server on which to register the package

netmdm: Manager

netmdmw: Relay system

KDSF0122-E

Packaging failed. Package information=D.cc.pppppppp.vvvv.ssss, Save to=hhhhhhhh (iiiiiiii), {Win32|Socket|Runtime|Protocol} error, Code=mm[: nnnnnn][, zzzzzzzz]

Cause

Packaging failed.

D.cc.pppppp.vvvv.ssss: Package information

- D: Type of Packager. D indicates that the package was registered from Windows Packager. D is always output as the type of Packager.

- cc: Cabinet ID

- pppppp: Package ID

- vvvv: Version number and the revision number

- ssss: Generation number

hhhhhhhh: Host name or IP address of the managing server in which to register the package

iiiiiiii: Product type of the managing server in which to register the package

netmdm: Manager

netmdmw: Relay system

{Win32|Socket|Runtime|Protocol}: Type of error

Win32: Win32 API error

Socket: Socket error

Runtime: C runtime error

Protocol: Protocol error

mm: Error code

nnnnnn: Explanation of the error code indicated by mm

zzzzzzzz: Maintenance information

Action

Check whether the host name or IP address of the managing server is correct and check whether a communication error has occurred.

KDSF0123-E

Creation of the package failed. (information = TablNum[xxxxxxxx], limit = [65535])

Cause

A package could not be created because the total number of targets# exceeded the maximum (65,535).

xxxxxxxx: Total number of targets

#: Information specific to the package to be created. The total number of targets is the total of the following values + 4:

Total number of the folders or files to be packaged

Total number of the short file names for folders or files to be packaged

Action

Make sure that the total number of targets does not exceed the maximum (65,535), and try again.

KDSF0130-E

An error occurred in a process pppppppp. {Win32|Socket|Runtime} error, Code=mm[: nnnnnn][, zzzzzzzz]

Cause

An error occurred in the process indicated by pppppppp.

pppppppp: Target process name

{Win32|Socket|Runtime}: Type of error

Win32: Win32 API error

Socket: Socket error

Runtime: C runtime error

mm: Error code

nnnnnn: Explanation of the error code indicated by mm

zzzzzzzz: Maintenance information

Action

Check the explanation of the error code, and take appropriate action.

KDSF0140-E

An application exception occurred in process pppppppp.

Cause

An application exception occurred in the process indicated by pppppppp.

pppppppp: Target process name

Action

Contact Hitachi if necessary. If you choose to contact Hitachi, obtain DUMP.LOG beforehand.

KDSF0350-I

Connect to internet gateway. URL=xxxxxxxx

Cause

Connect to an internet gateway.

xxxxxxxx: URL

KDSF0351-I

Connect result=xxxxxxxx

Cause

A result of connecting to internet gateway.

result: Result is output with one of the following:

SUCCESS

A connection was successfully established.

ERROR_INTERNET

One of the following causes is likely.

(1) The server cannot interpret requests.

(2) A server certificate has not been installed.

ERROR_INTERNET_MIXED_SECURITY

The issuer of the server certificate cannot be trusted.

ERROR_INTERNET_SEC_CERT_DATE_INVALID

The certificate has expired.

ERROR_INTERNET_SEC_CERT_CN_INVALID

The domain name of the URL does not match the host name of the Internet gateway.

Action

Take action according to the result indicated in the message as shown below:

result=ERROR_INTERNET

(1) Review the host set with Host Name or IP address and the port set with Port Number which you can set by opening the Agent Configurations view of the Settings module, and under Basic settings, selecting Internet Connection Settings, and then Internet Gateway.

(2) Install a server certificate on the Internet gateway.

result=ERROR_INTERNET_MIXED_SECURITY

Install client certificates on the managed computer, which are necessary to trust the server certificate installed on the Internet gateway.

result=ERROR_INTERNET_SEC_CERT_DATE_INVALID

Install a valid server certificate and client certificates.

result=ERROR_INTERNET_SEC_CERT_CN_INVALID

Install the server certificate on the server (Internet gateway server) that has the common name specified when a request for a server certificate was made, and specify the common name to the Connection-destination settings of the Internet gateway.

KDSF0352-I

HTTP response code=xxxxxxxx

Cause

A result of communication to internet gateway.

response code: Response code is output with one of the following:

200

Ended in success.

400

The server cannot interpret requests.

401

The user authentication failed.

403

Access was denied.

404, 405, or 406

The request was not accepted.

407

The proxy authentication failed.

408

A timeout occurred.

Other than the above

An internal error occurred.

Action

Take action according to the response code indicated in the message as shown below:

response code=400

Check the server and the port number at the connection destination.

response code=401

Check the authentication user ID and password for the Internet gateway. Alternatively, check the connection destination.

response code=403

Check the authority of the authentication user. Alternatively, check the connection destination.

response code=404, 405, or 406

Check the connection destination.

response code=407

Check the user and password for the proxy server. Alternatively, check the host name and port number of the proxy server.

response code=408

If the problem persists, contact Support Service.

Other than the above

If the problem persists, contact Support Service.

Appendix

A. Miscellaneous Information

This appendix provides miscellaneous information about using JP1/IT Desktop Management 2.

A.1 Amendments for each version

(1) Changes in 13-11

(a) Changes in the manual (3021-3-L78-30(E))

The messages that have the following IDs were added:

KDEX5525-I, KDEX5526-E, KDEX5527-E, KDEX5528-E, KDEX5529-E, KDEX5530-E, KDEX5531-I, KDEX5533-E, KDEX5534-E, KDEX5535-E, KDEX5536-E, KDEX5537-E

(2) Changes in 13-10

(a) Changes in the manual (3021-3-L78-20(E))

The messages that have the following IDs were added:

KDEX4452-E, KDEX4600-I, KDEX4601-I, KDEX4602-E, KDEX4603-E, KDEX4604-W, KDEX4605-E, KDEX4606-E, KDEX4607-E, KDEX4608-E, KDEX4609-E, KDEX4610-E, KDEX5513-E, KDEX5514-E, KDEX5521-E, KDEX5522-E

(3) Changes in 13-01

(a) Changes in the manual (3021-3-L78-10(E))

The messages that have the following IDs were added:

KDEX5513-E, KDEX5514-E, KDEX5515-E, KDEX5516-E, KDEX5517-E, KDEX5518-E, KDEX5519-E, KDEX5520-E, KDEX5521-E, KDEX5522-E, KDEX5523-E, KDEX5524-E

The following event log messages are now also displayed in relay system.

19100, 19101, 19102

(4) Changes in 13-00

(a) Changes in the manual (3021-3-L78(E))

Windows Server 2022 was added as an applicable operating system for the following products:

JP1/IT Desktop Management 2 - Manager

JP1/IT Desktop Management 2 - Agent

JP1/IT Desktop Management 2 - Network Monitor

JP1/IT Desktop Management 2 - Asset Console

JP1/IT Desktop Management 2 - Internet Gateway

Windows 11 was added as an applicable operating system for the following products:

JP1/IT Desktop Management 2 - Agent

JP1/IT Desktop Management 2 - Network Monitor

Windows Server 2012 was removed from applicable OSs for the following products:

JP1/IT Desktop Management 2 - Manager

JP1/IT Desktop Management 2 - Asset Console

JP1/IT Desktop Management 2 - Internet Gateway

The messages that have the following IDs were added:

KDEX6154-E

The messages that have the following IDs were changed:

KDEX5482-I, KDEX5483-I, KDEX5484-E

(5) Changes in 12-60

(a) Changes in the manual (3021-3-E18-30(E))

The messages that have the following IDs were added:

KDEX5511-I, KDEX5512-I, KDEX6512-I, KDEX6513-I, KDEX7000-I, KDEX7001-I, KDEX7002-E, KDEX7003-I, KDEX7004-E, KDEX7005-E, KDEX7006-E, KDEX7007-E, KDEX7008-E, KDEX7009-E, KDEX7010-W, KDEX7011-E

(6) Changes in 12-50

(a) Changes in the manual (3021-3-E18-20(E))

The messages that have the following IDs were added:

KDEX4476-W, KDEX4477-W, KDEX4478-I

The messages that have the following IDs were changed:

KDEX4085-I, KDEX4091-I, KDEX4100-E, KDEX4101-E

(7) Changes in 12-10

(a) Changes in the manual (3021-3-E18-10(E))

Windows Server 2019 was added as an applicable operating system for the following products:

JP1/IT Desktop Management 2 - Manager

JP1/IT Desktop Management 2 - Agent

JP1/IT Desktop Management 2 - Network Monitor

JP1/IT Desktop Management 2 - Asset Console

JP1/IT Desktop Management 2 - Internet Gateway

Remote Install Manager

Log files for managing devices via an API from an external system were added.

The messages that have the following IDs were added:

KDEX2013-I, KDEX2014-I, KDEX2015-W, KDEX2016-E, KDEX2017-E, KDEX2018-E, KDEX2019-E, KDEX2020-E, KDEX3392-I, KDEX3394-I, KDEX3396-E, KDEX3397-E, KDEX3398-E, KDEX3399-E, KDEX3400-E

(8) Changes in version 12-00

(a) Changes in the manual (3021-3-E18(E))

Windows Server 2008 R2 was removed from applicable OSs for the following products:

JP1/IT Desktop Management 2 - Manager

JP1/IT Desktop Management 2 - Network Monitor

JP1/IT Desktop Management 2 - Asset Console

Remote Install Manager

The messages that have the following IDs were added:

KDEX1086-E, KDEX3390-I, KDEX3391-E, KDEX4120-I, KDEX4121-I, KDEX4122-E, KDEX4123-E, KDEX5509-I, KDEX5510-I, KDEX8100-I, KDEX8101-E

The basic log messages output by Agents that have the following IDs were added:

KDSF0350-I, KDSF0351-I, KDSF0352-I

(9) Changes in version 11-51

(a) Changes in the manual (3021-3-B58-40(E))

The messages that have the following IDs were added:

KDEX4127-E, KDEX4128-I, KDEX4129-W, KDEX4130-W, KDEX4131-E, KDEX4132-W, KDEX4133-W, KDEX4473-I, KDEX4474-I

The event log messages that have the following IDs were added:

2022, 2023

(10) Changes in version 11-50

(a) Changes in the manual (3021-3-B58-30(E))

The messages that have the following IDs were added:

KDEX3381-E, KDEX3382-E, KDEX3383-E, KDEX3384-I, KDEX3385-E, KDEX3386-E, KDEX3389-I, KDEX4451-E, KDEX4460-I, KDEX4461-I, KDEX4462-W, KDEX4463-E, KDEX4464-E, KDEX4465-W, KDEX4466-E, KDEX4467-E, KDEX4468-E, KDEX4469-E, KDEX4470-E, KDEX4471-E

(11) Changes in version 11-10

(a) Changes in the manual (3021-3-B58-20(E))

Windows Server 2016 was added as an applicable operating system for the following products:

JP1/IT Desktop Management 2 - Manager

JP1/IT Desktop Management 2 - Agent

JP1/IT Desktop Management 2 - Network Monitor

JP1/IT Desktop Management 2 - Asset Console

Remote Install Manager

The messages that have the following IDs were added:

KDEX3369-I, KDEX3370-I, KDEX3371-E, KDEX3372-E, KDEX3374-I, KDEX3375-I, KDEX3377-I, KDEX3378-E, KDEX3379-E

The event log messages that have the following IDs were added:

19200

(12) Changes in version 11-01

(a) Changes in the manual (3021-3-B58-10(E))

JP1/IT Desktop Management 2 - Operations Director was added as a relevant program product.

Windows 10 was added as an applicable operating system for JP1/IT Desktop Management 2 - Network Monitor.

The messages that have the following IDs were added:

KDEX3356-I, KDEX3357-E, KDEX3358-I, KDEX3359-E, KDEX3362-I, KDEX3363-E, KDEX4440-I, KDEX4441-E, KDEX4442-E, KDEX4443-E, KDEX4445-E, KDEX4446-E, KDEX4447-E, KDEX4448-E, KDEX4449-E, KDEX4450-E, KDEX5457-E, KDEX5458-E, KDEX5505-I, KDEX5506-I, KDEX5507-E, KDEX5508-I, KDEX9005-E, KDEX9006-E, KDEX9007-E, KDEX9008-E

The messages that have the following IDs were changed:

KDEX9003-E

The event log messages that have the following IDs were added:

7018, 11030, 11031, 11032, 19100 , 19101, 19102, 20000

(13) Changes in version 11-00

(a) Changes in the manual (3021-3-B58(E))

The messages that have the following IDs were added:

KDEX1084-E, KDEX1505-E, KDEX1506-E, KDEX1508-E, KDEX1514-E, KDEX1607-Q, KDEX1608-W, KDEX1609-W, KDEX2009-I, KDEX2010-E, KDEX2011-I, KDEX2012-E, KDEX3252-I, KDEX3253-I, KDEX3344-I, KDEX3345-E, KDEX4025-E, KDEX4029-E, KDEX4032-E, KDEX4383-Q, KDEX4384-Q, KDEX4397-E, KDEX4404-I, KDEX4405-E, KDEX4406-E, KDEX4407-E, KDEX4408-I, KDEX4409-I, KDEX4410-E, KDEX4411-E, KDEX4412-E, KDEX4413-E, KDEX4414-E, KDEX4415-E, KDEX4416-E, KDEX4417-E, KDEX4418-E, KDEX4419-E, KDEX4420-E, KDEX4421-E, KDEX4430-E, KDEX9000-I, KDEX9001-I, KDEX9002-E, KDEX9003-E, KDEX9004-E, and KDEX9100-I

The messages that have the following IDs were changed:

KDEX1595-I, KDEX2001-I, KDEX2002-E, KDEX4065-E, KDEX4124-E, KDEX4210-Q, KDEX4211-Q, KDSF0110-I, KDSF0111-I, and KDSF0112-E

The public message log file (JDNSTRCn.LOG) relating to configuration changes was added.

(Changes from only this manual (3021-3-378(E))) The messages that have the following IDs were added:

KDEX5437-I, KDEX5438-E

(14) Changes in version 10-50

(a) Changes in the manuals (3021-3-284 and 3021-3-378(E))

The event log messages output by the management server (event IDs: 0 to 19003) were added.

The event log messages output by relay systems (event IDs: 0 to 19003) were added.

The event log messages output by Agents (event IDs: 0 to 20000) were added.

The basic log messages output by Agents (message IDs: KDSF0001-I to KDSF0140-E) were added.

The messages that have the following IDs were added:

KDEX1079-W, KDEX1080-W, KDEX1081-W, KDEX1082-W, KDEX1083-W, KDEX1599-E, KDEX1600-Q, KDEX1601-Q, KDEX1602-Q, KDEX1603-E, KDEX1604-W, KDEX1605-W, KDEX1606-W, KDEX3308-I, KDEX3309-E, KDEX3333-I, KDEX3334-E, KDEX3338-I, KDEX5472-I, KDEX5473-E, KDEX5474-I, KDEX5475-E, KDEX5477-I, KDEX5478-E, KDEX5479-E, KDEX5480-E, KDEX5481-E, KDEX5482-I, KDEX5483-I, KDEX5484-E, KDEX5501-I, KDEX5502-I, KDEX5503-I, KDEX5504-I, and KDEX6153-E

The messages that have the following IDs were changed:

KDEX1526-I, KDEX1527-I, KDEX1528-E, KDEX1529-E, KDEX1530-E, KDEX1533-W, KDEX1547-E, KDEX1579-E, KDEX1584-E, KDEX1587-Q, KDEX1588-Q, KDEX1589-Q, KDEX1598-E, KDEX4003-E, KDEX4010-E, KDEX4011-I, KDEX4012-I, KDEX4014-W, KDEX4015-I, KDEX4017-W, KDEX4020-E, KDEX4021-E, KDEX4022-W, KDEX4023-E, KDEX4053-W, KDEX4054-W, KDEX4071-E, KDEX4072-E, KDEX4073-I, KDEX4083-E, KDEX4104-E, KDEX4105-E, KDEX4204-E, KDEX4210-Q, KDEX4220-E, KDEX4232-E, KDEX4403-E, KDEX5014-W, KDEX5064-W, KDEX5316-E, KDEX5326-E, KDEX5336-I, KDEX5337-E, KDEX5338-E, KDEX5339-E, KDEX5340-I, KDEX5341-E, KDEX5342-E, KDEX5346-E, KDEX5347-E, KDEX5360-E, KDEX5370-E, KDEX5395-E, KDEX5399-E, KDEX5400-E, KDEX5434-E, KDEX5435-E, KDEX5436-E, KDEX6110-I, KDEX6111-E, KDEX6112-E, KDEX6113-E, KDEX6114-E, KDEX6115-E, KDEX6116-E, KDEX6117-E, KDEX6118-E, KDEX6119-E, KDEX6120-I, KDEX6121-E, KDEX6122-E, KDEX6131-E, KDEX6132-E, KDEX6151-E, KDEX6152-E, KDEX6211-E, KDEX6221-E, KDEX6511-E, KDEX8004-E, and KDEX8006-E

The messages that have the following IDs were deleted:

KDEX4074-E, KDEX4075-E, and KDEX4076-E

Index

M

miscellaneous information[1]