Content Server Fails to Start Due to CoreWebdav Exception

(Doc ID 1369032.1)

Last updated on JULY 26, 2017

Applies to:

Oracle Universal Content Management - Version: to - Release: 10gR3 to 10gR3
Information in this document applies to any platform.


The Content Server fails to start. The Content Server log shows an exception like the following:

'CoreWebdav' component, version '2009_06_17 (build 30) br-10g-', extends webdav:2.0-2.0 feature(s)
Failed to initialize the server.
(internal) 10.19 13:42:29.092 main !csFailedToInitServer (!syServiceRuntime,java.lang.NullPointerException
at webdavcomponent.WebdavLocksManager.loadLocks(
at webdavcomponent.WebdavFilters.doFilter(
at intradoc.shared.PluginFilters.filter(
at intradoc.server.IdcExtendedLoader.executeFilter(
at intradoc.server.IdcExtendedLoader.extraBeforeCacheLoadInit(
at intradoc.server.IdcSystemLoader.loadCaches(
at intradoc.server.IdcServerManager.init(
at IdcServer.init(
at IdcServer.main(
)-exception stack

If the CoreWebdav component is disabled, then the Content Server will start with no issue.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms