I am getting the error This form template is not enabled for viewing in the browser. when I publish my InfoPath 2013 to my Sharepoint 2010.
Steps I have already followed:
Site Collection Features has "Enterprise Features enabled"
Site Features also has "Enterprise Features" enabled
Forms Library has "View as Web Page" enabled in advance settings
Infopath Forms Service has Render and User Browser Compatible Forms enabled
Set Compatibility mode in InfoPath to Web Browser Form 2010
I have made a blank form just to test if it will publish, but I am receiving the same error.
Concerns:
Does it have to do with anything with publishing from InfoPath 2013 to Sharepoint 2010?
Please let me know if there is any confusion in the question.
Did this process used to work and now it has stopped working? Have you successfully published and used a form with this method?
A user here reported this same error yesterday, and it is one I've never seen before. Apparently, our company's updates of Microsoft patches installed a portion of Office 2010 on this person's system. Once this was uninstalled, InfoPath returned to working as normal.
(We also publish InfoPath 2010-compatible forms from systems running Office 2013.)
This may not be related at all to your problem, but since we saw this symptom just yesterday, I figured it might help.
Paul
Related
As there is a drastic change in architecture from SharePoint 2010 to 2013, I would like to know what are the restrictions for a developer while developing Solutions/Apps for Office 365.
In SharePoint 2010, only sandbox solutions were allowed on Office 365, but in SharePoint 2013 the sandbox solutions are depreciated and App model is introduced. Would be glad if someone can throw some light on what is allowed and what is restricted on Office 365 in the new 2013 environment.
Sharepoint 2013 is a game changer, starting with the fact now is possible to use framework 4.5 and, since the new release of visual studio 2013, it's possible to use MVC. From a developing point of view you have to know there are two flavors:
Sharepoint hosted. In this case, your whole application is installed within the Microsoft servers. Because of this, you MUST use client object model and javascript. No server code at all. So you will configure your sites, libraries, lists, etc with 365 and then access this information using the Sharepoint javascripts libraries. If you are familiar with js ans sp js the you won't have any problem.
Autohosted. In this case you can choose between azure or your hosting (provider hosted) in both cases you can use a more traditional aproach, with your server code, classes, aspx and so on. The difference is when you deploy your application, in this case the app is installed just as a reference in 365 and all the code in your hosting provider. In fact all your application will be displayed in 365 within an iframe. Keep in mind you will be dealing with lots of cross domain scripting.
Last but not least, you have one final flavor, but it's not 365, Sharepoin onpremise, in this case this is your own sharepoint, you create, manager, develop or deploy whatever you want. This is very similar to the current sp2010 model, so, I guess you already now what you can do.
For more information:
http://msdn.microsoft.com/en-us/library/office/apps/fp179930.aspx
http://blogs.msdn.com/b/amigan/archive/2012/12/10/part-2-introduction-to-sharepoint-2013-app-model.aspx
Figured I'd throw this out here because in-house because in-house ITS and myself can't figure it out at all.
I have some Access 2007 front-end forms connected to lists in Sharepoint 2010. I updated the columns in a few of the lists in Sharepoint. On some workstations, the lists that were updated cannot be opened in Access anymore. However, they can still be opened directly from the Sharepoint web portal.
Does anyone have any idea what might be going on? Does Access have some sort of hidden cache of the structure of Sharepoint lists? We've tried all the obvious such as deleting and relinking and refreshing the culprit lists. All the computers in question are running the same version of Access and the same version of Windows.
Figured I would post what happened just for the record.
We are using Sharepoint Server 2010 and Access 2007. The problem was being caused by miscommunication between the two versions. We temporarily fixed it by installing Sharepoint Designer on all the workstations that needed the Sharepoint app, as this updated some of the Office 2007 files to Office 2010 and allowed compatibility with Sharepoint 2010.
Unfortunately, each time Microsoft rolled out an update to Office 2007, it broke the compatibility again, and after one update I was not able to fix it again. I have since moved to a MySQL/PHP platform and never plan on looking at Sharepoint again as a database platform.
I'm currently tryign to get Infopath form services working on our farm however am running into a problem.
Doing some homework I found this thread:
Error on : Publishing InfoPath forms to the SharePoint site
Unfortunatly there is no date, but we are currently fully patched up to the latest CU and have infopath 2010 RTM installed on the web front end server (a neccessity for one of our farm features).
We recieve a generic error from Central Admin when we attempt to upload the form template to infopath server:
Method 'get_ServerInfo' in type 'Microsoft.Office.InfoPath.Server.SolutionLifetime.XmlFormProxy' from assembly 'Microsoft.Office.InfoPath.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' does not have an implementation.
Has anyone run into this before and/or found a solution? We are attempting to get a very basic infopath 2007 web form template uploaded (made it in infopath 2010 and saved it with the compatibility flags set for 2007 web forms).
It is a known issue with Infopath 2010. You will need to uninstall and install 2007 version:
Error on : Publishing InfoPath forms to the SharePoint site
How to fix this error in SharePoint:
"The list cannot be displayed in
Datasheet view. A datasheet component
compatible with Windows SharePoint
Services is not installed, your
browser does not support ActiveX
controls, or support for ActiveX
controls
It started to days ago, for apparently no reason. ActiveX is enabled on this site and I had everything working fine so far. Not sure what went wrong.
Thanks,
... from IE check out your Internet Options, and look under 'Programs'->'Manage Add-Ons'
When I had this problem it was because an add-on was missing or disabled... * thinks * "Microsoft Office List 12.0" or something.
I was getting the below in SharePoint 2010.
The Standard View of your list is being displayed because your browser
does not support running ActiveX controls.
Turns out the site (master page) was being rendered in IE9 mode and the datasheet supports only up to IE8.
The datasheet mode can be used temporarily by switching the Document mode and the User agent string both to IE 8, or permanently by using the meta tag X-UA-Compatible IE=8.
This is known issue and you have to install the hotfix provided by Microsoft.
The issue is addressed in the below specified link along with the URL for the hotfix.
http://www.himmeltech.com/blog/fix-for-datasheet-view-issue-error-in-sharepoint-2010/
Let me know whether the suggested solution fixes your issue
Please install below data connectivity component to resolve this issue.
http://www.microsoft.com/en-us/download/details.aspx?id=23734
This link helped me and it worked fine. Our environment was Windows 7 64bit and MS office 64bit as well, after installing this connectivity tools, user had a option edit the data sheet view in sharepoint.
I ran into the same issue after updating to Office 365 but remaining with IE 11 and Sharepoint 2010.
Issue:
using a 64-bit version of Office with a 32-bit version of IE
Reference: Technet
Resolution: Installed 2007 Office System Driver: Data
Connectivity Components
Seems like a client/browser problem.. do you have Microsoft Office installed? Did you change security settings in Internet Explorer?
My environment is SP2010 enterprise and after trying several solutions, I realized that the user that could not see the views in Datasheet style was because did not have installed "Microsoft Access" that is required when you are using views in datasheet style. So the solution for me was to upgrade that specific user from Office Standard to Office Professional
For me, I performed the following and it worked for me:
Open Control Panel and open Programs and Features
Find your instance of Microsoft Office and select it
Click change at the top
On the dialog that comes up, click Add or Remove Features and then continue
Make sure Microsoft Access Web Datasheet Component is installed under Office Tools/Microsoft SharePoint Foundation Support
Even if it is showing as installed, click Continue.
Let everything install, close any office programs out, then try again
These steps worked for me.
I'm trying to publish Browser Enabled Infopath Forms to the SharePoint sever but, at the end it was showing me the following Error:
The SOAP response indicates that an
error occurred on the server:
Server was unable to process request. ---> Method 'get_ServerInfo'
in type
'Microsoft.Office.InfoPath.Server.SolutionLifetime.XmlFormProxy'
from assembly
'Microsoft.Office.InfoPath.Server,
Version=12.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c' does
not have an implementation.
Do you have Infopath 2010 installed?
WORK-AROUND: The issue appears to be associated to having the new Office 2010 beta products installed and specifically InfoPath 2010. I am investigating the assembly conflict but the easiest work-around for now is to simply uninstall InfoPath 2010 (beta) and re-run psconfig again (you should not need to uninstall any other 2010 beta product and this will likely be a non-issue at RTM).
Source
This appears to be also an issue with Office 2010 RTM. I just experienced the exact same problems using office 2010 installed on a fully patched MOSS 2007 farm.