Troubleshoot bulk user upload | Adobe Admin Console

The Import Users (bulk upload) feature allows you as an enterprise administrator to create a file consisting of user identities and to submit this file to the enterprise customer admin user management page for processing. Each entry in the file represents a user and the result of processing is that each user has an account created. Since many thousands of accounts can be involved, the status and progress of processing is displayed to you, and you can cancel the processing of the file at any time.

Enterprise accounts are created as a result of a customer purchase of a license agreement with Adobe that entitles the customer to a specified number of licenses to various Adobe products. On the completion of the purchase transaction, an agent at Adobe creates an account for the organization and creates a user with administrative capabilities for that account. That administrator can create and manage the user accounts for members of their organization.

Function

When a file is selected for processing, the following pre-checks are made and error messages emitted in case checks fail.

• File in CSV format
• Header legal, if present
• 1-5000 entries

For each entry:

• The email address should be legal
• Zero or more specified product configurations
• Country, if present, is legal and a country where Adobe does business
• Options, if present, are legal

A limit of 5000 entries per file is the maximum that can be processed for each import operation.

When a file is processed, each entry is processed individually as follows:

When processing of all file entries is completed, an email message is generated to the initiating user informing them of completion and results summary.

If the import operation is canceled, processing ceases when practical. Processing that has been completed is not rolled back.

User interface

In the List Users panel of the administrative console, there is an icon for uploading a user file. The file must be of type "csv" and have a .csv suffix. Its format is described below.

When import in selected, a dialog shows that displays instructions, has a link to download a sample file, and has a link to browse and select a file for upload and processing.

Once a file is selected for processing, it is prechecked for validity and any detectable errors reported. If there are none, the file is saved on the server and processing begins. Only a single import operation can be in progress for a given organization (regardless of domain) so subsequent initiation of import operations is disabled until the first one is completed.

When accepted for processing a line is displayed in Import Results tab of the List Users panel. The entry shows the following:

• Filename
• date/time of upload and start of processing
• Status (Processing / Completed / Canceled) (updated periodically)
• Number of accounts created (updated periodically)
• Number of errors (updated periodically)
• Processing rate (entries/second) (updated periodically)
• Estimated time remaining (updated periodically)
• A control to cancel the operation (only when processing is in-progress)
• Link to report (when processing has finished)
• A control to delete the entry (when processing has finished)

Clicking the filename gives a pop-up report with more details of the processing when status is Completed or canceled. Summary counts of successes and various kinds of failures are shown. Only nonzero values are displayed.

As processing occurs, any created users begin to show up in the Active User List if it is displayed (or the count updated if that is displayed).

As processing occurs, and user invitations generated show up in the Pending invites list if it is displayed (or the count updated if that is displayed)

The report is available when processing finishes and shows the results for each entry processed. In the report, there are three columns:

• Line number
• Email address
• status and error message (if any)

The report is sorted by line number and the line numbers correspond to the original line number in the csv file.

Important: The Import Results page displays reports that are 90 days old or less. Reports that are more than 90 days old are automatically removed, without the interference of a System Admin.

File format

The file that lists the users must conform to RFC 4180 (CSV file specification).  If present, the header line must be as follows:

Type, Email, ProductConfigurations, user name, CountryCode, FirstName, LastName, Options

Note: these fields may change periodically. Make sure your header matches the latest sample from the Admin Console.

These fields are defined as follows:

Troubleshoot bulk upload

This section helps you troubleshoot error conditions or other problems that could arise when using the bulk import functionality with the Adobe Admin Console.

"Invalid Configuration Names" error

If you are getting the error "Invalid Configuration Names" ("INVALID_CONFIGURATIONS") check the product configuration in the Admin Console:

• If the product configuration is "Default configuration" this is a virtual configuration provided as an example. You must edit this configuration to convert it to a real, working product configuration.
• If you create a new product configuration "Default configuration" will disappear.
• After editing the product configuration or creating a new one, try the bulk import again.

Validate CSV format

Validate your CSV file by comparing it to the sample template in the dashboard. The important fields are first name, last name, user ID, email address, and country code.

If the user exists, the import doesn't fail. Instead, you see a message that the user exists in the bulk upload report.

The upload report lists other errors separately from existing user warnings.

Required fields for the different types of User ID:

Known issues

The import error message in the bulk import report is currently truncated on the right side. This will be corrected in a future build of the Admin Console.

Import error conditions, messages, and response codes

Some specific cases:

Peformance details

To avoid overloading, a 66.6% duty cycle rule is part of processing.  If the time to process an entry differs from the rolling average by more than 10%, then the throttle is adjusted so that request processing consumes only 2/3 of real time.

In addition, an operations team managed throttling control also limits the processing rate.  If the throttling control is explicitly set, then the duty cycle control is disabled. There is an API call to switch back to duty cycle-based throttling.

The number of requests processed per second is displayed to you to provide feedback on performance.

The target rate for creation of 1000 accounts with each being added to 2 product configurations is 1 account/second, not counting the 66.6% duty cycle, so the apparent processing rate would be .66 account/second, or about 40 accounts/minute.  Creation of 1000 accounts at this rate would take 25 minutes.  Creation of 5000 accounts at this rate would take two hours and five minutes.