I have SharePoint Foundation 2013 installed on a server. I want to do the development using My machine. I have Visual Studio 2015 installed, with Office tools. I can create an app and deploy it to office 365. But when i try to deploy to an on-premise server I get the following error;
Error occurred in deployment step 'Install SharePoint Add-in': The HTTP request was forbidden with client authentication scheme 'Anonymous'.
Please refer this the below link. As per my understanding Office 365 uses https and local used http. sslshopper.com/iis7-redirect-http-to-https.html. Also have you created a dns entry in your local server (host file) please check.
Related
When I try to publish project from Visual Studio 2019 to remote IIS server, I'm getting an error:
"The SQL provider cannot run because of a missing dependency. Please make sure that Microsoft SQL Server Management Objects (Version 10 or higher) is installed. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_SMO_NEEDED_FOR_SQL_PROVIDER".
This is the first time I installing software to server, so here is what I did, following instructions on the web:
Added features: Windows Deployment Services (with Deployment Server and Transport Server), IIS Management Console, IIS Management Scripts and Tools, Management Service, Logging Tools.
Installed SQL Server Management Objects (version 13.0.1601.5), Microsoft Web Deploy 3.6 (because of version 4.0 won't offer me to install IIS Deployment Handler and won't show me Deploy menu in the IIS).
Tried to configure Web Deploy Publishing for existing user from Active Directory with defining connection string to SQL server.
Allowed users in IIS Manager Permissions.
Some important information:
Server is in domain, connection to internet restricted. Application works in intranet.
Using Web Platform Installer permitted because of item 1. Any programs should be installed offline only.
Server haven't been used for Web Deploy before.
Before installing Microsoft Web Deploy 3.6, I was unable to check connection from Visual Studio and even hadn't current error.
I guess that error happens because of incorrect connnection strings (Enter SQL Server/MySQL connection string to be used for publishing).
I am trying to setup a Dynamics CRM 2016 Internet Facing Deployment. The application/SQL server is a Windows Server 2012 machine and CRM is hosted as a separate website(not the default website). Where do I install AD FS? Is it supposed to be on the Active Directory server or on the application server? Are there any other factors to be considered?
yes you can deploy your ADFS on the application server. If you look at page 10 of this deployment guide - https://www.microsoft.com/en-us/download/details.aspx?id=41701 you can see that same server deployments are supported. Although, it's a bit messy and separate server deployment is recommended.
One thing to keep in mind is that whenever you need to restart your application server (installing rollups\updates) your ADFS will go down as well, and if there are other applications using it, your users will loose access to them.
It could be any server but I would suggest to use separated server for that purpose.
This paragraph looks like error:
If you want to run SharePoint Products on a server other than Team
Foundation Server, you must install Team Foundation Server on the
SharePoint server and then configure the TFS Extensions for
SharePoint. This installs all of TFS on the SharePoint server,
including the TFS SharePoint Extensions. The application tier, the
build server, and the proxy server appear in the TFS administration
console, but you do not have to configure any of these additional
features.
Source
This article is about Configuring TFS Extensions for SharePoint on remote server.
Then, why would someone install TFS server on SharePoint server again if he has already got the TFS server installed on another machine? Isn't it that he will only install the SharePoint extension on the SharePoint server?
Please advice.
Installing TFS on the server installs the required prerequisites, TFS Client Object Model, The Server Object model, the WSP that installs the SharePoint Extensions and a few other items. These elements are required for the Sharepoint Extensions to connect to the remote TFS server.
Installing these only drops these bits, but does not activate anything. There will be no running services, no other bits. That is what the Configure step will do, which you will skip for these steps.
So, no, this is not a bug in the documentation. You need to install TFS on the server. it makes sense as it installs all the prerequisites. again installing the binaries on the server doesn't configure any of the features. It's the same as the first stage of installing SharePoint, it drops the bits, but doesn't create any services, websites or databases until you configure. And you will configure only the one feature you need, which is the SharePoint integration.
It is probably possible to manually install all the prerequisites, register the TFS server to the client object model and manually deploy the WSP, but that is not the standard way of doing it.
TFSPreview cloud service is not an option for us
I have install TFS express 2013 on my company network, we have developers at many place in the world so we want give access to the TFS server, but they never can successfully authenticate in the TFS Website, we can perfectly use it from inside.
In the IIS the tfs application: the authentication is set to Windows Authentication others are disable.
We have check the IIS logs and there is not firewall problem, their reach the server but always return a http 401 response.
My server is Windows 2012 and IIS 8.0, and i can't see where activate the Digest authentication as #Mike suggest
Any idea?
thanks in advance
I'm setting up a demo machine with Office and I want to be able to open an Office file using Sharepoint protocol. It seems like in Office 2010 that only SSL connections are allowed.
For this machine, I don't want to have to set up SSL.
This Microsoft article describes a workaround and how to configure it to use Basic Authentication, but it doesn't apply to Windows 2008. The Mr Fixit app fails because it doesn't work on Windows 2008 and the manual fixit doesn't apply.
This registry key doesn't exist in Windows 2008:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient
How can I enable Basic Authentication for Office 2010 on Windows 2008?
Create the above registry key? The description in the fixit makes it sound like it should already exist on those other Windows operating systems.
Considering that the WebClient key is missing it sounds like the WebDAV client is not installed.
A quick Google search yielded this:
On my Windows server 2008 system web client service is missing. Why so?
In Server 2008 edition, default setup does not have web client service. You need to install Desktop experience package to add web client service.