• SmartObject [name] could not be found
• SmartObject with name [name] could not be found

• The error can occur when the incorrect SmartObject name is used in your code
• In some cases, this error can occur if you don't have Server Administrator permissions on your K2 environment

• If using custom code, you may need to call the SmartObject using its System Name, not its Display Name
• Ensure you have the correct permissions on your K2 environment to execute the targeted SmartObject

Property [property] is a required property for selected method [method]. Value must be set.

• A blank value is being passed into a required property (for example, you mapped a workflow variable into a SmartObject step but the variable value is empty at runtime, or the rules mapping in SmartForms is passing an empty value into the required property)
• Someone edited the SmartObject method and added a method parameter, but the workflows/forms that call the SmartObject weren't updated to include the new parameter
• The underlying service object changed and it now requires a property to be set, but the SmartObject created against the service object is not passing the new required property
• If you have a composite SmartObject and you are passing a value returned by one service object method into a subsequent service object method, the value returned by the first service object method is empty and the second service object method fails

• Ensure there is no blank value being passed in the required property
• Ensure that the workflows/form are updated to reflect the updated SmartObject method and method parameter
• Ensure the SmartObject is updated to reflect the change in the service object
• Ensure there is no blank value being passed from the first service object method to the second service object method

Primary credentials not authenticated. session not authenticated.

The error can occur by an expired K2 service account admin/app token

Renew the expired admin/app token for the K2 service account by re-running SharePoint App Registration using an Azure Tenant Admin user account to grant consent

Transaction (Process Id [id]) was deadlocked on lock resources with another process

• The error can occur because the transaction selected in the service object is set to Rollback.
• The error can occur due to poor K2 database performance

• See KBT161728 to resolve this error
• Run database indexing maintenance to defragment the database for better performance, or adjust the behavior of the underlying SmartObject/Service Instance to execute faster

The SmartObject Unknown or one of its components could not be resolved

The error can occur when a composite SmartObject is missing method bindings to a SmartBox SmartObject.

To resolve this error, ensure there is data in the SmartBox SmartObject associated with the composite SmartObject.

SmartObject definition does not contain a method

This error can occur when the K2 service account does not have the db_owner permissions configured on your K2 environment.

To resolve this error ensure that the K2 service account has  db_owner permissions configured on your K2 environment.

SmartObject server exception: a nested transaction was not committed

This error typically occurs when a SmartObject executes but there is an underlying problem with a data store required as part of the internal execution, or the record being accessed is locked for editing by another operation.
Example 1: You may have a rule that uploads a file and the next rule updates the same record with some additional data. The file upload rule may not have completed yet, which means the row is locked for editing by the first rule when the second rule tries to update the same record.
Example 2: A SmartObject is that is accessing multiple data sources. For example, the SmartObject may be using OAuth with a resource for authentication. At runtime, the OAuth resource is not configured correctly which means that the SQL operation to retrieve the OAuth configuration fails, which in turn results in the ‘stack’ of internal operations for the SmartObject execution failing.
Example 3: The underlying K2 SQL database is full. When the SmartObject is executing, K2 cannot perform some SQL operation, resulting in the ‘stack’ of internal operations for the SmartObject failing.

For a scenario like example 1, try to move rule execution around or otherwise delay execution of the second rule until the first rule has completed. You can also try to change the rule execution block from a batch operation to a sequential (one after the other) operation.
For a scenario like example 2, ensure that the OAuth resource configuration for the Service Instance is correct. You can try to execute the SmartObject with static credentials to see if it is the OAuth configuration causing the transaction problem.
For a scenario like example 3, check that there are no underlying issues with the K2 database, such as being out of space or some permission error causing the internal operation to fail.

Error: Deserializing Type: [Type Name] Name: '' Message: ''[Message Detail]'

This error can occur due to a disconnect between the SQL SmartObject resource service instance and the object.

To resolve this error, package all the SmartObjects listed under the erroring category and then deploy them. By doing this, all the SmartObjects get reconnected to their resources and this resolves the error.

This operation can only be performed on a file; %truncated folder path% is a folder

This error occurs when you use a specific sequence of characters (such as /AAA_190022/022) for the Create Folder method of a SharePoint 2016 Library-based SmartObject

This a known issue. To resolve this error update your K2 environment with K2 Five 5.3 Fix Pack 32

The given key was not present in the dictionary

This error occurs when you execute an Advanced SmartObject and the SmartObject needs to join data from another SmartObject

This a known issue. To resolve this error update your K2 environment with K2 Five 5.2 Fix Pack 32

Unable to retrieve SmartObject. Input string was not in a correct format

This error occurs when you use the "?$filter" filter against an OData SmartObject

This a known issue. To resolve this error update your K2 environment with K2 Five 5.3 Fix Pack 17

SmartObject Server Exception: String or binary data would be truncated. The date for table-valued parameter “@ServiceObjects” doesn’t conform to the table type of parameter

Known Issue

This a known issue. To resolve this error update your K2 environment with K2 Five 5.3 Fix Pack 25