Bienabee

Code

Error

Description

ALM-U10000

Upgrade finished with internal problem: {0}

An internal error occurred during upgrade.

ALM-U10001

Found problems in a project that cannot be fixed. Upgrade aborted.

Upgrade failed. Problems were found in the project that cannot be fixed automatically by theRepair tool.

ALM-U10002

Verification failed on the project. Upgrade aborted.

Upgrade failed during the internal verification phase.

ALM-U10003

The verification process detects additional problems in the upgraded project. The project is corrupted.

Upgrade failed. Problems were found during the internal post-upgrade verification phase. The project status is set toCorrupted.

ALM-U10004

List field {0} does not exists in LISTS

Found list field that does not exist in the LISTS table.

ALM-U10005

A graph referenced by Document Generator does not exist. Graph name: {0}, Graph owner: {1}, Target module {2}.

Found reference to graph that does not exist.

ALM-U10006

Public Document Generator named {0} will lose reference to {1} graph named {2}. References to private graphs from public settings are not reproducible.  

Internal inconsistency in graph configuration.

ALM-U10007

Failed to copy template file: {0} from {1}.

Check for failure reason in log file.

ALM-U10008

Verify passed and found problems that will be fixed by the 'Repair tool'. For more information on the verification process you can refer HP Knowledge Base on the following link:http://support.openview.hp.com/selfsolve/document/KM1281892

The Verify tool found problems that can be fixed automatically by theRepair tool.

ALM-U10009

Verify passed and found problems that cannot be fixed by the 'Repair tool'. Open the verification report to view the problems that must be fixed manually. For guidance on how to fix your problems you can refer HP Knowledge Base on the following link:http://support.openview.hp.com/selfsolve/document/KM1281892

The Verify tool found problems that cannot be fixed automatically by theRepair tool.

ALM-U10108

Failed to upgrade the following analysis item record: {0}

Failed to upgrade an analysis item to the updated version format.

ALM-V10001

No database server type specified

Missing information about the project’s database type.

ALM-V10002

Database server type specified ({0}) is not supported

The detected database type is not supported by ALM.

ALM-V10003

Specified authentication mode is not recognized

The detected database authentication type is not supported by ALM.

ALM-V10004

no SID specified

No SID property was provided.

ALM-V10005

No project name specified

No project name was provided.

ALM-V10006

No user name specified

No user name was specified.

ALM-V10007

Exceptions file {0} does not exist

The specified exception file does not exist.

ALM-V10008

Exception occurred: {0}

A general software exception occurred.

ALM-V10009

No primary key found for table {0} while checking for duplicate values

Missing primary key for table.

ALM-V10010

A primary key with more than one column is invalid.

Invalid primary key.

ALM-V10011

The output folder {0} cannot be created. Using the temp folder {1} instead.

Cannot create output folder for reports.

ALM-V10012

Failed to write to log file {0}

Failed to write specified file.

ALM-V10013

Cannot parse the filters file {0}

Failed to read a configuration file.

ALM-V10014

Failed to create SQL commands from correction events

Failed to create SQL script to fix schema.

ALM-V10015

Unable to generate a log file name for {0} task

Failed to write log file.

ALM-V10016

Unable to find the corresponding handler {0} while parsing the exceptions file {1}

Internal error in reading exception file.

ALM-V10017

A schema difference that cannot be automatically corrected has been detected: {0}

Detected difference between actual schema and expected schema format. The Repairtool cannot fix detected problems.

ALM-V10018

The database schema name {0} contains invalid characters

Fix the schema name.

ALM-V10019

Operation system user {0} can't access the project repository

The specified user cannot access the project repository. This may be caused by a permissions issue.

ALM-V10020

Operation system user {0} does not have the necessary permissions on the following sub folder of the project repository: {1}

The specified user cannot access the project repository. This may be caused by a permissions issue.

ALM-V10021

Some duplicates found, see files under {0} for more information

Duplicated records found. See the specified report for more information.

ALM-V10022

Some sequence problems were found. See files under {0} for more information

Detected table sequence errors. See the specified report for more information.

ALM-V10023

