I would like to host a web page in SharePoint 2010 which is located on another app server. I am trying to find a simplest way of doing this and searching gives me mostly the hints around SharePoint web parts. Is there a starndard or third party web part that will play a host for my content stored outside of SharePoint or I need to create one myself?
Related
I have created a provider-hosted app which was developed and tested against SharePoint Online. I now want to install this on SharePoint 2013 On Premise.
It is my intention that, despite being a provider hosted app, I wish to host the app web in IIS on the SharePoint server (single farm not a cluster). I then intend to use a local URL for my App Web URL.
I understand the process of setting up an App Catalog (On SharePoint Online) as a repository for my App which in turn will enable users to add it to a site.
I have only been able to find a guide to setup On Premise SharePoint to allow users to use the SharePoint store but I only want to set it up for third party apps.
My question is do I need to go through all the steps in this link https://technet.microsoft.com/en-gb/library/fp161236.aspx even if I don't want/require store access? I don't not want to do more than necessary and I would prefer a simple solution for my clients.
I followed this guide https://technet.microsoft.com/en-gb/library/fp161234.aspx in the hope that creating the app catalog would be sufficient but I get the error "Sorry, apps are turned off. If you know who runs the server, tell them to enable apps."
I am currently trying to decide on a Sharepoint Farm Topology.
Currently (in terms of our needs), I think a simple three tier topology will work.
i.e.
Web Front-End Server
Application Server
Database server
To start with our primary aim will be to use SharePoint as a Intranet. However, on our roadmap we would like to extend some elements of this - as an Extranet with some coustomers.
Should we go with an Extranet option in the future, so do we just (in simple terms) create a new web application in Sharepoint 2013 on the existing web front end, sort out a host header and SSL and a means to manage permissions.
Or could we create a new front-end server, which is only houses a new web application (the Extranet) - but still uses the same Application and Database server (as it will be potentially sharing the some of the same content databases)?
I am primarily a C# Web Developer - which is typically how I view most things. As I am learning - in the world of SharePoint nothing is simple!
If the extranet users need access to the same content, you can stick with option 1 and and Extend the existing Webapplication for Extranet.
Hi all and sorry for the long title. I've had the management of a SharePoint 2010 farm environment tossed to me and while most things are working one thing is not. None of our users are able to connect to any of the sites in this farm with SharePoint Designer. They all get the dreaded "server could not complete the request" message followed by the eternally helpful MS error message "Object moved. Object moved to here."
I've dug around everywhere I can think to look and the closest explanation I see is that it may have something to do with our SP server hosting 5 SP applications, all with their own host headers. The things I find seem to suggest that Designer won't play with SP servers featuring multiple host headers...but I have to think that can't be the case. SharePoint encourages you to make use of host headers when setting up your applications.
I've tried installing Designer directly onto the server itself: no dice.
I've tried setting up the sites without a host header: sites don't work (and it wouldn't be a permanent fix because the user base this farm serves are barely computer literate so asking them to use IP addresses will be like Armageddon)
I've checked the farm settings to ensure that use of Designer is allowed: it is.
For this intranet instance, we do apparently have 5 separate IP addresses tracking to this box that will eventually host 5 SP applications (if that helps).
I'm a developer and not a server or network admin so any guidance or advice from anyone who's run into this and found a fix would be most welcome.
First of all update Sharepoint Designer and Sharepoint to the latest service pack and do an iisreset and use Sharepoint Designer 2010 for access Sharepoint 2010 Farm.
Enable anonymous authentication for the SharePoint web application in IIS.
See this KB2758431 for more details, this is for Sharepoint 2013 but I think is still valid for 2010.
Set the registry DisableLoopBackCheck entry
Check the ULS Log and Event Viewer for error messages.
Here a little explanation about IIS name resolutions of Sharepoint.
You have to check the DNS, the IIS host header (foreach web site) and settings from the client.
If there are an entry into DNS corresponding to an hostheader of web application you must use this name for accessing the sharepoint web site, try with the FQDN (i.e. if the entry in DNS is Server01 and you are on mydomain.lan you must use for connecting: http://server01.mydomain.lan), check also from your client a ping to the address to see if you reach the server.
If there are no entry into the DNS, add to your hosts file the hostheader of the corresponding sharepoint site and try (same thing as for the DNS, see above).
How can I develop web pages with .net on sharepoint online. A way is using visual web parts. Is there any other way?
Thank you
You can use Visual Web Parts, if you use the Sandbox Solutions. You'll need to put code in those which that type of solution is being deprecated. Instead you should be build a SharePoint App. There are three (3) types of hosting, SharePoint hosted, Auto hosted and Provider hosted.
SharePoint hosted will generally allow you to host .js and .html/.aspx files.
Auto hosted and Provider hosted will allow you to write server side code. The different being that Provider hosted will require that you provide a web server, and Auto hosted will put a simple web site and SQL Azure database in Azure for you.
All three of these can create App Web Parts which is generally the same thing as a Visual Web Part, except that they will be using an iframe to include you web app.
I am working within an intranet environment. We have both a production and development sharepoint server (WSS 3).
We have a 3rd party workflow product which runs on top of sharepoint. It is installed on both the production and development sharepoint servers. The workflow product can call web services I have written which are hosted on our web server.
How would I have the web services determine which sharepoint server made the call to the web service, be it the production or development server?
I would then use this information to retrieve server specific information from web.config or database etc.
Currently the site hosting web services is setup to allow anonymous access so code such as
System.Web.HttpContext.Current.User.Identity.Name;
returns an empty string. If windows authenticaion is used it returns the identity of the currently logged in user, which is no use in identifying the server the call was made from.
I need a push in the right direction to address what I believe is probably a common scenario please.
Try System.Web.HttpContext.Current.Request.UserHostName