Quantcast
Channel: SCN : Discussion List - BI Platform
Viewing all 5403 articles
Browse latest View live

Getting error while opening BI Admin cockpit in CMC after upgrade to BI 4.2 SP2

$
0
0

Hi All,

 

We have recently upgraded our BI system from 4.1 SP6 to BI 4.2 SP2 and post upgrade when we are trying to access BI administrator cockpit in CMC, it is giving the following error.

cockpiterror.JPG

 

I tried the option of renaming local host file to .old after stopping the Tomcat server and restarting the same. But this is not working. If anyone has come across similar problem. Please suggest how to resolve this issue.


Java Deserialization Remote Code Execution ob BOXI3.1SP7

$
0
0

I have this requirement to disable the Java Deserialization Remote code execution on one of our Tomcat Web App servers.

Can you please guide me how to execute/disable this on the Tomcat Web App server and then have to test Business objects Webi reports etc to make sure if this has any impact.

 

Thanks,

Shravan

CMC Error: Failed to Retrieve cluster name from Database

$
0
0

Hi All,

 

Iam getting this error message when Iam checking the properties of CMC.

 

BOXI Server intelligence Agent is running status . but no server is running.

 

In CCM , SIA Configuaration tab showing this error message

"Failed to Retrieve cluster name from Database"

 

 

Iam unable to change the cluster name of Server Intelligence AGent.

 

Please help us.

 

Thanks in advance..

Modify Name Server Port for CMS

$
0
0

We have installed our BI Platform 41. SP6 version sometime back and while installing (in clustered mode) we setup CMS 1 with default port number 6400 and CMS 2 with another port number (7425) for some testing purposes. It is working fine and we are using this server as our UAT server and so far so good. we are planning to change this second CMS Name server port number from 7425 to default 6400 port number (for various reasons).

 

Any Idea on how should I do this? Also, if any one has experienced issues while changing this please let me know. That would be a great help and really appreciated.

 

Thanks

Total Disk space consuming on SAP BI installed Server, How to get back free space?

$
0
0

Hi experts,

 

We are facing disk space consuming issue on our SAP BO server system.

 

Server configuration as follows:-

OS: Windows Server 2008 R2

Installed Tools: SAP BI and other supporting tools, MS-SQL Server 2008 DB, BMC Analyics for BSM etc...

RAM Size: Enough size 8GB appr..

ROM: Dedicated 200GB on C:\ drive.

 

Issue: The issue exactly is some unknown processes are consuming all disk data in a time period., 10 GB became 0 in days like that...

 

How to get free disk space back on C:\ drive?

 

Please let me know any solution for this...

 

 

Thanks in advance,

Sreenu

SAP BO Event Log Error occured Event: 45388

$
0
0

Hello we are getting lots of below events on our server. how to solve this and what is cause of this event error.

 

Error occured at                17:14:54  01/14/2013

 

Machine name:                toasas012242

Event:                  45388 

Event category:               6

Source:                                BusinessObjects_JobServer

Record:                               171216

 

Error message:  

Subprocess (Job Server Child) could not be started. Reason: Couldn't get IJob interface or writing IAudit: Pipe exception. Reason: jobserverchild (PublicationSchedulingService, 0, Timeout waiting for Child [13280] to register ([120]seconds).

.

 

Regards,

Atul.

BO migration from BO XI R2 SP1 to BI 4.1

$
0
0

We are planning to migrate from BO XI R2 SP1 to 4.1

 

I have few questions:

1) As SAP insists, migration to higher version should be from SP2 or higher.

But in market place, I did not find BO Xi r2 SP2 & SP3. So do I need to raise SAP incident for the same?

 

2) Some experience people, also say that direct migration from XI r2 SP2 to 4.1 is not advisable though SAP insists.

   We need to migrate to 3.1 and then to 4.1

So it will be 2 step migration.

i.e. xi r2 SP1 --------------> xi r2 SP2--------------> xi r3.1 -------------> 4.1

 

3) Please guide if someone have other way to tackle this.

