K2 for SharePoint AppDeployment error: "One or more app deployment processes could not complete successfully"

  • 24 February 2022
  • 0 replies
  • 10 views
MillaZ
Userlevel 5
Badge +20
 

K2 for SharePoint AppDeployment error: "One or more app deployment processes could not complete successfully"

kbt144947

PRODUCT
K2 blackpearl 4.7
This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
LEGACY/ARCHIVED CONTENT
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.

Issue

When trying to deploy the K2 for SharePoint App using K2 Setup AppDeployment, initial analysis is all green. When the App is being deployed to SharePoint, the following error is displayed

 

"One or more app deployment processes could not complete successfully"

Symptoms

After the error is displayed on the K2 for SharePoint AppDeployment screen, the following error is noticed when reviewing the K2 Setup - AppDeployment InstallerTrace File:
 

"The URL 'AppCatalog/K2 for SharePoint.app' is invalid.  It may refer to a nonexistent file or folder, or refer to a valid file or folder that is not in the current Web"

 

When attempting to manually upload the K2 for SharePoint App to the SharePoint App Catalog, the same error is displayed.

 

When reviewing the SharePoint ULS log, the following error is observed:
 

"Exception thrown storing stream in new SqlRemoteBlob: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation."

Troubleshooting Steps

This issue can be caused by low disk space on the SQL Server hosting the SharePoint Content database.

 

Please ensure sufficient free space is available on the local disk drive of the Server hosting the SharePoint Content SQL databases, as the K2 for SharePoint app is stored as binary data in the Content database.

Check out these Nintex University Learning paths: https://community.nintex.com/p/NintexUniversity

0 replies

Be the first to reply!

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings