locked
To export a list, you must have a Microsoft SharePoint Foundation-compatible application RRS feed

  • Question

  • Windows 7 Ultimate 64-bit, SharePoint Server 2010, Office 2010, Access data Engine 32-bit or Access data Engine 64-bit, IE 8 64-bit or IE 8 32-bit or Firefox. Configured Excel Services, Secure Store App ID. The export to Excel button is available but when I select the following error appears:

    To export a list, you must have a Microsoft SharePoint Foundation-compatible application (This is from Firefox because it allows me to copy the error)

    I also get this same error from a Production Sandbox (Multi Tennant) SharePoint 2010. After installing the Access Data Engine and clicking okay to the error I can download the owssvr.iqy file (This is the standard format in MOSS 2007) 

    Any help is greatly appreciated as I have very large spreadsheets that need to be turned into lists and have no access to SQL in the Sandbox,

    dataman777

    • Moved by Mike Walsh FIN Sunday, December 26, 2010 10:28 AM SP 2010 questions go only to SP 2010 forums (From:SharePoint - Setup, Upgrade, Administration and Operation (pre-SharePoint 2010))
    Sunday, December 26, 2010 9:33 AM

Answers

  • Update:

    After reading in Microsoft SharePoint 2010 Unleased by Michael Noel that Office 2010 64-bit is NOT compatible with SharePoint 2010, I installed Office 2007 32-bit along side my Office 2010 64-bit. When choosing install options for Office 2007 32-bit, I selected all the Excel, Access, Visio, and Advanced Office Sharepoint checkboxes. All the Office functions import, export, edit in datasheet, etc., etc. are now available in both my local Dev box and remote Sandbox.

    I would propose the solution is that Office 2010 64-bit is not currently compatible with SharePoint 2010.

    Thanks,

    dataman777

    • Marked as answer by dataman777 Sunday, January 2, 2011 5:38 PM
    Sunday, January 2, 2011 5:20 PM
  • Hey there,

    According to the 'plan browser support' technet article, your (64bit) scenario should be supported (At least with IE8). However, I've certainly had mixed results using 64bit Office and IE - http://technet.microsoft.com/en-us/library/cc288142.aspx.  Have you tried the above using IE8 (32bit) and Office 2010 (32bit).

    As well, is the SharePoint site you are attempting to perform this operation on, in your Internet Explorer Local Intranet zone? 


    Sean Wallbridge, SharePoint MVP Victoria, BC On The Web: http://www.itgroove.net My Blog: http://blog.brainlitter.com
    • Marked as answer by GuYuming Sunday, January 2, 2011 3:54 AM
    Tuesday, December 28, 2010 2:27 AM

All replies

  • Hey there,

    According to the 'plan browser support' technet article, your (64bit) scenario should be supported (At least with IE8). However, I've certainly had mixed results using 64bit Office and IE - http://technet.microsoft.com/en-us/library/cc288142.aspx.  Have you tried the above using IE8 (32bit) and Office 2010 (32bit).

    As well, is the SharePoint site you are attempting to perform this operation on, in your Internet Explorer Local Intranet zone? 


    Sean Wallbridge, SharePoint MVP Victoria, BC On The Web: http://www.itgroove.net My Blog: http://blog.brainlitter.com
    • Marked as answer by GuYuming Sunday, January 2, 2011 3:54 AM
    Tuesday, December 28, 2010 2:27 AM
  • Hi, dataman777, I don’t quite understand your problem. You can export list items to Excel now, don’t you? I can also see the error message in Firefox, but the .iqy file was still downloaded as you said.

     

    As to import Excel file into SharePoint list, you can click Site Actions->More Options->Import Spreadsheet.

    • Marked as answer by GuYuming Sunday, January 2, 2011 3:54 AM
    • Unmarked as answer by GuYuming Wednesday, March 6, 2013 1:28 AM
    Thursday, December 30, 2010 6:58 AM
  • Update:

    After reading in Microsoft SharePoint 2010 Unleased by Michael Noel that Office 2010 64-bit is NOT compatible with SharePoint 2010, I installed Office 2007 32-bit along side my Office 2010 64-bit. When choosing install options for Office 2007 32-bit, I selected all the Excel, Access, Visio, and Advanced Office Sharepoint checkboxes. All the Office functions import, export, edit in datasheet, etc., etc. are now available in both my local Dev box and remote Sandbox.

    I would propose the solution is that Office 2010 64-bit is not currently compatible with SharePoint 2010.

    Thanks,

    dataman777

    • Marked as answer by dataman777 Sunday, January 2, 2011 5:38 PM
    Sunday, January 2, 2011 5:20 PM
  • To answer your question, I was recieving the "not compatible....." error in both my local IE SharePoint and remote Sanbox SharePOint installations. Also recieved this with both IE 8 32-bit, IE8 64-bit, and Firefox. The problem seems to be with Office 2010 64-bit. After installing Office 2007 32-bit... all is well!

    Thanks,

    dataman777 

    • Proposed as answer by StarPowerNow Wednesday, March 6, 2013 1:08 AM
    Sunday, January 2, 2011 5:28 PM
  • Yes the error was in both local and remote zone.
    Sunday, January 2, 2011 5:29 PM
  • Yes I also recieved the error when trying click Site Actions->More Options->Import Spreadsheet. The error was apparently caused by Office 2010 64-bit not being compatible with both local and remote SharePoint 2010 installations.

    Thanks to the moderators for all your great work,

    dataman777

    Sunday, January 2, 2011 5:33 PM
  • Dataman777,

    That information is incorrect.  Export to Excel, and SharePoint 2010 in general, works correctly on systems running Office 2010 64-bit.  (As it should given that Windows 7 / Office 2010 64-bit was the intended client OS configuration.)  The only noted limitation is the unpatched bug with Datasheet View requireing the install of 2007 Office System Driver: Data Connectivity Components (see link provided by GuYuming).

    Where I am currently seeing this bug is, in fact, on clents running Office 2007.  I say "bug", not error, as they can still open the exported spreadsheet.  Its just an annoying pop-up, we'd like to see gone.


    <insert witty comment here>


    • Edited by Bill Nesbitt Thursday, June 7, 2012 8:59 PM Correction.
    Thursday, June 7, 2012 8:57 PM