Runtime

RUN_1

Required field <Field Name> can not be empty or SPACE filled.

Synchronized null /space value to a required field from sponsor to receiver.

Ensure that required field values are not null or filled with spaces.

RUN_2

error when reading web service response from SM: Resource Unavailable

Synchronize updates from QC side to locked change/problem records.

Close the locked records in SM side.

RUN_2

Error when reading web service response from SM: Not authorized

There are two possible causes:

• Insufficient rights for the SM Integration user when creating/updating defect/requirement in QC or running synchronization to create/update the corresponding change/problem.
• Maximum active logins for integration account is exceeded.

1. Check the rights of integration account.
2. Check and make sure that Unlimited session in the Security tab is selected.

RUN_3

Error 23scxmlapi(23) - XML DOM exception caught - code 5 msg An invalid or illegal XML character is specified

Synchronization is performed with an illegal WSDL caption.

Correct the WSDL configuration.

RUN_4

Update failed 1/2/3, retry in 10 seconds, error message=…

Record is locked in SM.

Close the locked record.

RUN_5

Update failed for 3 times, skip, error message=...

Record is locked in SM.

Synchronize the record manually or run a full synchronization to run all missing updates.

RUN_6

Cannot get field for <Field Name>.

SM adapter cannot get a field.

Ensure that the stub jar has been generated correctly.

RUN_7

Value cannot be reached for <Field Name>.

SM adapter cannot find this field from the stub class.

Ensure that the stub jar has been generated correctly.

RUN_8

Mapping error, no such property <property name> defined in type <type name>.

SM adapter cannot find this property.

Ensure that the stub jar has been generated correctly.

RUN_9

Error during setting value for key <key name> with value <value>.

Dynamic model cannot find this key.

Ensure that the stub jar has been generated correctly.

RUN_10

Mapping file <file path> cannot be found!

The configuration file isn't found.

Please check the configuration file.

RUN_10

<Module builder class name> cannot be created because of <message>.

SM adapter cannot load a specified class.

Ensure that the stub jar has been generated correctly.

RUN_11

Can not convert to <target class name> from value <value>.

Value cannot be converted to target type.

Ensure that the WSDL does not expose non-supported data types.

RUN_12

Exception when getting SM response, return code: <return code>.

Problem with SM communication.

Refer to references for error messages.

RUN_13

Error when reading web service response from SM, record is locked [changeID=<recordID>], message=<Message>.

Record is locked.

Close the locked record.

RUN_14

The data in the '<field name>' field of record <record id> - of file <file name> contains data that does not conform to the SOA data type in datadict.

The SOAP field data type in the WSDL is not correct. If the field is of the Number type, the value in the database is out of the range of the specified SOAP type. For example, when choosing IntType (data range: (-2,147,483,648 to 2,147,483,647) for a Number field, if this field has a value of 2,147,483,648 (2^31), it will cause this error when reading the record through the web service interface.

If this field has a Number type, choose DecimalType in the WSDL. Otherwise select the correct SOAP type.

RUN_15

Unable to create envelope from given source: ...

The name of a structure field in Service Manager may have non-English characters.

Use English characters in the name of a structure field.

RUN_16

QC: findRequirementById: Failed getting requirement with id: <id>

Failed to update, record was not found or deleted on target null

Deleting or removing a record may result in this problem, because incremental synchronization will fail to find the record.

Restore this record or just run a "Full Synchronization" to remove this mapping relationship established for the record before.

RUN_17

Invalid byte 2 of 3-byte UTF-8 sequence.

There are some special non-English characters in the values of fields.

Update the WSDL definition for this field in Service Manager by leaving the "Type" field bank instead of specifying "StringType" for this field.