3.1.5 Message Output with Active Directory Linkage Command

[ADSY-INF001] Active Directory Linkage command ended normally.

Cause

Message appears when Active Directory Linkage command completed execution successfully.

Resolution

[ADCI-ERR002] Parameter is not specified. Please specify parameter correctly.
DTKADCON /START [/R Retry Time]
Example: DTKADCON /START
Example: DTKADCON /START /R 5

Cause

In Active Directory Linkage command, the entered parameter is incorrect. The parameters are insufficient or unnecessary parameter has been set.

Resolution

Please inspect the parameter you entered.

[ADCI-ERR003] The parameter is specified incorrectly. Please specify parameter correctly.
DTKADCON /START [/R Retry Time]
Example: DTKADCON /START
Example: DTKADCON /START /R 5

Cause

In Active Directory Linkage command, the entered parameter is incorrect. The parameters are insufficient or unnecessary parameter has been set.

Resolution

Please inspect the parameter you entered.

[ADCI-ERR004] The parameter (retry times) is specified incorrectly. Please enter a value between 1 and 60.

Cause

A numeral out of the range from 1 to 60 has been enter in the retry times, or characters other than numerals have been entered.

Resolution

Please inspect the parameter you entered.

[ADSY-ERR005] Failed to get the information of user that logs on Windows.

Cause

The system environment has fault.

Resolution

Log off from Windows or restart OS, and then try again. If it cannot be started still, please contact Fujitsu technical staff.

[ADSY-ERR006] Administrator authority is required for executing this program.

Cause

This message appears when the current logon Windows user has no Administrator authority.

Resolution

Please logon to Windows as Administrator and then execute.

[ADSY-ERR007] Failed to get the domain information of the user that logs on Windows.

Cause

The system environment has fault.

Resolution

Log off from Windows or restart OS, and then try again. If it cannot be started still, please contact Fujitsu technical staff.

[ADSY-ERR008] Unable to start this program because it is set to not to execute Active Directory Linkage.

Cause

Because it is set as not Active Directory Linkage, so this program cannot be started.

Resolution

To Active Directory Linkage, please modify the settings of Active Directory Linkage in the system settings window of server settings tool.

[ADSY-ERR009] The Active Directory Linkage command has already been started. Unable to start repeatedly.

Cause

Active Directory Linkage command is under execution.

Resolution

Please confirm whether Active Directory Linkage command is under execution. In the console window, or confirm whether there is any user connected by using “Remote Desktop Connection” function (remote connection through the terminal service of Windows), and ask him/her to cancel executing Active Directory Linkage command.

[ADSY-ERR010] This program cannot be started because Backup Tool has been started.

Cause

The backup tool is under execution.

Resolution

To start Active Directory Linkage command, please finish the backup tool program first, and then start Active Directory Linkage command.

[ADSY-ERR011] This program cannot be started because Restoration Tool has been started.

Cause

The restoration tool is under execution.

Resolution

To start Active Directory Linkage command, please finish the restoration tool program first, and then start Active Directory Linkage command.

[ADDB-ERR012] This program cannot be started because collective update of database is running through the service program of Management Server. Please try again later.

Cause

In the service of the Management Server, data updating processing when the service is started is being performed.

Resolution

Please try again later. If it cannot be started after a while, confirm whether it is in exclusion status and remove the exclusion mark by using the exclusion status removal function of the server settings tool.

[ADDB-ERR013] The exclusion removal process failed when this program is ended.

Cause

Failed to access the database.

Resolution

Please confirm the database environment. Besides, confirm whether it is in exclusion status by using the exclusion status removal function of the server settings tool. If the exclusion mark of Active Directory Linkage command is in “Exclusion” status, please perform “Exclusion Removal”.

[ADSY-ERR014] Failed to decrypt the password for authenticating logon to Active Directory server.

Cause

The database environment has fault.

Resolution

Please contact Fujitsu technical staff.

[ADSY-ERR015] Failed to connect to Active Directory server. Please check whether the computer name, domain name, user name or password is correct.

Cause

It might be caused by the following.

In the Active Directory Linkage settings function of server settings tool, the computer name, domain name, user ID and password of Active Directory to be linked are incorrect.
Causes such as network, etc. result in the communication failure with the domain.

Resolution

In the Active Directory Linkage settings function of server settings tool, please set the computer name, domain name, user ID and password of Active Directory to be linked correctly.

