Access Services – Unexpected error occurred while running macro

I created an Access Services Database and published it to SharePoint. I created a BeforeChange macro that would calculate the next tracking number. The macro would execute fine when I ran it from the client Access, but when attempting to perform the same actions from the Web App, I’d get the following error. Access Services – Unexpected error occurred while running macro.

Error in the Event Logs on the Application Server:

(Event ID 6875) Error loading and running event receiver Microsoft.Office.Access.Server.AccessServicesListEventReceiver in Microsoft.Office.Access.Server.Application, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c. Additional information is below.

: “Microsoft.Office.Access.Server.Quickflow.Runtime.QuickflowContext, Microsoft.Office.Access.Server.Application, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” is not a type authorized for use in this workflow.

After a support call with Microsoft, it turns out Access Macros are converted into Workflows when run by the Access Database Service. When the server running on Access Database Services does not have the Microsoft SharePoint Foundation Web Application service, the Access Database Services is unable to retrieve the Workflow configuration settings from the Web Application’s Web.config file. Our current farm configuration is two Web Front Ends and two back ends, one for search and one for services.

There were a few options for the solution. On was to enable the Microsoft SharePoint Foundation Web Application service on the server running Access Database Services.

Another was to copy the web.config setting regarding workflows to the Web Application settings by running the below PowerShell Command-lets:

$WebApp = get-spWebApplication <URL>

$WebApp.UpdateWorkflowConfigurationSettings

Because we have licensing for third-party tools that count the number of Web Front Ends, we decided to start the Access Database Services on our WFE servers and stop them on the back-end services server.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: