This section explains the 658XX message series.
Description
When using internal authentication
The user account name user_account_name specified for User has not been registered.
When using Single Sign-On
user_account_name is not registered in the directory service.
When using OpenDS for the directory service, there are multiple occurrences of the user ID user_account_name between registered users.
The user account name specified is displayed for user_account_name.
Corrective Action
Take corrective action based on the authentication method being used.
When using internal authentication
Check with the administrator if the specified user_account_name has been registered.
When using coordination with Single Sign-On
Check with the administrator if the user_account_name has been registered in the directory service.
When using OpenDS for the directory service, check with the administrator whether there are multiple occurrences of the user ID (uid attribute value).
Check that the user account name user_account_name is correct. If the name is wrong, specify the name again and then perform the operation.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
Description
The user account name user_account_name specified for User has already been registered.
The user account name specified is displayed for user_account_name.
Corrective Action
Check with the administrator if the specified user account name user_account_name has been registered.
Check that the user account name user_account_name is correct. If the name is wrong, specify the name again and then perform the operation.
If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
Description
The user account user_account_name does not have the privileges required for this operation.
Corrective Action
The privilege level might have been changed on other clients. Log in again using a privileged account.
Description
An unexpected error has occurred.
The error message detected by the manager is displayed in the details of the error dialog.
Corrective Action
When an error message is displayed in the details of the error dialog
Check the number of the error message and take corrective action.
When no error message is displayed in the details of the error dialog
Collect troubleshooting information and contact Fujitsu technical staff.
Description
For the maximum number of characters "parameter_name : character length == length" permitted in parameter (user account, password, or server), the upper limit is upper_limit and the lower limit is lower_limit.
If parameter is a password, it is represented using asterisks ("*").
Corrective Action
Specify the parameter using a value between lower_limit and upper_limit.
Description
An invalid character is included in the parameter name parameter_name of parameter (user account, password, authority level, or server).
If parameter is a password, parameter_name is represented using asterisks ("*").
Corrective Action
Specify the parameter again using valid characters.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
See
For details of valid characters, refer to the following:
For Virtual Edition
The user ID given in "Chapter 5 Managing User Accounts" in the "User's Guide VE"
The password (and the password confirmation) given in "Chapter 5 Managing User Accounts" in the "User's Guide VE"
The authority level set in "Chapter 5 Managing User Accounts" in the "User's Guide VE"
The physical server name given in "7.3.2 Registering Blade Servers" or "7.4.1 Registering Rack Mount or Tower Servers" in the "User's Guide VE"
For Cloud Edition
The user ID given in "3.1 Registering User Accounts" in the "User's Guide for Infrastructure Administrators (Resource Management) CE"
The password (and the password confirmation) given in "3.1 Registering User Accounts" in the "User's Guide for Infrastructure Administrators (Resource Management) CE"
The physical server name given in "5.4.2 Registering Blade Servers" or "5.5.1 Registering Rack Mount or Tower Servers" in the " User's Guide for Infrastructure Administrators (Resource Management) CE ".
Description
Registration failed because a user with the same name as userid has already been registered.
Corrective Action
Enter a user ID that has not been registered.
[Cloud Edition]
Description
Registration failed because a user with the same name as userid has already been registered.
Corrective Action
Enter a user ID that has not been registered.
Description
Changing the user failed because the password entered is incorrect.
Corrective Action
Enter the current password of the user to be changed.
Description
Registration or changing of the user failed because the password to be registered or changed and the password for confirmation did not match.
Corrective Action
Use the same password for registration or changing of the user as the password used for confirmation.
Description
The specified user account cannot be deleted as there is only one user account with administrator authority registered.
Corrective Action
To delete the specified user account it is necessary to register another user account with administrator authority.
[Virtual Edition]
Description
Communication with the directory server used for ServerView Operations Manager to perform Single Sign-On failed.
Corrective Action
Check the following and take corrective action:
Confirm whether the configuration for communication with the directory server used for ServerView Operations Manager is correct, or the directory server has been started.
After checking the amount of free disk space and the network connection, perform the operation again.
For the configuration, refer to "10.4.1.3 Checking Directory Service Connection Information" in the "Design Guide VE".
When ServerView Operations Manager or the directory server used for ServerView Operations Manager has been re-installed, or certificates have been updated, re-registration of certificates with Resource Orchestrator is necessary.
For details on the method for registering certificates, refer to "Chapter 10 Installing and Defining Single Sign-On" in the "Design Guide VE".
When the following operations have been performed, re-registration of certificates with Resource Orchestrator is necessary.
Re-installation of ServerView Operations Manager
Re-installation of the directory server used for ServerView Operations Manager
Updating of the certificate of ServerView Operations Manager
Updating of the certificate of the directory server used by ServerView Operations Manager
For details on the method for registering certificates, refer to "Chapter 10 Installing and Defining Single Sign-On" in the "Design Guide VE".
The importing and registering of certificates performed when installing this product may have failed.
Check whether the certificates are imported correctly. For details on how to check the certificates, refer to "Chapter 10 Installing and Deciding Single Sign-On" in the "Design Guide VE".
The password for the administrator user of the directory server registered in Resource Orchestrator may be incorrect.
Check if the directory server can be accessed using the password specified when installing Resource Orchestrator, or when registering or updating the directory server.
When an incorrect password is used, refer to "10.4.1.3 Checking Directory Service Connection Information" in the "Design Guide VE".
[Cloud Edition]
Description
The directory server could not be communicated with.
Corrective Action
Check the following and take corrective action:
Check whether the settings for communication with the directory server are correct.
Settings for communication with the directory server can be checked using the rcxadm authctl command.
For details, refer to "5.4 rcxadm authctl" in the "Reference Guide (Command/XML) CE".
When the following operations have been performed, re-registration of certificates with Resource Orchestrator is necessary.
Re-installation of ServerView Operations Manager
Re-installation of the directory server used for ServerView Operations Manager
Updating of the certificate of ServerView Operations Manager
Updating of the certificate of the directory server used by ServerView Operations Manager
For details on the method for registering certificates, refer to "Chapter 12 Installing and Defining Single Sign-On" in the "Design Guide CE".
Confirm that the directory server has been started.
Then perform the operation again.
The importing and registering of certificates performed when installing this product may have failed.
Check whether the certificates are imported correctly. For details on how to check the certificates, refer to "Chapter 12 Installing and Deciding Single Sign-On" in the "Design Guide CE".
The password for the administrator user of the directory server registered in Resource Orchestrator may be incorrect.
Check if the directory server can be accessed using the password specified when installing Resource Orchestrator, or when registering or updating the directory server.
When an incorrect password is used, refer to "12.4.1.3 Checking Directory Service Connection Information" in the "Design Guide CE".
[Virtual Edition]
Description
The process failed because the specified user has no authority level for Resource Orchestrator.
Corrective Action
Check the following items:
The specified user needs to have a sufficient authority level for login on the Resource Orchestrator in order to use Single Sign-On.
Check the authority level of Resource Orchestrator, and then execute the command again.
For the configuration, refer to "Chapter 10 Installing and Defining Single Sign-On" in the "Design Guide VE".
The search base value specified during directory service registration may be incorrect.
Check the search base value, and then execute the command again.
For the configuration, refer to "Chapter 10 Installing and Defining Single Sign-On" in the "Design Guide VE".
[Cloud Edition]
Description
The process failed because the specified user has no authority level for Resource Orchestrator.
Corrective Action
Check the following items:
The specified user needs to have a sufficient authority level for login on the Resource Orchestrator in order to use Single Sign-On.
Check the authority level of Resource Orchestrator, and then execute the command again.
For the configuration, refer to "Chapter 12 Installing and Defining Single Sign-On" in the "Design Guide CE".
The search base value specified during directory service registration may be incorrect.
Check the search base value, and then execute the command again.
For the configuration, refer to "Chapter 12 Installing and Defining Single Sign-On" in the "Design Guide CE".
[Cloud Edition]
Description
The user information registered in the directory service could not be changed.
The following causes are possible:
The specified password is not compliant with the user password policy of the directory service
Corrective Action
Check the user password policy for the directory service and ensure that the specified password is compliant with the policy.
[Cloud Edition]
Description
The user cannot be created as a user with the same name as the user user exists in the directory service.
Corrective Action
Check if the specified user ID is correct.
When using a user registered in directory service in Resource Orchestrator, create a user with the settings configured not to register a user in directory service using the directory service operation definition file.
For details on the directory service operation definition file, refer to "8.6.1 Settings for Tenant Management and Account Management" in the "Operation Guide CE".
[Cloud Edition]
Description
The user cannot be changed as the specified user user does not exist in the directory service.
A user in the directory service may have been deleted.
Corrective Action
Perform one of the following corrective actions:
Delete the current user, then create a new one.
After creating a user in the directory service, add it to the members of "cn=IflowUsers,ou=group,base_DN" group.
[Cloud Edition]
Description
A user cannot be registered as the group group_name does not exist in the directory service. There is an error in directory service environment.
Corrective Action
Create the group "cn=group_name,ou=group,base_DN" in directory service.
[Cloud Edition]
Description
Operations of obj_name in the directory service failed.
The following causes are possible:
The specified password is not compliant with the user password policy of the directory service.
The specified user ID is not compliant with the restrictions for user names of the directory service.
Corrective Action
Check the information in detail_message or the logs in the directory service, and perform corrective action for the error.
When the password is not compliant with the password policy
Check the user password policy for the directory service and ensure that the specified password is compliant with the policy.
When the user name is not compliant with user name restrictions
Check the user name restrictions of the directory service, and then check if the specified user ID is compliant with the user name restrictions. When the specified user ID is not compliant with the user name restrictions, perform the operation again after changing the user ID.
For errors other than the above, refer to the manual of the directory server, and take corrective action.
Information
When setting "sAMAccountName" for "User Search Filter" in the directory service settings for ServerView Operations Manager using Active Directory as the directory service, the creatable user names are restricted as below.
User names must be within 20 characters.
A period cannot be specified as the last character of a user name.
For details on the directory service settings of ServerView Operations Manager, check with the system operation administrator or the infrastructure administrator. When installing ServerView Operations Manager, the default is sAMAccountName. When using the application process, it is necessary to set sAMAccountName.