How to clear an entire repository, deleting all user built reports, folders, etc and start fresh?

$
0
0

I am trying to figure out the best way to clear my repository on my test 4.2 server and start from scratch.

I've migrated a bunch of content from our 4.1 system, but I want to remove all of that and start fresh again.

 

I do not want to lose CMC configurations (FRS directories, custom request ports, etc), I just want to drop all of the reports/dashboards, etc.

 

I do not want to drop the built in samples, if possible.

 

I don't want to delete the FRS directory straight away because I understand that there are system files in there that should not be deleted, and are created by default as part of the install.

 

Has anyone attempted this and/or have scripts for the CMS database, and then maybe subsequently run a REPOSCAN to clean up the FRS?

 

Thank you for your input.


Crystal Reports Server 2008 - Jobserver fails!

$
0
0

Hi,

 

I've just installed Crystal Reports Server 2008 V1. With the server specs listed below:

 

ESX VMWare Server

OS: Windows Server 2003

RAM: 4GB

DISK: 20GB FREE

 

I've since started scheduling reports and setting up of the user profiles/access levels.

 

The scheduling of reports worked fine for the first 2-3 days. After that, it seems as though the job server just dies/stops scheduling. Any other instances that are run manually will be stucked with the status "Pending".

 

Only after rebooting the Jobserver, will the 'stuck' jobs be processed. This is getting kind of irritating and unacceptable. Anyone has any solutions to this issue that i am facing ?.

 

Really appreciate any help!

 

Also, my event log shows a couple of errors and warnings which i will add below:

 

Event Type:     Error

Event Source:     BusinessObjects_JobServer

Event Category:     Scheduling

Event ID:     45388

Date:          16/12/2009

Time:          2:45:31 PM

User:          N/A

Computer:     XXXCRS01

Description:

Subprocess (Job Server Child) could not be started. Reason: Couldn't get IJob interface or writing IAudit: Pipe exception. Reason: jobserverchild (procreport, 0, Timeout waiting for Child [5724] to register ([120]seconds).

.

 

Event Type:     Warning

Event Source:     BusinessObjects_CMS

Event Category:     General

Event ID:     33017

Date:          16/12/2009

Time:          2:44:58 PM

User:          N/A

Computer:     XXXCRS01

Description:

Unable to contact server XXXCRS01.WebApplicationContainerServer on machine XXXCRS01 to perform status notification. Please check the server's system log for errors.

 

Edited by: Tan Ivan on Dec 16, 2009 8:28 AM

 

Edited by: Tan Ivan on Dec 16, 2009 8:30 AM

Adaptive processing server is running with errors after 4.2 upgrade

$
0
0

Hi all,

 

 

I have upgraded SAP business objects 4.1 SP05 to 4.2 SP02 PL01, after upgraded adaptive processing server is running with errors.

 

anyone faced this error before? please help.

 

Please find the few info from log - .AdaptiveProcessingServer_trace.001378

 

DER_END

|82C83B2437E24A53AA705A49A59BC90F1112|2016 05 20 16:52:09.716|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal.InternalInfoStore.query(InternalInfoStore.java:1)

|82C83B2437E24A53AA705A49A59BC90F1113|2016 05 20 16:52:09.716|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal.InfoStore.query_aroundBody12(InfoStore.java:212)

|82C83B2437E24A53AA705A49A59BC90F1114|2016 05 20 16:52:09.716|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal.InfoStore.query_aroundBody13$advice(InfoStore.java:512)

|82C83B2437E24A53AA705A49A59BC90F1115|2016 05 20 16:52:09.716|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal.InfoStore.query(InfoStore.java:1)

|82C83B2437E24A53AA705A49A59BC90F1116|2016 05 20 16:52:09.716|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.common.Utilities.execQuery(Utilities.java:44)

|82C83B2437E24A53AA705A49A59BC90F1117|2016 05 20 16:52:09.716|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.extractor.boe.tasks.RepoCrawlingTask.getToBeExtractedObjects(RepoCrawlingTask.java:487)

