locked
Error opening InfoPath file from document library RRS feed

  • Question

  • Hi

    We have a customer who stores InfoPath files (xml) in a regular document library. This has worked without problems until today. The user now gets an error about "support for .NET development not installed" when opening an InfoPath file from SharePoint. It's not InfoPath services, but just opening the files using the InfoPath application. 

    • The user can open local InfoPath files from their machine
    • The user can open Word and Excel files from both SharePoint and local file system

    And the user is connected using their Small Business Server VPN.

    When the user is on the same network as the SharePoint server they can open InfoPath files without problems.

    Any idea what is causing this?

    -- 
    Christian 

    Wednesday, May 4, 2011 9:06 AM

Answers

  • How exactly are they connecting?  For example, are they taking their laptop home, connecting to vpn then trying to access the form?  Or are they using their home computer, connection to vpn, then remote desktop into their machine at the office?

    VPN can be great but it seems to work best when you use an outside computer, then remote into a computer that is on the network.  I'm thinking that if the scenario is like the first example then Microsoft Office is not recognizing that it's fully on the domain and not trusting the form.  Also, do you know what level of trust the form is set at?

    • Marked as answer by Peng Lei Tuesday, May 10, 2011 5:03 AM
    Wednesday, May 4, 2011 1:34 PM

All replies

  • That is usually because somebody added code to a form template and that particular user(s) does not have the .net programmability support installed for InfoPath.  They must also have .net some-what updated (if memory serves me right it only requires 1.0 or higher).  They can open older versions of the form, or other forms that do not have code, but any forms with code will give this error.

    You can go to their control panel > add or remove programs > select the microsoft office suite > select change > add or remove features > expand infopath and select everything for the .net programmability support & click next to install it.  If it does not allow you to select it, they don't have a high enough version of .net installed and you will need to update that first. 

    Wednesday, May 4, 2011 12:51 PM
  • That was what I thought, but the user can open the files when they are on the local network, but not when they connect to the same site using VPN.

    Any ideas?

    -- 
    Christian 

    Wednesday, May 4, 2011 1:18 PM
  • How exactly are they connecting?  For example, are they taking their laptop home, connecting to vpn then trying to access the form?  Or are they using their home computer, connection to vpn, then remote desktop into their machine at the office?

    VPN can be great but it seems to work best when you use an outside computer, then remote into a computer that is on the network.  I'm thinking that if the scenario is like the first example then Microsoft Office is not recognizing that it's fully on the domain and not trusting the form.  Also, do you know what level of trust the form is set at?

    • Marked as answer by Peng Lei Tuesday, May 10, 2011 5:03 AM
    Wednesday, May 4, 2011 1:34 PM