Some tree problems were found. See files under {0} for more information

Detected an entities hierarchy problem. See the specified report for more information.

ALM-V10024

Some tables were created with SQL Server Authentication and some with Windows Authentication

Not all tables were created using the same authentication method (MS-SQL).

ALM-V10025

Some objects were created on the project's schema by a different user

Not all objects in schema were created by the same user (ORACLE).

ALM-V10026

Database system user {0} does not have the necessary permissions on the DB server

Missing permissions are written in log file.

ALM-V10027

Requirement types sanity has found some warning

An internal inconsistency was found in the requirement types table. This can be fixed automatically by the Repair tool.

ALM-V10028

Requirement Name is not set to be Required for at least one Requirement Type

An internal inconsistency was found in the requirement types table. This can be fixed automatically by the Repair tool.

ALM-V10029

DB version {0} is not supported

The database version is not supported in the current version of ALM.

ALM-V10030

Repository folders were found outside project root. All '*_directory' values in 'DATACONST' table should lead to sub folder in project root. Please set it right and run verify again.

Project repository folder tree is invalid. Restore the project from backup.

ALM-V10031

Found incorrect group masks in new columns

Internal inconsistency in ALM configuration.

ALM-V10032

There is no write permissions for the file: {0}

Fix permission problem.

ALM-V10033

File not found: {0}

Check why file not found.

ALM-V10034

There is no information about the database.

Failed to read information on the project’s database.

ALM-V10035

Database user permissions for upgrade are insufficient

Missing database permissions. The log file contains a list of missing permissions.

ALM-V10036

Service Test resource type is missing.

Internal inconsistency in ALM configuration.

ALM-V10037

Obsolete transition rules were found

Internal inconsistency in ALM configuration.

ALM-V10038

Obsolete records in system field table were found

Internal inconsistency in requirement types table. This will be fixed automatically by the Repair tool.

ALM-V10039

Found records with incorrect zero values

Internal inconsistency in requirement types table. This will be fixed automatically by the Repair tool.

ALM-V10040

Found records with incorrect subtype information

Internal inconsistency in requirement types table. This will be fixed automatically by the Repair tool.

ALM-V10041

Found tests with an empty test type. Test ids = {0}

Internal inconsistency in requirement types table. This will be fixed automatically by the Repair tool.

ALM-V10042

Found empty subtype for TEST entity

Internal inconsistency in requirement types table. This will be fixed automatically by the Repair tool.

ALM-V10043

Found records in system field table with incorrect user label values

Internal inconsistency in requirement types table. This will be fixed automatically by the Repair tool.

ALM-V10044

Found record in system field table with incorrect permission value

Internal inconsistency in requirement types table. This will be fixed automatically by the Repair tool.

ALM-V10045

Found records in RBT_CUSTOMIZATION_QUESTIONS table with incorrect alignment value

Internal inconsistency in requirement types table. This will be fixed automatically by the Repair tool.

ALM-V10046

Found records in system field table with incorrect values for field size.

Internal inconsistency in requirement types table. This will be fixed automatically by the Repair tool.

ALM-V10047

Found records in system field table with incorrect field size value for link type record.

Internal inconsistency in requirement types table. This will be fixed automatically by the Repair tool.

ALM-V10048

Found obsolete records in modules table.

Internal inconsistency in requirement types table. This will be fixed automatically by the Repair tool.

ALM-V10051

The current text search feature is not configured well

‘Text Search’ configuration error.

ALM-V10052

Failed. Role 'CTXAPP' is not granted to schema.

‘Text Search’ configuration error.

ALM-V10054

Some duplicate values found, see file dup_values.txt under {0} for the list of duplicate values (the Repair tool will fix this problem)

Detected invalid duplicate values.

ALM-V10055

Schema differences were found

Actual schema differs from expected schema.

ALM-V10056

Schema name cannot contain the following characters

Fix schema name.

ALM-V10058

Text search is enabled for unsupported fields

‘Text Search’ configuration error.

ALM-V10059

Text search problems were found. Do not rebuild the text search indexes.

‘Text Search’ configuration error.

ALM-V10061

