Skip to main content
Nintex Community Menu Bar
Solved

Package deployment issue

  • Nov 12, 2025 5:47 AM UTC
  • 2 replies
  • 67 views
  • Translate All

Forum|alt.badge.img+4

I am trying to deploy a package created on my DEV server to the Production environment.
The solution is related to a SharePoint Online site, and I am working with K2 on-prem 5.8 FP17 + SharePoint Online.

When deploying to Production, I encounter the exact issue described here: 

In my case, this does not appear to be a permission issue. For the deployment, I am logged directly into the Production server and using a SharePoint admin account that also has K2 server administrator rights, so permissions should not be the problem.

Do you have any suggestions on how I can resolve this issue?

Thank you

Best answer by ovs

Hi ​@TinTex ,

Yes, the account is able to browse, is a site collection administrator and is able to start the K2 Application from the list level.

In the meantime I solved. On the destination (production) environment I tried to create a simple package with a SharePoint online test list and I was not able to create the package for errors.
The solution is this one, and is related to a OAuth token: 

 

 

View original

2 replies

Forum|alt.badge.img+11
  • Nintex Employee
  • Nov 12, 2025 3:23 PM UTC

Since the SharePoint Admin account reportedly has K2 access, can you confirm the ability of the same account to browse to the target site collection and the specific list/library in which you are deploying K2 to? Also, is the account able to successfully launch the 'K2 Application' on that list/library?

Translate

Forum|alt.badge.img+4
  • Author
  • Scholar
  • Answer
  • Nov 12, 2025 3:30 PM UTC

Hi ​@TinTex ,

Yes, the account is able to browse, is a site collection administrator and is able to start the K2 Application from the list level.

In the meantime I solved. On the destination (production) environment I tried to create a simple package with a SharePoint online test list and I was not able to create the package for errors.
The solution is this one, and is related to a OAuth token: 

 

 

Translate