Skip to main content


 

Symptoms

 

 

 

Forms integrated with Sharepoint 2013 were erring with:

 

Failed to initialize the Context: URL: https://portal.denallix.com/sites/k2 Username: Error Details: The remote server returned an error: (401) Unauthorized. Method: SharepointService.initializeContext.

 


When attempting to add the K2 App to a site, it is taking a long time while "We're adding your app" and then eventually errors out after 15~20 minutes with a retry option. Verbose ULS log contains error below:

Error when try to get access token when deploy AppInstanceId nguid] with AppPrincipalId i:0i.t|ms.sp.ext|pguid]. Exception=System.ArgumentNullException: Value cannot be null. Parameter name: applicationRealm
at Microsoft.SharePoint.SPSecurityContext.SecurityTokenForApplicationContext(SPIdentityContext userIdentityContext, String applicationId, Uri applicationRealm, SPApplicationContextAccessTokenType applicationTokenType, SPApplicationDelegationConsentType consentValue)
at Microsoft.SharePoint.SPServerToAppServerAccessTokenManager.GetAccessTokenForDeploymentTask(Guid siteId, SPUserToken userToken, String appPrincipalId)
at Microsoft.SharePoint.Lifecycle.SPAppPrincipalAccessTokenTask.<>c__DisplayClass1.b__0()

at Microsoft.SharePoint.SPUser.get_UserToken()
at Microsoft.SharePoint.Lifecycle.SPAppPrincipalAccessTokenTask.Deploy()
at Microsoft.SharePoint.Administration.SPAppTask.DeployOperation()
at Microsoft.SharePoint.Lifecycle.MonitoredTaskExecution.DoTask()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
 

 

Diagnoses

 


It was determined that Azure ACS proxy had been recently added.
 

 

Resolution

Removing the Azure Access Control Service (ACS) Proxy resolved the issue; allowing for the re-adding and re-running of the Registration wizard. Alternatively Microsoft may also have a fix for ACS Proxy if experiencing this issue when adding High Trust App on Premise.

 

 



 
Be the first to reply!

Reply