|82C83B2437E24A53AA705A49A59BC90F1118|2016 05 20 16:52:09.716|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.extractor.boe.tasks.RepoCrawlingTask.access$100(RepoCrawlingTask.java:35)

|82C83B2437E24A53AA705A49A59BC90F1119|2016 05 20 16:52:09.716|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.extractor.boe.tasks.RepoCrawlingTask$1.process(RepoCrawlingTask.java:82)

|82C83B2437E24A53AA705A49A59BC90F111a|2016 05 20 16:52:09.716|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.extractor.boe.tasks.RepoCrawlingTask$1.process(RepoCrawlingTask.java:58)

|82C83B2437E24A53AA705A49A59BC90F111b|2016 05 20 16:52:09.716|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.common.Utilities.executeQueries(Utilities.java:94)

|82C83B2437E24A53AA705A49A59BC90F111c|2016 05 20 16:52:09.717|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.common.Utilities.atomicExecute(Utilities.java:51)

|82C83B2437E24A53AA705A49A59BC90F111d|2016 05 20 16:52:09.717|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.extractor.boe.tasks.RepoCrawlingTask.invoke(RepoCrawlingTask.java:57)

|82C83B2437E24A53AA705A49A59BC90F111e|2016 05 20 16:52:09.717|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.sdk.common.Task.run(Task.java:86)

|82C83B2437E24A53AA705A49A59BC90F111f|2016 05 20 16:52:09.717|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

|82C83B2437E24A53AA705A49A59BC90F1120|2016 05 20 16:52:09.717|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)

|82C83B2437E24A53AA705A49A59BC90F1121|2016 05 20 16:52:09.717|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)

|82C83B2437E24A53AA705A49A59BC90F1122|2016 05 20 16:52:09.717|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)

|82C83B2437E24A53AA705A49A59BC90F1123|2016 05 20 16:52:09.717|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

|82C83B2437E24A53AA705A49A59BC90F1124|2016 05 20 16:52:09.717|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

|82C83B2437E24A53AA705A49A59BC90F1125|2016 05 20 16:52:09.717|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at java.lang.Thread.run(Thread.java:812)

|82C83B2437E24A53AA705A49A59BC90F1126|2016 05 20 16:52:09.718|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| ||||||||||||||||||||||Caused by: com.crystaldecisions.enterprise.ocaframework.idl.OCA.oca_abuse: IDL:img.seagatesoftware.com/OCA/oca_abuse:3.2

|82C83B2437E24A53AA705A49A59BC90F1127|2016 05 20 16:52:09.718|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.enterprise.ocaframework.idl.OCA.oca_abuseHelper.read(oca_abuseHelper.java:106)

|82C83B2437E24A53AA705A49A59BC90F1128|2016 05 20 16:52:09.718|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.enterprise.ocaframework.idl.OCA.OCAi._InfoStore_XRL4Stub.queryEx3(_InfoStore_XRL4Stub.java:468)

|82C83B2437E24A53AA705A49A59BC90F1129|2016 05 20 16:52:09.718|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source)

|82C83B2437E24A53AA705A49A59BC90F112a|2016 05 20 16:52:09.718|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

|82C83B2437E24A53AA705A49A59BC90F112b|2016 05 20 16:52:09.718|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at java.lang.reflect.Method.invoke(Method.java:497)

|82C83B2437E24A53AA705A49A59BC90F112c|2016 05 20 16:52:09.718|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.enterprise.ocaframework.ManagedService.invoke(ManagedService.java:356)

|82C83B2437E24A53AA705A49A59BC90F112d|2016 05 20 16:52:09.718|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal._InfoStoreEx4Proxy.queryEx3(_InfoStoreEx4Proxy.java:364)

|82C83B2437E24A53AA705A49A59BC90F112e|2016 05 20 16:52:09.718|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal.InternalInfoStore$XRL3WireStrategy.query(InternalInfoStore.java:1685)

