Cause
Message appears when Active Directory Linkage command completed execution successfully.
Resolution
-
Cause
In Active Directory Linkage command, the entered parameter is incorrect. The parameters are insufficient or unnecessary parameter has been set.
Resolution
Inspect the parameter you entered.
Cause
In Active Directory Linkage command, the entered parameter is incorrect. The parameters are insufficient or unnecessary parameter has been set.
Resolution
Inspect the parameter you entered.
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
Inspect the parameter you entered.
Cause
The system environment has fault.
Resolution
Log off from Windows or restart OS, and then try again. If it cannot be started still, contact Fujitsu technical staff.
Cause
The current logon Windows user has no Administrator authority.
Resolution
Logon to Windows as Administrator and then execute.
Cause
The system environment has fault.
Resolution
Log off from Windows or restart OS, and then try again. If it cannot be started still, contact Fujitsu technical staff.
Cause
Because it is set as not Active Directory Linkage, so this program cannot be started.
Resolution
To Active Directory Linkage, modify the settings of Active Directory Linkage in the system settings window of Server Settings Tool.
Cause
Active Directory Linkage command is under execution.
Resolution
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.
Cause
The backup tool is under execution.
Resolution
To start Active Directory Linkage command, start Active Directory Linkage command after finishing the backup tool program.
Cause
The restoration tool is under execution.
Resolution
To start Active Directory Linkage command, start Active Directory Linkage command and then finish the restoration tool program.
Cause
In the service of the Management Server, data updating processing when the service is started is being performed.
Resolution
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.
Cause
Failed to access the database.
Resolution
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, perform "Exclusion Removal".
Cause
The database environment has fault.
Resolution
Contact Fujitsu technical staff.
Cause
Probable causes are as follows:
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, set the computer name, domain name, user ID and password of Active Directory to be linked correctly.
Cause
In the process of executing Active Directory Linkage command, data on Active Directory side has been moved or deleted.
Resolution
Try again later.
Cause
Failed to access the database.
Resolution
Confirm the database environment.
Cause
File SWDB.ini in Windows folder has been deleted, or content of file SWDB.ini is incorrect.
Resolution
Contact Fujitsu technical staff.
Cause
Content of file SWDB.ini is incorrect.
Resolution
Contact Fujitsu technical staff.
Cause
Content of file SWDB.ini is incorrect.
Resolution
Contact Fujitsu technical staff.
Cause
Failed to access the database.
Resolution
Confirm the database environment.
Cause
Failed to access the database.
Resolution
Confirm the database environment.
Cause
Failed to access the database.
Resolution
Confirm the database environment.
Cause
Failed to access the database.
Resolution
Confirm the database environment.
Cause
Failed to access the database.
Resolution
Confirm the database environment.
Cause
Failed to access the database.
Resolution
Confirm the database environment.
Cause
Failed to access the database.
Resolution
Confirm the database environment.
Cause
Failed to access the database.
Resolution
Confirm the database environment.
Cause
Failed to access the database.
Resolution
Confirm the database environment.
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
Try again later.
Cause
In the process of executing Active Directory Linkage command, computer on Active Directory side has been deleted, contradictions occurred in the processing.
Resolution
Try again later.
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
Try again later.
Cause
The registry has not be updated when the command is completed. The environment has fault.
Resolution
Contact Fujitsu technical staff.
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
Confirm whether the construction of the database is correct, or restore master information by using restoration function. When errors occurred, reconstruct the database or restore the master information.
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
Set correct path and file in the system settings window of Server Settings Tool.
Cause
Failed to read "Reference File of CT Logon Location". The file might have been destroyed.
Resolution
Confirm the file content.
Cause
Failed to close "Reference File of CT Logon Location". The file might have been destroyed.
Resolution
Confirm the file content.
Cause
CSV format of "Reference File of CT Logon Location" is incorrect.
Resolution
Confirm whether the double quotation mark and space characters are set correctly.
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
Set the computer name, user ID and domain name information in one line.
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
Set the correct computer name, user ID and domain name.
Cause
System error occurred when inspecting whether "Remote Desktop Connection" is used.
Resolution
Execute the program directly in the Management Server/Master Management Server under the condition that there is no user connected through the "Remote Desktop Connection" function.
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
Execute the program directly in the Management Server/Master Management Server under the condition that there is no user connected through the "Remote Desktop Connection" function.
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
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 get deleted, pay attention to this.
Cause
This command can only be used in Standard Edition.
Resolution
-
Cause
Failed to access the database. The level object information record of the affiliated group does not exist.
Resolution
Confirm whether the construction of the database is correct, or restore master information by using the restoration function correctly. When error occurred, reconstruct the database, or restoring the master information.
Cause
Failed to access the database. The user policy information record of the affiliated group does not exist.
Resolution
Confirm whether the construction of the database is correct, or restore master information by using the restoration function correctly. When error occurred, reconstruct the database, or restore the master information.
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
Set the correct path and file in the system settings window of Server Settings Tool.
Cause
Failed to read "Active Directory Linkage OU Target List". The file might have been destroyed.
Resolution
Confirm the file content.
Cause
Failed to close "Active Directory Linkage OU Target List". The file might have been destroyed.
Resolution
Confirm the file content.
Variable Information
%ld: where the exceeded characters in the "Active Directory Linkage OU Target List" are limited
Cause
The characters in the "Active Directory Linkage OU Target List" have exceeded the limit of 512 characters.
Resolution
Set the characters of each line within 512. (Including line break CR+LF)
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" exceeds the maximum length of the characters. Halfwidth and fullwidth are not distinguished in the OU name, and the maximum is 64 characters.
Resolution
Set the OU name within 64 characters.
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
Set the correct OU name.
Cause
Number of logon cases of "Active Directory Linkage OU Target List" has exceeded the upper limit. Set the number of logon cases within 100.
Resolution
Delete the unnecessary data in "Active Directory Linkage OU Target List".
Cause
The number of logon cases of "Reference File of CT Logon Location" has exceeded the upper limit. Set the number of logon cases within 200,000.
Resolution
Delete the unnecessary data in "Reference File of CT Logon Location".
Cause
The path of Active Directory Linkage processing settings file is too long.
Resolution
Confirm the entered value in ALLUSERSPROFILE of the environment variable parameter.
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
Use the available items only to record in the user properties of Active Directory Linkage processing settings file.
Cause
Values in unexpected format are contained in the data obtained from Active Directory.
Resolution
Contact Fujitsu technical staff.
Cause
The Computer Search Library of Active Directory is incorrect.
Resolution
Prepare the Search Library with the correct version number.
Cause
Probable causes are as follows:
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
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.
Cause
Probable causes are as follows:
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
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.
Cause
The computer level to be searched is too deep, and the path length of Active Directory has exceeded the upper limit.
Resolution
Modify the computer level of Active Directory.
Cause
"Active Directory Linkage OU Target List" does not exist. It might be caused because the drive, path or file does not exist.
Resolution
Set the correct path and file in the system settings window of Server Settings Tool.
Cause
The exclusion was not performed when intending to remove the exclusion status for Active Directory Linkage.
Resolution
Removal processing cannot be performed.
Cause
Systemwalker Desktop Patrol composition information import command is under execution.
Resolution
Confirm whether Systemwalker Desktop Patrol configuration information import command is under execution.
Cause
In the Active Directory Linkage settings function of Server Settings Tool, the relevant information of Active Directory to be linked is not registered.
Resolution
Specify Active Directory information of target path to be linked in the Active Directory Linkage settings function of Server Settings Tool.
Cause
Number of the logon items on the database end has exceeded the upper limit of possible data amount of linkage. The number of logon items on Systemwalker Desktop Keeper in linkage range are 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
Delete unnecessary data on Desktop Keeper side.
Cause
Number of the logon items on Active Directory side has exceeded the upper limit of possible data amount of linkage. 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
Delete the unnecessary data on Active Directory side.
Cause
The required memory space cannot be guaranteed.
Resolution
Execute again after canceling the unnecessary application, or deleting the unnecessary data on Active Directory side. If the memory is still insufficient, enlarge the server memory.
Cause
Characters that cannot be processed exist in Active Directory data, or the system environment of Active Directory Linkage command has fault.
Resolution
Confirm whether there are characters that cannot be processed on Active Directory. Besides, confirm the action environment of the program, if errors occurred during re-execution, restart Management Server, etc.
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 logon ID.
Resolution
After logon to "User Logon Name (UserPrincipalName)", perform Active Directory Linkage operation again.
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 halfwidth 40 characters (fullwidth 20 characters). This user information is not imported because it cannot be used as logonID.
Resolution
Shorten the length of "User Logon Name (UserPrincipalName)" to less than halfwidth 40 characters (fullwidth 20 characters), and then perform Active Directory Linkage operation again.
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" so that it does not include UNICODE characters, and then perform Active Directory Linkage operation.
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.
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.