[ADSY-ERR016] Data linkage cannot be continued because data in Active Directory has been moved or deleted while running the Active Directory Linkage command. The processing is interrupted.

Cause

In the process of executing Active Directory Linkage command, data on Active Directory side has been moved or deleted.

Resolution

Please try again later.

[ADDB-ERR017] Failed to access to database. Please confirm database environment.

Cause

Failed to access the database.

Resolution

Please confirm the database environment.

[ADDB-ERR018] DB connection information setting file (SWDB.ini) is not installed properly.

Cause

File SWDB.ini in Windows folder has been deleted, or content of file SWDB.ini is incorrect.

Resolution

Please contact Fujitsu technical staff.

[ADDB-ERR019] Unable to decrypt the password for DB connection of DB connection information setting file (SWDB.ini). The password may have been changed.

Cause

Content of file SWDB.ini is incorrect.

Resolution

Please contact Fujitsu technical staff.

[ADDB-ERR020] Unable to connect to the connection target database of DB connection information setting file (SWDB.ini).

Cause

Content of file SWDB.ini is incorrect.

Resolution

Please contact Fujitsu technical staff.

[ADDB-ERR021] Failed to access to database. (Failed to initialize recordset)

Cause

Failed to access the database.

Resolution

Please confirm the database environment.

[ADDB-ERR022] Failed to access to database. (Failed to get record)

Cause

Failed to access the database.

Resolution

Please confirm the database environment.

[ADDB-ERR023] Failed to access to database. (Failed to update record)

Cause

Failed to access the database.

Resolution

Please confirm the database environment.

[ADDB-ERR024] Failed to access to database. (Failed to add record)

Cause

Failed to access the database.

Resolution

Please confirm the database environment.

[ADDB-ERR025] Failed to access to database. (Failed to delete record)

Cause

Failed to access the database.

Resolution

Please confirm the database environment.

[ADDB-ERR026] ailed to access to database. (Failed to start transaction)

Cause

Failed to access the database.

Resolution

Please confirm the database environment.

[ADDB-ERR027] Failed to access to database. (Failed to submit transaction)

Cause

Failed to access the database.

Resolution

Please confirm the database environment.

[ADDB-ERR028] Failed to access the database. (Fail to rollback the transaction)

Cause

Failed to access the database.

Resolution

Please confirm the database environment.

[ADDB-ERR029] Failed to access the database. (Other DB errors)

Cause

Failed to access the database.

Resolution

Please confirm the database environment.

[ADSY-ERR030] Data linkage cannot be continued because data in Active Directory has been moved or deleted while running the Active Directory Linkage command. (The affiliated OU and container have been moved)The processing is interrupted.

Cause

In the process of executing Active Directory Linkage command, data on Active Directory side has been moved (the affiliated Container or OU has been changed), contradictions occurred in the processing.

Resolution

Please try again later.

[ADSY-ERR031] Data linkage cannot be continued because data in Active Directory has been moved or deleted while running the Active Directory Linkage command. (CT has been deleted) The processing is interrupted.

Cause

In the process of executing Active Directory Linkage command, computer on Active Directory side has been deleted, contradictions occurred in the processing.

Resolution

Please try again later.

[ADSY-ERR032] Data linkage cannot be continued because data in Active Directory has been moved or deleted while running the Active Directory Linkage command. (The affiliated OU and container have been deleted) The processing is interrupted.

Cause

In the process of executing Active Directory Linkage command, data on Active Directory side has been moved (the affiliated Container or OU has been deleted), contradictions occurred in the processing.

Resolution

Please try again later.

[ADSY-ERR033] Failed to output to registry.

Cause

The registry has not be updated when the command is completed. The environment has fault.

Resolution

Please contact Fujitsu technical staff.

[ADSY-ERR034] Failed to access to database. (Failed to view the record for viewing policy)

Cause

Failed to access the database. The record of terminal Initial Settings does not exist, or the level object information record of the affiliated group does not exist.

Resolution

Please confirm whether the construction of the database is correct, or restore master information by using restoration function. When errors occurred, please reconstruct the database or try restoring master information again.

[ADSY-ERR035] Failed to open "Viewing files of CT registration location".

Cause

Failed to open “Reference File of CT Logon Location”. It might be caused by the following.

Drive, path or file does not exist
No authority to access this path or file

Resolution

Please set correct path and file in the system settings window of server settings tool.

[ADSY-ERR036] Failed to read "Viewing files of CT registration location".

Cause

