• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 787
  • Last Modified:

Script or Unattend for Adding Features to Microsoft Office InfoPath 2007

We've recently started publishing InfoPath 2007 Forms to SharePoint, and I've been getting an error on most our clients' computers.  The error message boils down to:

"The required version of the Microsoft .NET Framework is not installed on your computer or the InfoPath Primary Interop Assembly (PIA) is not registered. Use Add or Remove Programs in Control Panel to make sure that the required version of the Microsoft .NET Framework is installed. Or install it using Windows Update and run the Setup program again to confirm that the corresponding version of the .NET Programmability Support is installed, or contact your system administrator.

I've checked that all our systems have the necessary .NET Framework 2.0 installed, but it seems that the .NET Programmability Support is not installed.  

see this article: http://blogs.msdn.com/sameersurve/archive/2008/09/26/infopath-error-the-required-version-of-the-microsoft-net-framework-is-not-installed-on-your-computer-or-the-infopath-primary-interop-assembly-pia-is-not-registered.aspx)

See also, this MS KB: http://support.microsoft.com/kb/914360

While I've written up a nice step-by-step for our end users to manually add the .NET Programmability Support for InfoPath, I'd like to find an automated or scripted solution.

Anyone out there know how to programatically initiate an Add or Remove Features function that a user would normally do via the control panel?

All our end users are on WinXP SP3.

  • 2
1 Solution
HSWENTAuthor Commented:
I ran across this article: http://technet.microsoft.com/en-us/library/cc179097.aspx

Does anyone with in-depth deployment or scripting experience have a suggestion how I would push a simple settings change and have .NET Programmabiliy Support for InfoPath feature to "run from computer" as opposed to being "not installed"?
if possible install .net frame work 3.5 sp1.  thats what we are running on clients.  see if that fixes it and if so, then you can see if they can push it down to the client machines.  
HSWENTAuthor Commented:
It turned out it is not a .net framework 3.5 sp1 issue... there simply was no way I could figure out how to add the .NET Programmability Support as a push from our System Center.  We ended up creating a step-by-step article that teaches end users how to add that through Add/Remove Programs and changing the installation of InfoPath 2007 to include .NET Programmability Support.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now