Troubleshooting user creation jobs

 This topic describes troubleshooting user creation jobs. It contains the following sections:

• • Overview
  • To troubleshoot user creation jobs
  • Known issues relating to user creation jobs

Overview

After successfully completing the Update Server Properties (USP) job (that is, after the target RSCD agent is licensed and responding), BMC Cloud Lifecycle Management starts an NSH Script Job in BMC Server Automation that creates users.

Example from the log:

The user creation job creates a new user on the target virtual machine provided at the time the request for the service offering instance (SOI) was submitted. 

The script for the NSH Script Job is located in the /CSM_Scripts folder in the BMC Server Automation Depot. The script is named:

• (Windows) create_user_windows.nsh
• (Linux) create_user_linux.nsh

To troubleshoot user creation jobs

Check the job run log from the BMC Server Automation Console to determine if any failures occurred in the user creation job. If failures do occur, SOI provisioning fails and rollback occurs.

Known issues relating to user creation jobs

The following are known issues relating to user creation jobs.

Access denied error

This error can happen if insufficient permissions are configured on the source VM template.

To avoid this error, ensure that the exports file is configured for an administrator or an account that is part of an administrator group. Also, determine whether the configurations in the users and users.local files are valid.

"JNI file copy: No such file or directory" error

This issue occurs because the length of the source file location and destination is more than 256 characters, which exceeds the Windows limit.

There are two reasons for this:

• The installation location of BMC Server Automation that was specifed during installation of BMC Cloud Lifecycle Management is different and longer than the stand alone BMC Server Automation installation.
  
  Stand alone BMC Server Automation installation location: /opt/bmc/BladeLogic/8.1/NSH
  BMC Cloud Lifecycle Management installation location: /opt/bmc/BladeLogic/8.1/Operations Manager/NSH

• BMC Cloud Lifecycle Management creates two Application Server instances by default: job_deployment_hostname and config_deployment_hostname
  
  If the hostname includes the fully qualified domain name, then the length will be too long.
  For example: job_deployment_COELSEDVHQC119.iaas.coe.local
  
  The Application Server name can be shortened to honor the Windows 256 character limit.

  Note

  To rename an Application Server instance to a shorter name, the existing Application Server instance must be deleted first and then a new Application Server instance with a shorter name can be added.