Some text search indexes are invalid: {0}

‘Text Search’ configuration error.

ALM-V10062

Smart repository folder under {0} is not allowed.

Optimized repository verification found a problem in the existing repository structure.

ALM-V10063

Smart repository folder exists in project that do not use smart repository feature.

Optimized repository verification found a problem in the existing repository structure.

ALM-V10064

Smart repository folder under {0} is missing.

Optimized repository verification found a problem in the existing repository structure.

ALM-V10065

Smart repository folder is missing under repository root.

Optimized repository verification found a problem in the existing repository structure.

ALM-V10066

Projects using Version Control for versions earlier than Quality Center 10.00 cannot be upgraded.

You should disable version control in projects older than Quality Center 10.00.

ALM-V10067

Projects with checked out entities cannot be upgraded.

All entities must be checked in before upgrade begins.

ALM-V10069

Failed registering a feature as denied in an edition.

License error. Check for solution in support site.

ALM-V10070

Failed registering a field to a feature.

License error. Check for solution in support site.

ALM-V10071

Failed signing the given license file.

License error. Check for solution in support site.

ALM-V10072

Failed verifying public key.

License error. Check for solution in support site.

ALM-V10073

Failed verifying signature.

License error. Check for solution in support site.

ALM-V10074

Invalid date format (should use 'yyyy-MM-dd').

License error. Check for solution in support site.

ALM-V10075

Invalid QC Edition name.

License error. Check for solution in support site.

ALM-V10076

License ID for extension is invalid or not specified.

License error. Check for solution in support site.

ALM-V10077

Invalid license file.

License error. Check for solution in support site.

ALM-V10078

License file not signed properly.

License error. Check for solution in support site.

ALM-V10079

A license violation has occurred. Operation aborted.

License error. Check for solution in support site.

ALM-V10080

License file is missing a mandatory license term {0}.

License error. Check for solution in support site.

ALM-V10081

Unsupported license file version.

License error. Check for solution in support site.

ALM-V10082

Modify License Operation Failed. Value of 'Issued To' field must be identical to the value in the existing license.

License error. Check for solution in support site.

ALM-V10083

Failed to move license quotas.

License error. Check for solution in support site.

ALM-V10084

Critical error in licensing mechanism.

License error. Check for solution in support site.

ALM-V10085

Current license file was corrupted.

License error. Check for solution in support site.

ALM-V10086

Try to load invalid PPU license file.

License error. Check for solution in support site.

ALM-V10087

Failed activate domain license pool.

License error. Check for solution in support site.

ALM-V10088

Failed deactivate domain license pool.

License error. Check for solution in support site.

ALM-V10089

Failed clean license statistic usage

License error. Check for solution in support site.

ALM-V10100

Failed to initialize license service.

License error. Check for solution in support site.

ALM-V10101

Failed to update administrator properties.

License error. Check for solution in support site.

ALM-V10102

The license file is already loaded.

License error. Check for solution in support site.

ALM-V10103

License XML Schema not found. License file not validated.

License error. Check for solution in support site.

ALM-V10104

Cannot synchronize {0} with id {1} because it is checked out by another user.

Library synchronization failed.

ALM-V10105

Failed rich text conversion for requirement {0}

Failed to convert requirement rich text field to new format.

ALM-V10106

Cannot convert requirement ID: {0} because its file is too big.

Rich content field conversion failed.

ALM-V10107

Conversion has not enough memory to continue.

Rich content field conversion failed.

ALM-V10109

{0} is a core feature and its settings cannot be modified.

License error. Check for solution in support site.

ALM-V10110

Update license file cannot serve as QC main license.

License error. Check for solution in support site.

ALM-V10111

Unable to create license terms parser.

License error. Check for solution in support site.

ALM-V10112

Failed extracting edition from license file.

License error. Check for solution in support site.

ALM-V10113

Failed generating evaluation license.

License error. Check for solution in support site.

ALM-V10114

Failed generating private key.

License error. Check for solution in support site.

ALM-V10115

Failed generating public key.

License error. Check for solution in support site.

ALM-V10116

Failed to make signature for given input.