Failed to read “Reference File of CT Logon Location”. The file might have been destroyed.

Resolution

Please confirm the file content.

[ADSY-ERR037] Failed to close "Viewing files of CT registration location".

Cause

Failed to close “Reference File of CT Logon Location”. The file might have been destroyed.

Resolution

Please confirm the file content.

[ADSY-ERR038] Data format of "Viewing files of CT registration location" is incorrect.

Cause

CSV format of “Reference File of CT Logon Location” is incorrect.

Resolution

Please confirm whether the double quotation mark and space characters are set correctly.

[ADSY-ERR039] CSV format of "Viewing files of CT registration location" is incorrect.(line No. %ld)

Variable Information

%ld: where the CSV format is incorrect

Cause

There is no data in the CSV record of CT logon location file. Items of lines specified by “Reference File of CT Logon Location” are insufficient.

Resolution

Please set the computer name, user ID and domain name information in one line.

[ADSY-ERR040] Illegal characters are contained in the data of "Viewing files of CT registration location".(line No. %ld)

Variable Information

%ld: where the data of “Reference File of CT Logon Location” is incorrect

Cause

Incorrect characters exist in any of the computer name, user ID and domain name content in the specified line of “Reference File of CT Logon Location”.

Resolution

Please set the correct computer name, user ID and domain name.

[ADSY-ERR041] System error occurred when checking "Remote Desktop Connection". The processing is interrupted.

Cause

System error occurred when inspecting whether “Remote Desktop Connection” is used.

Resolution

Please execute the program directly in the Management Server or Master Management Server under the condition that there is no user connected through the “Remote Desktop Connection” function.

[ADSY-ERR042] This program cannot be used via the remote connection function of terminal service.

Cause

Try using the “Remote Desktop Connection” function (remote connection through the terminal service of Windows) to start this program. Or when there is user connected through the “Remote Desktop Connection” function in the system, try starting this program in the Central Console window.

Resolution

Please execute the program directly in the Management Server or Master Management Server under the condition that there is no user connected through the “Remote Desktop Connection” function.

[ADDB-ERR043] The registration information of Management Server is incomplete. The content of tables managed by Master Management Server/Management Server in database is abnormal.

Cause

The key value of node information table does not match that of physical node list table. Data restoration failed or errors occurred when constructing Management Server previously.

Resolution

Please logon after using server settings tool to delete Management Server in order to confirm whether the restored data is the correct backup data. Besides, when deleting Management Server, the combined CT below will also be deleted, please pay attention to this.

[ADDB-ERR044] This command is not supported in Base Edition.

Cause

This command can only be used in Standard Edition.

Resolution

[ADSY-ERR045] Failed to access to database. (Failed to view the record for viewing policy)

Cause

Failed to access the database. The level object information record of the affiliated group does not exist.

Resolution

Please confirm whether the construction of the database is correct, or restore master information by using the restoration function correctly. When error occurred, please reconstruct the database, or try restoring master information again.

[ADSY-ERR046] Failed to access to database. (Failed to view the record for viewing policy)

Cause

Failed to access the database. The user policy information record of the affiliated group does not exist.

Resolution

[ADSY-ERR047] Failed to open "List of organization unit targets for linking with Active Directory".

Cause

Failed to open “Active Directory Linkage OU Target List”. It might be caused by the following.

Drive, path or file does not exist
No authority to access this path or file

Resolution

Please set the correct path and file in the system settings window of server settings tool.

[ADSY-ERR048] Failed to read "List of organization unit targets for linking with Active Directory".

Cause

Failed to read “Active Directory Linkage OU Target List”. The file might have been destroyed.

Resolution

Please confirm the file content.

[ADSY-ERR049] Failed to close "List of organization unit targets for linking with Active Directory".

Cause

Failed to close “Active Directory Linkage OU Target List”. The file might have been destroyed.

Resolution

Please confirm the file content.

[ADSY-ERR050] Each line of "List of organization unit targets for linking with Active Directory" contains too many words.(line No. %ld)

Variable Information

%ld: where the exceeded characters in the line of “Active Directory Linkage OU Target List” are limited

Cause

Characters in the line of “Active Directory Linkage OU Target List” have exceeded the limit of 512 characters.

Resolution

Please set the characters of each line within 512. (Including line break CR+LF)

[ADSY-ERR051] The organization unit name of "List of organization unit targets for linking with Active Directory" is too long.(line No. %ld)

Variable Information

