3.1 Adaptive Processing Server

I am using 3.1 SP4 and my Adaptive Processing Server has abruptly developed an issue.

  1. When I restart the SIA the Adaptive Processing Server will not restart, so after the reboot it is stopped but it is enabled.
  2. If I manually start it, the state changes to disabled.
  3. If after I manually start it, I attempt to change the state to enabled the state will not change.
  4. I can only change the state if the Adaptive Processing Server is not running.

Does anyone have any ideas? It’s a test server, so I don’t want to log with SAP if avoidable because it will take so long…

Thanks for looking.


soulie :us: (BOB member since 2005-03-15)

What’s your environment, windows, unix, ?

Anything in your logs, windows event or BO??

B


bdouglas :switzerland: (BOB member since 2002-08-29)

Windows 2008 R2 SP1.

The logs have shown nothing.

Thanks.


soulie :us: (BOB member since 2005-03-15)

I wonder if the r2 permissions are an issue… can you try opening up permissions to your BO service account, stuff like escalate without prompting, etc…? Maybe it’s trying to kill a process, delete temp files, and the new permissions are holding it up.

Just a thought, but permissions are always my first instinct.

B


bdouglas :switzerland: (BOB member since 2002-08-29)

Hi,

Did you solved this already. We’re using BOXI 3.1 SP5 and see the Adaptive processing server disabled and we tried to give it the enable status but sofar it didn’t work…

We already tried the following:

  • stopping/starting / restarting /enable this server from CMC didn’t work
  • stopping SIA, Tomcat from CCM did not work.
  • because we have a clustered environment I also stopped the complete clustered environment from CCM> didn’t work also

TurningPointHolland :netherlands: (BOB member since 2006-09-06)

Hi,

One more thing we tried, we did a repair install of BO XI3.1 SP5 and this did also NOT help!


TurningPointHolland :netherlands: (BOB member since 2006-09-06)

We had the same issue. I deleted and recreated the APS. This resolved the issue.


hcrowe (BOB member since 2008-10-20)

Finally we rebooted the whole environment and then it was solved…! But is still strange behaviour!


TurningPointHolland :netherlands: (BOB member since 2006-09-06)