This content has been marked as final. Show 14 replies
Probably cause is that the DAV redirector (WEBDAV client in Windows 7) is not configured to allow basic authenticiation...
The info for VISTA applies to Win 7.x
Note that it also depends on how you 'map' the drive..
If you use "MAP NETWORK DRIVE" you go through the redirector and the above applies...
If you use the "Connect to a Website that you can use to store documents and pictures link" on the Map Network Drive dialog, then you use the older Microsoft DAV client and the KB mentioned above does not work.
Also note that if using the Redirector you will need 220.127.116.11.0
Edited by: mdrake on Nov 17, 2010 11:43 AM
Thanks for the reply.
I am trying to create "Add Network Location" in win 7 which is similar to "My network places" in Windows XP.
The main reason of doing it as you said i can access the folders of the XMLDB repository copy files create folders etc.,.
I am able to view the xmldb repository file hierarchy when i enter the url http://localhost:8080/ in the browser. Below is the list of hierarchy folders which are shown in the browser.
Index of /
OLAP_XDS/ Fri, 02 Apr 2010 13:43:43 GMT
home/ Tue, 16 Nov 2010 18:54:19 GMT
images/ Fri, 02 Apr 2010 14:18:49 GMT
olap_data_security/ Fri, 02 Apr 2010 13:43:44 GMT
public/ Tue, 16 Nov 2010 21:06:59 GMT
sys/ Mon, 15 Nov 2010 21:51:29 GMT
xdbconfig.xml Mon, 15 Nov 2010 22:31:25 GMT
xds/ Fri, 02 Apr 2010 13:43:44 GMT
The version of oracle 11g installed on my win 7 enterprise edition machine is Oracle Database 11g Enterprise Edition Release 18.104.22.168.0
So i am seeing the problem of invalid folder name when i am creating the Network location.
And what is the older Microsoft DAV client which u mentioned ?
Edited by: MadhuK1 on Nov 17, 2010 12:35 PM
Edited by: MadhuK1 on Nov 17, 2010 12:47 PM
I'm sorry but the DAV implementation in the "Add Network Location" in Windows 7 is impemented very differently from the "My Network Places" implentation in Windows XP. Microsoft has (and actually has had for a while) 2 DAV clients, both of which are accessable via the Windows Explorer / "Add Network Location" feature....
The first is the original DAV Client [which allows DAV enabled clients, such as the Microsoft Office products, to access DAV resources via HTTP URLs]. The second is a newer implemtentation, known as the Windows DAV Redirector, that enables mapping a DAV server as a network drive. (This implementation allows any applicaiton to access content on the DAV server since by masking the fact that the content is being accesssed by HTTP from the application).
In XP when you mapped a DAV Server folder using the wizard launched from the "My network places" dialog it used the older implementation
(The only way to use the newer implementation in XP that I was aware of was via a specific "net use" command issued via from a dos command prompt)
In Windows 7 (and Vista) when you use the Map Network Drive option to map a drive to a DAV server you are using the redirector. If you click on the link in the Map Network Drive dialog then you can access the older HTTP only implementation.
Other than the fact it allow a DAV server to be mapped as a network driver the biggest difference between the newer and older implementations is that by default the redirector only supports Digest Authentication out of the box. It does not support Basic Authentication. So when the redirector attempts to connect to the XML DB (and other DAV Servers which do not support Digest Authentication, such as share point) it cannot authenticate so you get folder not found errros. ONce you follow the steps in the document i referenced the redirector will use Basic authentication and you will be able to access your content.
HTTP access via a browser still works since the HTTP Authentication implementation in the Browser is shared with the HTTP Authentication implementation in the older DAV client, which supports Basic Authentication without having to edit the registry.
Am I allowed to set XDB to "digest" instead of "basic" authentication ?
I did changed the registry settiings as mentioned in the link "http://support.microsoft.com/kb/841215".
I still see the same error. I am unable to create network location for http://localhost:8080/.
Edited by: MadhuK1 on Nov 17, 2010 6:09 PM
1. Did you restart the machine after modifying the registry per the instructions for Windows Vista
2. Is the "WebClient" Service started on your machine
Also make sure an export of the WebClient\parameters key looks like this
Windows Registry Editor Version 5.00
BTW this is not a supported configuration until you have database release 22.214.171.124.0
I checked the registry values, they are same as you yours.
Yes the Webclient is started.
My oracle 11g version is 126.96.36.199.0. 32 bit for window 7 enterprise edition.
I still c the problem.
OK, so you will need to wait for 11gR2 to become available on Windows for this to work
Also, can you try this
Edited by: mdrake on Nov 17, 2010 9:56 PM
C:\Users\Mark D Drake>net use w: /delete w: was deleted successfully. C:\Users\Mark D Drake>net use w: http://localhost:80 /USER:SCOTT tiger The command completed successfully. C:\Users\Mark D Drake>dir w: Volume in drive W has no label. Directory of W:\ 10/29/2010 01:31 PM <DIR> . 10/29/2010 01:31 PM <DIR> .. 10/20/2010 07:26 PM <DIR> OLAP_XDS 10/29/2010 01:38 PM <DIR> XFILES 10/29/2010 01:31 PM <DIR> home 10/20/2010 07:26 PM <DIR> olap_data_security 11/16/2010 09:54 AM <DIR> public 10/29/2010 01:58 PM <DIR> publishedContent 10/29/2010 01:27 PM <DIR> sys 10/20/2010 07:26 PM <DIR> xds 0 File(s) 0 bytes 10 Dir(s) 190,859,694,080 bytes free C:\Users\Mark D Drake>
There are 2 bugs tracking this issue, which I just marked as PUBLISHED.
BUG:Oracle 9260456 80 METADATA STORED BY WINDOWS 7 DAV CLIENT CAUSES SERVER SIDE CRASH
BUG:Oracle 9057015 32 WEBDAV DOES NOT WORK WITH WINDOWS 7 DAV PROVIDER
The dos comand net works great !!
After i run the command in the dos window, i opened the Windows explorer i see the the network folder got created and i can create folders, copy files, delete ...
Thanks alot for your patience and understanding in responding to the issue.
Thank you, Thank you, Thank you, Thank you, Thank you, Thank you,Thank you, Thank you, Thank you,Thank you, Thank you, Thank you,Thank you, Thank you, Thank you,Thank you, Thank you, Thank you,Thank you, Thank you, Thank you !!!
Updating the Windows 7 Registry key to value 2 (the regisitry key already existed) finally did it. After keeping into account Firewalls, IPV6 configurations, routing, virus software, iptables, etc, on local and server environments, I finally can connect once again via Windows Explorer WebDAV and FTP, without using "old" environments in demo and test setups.
Very happy man here.