%ld: where the OU name of “Active Directory Linkage OU Target List” is too long

Cause

The OU name of “Active Directory Linkage OU Target List” has exceeded the maximum number of characters. Single-byte and double-byte are not distinguished in the OU name, and the maximum is 64 characters.

Resolution

Please set the OU name within 64 characters.

[ADSY-ERR052] Illegal characters are contained in the organization unit name of "List of organization unit targets for linking with Active Directory".(line No. %ld)

Variable Information

%ld: where the OU name of “Active Directory Linkage OU Target List” is incorrect

Cause

Incorrect characters are contained in the specified line of “Active Directory Linkage OU Target List”.

Resolution

Please set the correct OU name.

[ADSY-ERR053] Data imported from "List of organization unit targets for linking with Active Directory" is too much, it is unable to continue processing.

Cause

Number of logon cases of “Active Directory Linkage OU Target List” has exceeded the upper limit. Please set the number of logon cases within 100.

Resolution

Please delete the unnecessary data in “Active Directory Linkage OU Target List”.

[ADSY-ERR054] Data imported from "Viewing files of CT registration location" is too much, it is unable to continue processing.

Cause

The number of logon cases of “Reference File of CT Logon Location” has exceeded the upper limit. Please set the number of logon cases within 200,000.

Resolution

Please delete the unnecessary data in “Reference File of CT Logon Location”.

[ADSY-ERR055] Failed to get the path of Active Directory Linkage setting file (DTKADCON.ini).

Cause

The path of Active Directory Linkage processing settings file is too long.

Resolution

Please confirm the entered value in ALLUSERSPROFILE of the environment variable parameter.

[ADSY-ERR056] Items not allowed to be used is recorded in user properties of Active Directory Linkage setting file (DTKADCON.ini).

Cause

Unavailable items are recorded in the user properties of Active Directory Linkage processing settings file. Available items are the following four.

UserPrincipalName
Employeeid
Title
Department

Resolution

Please use the available items only to record in the user properties of Active Directory Linkage processing settings file.

[ADSY-ERR057] Unexpected value is set in the data obtained from Active Directory.

Cause

Values in unexpected format are contained in the data obtained from Active Directory.

Resolution

Please contact Fujitsu technical staff.

[ADSY-ERR058] Failed to search computer in Active Directory. Please confirm the version of library.

Cause

Incorrect computer Search Library of Active Directory is used.

Resolution

Please prepare the Search Library with the correct version number.

[ADSY-ERR059] Failed to search computer in Active Directory. Please check if the computer name, domain name, user name or password is correct.

Cause

It might be caused by the following.

In the Active Directory Linkage settings function of server settings tool, the computer name, domain name, user ID and password of Active Directory to be linked are incorrect.

Resolution

Please set the computer name, domain name, user ID and password of Active Directory to be linked correctly in the Active Directory Linkage settings function of server settings tool.

[ADSY-ERR060] Failed to connect to search while searching the computer in Active Directory. Please check whether the computer name, domain name, user name or password is correct.

Cause

It might be caused by the following.

In the Active Directory Linkage settings function of server settings tool, the computer name, domain name, user ID and password of Active Directory to be linked are incorrect.
Cannot communicate with the domain due to network, etc.

Resolution

Please set the computer name, domain name, user ID and password of Active Directory to be linked correctly in the Active Directory Linkage settings function of server settings tool.

[ADSY-ERR061] Failed to search computer in Active Directory because the level of search target computer is too deep.

Cause

The computer level to be searched is too deep, and the path length of Active Directory has exceeded the upper limit.

Resolution

Please modify the computer level of Active Directory.

[ADSY-INF062] Unable to link through organization unit because "List of organization unit targets for linking with Active Directory" does not exist.

Cause

“Active Directory Linkage OU Target List” does not exist. It might be caused by the following.

Drive, path or file does not exist

Resolution

Please set the correct path and file in the system settings window of server settings tool.

[ADSY-ERR063] The exclusion management table is in the status that exclusion control is not executed. Exclusion removal processing is not needed.

Cause

Message appears if the exclusion has not be performed when intending to remove the exclusion status for Active Directory Linkage.

Resolution

Removal processing cannot be performed.

[ADSY-ERR064] Unable to start this program because Systemwalker Desktop Patrol configuration information import command has been started

Cause

Systemwalker Desktop Patrol composition information import command is under execution.

Resolution

Please confirm whether Systemwalker Desktop Patrol configuration information import command is under execution.

