After you add a new field to a CRM Desktop form, CRM Desktop displays an error that is similar to the following:

Updating error of object name object on storage {CEDC3D49-DDBB-93A2-4992-E5B2CAE62932}: object_locked (Conversion of input Message to Property Set failed with the error : Cannot convert XML Hierarchy to Integration Object Hierarchy. (SBL-EAI-04111)

This error occurs if the definition of an integration object in the SRF does not match the definition of the custom CRM Desktop form.

You can do the following work:

• Deploy your changes to the Siebel Runtime Repository.

After you add a new field to a form, CRM Desktop displays the form with the native Outlook form and then logs the following error:

Exception (struct ml::rethrowable_exception<struct resource_manager::resource_not_found>) encountered: "resource id 'lbl_location' not found"

This error occurs if you fail to add a localized value to the package_res.xml file.

You can do the following work:

• Add the appropriate localized value to the package_res.xml file. For example:

  <str key="lbl_location">Site:</str>

• Republish the package.

You add a new validation rule to a form but you cannot save or close the form when you add a new record. CRM Desktop displays an error that is similar to the following:

Exception 'class scripting::execute_exception' throwing: Script run-time error. 'phonetest' is undefined (Microsoft JScript runtime error) Line: 6, Char 7

Consider the following custom validation rule:

<rule message="#msg_business_phone_validation"> <expression>
<![CDATA[
var phonetes = new RegExp(/^[+]?[0-9]{0,3}[\s]?[\(-. ]?[0-9]{2,3}[\)-. ]?[\s]?[0-9]{3}[-. ]?[0-9]{2}[-. ]?[0-9]{2}$/);
item["Work Phone #"] != '' ? (item["Work Phone #"].match(phonetest) != null ? true : false) : true;
]]>
</expression>
</rule>

This example includes a typographical error in the declaration of the phonetest variable. The variable name is missing the last t character.

For more information, see Validation Rules You Can Configure for Custom Forms.

You can do the following work:

• Fix the variable name.
• Republish the package. For more information, see Republishing Customization Packages.

After you add a new field to a form, CRM Desktop displays the form with the native Outlook form and then logs the following error:

Exception 'struct xml::parse_error' throwing: Errors occurred during parsing the document! Code: 0xc00ce504 Line: 4 Column: 4 Public ID: unknown System ID: unknown. A name was started with an invalid character.

The following message in this log indicates that the XML is not valid:

'struct xml::parse_error'

You can do the following work:

• Make sure the custom XML you created uses the correct XML format and does not contain errors.
• To help locate the invalid syntax, identify all changes. You can use a diff tool that compares the XML to a previously working package and then highlights the changes.
• To identify an XML format error, use an XML schema validation tool.

You remove an existing field from a form. CRM Desktop displays the form momentarily but then the form goes blank. CRM Desktop logs the following errors:

14:46:21:262-2628: Exception 'class scripting::execute_exception' throwing: Script run-time error. 'undefined' is null or not an object (Microsoft JScript runtime error) Line: 77, Char 6

14:46:21:262-2628: Exception (struct ml::rethrowable_exception<class scripting::execute_exception>) encountered: "Script run-time error. 'undefined' is null or not an object (Microsoft JScript runtime error) Line: 77, Char 6"

These errors occur if JavaScript references a control that does not exist or if the control is not spelled correctly.

You can do the following work:

• To identify the control Id values, review the deleted elements.
• Perform a global search for code that references these values.
• Modify or remove all JavaScript code that references these control Ids.
• Republish the customization package.