License error. Check for solution in support site.

ALM-V10117

Failed loading license file.

License error. Check for solution in support site.

ALM-V10118

Failed parsing license file.

License error. Check for solution in support site.

ALM-V10119

Failed parsing license file terms.

License error. Check for solution in support site.

ALM-V10120

Missing mandatory element 'full_test_director'.

License error. Check for solution in support site.

ALM-V10121

Failed parsing XML document.

License error. Check for solution in support site.

ALM-V10122

Failed reading license file.

License error. Check for solution in support site.

ALM-V10123

Verification of the project failed. Repository migration aborted.

Optimized repository verification found a problem in the existing repository structure.

ALM-V10124

Found problems in a project that cannot be fixed. Repository migration aborted.

Optimized repository verification found a problem in the existing repository structure.

ALM-V10125

Repository migration failed. Resume the migration process by starting the process again.

Optimized repository migration error. Try to resume the operation.

ALM-V10126

Project is already migrated to new repository.

Internal error during migration to the Optimized Repository.

ALM-V10127

Error when setting project status as pending repository migration.

Internal error during migration to the Optimized Repository.

ALM-V10128

The project has files or folders which contain characters of locale that is not supported in the project's DB.

Internal error during migration to the Optimized Repository.

ALM-V10129

The project's schema should be restored into DB with the same locale as the file system locale.

Internal error during migration to the Optimized Repository.

ALM-V10130

