SharePoint 2016 with K2 Deploy App Failed

Note, this answer applies to K2 for SharePoint 4.7.

With K2 for SharePoint 4.7, for various reasons, it is now installed to your App Catalog, the app is then Registered with your K2 Server instance, then from there you deploy out to your site collections to make it available to them as needed. Once deployed, you will Activate the K2 App in those site collections. The following links show, in more detail, how to install the K2 App in your SharePoint Environment: 

Article from K2 for SharePoint User Guide:  To add the K2 for SharePoint app to the app catalog site 

Video walk-thru: Add K2 App - K2 for SharePoint - v4.7+

 If you're still struggling, our support team can help you step through the process as well.

Jason

As far as using MinRole to install and configure your SharePoint Farm environment, K2 isn't going to care as long as the required SharePoint features that it needs are available in your environment when you finally get to the stage of installing and configuring the K2 app in an App Catalog.

For instructions on Preparing SharePoint On-Premises for K2, look here:  Preparing SharePoint On-Premises

   -NOTE: this document lists the needed SharePoint Features and Capabilities for K2 for SharePoint to work.

For your App Catalog site location, you'll need to follow Microsoft's guidance based on how you're scoping your SharePoint web applications and site collections. I stress that because you may also have a need for SharePoint apps other than K2 as well, so take that into consideration. The following article from Microsoft Technet talks about how to Manage an App Catalog in SharePoint 2016:  https://technet.microsoft.com/en-us/library/fp161234(v=office.16).aspx

It's a bit more involved than what I can explain in a community site answer, but basically, because the App Catalog is scoped to a SharePoint Web Application, you typically create it with the URL of that web application. I've seen it created under the "/Sites/" managed path quite often for many web applications, but definitly plan that out first and be sure to review best practices from Microsoft. Then all site collections falling under that Web Application will be coupled to that specific App Catalog.

So, for example, my web application lives at: https://www.denallix.com, my App Catalog is created at https://www.denallix.com/sites/AppCatalog.

Then, for installing the K2 for SharePoint App into that App Catalog, look here: K2 for SharePoint App Deployment

You may be following this, but for detailed instructions on Planning, Installing and Configuring K2 on the whole, look here: Installation and Configuration Guide

I'll also mention, I know that there is obviously a lot of info in those links above, so if you need faster help and response, I would recommend contacting K2 Support. That way we can get someone to answer your questions on the spot. We can also guage much more quickly what your environment looks like and where you want to take it.

Regards,

Jason

This may be a little more than you need, but I wanted to add a little extra info for clarity in case others were reading.

From the standpoint of setting up your SharePoint Farm with MinRole, K2 isn't going to care as long as the features required by K2 for SharePoint to run, are present. Review, Preparing SharePoint On-Premises, if necessary though.

You'll need to follow Microsoft's best practices for where to create your App Catalog for a SP web application, so take a look at this article from Microsoft Technet. https://technet.microsoft.com/en-us/library/fp161234(v=office.16).aspx Basically, per the article, you may already know this too, "The App Catalog site is a special site collection. Because an App Catalog is scoped to a web application, all apps that you want to make available for a web application have to be in the App Catalog site collection for that web application."

So typically I've seen the app catalog created under the /sites/ managed path for a SharePoint web application. For example, a web application lives at [https://www.denallix.com], then the App Catalog coupled with that web application could be installed inside that web application at [https://www.denallix.com/sites/AppCatalogName]. Be sure to scope it out based on your business needs. You may have other SharePoint apps besides the K2 app to install, so be sure to consider that as well.

From there the K2 App will need to be installed into the App Catalog for your Web Application. See the K2 for SharePoint App Deployment page that talks about how to get the K2 for SharePoint App going under the SharePoint On-Premises section. You'll register the app with your K2 Server in the Application App Catalog, Deploy to the site collections that you will build your K2 Applications in from the Application App Catalog, then it's recommended that you do the Activation from there too. It's all pretty much manged from the Application's App Catalog now.

For more reference, you can get to the overall Installation and Configuration Guide here: https://help.k2.com/onlinehelp/K2blackpearl/ICG/4.7/Default.htm