[ADSY-ERR095] The target of Active Directory Linkage is not registered. The processing is interrupted.

Cause

In the Active Directory Linkage settings function of server settings tool, the relevant information of Active Directory to be linked has not logged on.

Resolution

Please specify Active Directory information of target path to be linked in the Active Directory Linkage settings function of server settings tool.

[ADSY-ERR096] The data imported from database is too much, data linkage cannot be continued. The processing is interrupted.

Cause

Number of the logon items on the database end has exceeded the upper limit of possible data amount of linkage. Please specify the number of logon items on Desktop Keeper end in linkage range within the following range.

The maximum logon amount of node information is 255 cases
The maximum logon amount of domain information is 255 cases
The total maximum logon number of computers and groups is 100,000 cases
The total maximum logon number of users and groups is 100,000 cases

Resolution

Please delete unnecessary data on Desktop Keeper side.

[ADSY-ERR097] The data imported from Active Directory is too much, data linkage cannot be continued. The processing is interrupted.

Cause

Number of the logon items on Active Directory side has exceeded the upper limit of possible data amount of linkage. Please specify the number of logon items on Desktop Keeper end in linkage range within the following range.

The total maximum logon number of users, computers, OU and Containers is 200,000 cases
The maximum logon number of users is 100,000 cases
The maximum logon number of OU and Containers is 10,000 cases

Resolution

Please delete the unnecessary data on Active Directory side.

[ADSY-ERR098] Insufficient memory occurred when importing registration information of Active Directory. The processing is interrupted.

Cause

The required memory space cannot be guaranteed.

Resolution

Please execute again after canceling the unnecessary application, or deleting the unnecessary data on Active Directory side. If the memory is still insufficient, please enlarge the server memory.

[ADSY-ERR099] Error occurred.

Cause

Characters that cannot be processed exist in Active Directory data, or the system environment of Active Directory Linkage command has fault.

Resolution

Please confirm whether there are characters that cannot be processed on Active Directory. Besides, please confirm the action environment of the program, if errors occurred during re-execution, please restart Management Server, etc.

Because "User Logon Name" in the user information of Active Directory is blank, the user information that is not imported exists. (%d name)

Variable Information

%d: number of people whose “User Logon Name (UserPrincipalName)” is blank

Cause

“User Logon Name (UserPrincipalName)” in the user information of Active Directory is blank. This user information has not been imported because it cannot be used as logonID.

Resolution

After logon to “User Logon Name (UserPrincipalName)”, please perform Active Directory Linkage operation again.

Because "User Logon Name" in user information of Active Directory exceeded40single-byte characters (20 double-byte characters), the user information that is not imported exists. (%d name)

Variable Information

%d: number of people whose “User Logon Name (UserPrincipalName)” has exceeded the specified length

Cause

In the user information of Active Directory, [User Logon Name] has exceeded the limit of single-byte 40 characters (double-byte 20 characters). This user information is not imported because it cannot be used as logonID.

Resolution

Please shorten the length of “User Logon Name (UserPrincipalName)” to less than single-byte 40 characters (double-byte 20 characters), and then perform Active Directory Linkage operation again.

Because the path name in path information of Active Directory is messy code, the path information that is not imported exists. (%d items)

Variable Information

%d: number of name of UNICODE characters in “OU Name”

Cause

UNICODE characters are used in the OU name of Active Directory. This OU information has not been imported because it cannot be used as group name.

Resolution

Modify the OU name as unusing UNICODE characters, and then perform Active Directory Linkage operation.

Because the computer name in computer information of Active Directory is messy code, the path information that is not imported exists. (%d items)

Variable Information

%d: number of name of UNICODE characters used in “Computer Name”

Cause

UNICODE characters are used in some “Computer Name” in the computer information of Active Directory. This computer information has not been imported because it cannot be used as computer name.

Resolution

Modify “Computer Name” as without using UNICODE characters, and then perform Active Directory Linkage operation.

Because user information of Active Directory contains messy code, the user information that is not imported exists.(%d name)

Variable Information

%d: number of people who use the name of UNICODE character in “User Logon Name (UserPrincipalName)”.

Cause

UNICODE characters are used in some “User Logon Name (UserPrincipalName)” in the user information of Active Directory. This user information has not been imported because it cannot be used as logon ID.

Resolution

After the modification of “User Logon Name (UserPrincipalName)” without using UNICODE characters, perform Active Directory Linkage operation again.