Following are the files/folders paths (relative to project's repository root path) which have the problematic characters (represented with '?'):

Internal error during migration to the Optimized Repository.

ALM-V10131

DB Tables Population thread: {0} - failed

Internal error during migration to the Optimized Repository.

ALM-V10132

Skipping file. The file path {0} contains illegal characters.

Internal error during migration to the Optimized Repository.

ALM-V10133

Repository scanning found {0} files containing illegal characters. Check that the locale of the projects repository file system is compatible with the skipped file names character set. In case there is no problem with the projects repository file system locale, follow the instructions in the following file\: {1} 

Internal error during migration to the Optimized Repository.

ALM-V10134

There are duplicate files by the path {0}. These files differ only by case. This may occur, when the project repositories file system is case sensitive, and the projects database schema is case insensitive. 

Internal error during migration to the Optimized Repository.

ALM-V10135

Migration of project {0} under domain {1} has completed with warnings

Internal error during migration to the Optimized Repository.

ALM-V10136

Migration of project {0} under domain {1} has completed with warnings. For more details, download the migration log from the Repository Migration Status dialog box.

Internal error during migration to the Optimized Repository.

ALM-V10137

Migration of project {0} under domain {1} has stopped unexpectedly

Internal error during migration to the Optimized Repository.

ALM-V10138

Migration of project {0} under domain {1} has stopped unexpectedly. For more details, download the migration logs from the Repository Migration Status dialog box, and resume the process after the problem is resolved.

Internal error during migration to the Optimized Repository.

ALM-V10139

Migration of project {0} under domain {1} has stopped unexpectedly. For more details, review the attached migration logs, and resume the process in the Repository Migration Status dialog box after the problem is resolved.

Internal error during migration to the Optimized Repository.

ALM-V10140

Repository alignment failed. Resume the alignment process by starting the process again.

Internal error during migration to the Optimized Repository.

ALM-V10141

File system scanner thread: {0} - failed

Internal error during migration to the Optimized Repository.

ALM-V10142

File system scanning thread {0} failed to fill in file descriptors - sanity timeout. File entries queue is full more than {1} minutes.

Internal error during migration to the Optimized Repository.

ALM-V10143

The project repository migration did not start since the repository migration was not completed yet

Internal error during migration to the Optimized Repository.

ALM-V10144

Failed scanning the project's optimized repository

Internal error during migration to the Optimized Repository.

ALM-V10145

The project repository root folder is missing. Canceling repository realigning

Internal error during migration to the Optimized Repository.

ALM-V10146

Failed enabling foreign key of optimized repository tables. Run the following SQL query  on your project DB to locate the problematic records\:

Internal error during migration to the Optimized Repository.

ALM-V10147

Optimized repository scan works too slow. Check connection to database and file system (Only {0} files scanned per second).

Internal error during migration to the Optimized Repository.

ALM-V10148

BPT DB Inconsistencies Found.

Business Components configuration error.

ALM-V10149

Records in SYSTEM_FIELD table (SF_ROOT_ID column) contain references to missing or invalid records in {1} table ({2} column).

Database corruption. Records in SYSTEM_FIELD table contain references to lists in LISTS or ALL_LISTS table that either do not exist or are not to be referenced.

Refer to documentKM1415350 (internal document to be required from the support with further assistance).

ALM-V10150

Incorrect Oracle sequences found.

Database corruption: The Oracle sequence objects are not synchronized with related table values. The Repair tool will automatically fix this issue.

ALM-V10160

Failed to extract model from license file.

License configuration error.

ALM-V10161

Failed loading license key X.

License configuration error.

ALM-V10162

Failed adding the following license keys:

License configuration error.

ALM-V10163

Failed reading license key X.

License configuration error.

ALM-V10164

Failed verifying license file validity.

License configuration error.

ALM-V10165

Failed installing license file.

License configuration error.

ALM-V10166

Critical error in licensing mechanism.

License configuration error.

ALM-V10167

Failed signing the license used count file.

License configuration error.

ALM-V10168

Required license type does not exist. Verify the types required by the license file are declared in Spring files of the deployed extensions, and that those extensions are loaded.

License configuration error.

ALM-V10169

The product license is not loaded properly. Please contact your Site Administrator.

License configuration error.

ALM-V10170

Invalid ALM Edition name X. Using platform edition instead.

License configuration error.

ALM-V10171

Invalid domain and project license assignments. Please check the total available licenses in the site.

License configuration error.

ALM-V10172

Invalid domain name in license assignments. Domain name X does not exist in the Site.

License configuration error.

ALM-V10173

Invalid project uid in license assignments. Project uid X does not exist in the Site.

License configuration error.

ALM-V10174

Invalid assignment for license type id X. There are no installed licenses for this type.

License configuration error.

ALM-V10175

Invalid assignment for license type X. There are no installed licenses for this type.

License configuration error.

ALM-V10176

License type id X assigned more licenses than Y that available on site.

License configuration error.

ALM-V10177

Invalid license assignments under domain X for license type id Y.

License configuration error.

ALM-V10178

Invalid domain and project license assignments file. The signature is wrong. Reassign the licenses or reinsert the original license assignment file.

License configuration error.

ALM-V10179

Invalid license usage count xml. The signature is wrong. Reinsert the original xml.

License configuration error.

ALM-V10180

Reassignment of user X from license type Y with expiration Z cannot be changed within 30 days from the assignment itself.

License configuration error.

ALM-V10181

Failed building new AutopassJ with properties

License configuration error.

ALM-V10182

Edition name X does not exist. The mapping from edition name to enabled features contains invalid edition name.

License configuration error.

ALM-V10183

Feature name X does not exist. The mapping from edition name to enabled features contains invalid feature name.

License configuration error.

ALM-V10184

License type ID X does not exist. The mapping from license type ID to supported licensed features contains invalid License type ID.

License configuration error.

ALM-V10185

Licensed feature ID X does not exist. The mapping from license type ID to supported licensed features contains invalid licensed feature ID.

License configuration error.

ALM-V10186

Licensed feature ID X does not exist. The dependency of extension Y is invalid.

License configuration error.

ALM-V10187

The extension name X is invalid. This extension is not deployed to the server.

License configuration error.

ALM-V10188

Project contains customized folders. Needs manual repair.

Needs manual repair. Refer to document:KM1330901

ALM-V10189

Project contains entity update permission inconsistencies.

Some entities have field update permission without entity update permission or have entity update permission without field update permission for some groups.

ALM-V10191

New licenses have been loaded, but no edition is reported. The user cannot log in to any project. Load the proper licenses.

License configuration error.

ALM-V10192     

Found SMART_REPOSITORY_LOGICAL_FILE table requires defrag 

In order to overcome exceeding of the signed int that server as table key