I hope this points you in a helpful direction, but I do recommend calling K2 Support if you need a faster more taylored response. That way we can get a better picture of your environment to answer your questions immediately and make sure you're configuring it optimally, especially so you only have to do it once. :)

Regards,

Jason

This may be a little more than you need, but I wanted to add a little extra info for clarity in case others were reading.

From the standpoint of setting up your SharePoint Farm with MinRole, K2 isn't going to care as long as the features required by K2 for SharePoint to run, are present. Review, Preparing SharePoint On-Premises, if necessary though.

You'll need to follow Microsoft's best practices for where to create your App Catalog for a SP web application, so take a look at this article from Microsoft Technet. https://technet.microsoft.com/en-us/library/fp161234(v=office.16).aspx Basically, per the article, you may already know this too, "The App Catalog site is a special site collection. Because an App Catalog is scoped to a web application, all apps that you want to make available for a web application have to be in the App Catalog site collection for that web application."

So typically I've seen the app catalog created under the /sites/ managed path for a SharePoint web application. For example, a web application lives at [https://www.denallix.com], then the App Catalog coupled with that web application could be installed inside that web application at [https://www.denallix.com/sites/AppCatalogName]. Be sure to scope it out based on your business needs. You may have other SharePoint apps besides the K2 app to install, so be sure to consider that as well.

From there the K2 App will need to be installed into the App Catalog for your Web Application. See the K2 for SharePoint App Deployment page that talks about how to get the K2 for SharePoint App going under the SharePoint On-Premises section. You'll register the app with your K2 Server in the Application App Catalog, Deploy to the site collections that you will build your K2 Applications in from the Application App Catalog, then it's recommended that you do the Activation from there too. It's all pretty much manged from the Application's App Catalog now.

For more reference, you can get to the overall Installation and Configuration Guide here: https://help.k2.com/onlinehelp/K2blackpearl/ICG/4.7/Default.htm

I hope this points you in a helpful direction, but I do recommend calling K2 Support if you need a faster more taylored response. That way we can get a better picture of your environment to answer your questions immediately and make sure you're configuring it optimally, especially so you only have to do it once. :)

Regards,

Jason

This may be a little more than you need, but I wanted to add a little extra info for clarity in case others were reading.

From the standpoint of setting up your SharePoint Farm with MinRole, K2 isn't going to care as long as the features required by K2 for SharePoint to run, are present. Review, Preparing SharePoint On-Premises, if necessary though.

You'll need to follow Microsoft's best practices for where to create your App Catalog for a SP web application, so take a look at this article from Microsoft Technet. https://technet.microsoft.com/en-us/library/fp161234(v=office.16).aspx Basically, per the article, you may already know this too, "The App Catalog site is a special site collection. Because an App Catalog is scoped to a web application, all apps that you want to make available for a web application have to be in the App Catalog site collection for that web application."

So typically I've seen the app catalog created under the /sites/ managed path for a SharePoint web application. For example, a web application lives at [https://www.denallix.com], then the App Catalog coupled with that web application could be installed inside that web application at [https://www.denallix.com/sites/AppCatalogName]. Be sure to scope it out based on your business needs. You may have other SharePoint apps besides the K2 app to install, so be sure to consider that as well.

From there the K2 App will need to be installed into the App Catalog for your Web Application. See the K2 for SharePoint App Deployment page that talks about how to get the K2 for SharePoint App going under the SharePoint On-Premises section. You'll register the app with your K2 Server in the Application App Catalog, Deploy to the site collections that you will build your K2 Applications in from the Application App Catalog, then it's recommended that you do the Activation from there too. It's all pretty much manged from the Application's App Catalog now.

For more reference, you can get to the overall Installation and Configuration Guide here: https://help.k2.com/onlinehelp/K2blackpearl/ICG/4.7/Default.htm

I hope this points you in a helpful direction, but I do recommend calling K2 Support if you need a faster more taylored response. That way we can get a better picture of your environment to answer your questions immediately and make sure you're configuring it optimally, especially so you only have to do it once. :)

Regards,

Jason