SharePoint Experts, Information Architects, Expert Witness

SICG provides a broad array of business and technology consulting from architecture to design to deployment of global systems with a focus on surfacing data in the enterprise. We focus on the "How", not just the possible. Contact me direct: or call 704-873-8846 x704.

Search This Blog

Wednesday, August 25, 2010

SharePoint Designer 2010 Error - The list of workflow actions on the server references an assembly that does not exist

When attempting to create a new workflow using SharePoint Designer 2010, I've encountered the error:

"The list of workflow actions on the server references an assembly that does not exist. Some actions will no be available. The assembly strong name is Microsoft.SharePoint, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c. Contact your administrator for more information."

In investigating this, I did find a post answered by Paul Stork on the Microsoft site - in his reply to the problem, he inidcated that this would typically happen when someone had added a custom workflow DLL to the WSS.ACTIONS or MOSS.ACTIONS files located in the hive under Template\1033\Workflow.

That said, as you can see by the error above, "Microsoft.SharePoint" is hardly a custom DLL. I got the above to occur when trying to create a workflow in a team site type site collection in a full instance of SharePoint (Standard or Enterprise).

I found two ways that seem to fix this:

1) Close Designer and run an IISReset - reopen Designer and try again
2) Use Designer to open an existing SharePoint publishing site (or create one if necessary) and create a new workflow (you should not get the error). Don't save it, just simply close Designer. Reopen the original site and try again.

MOSS MA Not Found error in User Profile Synchronization or System.ServiceModel.EndpointNotFoundException occurred in OWSTIMER

When setting up a user profile service, connecting to AD or similar, when you try to complete the process, you get the very vauge error message "MOSS MA not found". A little confusing (after all, there's no more MOSS right?) but turns out the problem is that the Forefront Identity Management Service is not running.

OR - you see errors in the Event Application Log (Event ID 4096) showing:

An unhandled exception ('System.ServiceModel.EndpointNotFoundException') occurred in OWSTIMER.EXE.

Followed by "ResourceManagementService/MEX. TCP error code 10061".

NOTE: On a development machine, the second error will often open the Just In Time Debugger.

The issue is that the service is set to automatically start but if no connections are established, it shuts down.

To correct both issues, simply go to Start > Administrative Tools > Services then find "Forefront Identity Manager Service" and start it (make sure it actually starts). When done, return to Central Admin and try the sync again.

IMPORTANT NOTE: If you perform a restart of the Server and again, the ForeFront service does not start, use the Services and modify the properties to set the Startup type to be 'Automatic (Delayed Start)',

NOTE: As a related issue:

Fixing the user profile service may require a bunch of fixes; one may be that you simply can't open the Configure Synchronization Connections (you get an error page).

Here's one possible fix:

First, try to connect to the Forefront Identity Manager -
c:\Program Files\Microsoft Office Servers\14.0\Synchronization Service\UIShell\miisclient.exe

If you get an error it might be because of:

1) The service itself is not running - you have to go through Administrative Tools > Services  then start both FFI services
2) The account you are using is not a member of the local system group called FIMSyncAdmins

These aren't the only fixes - there may be others but the above might help! Sometimes a complete reboot is required.

Friday, August 13, 2010

SharePoint 2010 - InfoPath cannot generate a form template for the SharePoint list error

Common error new users might see when trying to edit a List/Libary Form using InfoPath:

InfoPath cannot generate a form template for the SharePoint list.

The SOAP response indicates that an error occurred on the server:

Exception of type 'Microsoft.SharePoint.SoapServer.SoapServerException' was thrown.
<detail><errorstring xmlns="">
List does not exist.
The page you selected contains a list that does not exist. It may have been deleted by another user.
</errorstring><errorcode xmlns="">0x82000006</errorcode></detail>

Nasty eh? Actually it simply means that the list is in Datasheet view - apparently, SharePoint doesn't know this....change back to the normal view and try again.

Thursday, August 12, 2010

Sharepoint 2010 Error - The list cannot be displayed in Datasheet view...

When you try to open a list in a datasheet view, you recieve:

The list cannot be displayed in Datasheet view for one or more of the following reasons:

- A datasheet component compatible with Microsoft SharePoint Foundation is not installed.
- Your Web browser does not support ActiveX controls.
- A component is not properly configured for 32-bit or 64-bit support.

Thanks to for this one for a solution on Windows 2008R2 x64 is to do the following:

1) Download and install the 2007 Office System Driver: Data Connectivity Components (AccessDatabaseEngine.exe) from

2) Download and install the Microsoft Office Access Runtime and Data Connectivity 2007 Service Pack 2 (SP2) (accessruntimeanddataconnectivity2007sp2-kb957262-fullfile-en-us.exe) from

Run IISReset to reset and try again.

SharePoint 2010 Error - Event ID 7043

SharePoint front end Application Event Log shows error 7043 over and over relating to the TaxonomyPicker.ascx - located in c:\Program files\common files\microsoft shared\web server extensions\14\template\Controltemplates

Update: Applies to SharePoint 2010 (2013 not confirmed yet)

This file is a left over file from the 2007 version for compatibility - there is not only a typo in it, the file itself is not required. Since SharePoint manages this folder, it detects it and tries to load it.

Fix is simple - navigate to the folder using Windows Explorer and rename the file from from taxonomypicker.ascx to taxonomypicker.hold_ascx