|82C83B2437E24A53AA705A49A59BC90F112f|2016 05 20 16:52:09.718|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer|11220| 289|PSS (20160520163806): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal.InternalInfoStore.queryHelper(InternalInfoStore.java:1071)

 

 

 

 

  ... 22 more

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a0c|2016 05 20 17:55:43.810|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |2|0|0|0|BIPSDK.InfoStore:query|CH00SSO1:6808:202.411132:1|-|-|BIPSDK.InfoStore:query|CH00SSO1:6808:202.411132:1|Co_goTxCDUobrBujGEGE5mY15645|||||||||||[Fatal Error] :1:1: Content is not allowed in prolog.

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a0d|2016 05 20 17:55:43.810|+0200|Error| |==|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |2|0|0|0|BIPSDK.InfoStore:query|CH00SSO1:6808:202.411132:1|-|-|BIPSDK.InfoStore:query|CH00SSO1:6808:202.411132:1|Co_goTxCDUobrBujGEGE5mY15645|||||||||com.businessobjects.foundation.exception.ExceptionSerializer||Failed to serialize exception. Encountered SAXException. Content is not allowed in prolog.

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a0e|2016 05 20 17:55:43.811|+0200|Error| |==|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |2|0|0|0|BIPSDK.InfoStore:query|CH00SSO1:6808:202.411132:1|-|-|BIPSDK.InfoStore:query|CH00SSO1:6808:202.411132:1|Co_goTxCDUobrBujGEGE5mY15645|||||||||com.businessobjects.foundation.exception.ExceptionSerializer||Error occured while parsing the serialized exception. null Content is not allowed in prolog.

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a0f|2016 05 20 17:55:43.811|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| ||||||||||||||||||||||com.crystaldecisions.sdk.exception.SDKServerException: The value '4294969733' cannot be compared to the value in the property SI_ID because the type conversion is not valid.

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a10|2016 05 20 17:55:43.811|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| ||||||||||||||||||||||cause:com.crystaldecisions.enterprise.ocaframework.idl.OCA.oca_abuse: IDL:img.seagatesoftware.com/OCA/oca_abuse:3.2

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a11|2016 05 20 17:55:43.811|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| ||||||||||||||||||||||detail:The value '4294969733' cannot be compared to the value in the property SI_ID because the type conversion is not valid.

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a12|2016 05 20 17:55:43.812|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| ||||||||||||||||||||||The server supplied the following details: OCA_Abuse exception 0 at [.\exceptionmapper.cpp : 79]  50216 {4294969733, SI_ID}

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a13|2016 05 20 17:55:43.812|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| ...The value '4294969733' cannot be compared to the value in the property SI_ID because the type conversion is not valid. Bad value in property

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a14|2016 05 20 17:55:43.812|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.exception.SDKServerException.map(SDKServerException.java:99)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a15|2016 05 20 17:55:43.812|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.exception.SDKException.map(SDKException.java:132)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a16|2016 05 20 17:55:43.812|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal.InternalInfoStore.queryHelper(InternalInfoStore.java:1083)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a17|2016 05 20 17:55:43.812|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal.InternalInfoStore.queryHelper(InternalInfoStore.java:1059)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a18|2016 05 20 17:55:43.812|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal.InternalInfoStore.query_aroundBody18(InternalInfoStore.java:928)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a19|2016 05 20 17:55:43.812|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal.InternalInfoStore.query(InternalInfoStore.java:1)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a1a|2016 05 20 17:55:43.813|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal.InfoStore.query_aroundBody12(InfoStore.java:212)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a1b|2016 05 20 17:55:43.813|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal.InfoStore.query_aroundBody13$advice(InfoStore.java:512)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a1c|2016 05 20 17:55:43.813|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal.InfoStore.query(InfoStore.java:1)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a1d|2016 05 20 17:55:43.813|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.common.Utilities.execQuery(Utilities.java:44)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a1e|2016 05 20 17:55:43.813|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.extractor.boe.tasks.RepoCrawlingTask.getToBeExtractedObjects(RepoCrawlingTask.java:487)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a1f|2016 05 20 17:55:43.813|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.extractor.boe.tasks.RepoCrawlingTask.access$100(RepoCrawlingTask.java:35)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a20|2016 05 20 17:55:43.813|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.extractor.boe.tasks.RepoCrawlingTask$1.process(RepoCrawlingTask.java:82)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a21|2016 05 20 17:55:43.813|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.extractor.boe.tasks.RepoCrawlingTask$1.process(RepoCrawlingTask.java:58)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a22|2016 05 20 17:55:43.813|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.common.Utilities.executeQueries(Utilities.java:94)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a23|2016 05 20 17:55:43.813|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.common.Utilities.atomicExecute(Utilities.java:51)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a24|2016 05 20 17:55:43.814|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.extractor.boe.tasks.RepoCrawlingTask.invoke(RepoCrawlingTask.java:57)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a25|2016 05 20 17:55:43.814|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.sdk.common.Task.run(Task.java:86)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a26|2016 05 20 17:55:43.814|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a27|2016 05 20 17:55:43.814|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a28|2016 05 20 17:55:43.814|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a29|2016 05 20 17:55:43.814|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a2a|2016 05 20 17:55:43.814|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a2b|2016 05 20 17:55:43.814|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a2c|2016 05 20 17:55:43.814|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at java.lang.Thread.run(Thread.java:812)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a2d|2016 05 20 17:55:43.815|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| ||||||||||||||||||||||Caused by: com.crystaldecisions.enterprise.ocaframework.idl.OCA.oca_abuse: IDL:img.seagatesoftware.com/OCA/oca_abuse:3.2

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a2e|2016 05 20 17:55:43.815|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.enterprise.ocaframework.idl.OCA.oca_abuseHelper.read(oca_abuseHelper.java:106)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a2f|2016 05 20 17:55:43.815|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.enterprise.ocaframework.idl.OCA.OCAi._InfoStore_XRL4Stub.queryEx3(_InfoStore_XRL4Stub.java:468)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a30|2016 05 20 17:55:43.815|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at sun.reflect.GeneratedMethodAccessor115.invoke(Unknown Source)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a31|2016 05 20 17:55:43.815|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a32|2016 05 20 17:55:43.815|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at java.lang.reflect.Method.invoke(Method.java:497)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a33|2016 05 20 17:55:43.815|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.enterprise.ocaframework.ManagedService.invoke(ManagedService.java:356)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a34|2016 05 20 17:55:43.815|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal._InfoStoreEx4Proxy.queryEx3(_InfoStoreEx4Proxy.java:364)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a35|2016 05 20 17:55:43.816|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal.InternalInfoStore$XRL3WireStrategy.query(InternalInfoStore.java:1685)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a36|2016 05 20 17:55:43.816|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal.InternalInfoStore.queryHelper(InternalInfoStore.java:1071)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a37|2016 05 20 17:55:43.816|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| ... 22 more

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a38|2016 05 20 17:55:44.816|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| ||||||||||||||||||||||com.crystaldecisions.sdk.exception.SDKServerException: The value '4294969733' cannot be compared to the value in the property SI_ID because the type conversion is not valid.

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a39|2016 05 20 17:55:44.816|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| ||||||||||||||||||||||cause:com.crystaldecisions.enterprise.ocaframework.idl.OCA.oca_abuse: IDL:img.seagatesoftware.com/OCA/oca_abuse:3.2

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a3a|2016 05 20 17:55:44.816|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| ||||||||||||||||||||||detail:The value '4294969733' cannot be compared to the value in the property SI_ID because the type conversion is not valid.

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a3b|2016 05 20 17:55:44.816|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| ||||||||||||||||||||||The server supplied the following details: OCA_Abuse exception 0 at [.\exceptionmapper.cpp : 79]  50216 {4294969733, SI_ID}

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a3c|2016 05 20 17:55:44.816|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| ...The value '4294969733' cannot be compared to the value in the property SI_ID because the type conversion is not valid. Bad value in property

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a3d|2016 05 20 17:55:44.817|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.exception.SDKServerException.map(SDKServerException.java:99)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a3e|2016 05 20 17:55:44.817|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.exception.SDKException.map(SDKException.java:132)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a3f|2016 05 20 17:55:44.817|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal.InternalInfoStore.queryHelper(InternalInfoStore.java:1083)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a40|2016 05 20 17:55:44.817|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal.InternalInfoStore.queryHelper(InternalInfoStore.java:1059)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a41|2016 05 20 17:55:44.817|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal.InternalInfoStore.query_aroundBody18(InternalInfoStore.java:928)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a42|2016 05 20 17:55:44.817|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal.InternalInfoStore.query(InternalInfoStore.java:1)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a43|2016 05 20 17:55:44.817|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal.InfoStore.query_aroundBody12(InfoStore.java:212)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a44|2016 05 20 17:55:44.817|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal.InfoStore.query_aroundBody13$advice(InfoStore.java:512)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a45|2016 05 20 17:55:44.817|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.crystaldecisions.sdk.occa.infostore.internal.InfoStore.query(InfoStore.java:1)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a46|2016 05 20 17:55:44.818|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.common.Utilities.execQuery(Utilities.java:44)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a47|2016 05 20 17:55:44.818|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.extractor.boe.tasks.RepoCrawlingTask.getToBeExtractedObjects(RepoCrawlingTask.java:487)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a48|2016 05 20 17:55:44.818|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.extractor.boe.tasks.RepoCrawlingTask.access$100(RepoCrawlingTask.java:35)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a49|2016 05 20 17:55:44.818|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.extractor.boe.tasks.RepoCrawlingTask$1.process(RepoCrawlingTask.java:82)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a4a|2016 05 20 17:55:44.818|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.extractor.boe.tasks.RepoCrawlingTask$1.process(RepoCrawlingTask.java:58)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a4b|2016 05 20 17:55:44.818|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.common.Utilities.executeQueries(Utilities.java:94)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a4c|2016 05 20 17:55:44.818|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.common.Utilities.atomicExecute(Utilities.java:51)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a4d|2016 05 20 17:55:44.818|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.extractor.boe.tasks.RepoCrawlingTask.invoke(RepoCrawlingTask.java:57)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a4e|2016 05 20 17:55:44.818|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at com.sap.businessobjects.platform.search.sdk.common.Task.run(Task.java:86)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a4f|2016 05 20 17:55:44.819|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a50|2016 05 20 17:55:44.819|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a51|2016 05 20 17:55:44.819|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a52|2016 05 20 17:55:44.819|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a53|2016 05 20 17:55:44.819|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

