locked
To export a list, you must have a Windows SharePoint Services-compatible application RRS feed

  • Question

  • Hello community,

    Users reported they started noticing recently the following message when they try to 'export to spreadsheet' - the list opens in Excel 2010 just fine once they choose OK from the popup message. I'm trying to figure out why this started and how I can suppress this.

    This is a SharePoint 2007 SP2 with Aug 2010 CU applied. I can reproduce this message from my Windows 7 with IE9 and Excel 2010 (64 bit). Interestingly from the same location on another computer with XP, IE8 and Excel 2007 I don't get this prompt. Tested with another remote use with Win 7, IE9 and Excel 2010 and no prompt. Which tell me it's not a sever side issue. But can't figure out what the clients are missing. Anyone has any experience with this?

    Please note I've made sure client has Office Toos > "Microsoft SharePoint Foundation Support" already installed and run 'Microsoft Office Diagnostics' wiht no luck.

    Any suggestions would be greatly appreicated.

    Many thanks in advanced!


    BlueSky2010
    Please help and appreciate others by using forum features: "Propose As Answer", "Vote As Helpful" and "Mark As Answer"

    Friday, September 14, 2012 1:25 PM

Answers

  • This really
    comes down to IE looking for the particular DLL's that are associated with an Office client being installed. <o:p></o:p>

    What you could do is take a Procmon of a working machine and then follow the request for
    iexplore.exe then compare against the nonworking to see what is missing.<o:p></o:p>

    I know IE9x64 has issues with Office x86. <o:p></o:p>

    Also interestingly is these articles gives us a clue on what is happening:<o:p></o:p>

    http://technet.microsoft.com/en-us/library/cc263526(v=office.12).aspx#section1<o:p></o:p>

    http://technet.microsoft.com/en-us/library/cc263526.aspx<o:p></o:p>

    Since you know who I am :-), then you probably know that I primarily work with server
    side aspect. What we need in this case is input from a client side engineer that why I suggested opening a ticket.<o:p></o:p>



    Regards, Savoeurn Va Microsoft Online Community Support

    • Marked as answer by Emir Liu Monday, October 8, 2012 4:10 AM
    Sunday, September 30, 2012 10:41 PM

All replies

  • Hi,

    Thank you for your post.

    I'm trying to involve someone familiar with this topic to further look at this issue. Appreciate your patience.

    Thanks & Regards,
    Emir Liu
    TechNet Subscriber Support in forum
    If you have any feedback on our support, please contact tnmff@microsoft.com.


    Emir Liu

    TechNet Community Support

    Monday, September 17, 2012 2:50 AM
  • Hi,

    Are all the affected machines with Office 2010 x64?

    Try running IE9 x64 and see if that makes a difference.  I’m suspecting the x86 IE is looking for an x86 Office DLL. 

    If this doesn’t work out you may want to open a ticket with an Office Client Integration Engineer to look at this at a deeper level.


    Regards, Savoeurn Va Microsoft Online Community Support

    Monday, September 17, 2012 5:37 PM
  • Hi Vern,

    IE9 x64 also have the same issue and as indicated above not all Office x64 affected.

    Any other suggestion [apart from MS ticket - which I never find useful :-(]?

    Thank you!


    BlueSky2010
    Please help and appreciate others by using forum features: "Propose As Answer", "Vote As Helpful" and "Mark As Answer"

    Tuesday, September 18, 2012 12:43 PM
  • This really
    comes down to IE looking for the particular DLL's that are associated with an Office client being installed. <o:p></o:p>

    What you could do is take a Procmon of a working machine and then follow the request for
    iexplore.exe then compare against the nonworking to see what is missing.<o:p></o:p>

    I know IE9x64 has issues with Office x86. <o:p></o:p>

    Also interestingly is these articles gives us a clue on what is happening:<o:p></o:p>

    http://technet.microsoft.com/en-us/library/cc263526(v=office.12).aspx#section1<o:p></o:p>

    http://technet.microsoft.com/en-us/library/cc263526.aspx<o:p></o:p>

    Since you know who I am :-), then you probably know that I primarily work with server
    side aspect. What we need in this case is input from a client side engineer that why I suggested opening a ticket.<o:p></o:p>



    Regards, Savoeurn Va Microsoft Online Community Support

    • Marked as answer by Emir Liu Monday, October 8, 2012 4:10 AM
    Sunday, September 30, 2012 10:41 PM