intradoc.common.ServiceException

!csServiceDataException,DBSEARCH_UPDATE_ZONE_FIELDS,addOrRemoveZoneFields!$ (internal)/6 11.09 11:30:55.755 [ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' *ScriptStack DBSEARCH_UPDATE_ZONE_FIELDS (internal)/6 11.09 11:30:55.755 [ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' 3:addOrRemoveZoneFields,**no captured values**

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web169

  • via Unknown by 690263,
  • via Unknown by 2957385,
  • Stack trace

    • intradoc.common.ServiceException: !csServiceDataException,DBSEARCH_UPDATE_ZONE_FIELDS,addOrRemoveZoneFields!$ (internal)/6 11.09 11:30:55.755 [ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' *ScriptStack DBSEARCH_UPDATE_ZONE_FIELDS (internal)/6 11.09 11:30:55.755 [ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' 3:addOrRemoveZoneFields,**no captured values** at intradoc.server.ServiceRequestImplementor.buildServiceException(ServiceRequestImplementor.java:2176) at intradoc.server.Service.buildServiceException(Service.java:2410) at intradoc.server.Service.createServiceExceptionEx(Service.java:2404) at intradoc.server.Service.createServiceException(Service.java:2399) at intradoc.server.ServiceRequestImplementor.handleActionException(ServiceRequestImplementor.java:1816) at intradoc.server.ServiceRequestImplementor.doAction(ServiceRequestImplementor.java:1766) at intradoc.server.Service.doAction(Service.java:566) at intradoc.server.ServiceRequestImplementor.doActions(ServiceRequestImplementor.java:1483) at intradoc.server.Service.doActions(Service.java:561) at intradoc.server.ServiceRequestImplementor.executeActions(ServiceRequestImplementor.java:1415) at intradoc.server.Service.executeActions(Service.java:547) at intradoc.server.ServiceRequestImplementor.doRequest(ServiceRequestImplementor.java:751)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown visitor
    Unknown visitorOnce,
    Unknown visitor
    Unknown visitorOnce,