We have implemented the iT Hit server (v3.9) and Ajax library (v1.8.0.1342) and everything is fine with Word 2010 and 2013 and even Office for Mac:2011 but Word 2007 opens the document as read-only...we have tried using the information at http://www.webdavsystem.com/server/documentation/ms_office_read_only. We are using WebDAV.Client.DocManager.EditDocument(sFilename, "/ITHitMountOpenDocument.jar"); to open the document from a link on a web page. With 2007, there is not LOCK commands in the IIS log or in Fiddler...With 2010 and 2013, the LOCK command is in both...Also tried Webfldrs-KB907306-ENU.exe and updating the MSDAIPP.dll file. The client PC configuration is Windows 7 Professional SP1 (32bit), IE11 and Word 2007 (12.0.6715.5000) SP3 MSO (12.0.6683.5000).
The most typical cause of read-only issue with Microsoft Office 2007 is WebDAV server does not process requests on website root.
Microsoft Office 2007 and earlier may submit OPTIONS and PROPFIND
requests to site root (http://server/) and requires the server to
respond properly. If your WebDAV server is non-root (for example
http://server/dav/) Microsoft Office 2007 may open documents as
read-only.
If you are adding WebDAV to your project using 'Add WebDAV Server Implementation' wizard you will find the following code in your web.config file added by the wizard:
<system.webServer>
<handlers>
<add verb="OPTIONS,PROPFIND" path="*" type="WebApplication1.WebDAVServerImpl.DavHandler" name="My WebDAV Handler Root" preCondition="integratedMode" />
</handlers>
</system.webServer>
This enables WebDAV requests processing on site root in addition to your WebDAV folder (by default located in /DAV/ folder).
You can use Fiddler or any other HTTP debugging proxy to capture the request and see if there are any failed requests sent to site root.
EDIT: How to configure WebDAV server on root
As soon as WebDAV server is to large extent is a regular ASP.NET application, the configuration process is no different from configuring an ASP.NET web site on site root.
In short: Go to Sites node in IIS Manager and select Add Website in context menu. Fill-in the Site name in the Add Website dialog and select the application pool. In the Physical path field provide the path to the folder where your web.config file is located. Specify Binding options, such as hostname and port if necessary. Click OK.
You can find detailed instractions about how to configure WebDAV samples in WebDAV Server Examples section. The specifics of IIS configuration could be found in How to Configure Your WebDAV Server in IIS article.
Related
I am moving some old web applications from an old Server to a Server 2016. We are using a domain account for the application identity and we need to use windows authentication. I am getting a 401.3 error when I try a test.html page on the server. I am only getting this for static content though as I tried a home.aspx page and that page worked.
Things I have tried/checked
Static Content is installed under the Common HTTP Features
The domain account used for the app pool has full access to the directory containing test.html
Tried NTLM first as provider instead of Negotiate on IIS Windows Authentication Providers
Tried "Enable Kernel-mode authentication" checked and unchecked
Tried all settings of "Extended Protection" under Advanced settings for windows authentication.
Tried ProcMon. All I get when I filter for test.html is 2 QueryOpen operations with result SUCCESS
The solution for this was that we need to have the account that was running the application pool set up in the "Impersonate a client after authentication." Our local group policy had this locked down. I am guessing the default install may have IIS_USRS group in this policy but our server did not.
My problem is the opposite of many problems...
We have a WCF web service which works fine on our 'live' IIS server.
When I run the code in VS (even if running as admin) on the dev machine, I get nothing in the browser, and cannot request ?wsdl which also works on the server.
The web config files on both machines are identical.
What is wrong here, please?
EDIT:
I have added a new WCF project to the solution. That one DOES show the service, present the WSDL and allow browsing of the folder contents.
I copied the web config setting:
<directoryBrowse enabled="true"/>
into my existing web config, but it still won't allow directory browsing.
I have a question as to how the Visual Studio 2013 debug emulator for Web API works.
I had built a Web API project in Visual Studio 2013 to access a database on an external server. The code was built using VS2013's ASP.NET Web Application project template for a Web API application. Once built, running debug opened a browser window for localhost port 56618, which allowed access from Fiddler to test Http requests.
Once I had the project finished, I published it to a website using Web Deploy to IIS. However, whilst the page would open (now at localhost:9812), an http request would throw an Internal Server Error 500.
Perusing the IIS FailedReqLogFiles, I noticed that the reason that it was failing was that the database server was refusing access to '<Domain>\<machine-name>$'.
I added '<Domain>\<machine-name>$' as a valid login (windows authentication, as the connection string included "Integrated Security=true") on the sql instance with read and write privileges, and the problem was resolved.
The question is, why didn't the Visual Studio debug emulator have the same issue?
Because the emulator was running the website under the context of your own account (e.g. <Domain>\You). Your account had access to the database, so there was no issue.
When you published it to IIS, it started running under the context of a different account (<Domain>\Machine-Name - but there are other variants depending on how IIS is configured, and the version of IIS), which didn't have access to your database.
I have a Federated Authentication Server that is fully operational, Azure Synced, Office 365 Synced and local. Every part of the configuration works flawlessly. The issue that i am having is that
There is no trace of any Web Directory Files, I have looked in every location, and the virtual directories do no exist on my Federation Proxy or Federation Server.
I am trying to edit the Log in pages or create a new form. Where are these files? or how can i create them so The federation server displays the Log in pages i have created?
You can't find them because they don't exist!
ADFS 3.0 does not use IIS (hence no pages) - it runs directly on http.sys.
You can customize it to a limited extent.
Refer: ADFS : Customising the screen for ADFS 2012 R2 or ADFS 3.0 or ADFS 2.2 .
I am just starting out with Team Foundation Server 2008, and one of the hangups I've experienced is the following:
I create a new Team Project, as well as a Project Portal (which I believe is just a Sharepoint site). When I go to view the project portal in the browser, it prompts me for a username and password. I want it to use digest authentication (meaning it just uses my current domain credentials). I have this working on the Team Foundation site itself, but I cannot seem to get it working at all on the Project Portal sites that TFS creates for me.
Any thoughts? I've already attempted to set digest authentication on the Default Website as well as the Sharepoint Central Administration (v3) site, both of which did not fix my problem.
EDIT: I am running this on Windows Server 2003.
Check whether the pool account running the TFS sites is in your domain.
Your host may also not be in the 'Safe sites' / 'Intranet Zone' config in Internet Explorer, you can make it a trusted site and mark in the advanced options to send username and password.