|A35D4AFBCDBC4275B0C87BFF5E7DAD313a54|2016 05 20 17:55:44.819|+0200|Error| |>>|E| |aps_SIAOS1.AdaptiveProcessingServer| 6808| 202|PSS (20160520170812): extraction.management Thread: 1/4| |||||||||||||||||||||| at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

CMC login issue after new node added....

$
0
0

Hi,

 

We are on SAP BI 4.1 SP6 On Win2008 R2 server on SQL Anywhere.

 

I have a BI 4.1 already installed on server1 and I open the CMC using the below link -

 

http://server1.abc.com:8080/BOE/CMC

 

I have build another standalone node on server2 and I open the CMC using below link

 

http://server1.abc.com:8080/BOE/CMC

 

Now I have added the node on server2 to CMS running on server1. It is added successfully. I have disable the SIA on server2, I logged on to the link "http://server1.abc.com:8080/BOE/CMC" and I can see the new node added under CMC - Servers - Node.

The issue is that when I open the CMC link for server2 http://server2.abc.com:8080/BOE/CMC then it gives following error -

 

"Account information not recognized: All the servers with CMS server2:6400, cluster @server2:6400, kind cms which host service null, are down or disabled" I was assuming that it will open the link.

 

I also want to state that the launchpad link on server2 "http://server1.abc.com:8080/BOE/BI" has no issue and it is opening and working fine. Is it normal behaviour?

 

