Category: Office

SharePoint Workspace cannot take a BCS list offline

Today I installed a BCS solution to a SharePoint 2010 farm. I wanted to take the list offline. So I clicked on the SPW button in the ribbon.


As expected, SharePoint Workspace popped open, and tried to get the list. But all I got was an message, that there was an error installing the list.

The eventlog, of the client I was working on, revealed that there was an error installing the solution (And we need the solution, to get the data on our clients. BCS uses solution which are deployed to clients as click-once applications to sync data.). The error details showed something like “Solution Install Stage:PendingDownload Solution Install Error”,the EventId was 2012 and the Datasource “Business Connectivity Services”. Not really a helpful message.

So I went to the SharePoint server and took a close look at the ULS log. And voilà, there was the answer: “External lists can only be synchronized with your computer from Microsoft SharePoint Server 2010 with Enterprise Client Access License features enabled. For more information, contact your system administrator.”

You need to activate enterprise features in order to use SharePoint Workspace with BCS data.


Lessen learned…

Oh. Don’t forget to switch on the Offline Synchronization feature for External Lists!


Do not install Office 2010 x64

Now you will think “Why not?”. Some time ago I read a blog post which said “If you are asking yourself if you want to install Office 2010 as 64bit version, you should install the x86 version”. Why that?

The reason is, that if you are asking yourself you worry about incompatibility with over software. And you are right! If you install x64, all add-ins you use have to be x64 as well. You should however install x64, if you need more than 2GB for Excel :-/ Or you use a SQL Server to store your data and install x86…

If you want to read more, take a look at 64-bit editions of Office 2010 on MSDN:

If users in your organization depend on existing extensions to Office, such as ActiveX controls, third-party add-ins, in-house solutions built on previous versions of Office, or 32-bit versions of programs that interface directly with Office, we recommend that you install 32-bit Office 2010 (the default installation) on computers that are running both 32-bit and 64-bit supported Windows operating systems.

Ishai Sagi mentioned that the ActiveX control which is used for the Datasheet view for SharePoint lists needs x86 as well!

Update July 2010:

MS has posted a knowledgebase article

You cannot view a list in Datasheet view after you install the 64-bit version of Office 2010

If your business needs justify using the 64-bit version of Office 2010, you can install the 2007 Office System Driver: Data Connectivity Components to enable the Datasheet component. These components are available from the Microsoft download center: (


Great. So you can at least use the Datasheet View if you need to install Office 2010 x64 🙂

Office 2007 + SharePoint Document Library = Prompt for Credentials


Even if you configure your SharePoint site as Intranet in the Internet Explorer, you will be prompted for user credentials when you open an Office document with Office 2007.

This is true, if you haven’t configured a proxy in your browser, access your SharePoint site with a FQDN (fully qualified domain name) and you are using Windows Vista or Windows 7.


(Quote from the KB aticle below) In Windows Vista, Internet Explorer uses the Web Client service when you use Internet Explorer to access a WebDAV resource. The Web Client Service uses Windows HTTP Services (WinHTTP) to perform the network I/O to the remote host. WinHTTP sends user credentials only in response to requests that occur on a local intranet site. However, WinHTTP does not check the security zone settings in Internet Explorer to determine whether a Web site is in a zone that lets credentials be sent automatically…

If the URL contains periods, the server is assumed to be on the Internet <—this is the important point 🙂


Install Vista SP1 if you haven’t already. Otherwise you’ll need to install the hotfix from the KB article!

See this KB article: You are prompted to enter your credentials when you access an FQDN site by using a Windows Vista-based client computer that has no proxy configured

The article shows how to add an entry to the client registry, which will tell the WebClient Service to send credentials with the request.

Note: You have to restart the WebClient service after you modify the registry.