Symptoms

We have created a new production SharePoint 2013 Farm. We installed K2 for SharePoint using the K2 for SharePoint Application Deployment executable. Everything appears to be ok. I can see the app in the app catalog, and I can add it to the site contents of a site. However, when we click on the app to Configure K2 Permissions and run the Registration Wizard we only get a blank screen. I have compared it with our development farm and all the settings appear to be correct. I am wondering if we missed something in the setup.
 

Diagnoses

_1
We determined that the new Sharepoint farm was using the same app domain URL as the existing Sharepoint farm. Each Sharepoint farm will need a separate app domain URL so traffic can be routed to the correct farm:

http://sharepoint.stackexchange.com/questions/141885/sharepoint-2013-app-domain-do-i-need-to-create-a-separate-app-domains-for-sepa

_2
When attempting to deploy the K2 application after the app domain changes, the following error occurred:

1:5: K2Application.LogErrors: 15:31:44:>> Logged Error: The following errors occurred while running the Powershell script:
Exception Info: ArgumentException, The name exceeds the maximum allowed length. Invocation Info: The error was generated by the following Powershell command: New-SPTrustedSecurityTokenIssuer. Stack trace: at <ScriptBlock>, C:SupportK2 for SharePoint 4.6.9 (4.13350.1660.1)InstallationSetupS2S-portal_intranet-80.ps1: line 54.
 

Resolution

_1
1. After obtaining a new Sharepoint app domain, please reconfigure the APP URL in the new farm to use this new app domain: Central Administration > Apps > App URLs.

* I believe the app prefix can remain the same, only the app domain will need to be updated
** Afterward please try pinging "apps-12345678ABCDEF.newappdomainurl.com" to see if it resolves to your new farm

2. Delete and recreate the app catalog in your new farm

3. Re-run the K2 "appdeployment.exe" on this new farm to redeploy the K2 apps to the app catalog

4. Test the adding and registration of the K2 apps again

_2
This was an issue recognized in 4.6.9 that was resolved in the 4.6.10 update. As a workaround, comment out the following in the above Powershell script and ran it manually:

_ $k2Uri = (USystem.Uri]$webServiceEnvFieldDefaultUrl).Authority.Replace(":","_")
_ $appName = "-" $k2Uri

_3
The user profile service sync task was also not setup correct, as such we configured the sync task:

http://help.k2.com/onlinehelp/K2ForSharePoint/ICG/4.6.11/default.htm_Install_Topics/Before/SP_Requirements.htm_UPS

We also ran this command below to address additional warning as K2 and Sharepoint was configured fot HTTP:

$c = Get-SPSecurityTokenServiceConfig
$c.AllowMetadataOverHttp = $true
$c.AllowOAuthOverHttp= $true
$c.Update()

https://technet.microsoft.com/en-us/library/jj655400.aspx