Please advice.

 

Regards,

SS

Distributed Landscape - SAP BO 4.2

$
0
0

We are planning to install SAP BO 4.2 in a distributed environment. We have 4 different servers

 

  1. Server 1 : CMS
  2. Server 2 : Tomcat
  3. Server 3 : Design studio
  4. Server 4 : Database Server

 

As CMS and Design Studio are on different servers and have common Tomcat server, I was looking to have some insights on integration of these 2 servers (CMS & Design studio)

Please help me with some helpful links on this if possible.

upgrade of bw 7.0 sp10 to sp18

$
0
0

Dear All,

Hope doing good.

 

My project going to upgrade bw 7.0 sp 10 to SP 18,Can you please provide me what are the activities going to do.?

what is the new upgrades between SP10 to SP18.?

Please tell me the brief project flow ativities .?

 

Thanks to all.

webi report keep refreshing

$
0
0

Hi Expert,

we have one issue that, user belongs to Germany region for them one Webi report keep refreshing in BI launchpad, Generally report should refresh in 7 minutes, for same input parameters It works good for APAC region user, but again issue for Germany region user is  specific to amount of data, for some parameter it works for them (less data), for more data report keep running

 

We increased the connection parameter, but still have same problem.

we have recreated the report and converted UNX universe still have the same problem

 

