Setting "HtmlDataInputFilterLevel=exceptsafe" Causes WebDAV and CheckOutAndOpen Error "Documents in this Folder are not Available"
(Doc ID 741637.1)
Last updated on MAY 10, 2023
Applies to:
Oracle WebCenter Content - Version 10.0 and laterInformation in this document applies to any platform.
Symptoms
Upon browsing in the Content Server user interface to a Contribution Folder with a Microsoft Word doc in it and selecting the document's Action of "Check Out and Open", the following error and exception are thrown although other Content Server functions operate correctly:
Error thrown in Microsoft Windows Explorer Web Folders:
---------
Error
Documents in this folder are not available. The folder may have been moved or deleted, or network
problems may be preventing a connection to the server.
[ OK ]
---------
Error
Documents in this folder are not available. The folder may have been moved or deleted, or network
problems may be preventing a connection to the server.
[ OK ]
---------
Exception thrown in the Content Server log:
Unable to execute service FOLDERS_PROPFIND and function foldersWebdavPropFind.
(System Error: Could not parse incoming WebDAV XML request. Reference is not allowed in prolog.)
Could not parse incoming WebDAV XML request. Reference is not allowed in prolog. [ Details ]
An error has occurred. The stack trace below shows more information.
!csServiceDataException,FOLDERS_PROPFIND,foldersWebdavPropFind!$!csSystemError,\!csCouldNotParseInco
mingWebdavXML\!$Reference is not allowed in prolog.!csCouldNotParseIncomingWebdavXML!$Reference is
not allowed in prolog.
intradoc.common.ServiceException:
!csServiceDataException,FOLDERS_PROPFIND,foldersWebdavPropFind!$!csSystemError,\!csCouldNotParseInco
mingWebdavXML\!$Reference is not allowed in prolog.
at
intradoc.server.ServiceRequestImplementor.buildServiceException(ServiceRequestImplementor.java:1710)
at intradoc.server.Service.buildServiceException(Service.java:1987)
at intradoc.server.Service.createServiceExceptionEx(Service.java:1981)
at intradoc.server.Service.createServiceException(Service.java:1976)
at
intradoc.server.ServiceRequestImplementor.handleActionException(ServiceRequestImplementor.java:1429)
at intradoc.server.ServiceRequestImplementor.doAction(ServiceRequestImplementor.java:1396)
at intradoc.server.Service.doAction(Service.java:450)
at intradoc.server.ServiceRequestImplementor.doActions(ServiceRequestImplementor.java:1170)
at intradoc.server.Service.doActions(Service.java:445)
at intradoc.server.ServiceRequestImplementor.executeActions(ServiceRequestImplementor.java:1090)
at intradoc.server.Service.executeActions(Service.java:431)
at intradoc.server.ServiceRequestImplementor.doRequest(ServiceRequestImplementor.java:632)
at intradoc.server.Service.doRequest(Service.java:1697)
at intradoc.server.ServiceManager.processCommand(ServiceManager.java:357)
at intradoc.server.IdcServerThread.run(IdcServerThread.java:195)
Caused by: intradoc.data.DataException: !csCouldNotParseIncomingWebdavXML!$Reference is not
allowed in prolog.
at webdavcomponent.WebdavXMLUtils.parseDocument(WebdavXMLUtils.java:92)
at webdavcomponent.WebdavXMLUtils.getXML(WebdavXMLUtils.java:120)
at folderswebdav.FoldersW ebdavHandler.foldersWebdavPropFind(FoldersWebdavHandler.java:1383)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at intradoc.common.IdcMethodHolder.invokeMethod(ClassHelperUtils.java:461)
at intradoc.common.ClassHelperUtils.executeMethodReportStatus(ClassHelperUtils.java:142)
at intradoc.server.ServiceHandler.executeAction(ServiceHandler.java:75)
at intradoc.server.Service.doCodeEx(Service.java:488)
at intradoc.server.Service.doCode(Service.java:470)
at intradoc.server.ServiceRequestImplementor.doAction(ServiceRequestImplementor.java:1329)
... 9 more
(System Error: Could not parse incoming WebDAV XML request. Reference is not allowed in prolog.)
Could not parse incoming WebDAV XML request. Reference is not allowed in prolog. [ Details ]
An error has occurred. The stack trace below shows more information.
!csServiceDataException,FOLDERS_PROPFIND,foldersWebdavPropFind!$!csSystemError,\!csCouldNotParseInco
mingWebdavXML\!$Reference is not allowed in prolog.!csCouldNotParseIncomingWebdavXML!$Reference is
not allowed in prolog.
intradoc.common.ServiceException:
!csServiceDataException,FOLDERS_PROPFIND,foldersWebdavPropFind!$!csSystemError,\!csCouldNotParseInco
mingWebdavXML\!$Reference is not allowed in prolog.
at
intradoc.server.ServiceRequestImplementor.buildServiceException(ServiceRequestImplementor.java:1710)
at intradoc.server.Service.buildServiceException(Service.java:1987)
at intradoc.server.Service.createServiceExceptionEx(Service.java:1981)
at intradoc.server.Service.createServiceException(Service.java:1976)
at
intradoc.server.ServiceRequestImplementor.handleActionException(ServiceRequestImplementor.java:1429)
at intradoc.server.ServiceRequestImplementor.doAction(ServiceRequestImplementor.java:1396)
at intradoc.server.Service.doAction(Service.java:450)
at intradoc.server.ServiceRequestImplementor.doActions(ServiceRequestImplementor.java:1170)
at intradoc.server.Service.doActions(Service.java:445)
at intradoc.server.ServiceRequestImplementor.executeActions(ServiceRequestImplementor.java:1090)
at intradoc.server.Service.executeActions(Service.java:431)
at intradoc.server.ServiceRequestImplementor.doRequest(ServiceRequestImplementor.java:632)
at intradoc.server.Service.doRequest(Service.java:1697)
at intradoc.server.ServiceManager.processCommand(ServiceManager.java:357)
at intradoc.server.IdcServerThread.run(IdcServerThread.java:195)
Caused by: intradoc.data.DataException: !csCouldNotParseIncomingWebdavXML!$Reference is not
allowed in prolog.
at webdavcomponent.WebdavXMLUtils.parseDocument(WebdavXMLUtils.java:92)
at webdavcomponent.WebdavXMLUtils.getXML(WebdavXMLUtils.java:120)
at folderswebdav.FoldersW ebdavHandler.foldersWebdavPropFind(FoldersWebdavHandler.java:1383)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at intradoc.common.IdcMethodHolder.invokeMethod(ClassHelperUtils.java:461)
at intradoc.common.ClassHelperUtils.executeMethodReportStatus(ClassHelperUtils.java:142)
at intradoc.server.ServiceHandler.executeAction(ServiceHandler.java:75)
at intradoc.server.Service.doCodeEx(Service.java:488)
at intradoc.server.Service.doCode(Service.java:470)
at intradoc.server.ServiceRequestImplementor.doAction(ServiceRequestImplementor.java:1329)
... 9 more
.
Changes
"HtmlDataInputFilterLevel=exceptsafe" was recently set in the Content Server's <cs>/config/config.cfg.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |