Thursday, June 26, 2014

Procedure to debug and resolve SharePoint 2013 Access App creation common errors "Sorry, something went wrong."

Microsoft provides the following three major instructions to configure SharePoint 2013 Access App.

If you follow the steps described, you might still running into several major issues creating Access Apps. Kirk Evans provided additional procedures to fix additional configuration issue. In this blog, I’ll summarize the most common error when we creating the Access App and the procedure how to debug and fix them.

1. The first common error is to create access app and get the following "small problem" message:

“Let’s Try this again… Everything is fine, but we had a small problem getting your license. Please go back to the SharePoint Store to get this app again and you won’t be charged for it.
If ‘Retry’ doesn’t work, return to your site and try again later.”

The message probably means you’re trying to add Apps using the SharePoint System Account, which we found out is not allowed by design as importing App licenses under this account could lead to performance problems. Change to no system account will fix the issue.

2. The second issue is to create access app and get the following "don't have sufficient permissions" message:

"Sorry, but you don't have sufficient permissions to perform that action."  

The message probably means you have missed some configuration steps and some of them could be the followings.
  • SharePoint database setting needed to create Access App databases
    • Access service pool account with dbcreator, securityadmin permission
    • Enable Contained Databases = True
    •  Allow Triggers to Fire Others = True
  • SharePoint Server side
  • IIS setting
    • Access service pool need to set “Load User Profile” value to True.
Please note some database setting change requires database restart and SharePoint might also need to be restarted in order to take the latest configuration changes.

3. The third issue is to create access app and get the "Sorry, something went wrong." message:

"Access Services is unable to process the request."

If you have already fixed the configuration listed in 1 & 2, this message probably means you have site collection that are created in the NEW content databases that Access Service do not have permission to access. This is common for Excel Service and Office Web Apps. The fix is to run the following powshell commands to grant access to process identity for the Access service account.

$w = Get-SPWebApplication –Identity http://sharepointwebapp


4.  The forth issue is to create access app and get server error message:

“Server Error in ‘/’ Application  The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL
and make sure that it is spelled correctly.”

The message probably means the Webapp has been configured with host header. You could remove the host header to resolve this issue.

5. The fifth issue is to create access app and get the following error messge "Access Service unable to process the request".

The ULS logs usually display the error like this:

WcfSendRequest: RemoteAddress: 'http://spsbx15:32843/6b6e34f635b243f8b7ba23a98ecf70cb/AccessService.svc' Channel: 'Microsoft.Office.Access.Services.WebService.IAccessServiceSoap' Action: '' MessageId: 'urn:uuid:ccf3ee91-0f6d-45f7-a679-7668a38434cb'   b7feb29c-98fc-00e4-e462-3c75d2f0ff50
                Line 18724: 08/28/2014 10:51:53.77          w3wp.exe (0x44F4)                       0x32A4 Access Services                 Web Front End                            agpau    High       [Forced due to logging gap, Original Level: Verbose] ServerSession.ExecuteWithSecurityContext: After issuing the request to server {0} [id: {1}]. ServerRequestCount: {2}, AllServersRequestCount: {3}, workerThreads: {4}, completionPortThreads: {5}           b7feb29c-98fc-00e4-e462-3c75d2f0ff50
                Line 18725: 08/28/2014 10:51:53.85          w3wp.exe (0x44F4)                       0x32A4 Access Services                 Web Front End                            agpao    Medium               ServerSession.ProcessServerSessionException: An exception during ExecuteWebMethod has occurred for server: http://SPSBX15:32843/6b6e34f635b243f8b7ba23a98ecf70cb/AccessService.svc, method: OpenWorkbook, ex: Microsoft.Office.Access.Services.Proxy.ServerSessionException: An error has occurred. ---> System.ServiceModel.ServiceActivationException: The requested service, 'http://spsbx15:32843/6b6e34f635b243f8b7ba23a98ecf70cb/AccessService.svc' could not be activated. See the server's diagnostic trace logs for more information.    Server stack trace:      at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory`1 factory, WebException responseException, ChannelBinding channelBinding)     at System.Servic...     b7feb29c-98fc-00e4-e462-3c75d2f0ff50
                Line 18726: 08/28/2014 10:51:53.85*        w3wp.exe (0x44F4)                       0x32A4 Access Services                 Web Front End                            agpao    Medium                  ...eModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)     at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)     at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout)     at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)     at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)     at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)    Exception rethrown at [0]:      at System.Runtime.Remoting.Proxies.RealProxy.HandleRetur...

Please check the URL highlighted (http://spsbx15:32843/6b6e34f635b243f8b7ba23a98ecf70cb/AccessService.svc) and the page will not be loaded. You could find the access service from IIS server and bounce the service. This will resolve the issue.
There are dozens of configuration you should be double check based on Microsoft's white paper and Kirk Evans' blog.