database is SQL server

 

we are using BO4.1 SP4

 

Is it seems to network problem related any firewall., which option should we need check?

Any support?

 

Thanks in advance.

 

Regards,

Ganesha

Webi #MULTIVALUE issue

$
0
0

Hi

 

Two of  the columns is returning value  as #MULTIVALUE for certain rows in webi report .

I assume it's because the report is not able to handle multiple values for certain columns .

 

 

What could be the issue .

Any input will be helpful.(Let me know if further details required )

 

 

 

Regards,

Prabin


Bex report report into Prod

$
0
0

Hi gurus,

 

I have created a Bo report in prod with Bex query now want to get new fields in the Query can i change the same query or report that query which in dev so that query name and technical name  not get change.

 

once i tried to do the same i am getting a error in Bex Query  error is : bex query transport request is not suitable not available..

 

and suppose i create the new the query name getting change which is again to remap the object in Bo report further.

Please help..

 

Regards

BI 7.0 sp10 & we plan to upgarde sp18

$
0
0

Hi All, Our BW system is on BI 7.0 sp10 & we plan to upgarde sp18. An BW person should do in order to test them?

Any checklist or tasks that I need to do?

The BI support pack task checklist doesn't mention anything except Basis steps.

Are there some things to keep in mind?

 

Thanks All!

How to make Publication Email massage dynamic

$
0
0

Hello Experts,

 

I am trying to add Email massage in Publication originally which is look like

 

Capture.PNG

 

As you see in above image in that all MTD,FTD values and E-APP table are dynamic which is coming from report.

please suggest how can i add massage in publication Email.


Regards,

GK

Clients tools and https configuration

$
0
0

Hello everyone,

 

I've finished the https configuration in a Windows server with BI 4.1 SP 6, teh connection to BIlaunchPAd and the CMC is ok and no problem with the generation of the certificat. However at the moment of the configuration fo the clients tools, something is wrong. I run the comman sslconfig from the client machine and I exported the certificats and all the files from the BO server, but the command doesn't do nothing.

 

bellow the print:

 

httpssl.PNG

 

so, when i try to connect to IDT designer, i still have the same response :

 

[repo_proxy 13] SessionFacade::openSessionLogon with user info has failed(Transport error: Insufficient resources.(FWM 00002)

(hr=#0x80042a01)

 

 

i already tried in a different client machine, and is always the same issue. the command sslconfig doens't read the certificate.

 

 

thanks in advance!!!!!

BOBI integration with Google Apps

$
0
0

Hi BO Experts ,

 

Can some one share information around BO intergration with Google Apps .

What i am looking for is

1. Integration details (technical)

2. Some documents how to implement this ?

3. SAP Help links around this .

4. Anything that would be helpful for us to explore and start working with BO tools .

 

We are moving away from Microsoft Excel and would start using Google sheets instead ..

 

Any inputs !

 

Regards

Zee

Viewing all 5403 articles
Browse latest View live