BOE XI3.0 and AdaptiveProcessingServer set to disabled

Can’t start the ADaptiveProcessingServer within manage server window of SIA. I have restarted the SIA, but it continues to show stopped state and disabled for 2 servers. I also have the same exact issue with the Multi Dimensional Analysis Services Server.

I was originally looking into a publication issue that i am having with what I’m guessing to be a classpath issue? That is when I noticed the disabled state on the 2 services within SIA. The following is the failed error message when running publications for a report:

Server Used: hostname.PublicationJobServer
Folder Path: Report Scheduler/
Remote Instance: No
Error Message: Unexpected exception caught. Reason: [java.lang.NoClassDefFoundError: com/crystaldecisions/sdk/occamgr/internal/EnsureActiveSession].
Log File: View Log File

Here is what the logging folder shows for one of the services not starting:

<log4j:event logger=“org.apache.geronimo.gbean.runtime.GBeanInstanceState” timestamp=“1251816497932” level=“ERROR” thread=“main”>
log4j:message</log4j:message>
log4j:throwable<![CDATA[java.lang.NoClassDefFoundError: com/crystaldecisions/sdk/occamgr/internal/EnsureActiveSession
at com.businessobjects.framework.servers.platform.modules.serversession.ServerSessionProvider.doStart(ServerSessionProvider.java:118)
at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:977)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124)
at org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:527)
at com.businessobjects.framework.servers.common.fast.FastKernel.startRecursiveGBean(FastKernel.java:357)
at org.apache.geronimo.kernel.config.ConfigurationUtil.startConfigurationGBeans(ConfigurationUtil.java:374)
at org.apache.geronimo.kernel.config.KernelConfigurationManager.start(KernelConfigurationManager.java:187)
at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:527)
at org.apache.geronimo.kernel.config.SimpleConfigurationManager.startConfiguration(SimpleConfigurationManager.java:508)
at com.businessobjects.framework.servers.platform.bootstrap.Boot.buildConfiguration(Boot.java:266)
at com.businessobjects.framework.servers.platform.bootstrap.Boot.doStart(Boot.java:95)
at org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:977)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:267)
at org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102)
at org.apache.geronimo.gbean.runtime.GBeanInstance.start(GBeanInstance.java:513)
at org.apache.geronimo.gbean.runtime.GBeanDependency.attemptFullStart(GBeanDependency.java:111)
at org.apache.geronimo.gbean.runtime.GBeanDependency.addTarget(GBeanDependency.java:146)
at org.apache.geronimo.gbean.runtime.GBeanDependency$1.running(GBeanDependency.java:120)
at com.businessobjects.framework.servers.common.fast.FastLifecycleMonitor.fireRunningEvent(FastLifecycleMonitor.java:178)
at com.businessobjects.framework.servers.common.fast.FastLifecycleMonitor.access$200(FastLifecycleMonitor.java:45)
at com.businessobjects.framework.servers.common.fast.FastLifecycleMonitor$RawLifecycleBroadcaster.fireRunningEvent(FastLifecycleMonitor.java:291)


steiners (BOB member since 2008-10-09)

For most other servers you can simply create another one and delete the original, but not with the Adaptive servers - have you tried a Repair?


MikeD :south_africa: (BOB member since 2002-06-18)

That seems to be the case, Mike but actually you can create a new server, select, for example, the Client Auditing Proxy Server and when you click next you can select other Adaptive Processing Server functions. It will even name the new server as an AdaptiveProcessingServer1.

Also, you can try and create a new MDAS server and see if that fixes it for MDAS.

So going back to MikeD’s original solution - just try and create a new server instance and see if that fixes things.

BTW - I have seen this once in a training environment but as that was a VMware image I just went back to the original state and that ‘fixed’ it.


Orange :netherlands: (BOB member since 2006-09-18)

Interesting - we live and learn - thanx for the headsup Orange - and yeah, I’d go try that option …


MikeD :south_africa: (BOB member since 2002-06-18)

any solutions yet, i tried recreating but it did not help in my case; surprisingly it happened only after xi 3.1 sp2 install


bdharma (BOB member since 2008-07-07)

any solutions yet, i tried recreating but it did not help in my case; surprisingly it happened only after xi 3.1 sp2 install


bdharma (BOB member since 2008-07-07)

I ended unistalling SP2 and re-installed the BOE product with fix pack 1.8 (after clean up of previous install) and made it to work


bdharma (BOB member since 2008-07-07)