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
Related
I have been reading several articles to get SharePoint Online client context with the generated access token. All of them use TokenHelper class to get the client context as shown below:
ClientContext clientContext = TokenHelper.GetClientContextWithAccessToken(targetWeb, AccessToken);
My question is how do we access TokenHelper class? I could not find it in the reference Microsoft.SharePoint.Client version 16.1.0.0. What reference do we need to add to access this class?
I was able to get answer from here. In case anyone needs it in future, below is the answer:
Just add the NuGet package AppForSharePointOnlineWebToolkit. It will add the TokenHelper.cs and SharePointContext.cs files to your project.
Please install the below NuGet package in your solution:
--> AppForSharePointWebToolkit
Installation will add the following files & references to your solution :
For more information:
https://www.nuget.org/packages/AppForSharePointWebToolkit/
Please Note:
AppForSharePointWebToolkit is for SharePoint 2013
If you are working on SharePoint 2016 or working on Visual Studio 2017 you have to install AppForSharePoint16WebToolkit
You don't need any NuGet packages or other external sources as long you work with Visual Studio and you have the Office developer Tools and SharePoint Server 2013 Client Components SDK installed, just as written in the forum thread you referred to.
Simply create a new project, and select the SharePoint Add-in project template from Installed / Visual C# / Office/SharePoint / Add-ins hive. On the first page of the project wizard select the Provider-hosted option (I think it is the default one), and on the second page select SharePoint Online if you want to work with O365. The TokenHelper.cs will be included in the project generated by Visual Studio.
See these tutorials for more details:
Create high-trust SharePoint Add-ins
How to Create a High-Trust, Provider-Hosted Add-In?
Get started creating provider-hosted SharePoint Add-ins
Step by Step approach to create a Provider Hosted Application in SharePoint 2013
Is following scenario possible?
We have got TFS 2013 installed as a standard single server. This server has got the SQL db.
We have got SharePoint 2013 installed on another machine.
Now we want to integrate TFS 2013 with SharePoint 2013 along with SSRS and SSAS for reports, etc.
Please guide whether this is possible or we need to install TFS via Advanced mode again?
No problem, you can integrate your existing TFS single server deployment with your external SharePoint server assuming you have the necessary permissions.
MSDN: Verify your SharePoint installation
https://msdn.microsoft.com/library/dd578601(v=vs.120).aspx
MSDN: Set up remote SharePoint
https://msdn.microsoft.com/library/hh548140(v=vs.120).aspx
Cheers
Adding SSRS and SSAS is relatively simple too and can be on the same server as TFS or a different one.
MSDN: Add a report server
https://msdn.microsoft.com/en-gb/library/dn148128.aspx
Martin Hinshelwood has a couple of useful blog posts on this subject too:
http://nakedalm.com/integrate-sharepoint-2013-with-team-foundation-server-2013/
http://nakedalm.com/integrate-reporting-and-analyses-services-with-team-foundation-server-2013/
*sorry for the multiple answers, new account and SO doesn't trust me to post 5 links yet! :)
I'd like to put a table form oracle on my sharepoint 2010 (and soon to be updated 2013) site so that the table can be updated and new rows can be inserted. After googling using BCS seems to be the only option. Is this correct? the Sharepoint designer will not work with Oracle?
Also when I open Visual Studio 2012 Professional and click on new project>>Sharepoint>>Sharepoint 2010 Project I get an error saying
Sharepoint server must be installed to workwith share point projects.
Do I need to install sharepoint server on my machine?
Can anyone provide any documentation on how to do this? what happens when I go to Sharepoint 2013?
Oh yea and I have windows 7. Will sharepoint server work on windows 7?
Thank you!
I'll try to answer all your questions.
Oracle connectivity
BCS supports Oracle but it's not trivial. Sharepoint designer is a tool where you can create External Types (BCS types). But with Sharepoint Designer you are limited to SQL Server, WCF Services and .NET assemblies. There are few workarounds:
Create linked server to oracle in SQL Serve Management Studio and use Sharepoint Designer to create BCSentities
You can create service for fetching oracle data and use Sharepoint designer to create BCS entities
If you just want to display some data from oracle and have developer knowledge. You can use ODAC for .NET and create webparts for displaying data (the simplest solution of all).
For Sharepoint 2010 Development you have to install sharepoint (foundation or server) on copmuter where your VS resides. Sharepoint foundation could be installed on Windows 7 x64. Installation is trivial download sharepoint foundation and run installation file.
For Sharepoint 2013. You can create apps and client apps on remote computer but for farm solutions there is the same rule (but SP 2013 can't be installed on Windows 7).
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
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.