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

Deployment of Patched Software

May 2, 2016, 12:57 pm
$
0
0

We recently upgraded our Business Objects Platform servers from 4.0 sp4 to 4.1 sp6 fp3. We also had to upgrade the Business Objects Client.

 

Together the base version (4.1 sp6) and sp6 fp3 combine to be over 2.5 gbs. Its a large update to a machine.  It takes about 40 minutes to update a machine.

 

Our deployment team found a method to deploy as one package instead of deploying the base version and then installing the patch.   They do this by only copying over the files that are different between the patch and the base install. They used beyond compare to do the comparison.

 

As a result of doing this and removing language files, the single install patch is only about 1.5 gbs and takes less than 20 minutes to remove the old program and add in the new program.  It does seem to work. We have not had any problems with the software deployed through this method yet.

 

My question is has anyone else done or tried this? I have not found anything in the SAP literature or this merging or "slipstreaming" with Business Objects Software.

↧
Search

got "Running the program failed with error code -1."

August 20, 2014, 9:07 am
$
0
0

I have one crystal report job and schedule it to run daily.

Mostly it run ok but sometime it got "Running the program failed with error code -1.".

What does that mean?

And where I can check it and fix it?

 

Thanks,

Ivan

↧
↧

Kerberos(SSO): throw RC4 away, adopt AES !

December 27, 2015, 3:47 pm
$
0
0

Hello,

 

We can find on "SAP Community" site many nice tutorials explaining how to configure "Windows AD" authentication + SSO.

 

Some of them are quite old or are recent copies from parts of old ones.

 

In Kerberos configuration "krb5.ini" file, they all give RC4 algorithm for encryption type to be used. That was true with "Windows Server 2003"...

 

/!\ But be careful, in 2015 and soon 2016, RC4 is no more considered as a secured encryption algorithm /!\

 

Assuming nobody uses" Windows Server 2003" anymore, I would strongly suggest you to modify "krb5.ini" sample files like this :

 

Replace:

 

default_tgs_enctypes = rc4-hmac

default_tkt_enctypes = rc4-hmac

 

with:

 

default_tgs_enctypes = aes128-cts-hmac-sha1-96

default_tkt_enctypes = aes128-cts-hmac-sha1-96

 

or even better (requires Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files for Java 7 or 8)

 

default_tgs_enctypes = aes256-cts-hmac-sha1-96

default_tkt_enctypes = aes256-cts-hmac-sha1-96

 

 

In fact, it's Microsoft's recommandation for "Windows Server 2008 R2" and above.

 

I've tested SAP/BO BI4.1 SP7 + AES-128 and AES-256 for Kerberos on Windows 2008 R2 and 2012 R2: it works great !

 

In fact, it would be nice if the authors of tutorials could modify them and add this security update.

 

Don't joke with security ! ;o)

 

Regards,

 

Stephane.

↧

dynamic filters based on optional prompt value

May 11, 2016, 12:47 am
$
0
0

Hi there,

I am very new to business Objects, I am using BO 4.1 SP03. My business requirement is as below but I am not sure how to set this up in.

I have Universe built in IDT sourcing data from SQL database. I have field in database called Sales Cat type with 4 types 1,2,3,4.

I have build Webi report on top of this universe with optional prompts - prompt 1, prompt 2, prompt 3, prompt 4.

When prompt 1 is Null then I want all the sales category data. But when Prompt 1 is not null then I want only 1.

I want this to be dynamic and not static, I know that in static mode I can set filter on table itself.

It is very urgent and thanks so much for your excellent expert advices in advance.

 

Thanks

Happy

↧

List of users getting reports through publication or schedule

May 19, 2016, 5:36 pm
$
0
0

Hi,

 

If there a way I can get a list of users who are recipient of the reports through a publication or a schedule? I need to get the list of these information consumers who are accessing the reports but are not actively using the system .

 

Appreciate all help!

 

Thanks

↧
↧

List of users getting reports through publication or schedule

May 19, 2016, 5:53 pm
$
0
0

Hi,

 

If there a way I can get a list of users who are recipient of the reports through a publication or a schedule? I need to get the list of these information consumers who are accessing the reports but are not actively using the system .

 

Appreciate all help!

 

Thanks

↧

"404 Missing Page" when opening Central Management Console bo 4.1

May 19, 2016, 9:43 am
$
0
0

Hi All,

 

SAP BO 4.1 SP7

Im having  404 missing page since this morning, this happen when l open CMC

BI launch  Pad is fine

 

I have tried all the solution -Run Wdeploy and repaired SAP BO 4.1

but still same error

 

 

Any solution

 

 

Thanks

PC

↧

Using WACS for RESTful With Tomcat In Use

December 9, 2014, 7:12 am
$
0
0

Hi All,

 

Sorry for the cryptic title.

I have a request from a developer to use the RESTful web service. My research has shown that this is only available through a WACS server.

 

We are currently using tomcat and do not have a WACS server enabled.

My question, would there be issues of creating a WACS server in the CMC just for the purpose of using the RESTful functionality?

 

I am looking for some assistance to see if this is possible. If anyone has any information on this, that would be great.

 

Thanks in advance.

 

Regards,

Michael Welch

↧
Search

BOBJ 4.0 Admin Login Disabled: cannot access CMC

March 28, 2014, 7:15 am
$
0
0

We have one admin account, which somehow (potential employee tampering) is now disabled.  So, we no longer have access to the CMC.  How can I get the Admin Account enabled, outside of the CMC application?  Is there a super-user password that I can use to login?

 

Thanks

↧
↧

RESTful service in BOBJ Server

May 20, 2016, 3:56 am
$
0
0

Hi Experts ,

 

 

 

 

I read, apps like Lumira, Liveoffice utilize the RESTful service?  What other apps utilize it?  Design Studio, WEBI etc?  Is dswsbobje connection

 

incorporating it or is that separate?

 

 

 

Thanks

Kiran.GVL

↧

Crystal Reports 2008 Server, CMC log in slows over time

May 16, 2016, 7:48 am
$
0
0

We have Crystal Reports Server 2008.  This is the second time I have dealt with this issue and I have no idea how to resolve this or what causes it.  Over time, logging into the CMC web console gets slower and slower.  Same thing when opening the crystal reports 2008 client tool, logging into the "enterprise" server (our server), then once I expand the enterprise tree, it take almost ten minutes for our reports to show up.  Same thing with the CMC log in, it takes that long to log into the console.  Once open clicking on various things is a little slow too.  Even worse, if I go into the Infoview page, log in, once in I try to navigate publications, it's super slow.  Once a reports is open, the report runs fine.  Any scheduled reports seem to run just fine in the background however it's almost unusably slow when we try to log into the CMC over web UI or through the crystal client by logging into enterprise or using infoview looking for reports or publications.  The server operating system is windows 2008 and the default install was chosen with MySQL.  The server OS performance is fine, all resources are showing a low utilization percentage.

 

In the past, I fixed this simply by reinstalling the whole server, manually re-uploading reports and recreating publications and schedules.  I really don't want to do this again.  There must be an explanation to this behavior and a way to resolve.

 

Any help is greatly appreciated.

↧

CORBA error while communicating with the SL Service

May 19, 2016, 11:59 pm
$
0
0

Hi Friends,

 

We we schedule the report on inbox getting error:CORBA error while communicating with the SL Service

 

It is working for smaller reports which scheduled to inbox but larger reports getting CORBA error.

 

Error:

 

 

Title: Daily Sales and Stock(999) - ABC Purchase Org

Document Type: Microsoft Excel

Status Failed

Destination: Inbox

Owner: Administrator

Creation Time: 5/20/2016 8:57 AM

Start Time: 5/20/2016 8:57 AM

End Time: 5/20/2016 9:45 AM

Server Used: TEST.JobServer1

PID: 8573

Parent Object Path: Daily Sales and Stock/

Remote Instance in Federated Cluster: No

Expiry: 5/20/2026 8:57 AM

Formats: Microsoft Excel

Parameters: 4/1/2016;5/17/2016

Error Message: CORBA error while communicating with the SL Service

 

Please advice.

 

Regards,

Karthik

↧

Connectivity to Cloudera Impala

May 20, 2016, 11:11 am
$
0
0

Hi Experts,

 

I referred Data access and IDT guides (BI 4.2 SP2). In IDT, i can't create relational connection with Simba JDBC Drivers.. (using Network Layer - Simba JDBC Drivers and Database Engine - "Cloudera Impala 1.0" , as per guide, no additional configuration is required to set this up. )

 

I tried to access the database using "CSCHECK Ping" command tool. It fails...(attached connectivity command  screenshot)

 

I searched SCN forums with no luck. Please suggest.

 

Environment Details: BI 4.2 on Windows Server 2012 R2

Database: Cloudera Impala on Linux server (AWS cluster)

 

Thanks,

Sabala

↧
↧

Adaptive processing server is running with errors after 4.2 upgrade

May 20, 2016, 9:01 am
$
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)

↧

"Conversion from UTF8 to charset failed : Encoding not loaded"

May 20, 2016, 2:59 pm
$
0
0

Hello All,

 

We are facing issue with multi source connection with Oracle when using IDT.

 

Currently we are at SAP BIBO 4.0 SP4 Patch 4 and using windows environment.

 

I googled on the issue , SAP note suggested

 

Add "C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win64_x64" to the PATH environment variables on the SAP Business Objects Enterprise machine

 

 

What exactly do we need to add to the location specified? I didnt get the point. Could someone brief me.

 

 

 

 

Best Regards

Sandy

↧
Search

Moving BOE BI4.1 to cloud, what all we need to test. Need some help?

April 19, 2016, 3:09 am
$
0
0

http://www.google.co.in/?gfe_rd=cr&ei=o-sVV-OUE6XT8ge-3a2gDg&gws_rd=ssl#q=what+to+test+when+BOE+bi4.1+is+moved+to+cloud

 

http://www.slideshare.net/albertspijkers/key-considerations-for-moving-to-sap-business-objects-bi-41

 

http://rbranger.wordpress.com/2012/04/30/testing-bo-bi-4-x-using-the-cloud/

 

http://scn.sap.com/docs/DOC-56525

 

Hi,

Company has decided to move entire BOE BI4.1 platform to cloud and I am assigned with task to create test cases for testing the BOE platform once we move to cloud. Can someone give me an idea of what all areas should be considered or kept in scope while designing test cases. Our BOE connects to both SQL as well as BW backend. Apart from this, rest all is same standard BOE implementation. Reports, universes, connections, Publications\Schedules, users\groups and also mobile BI server.

additionally, BW will be moved to HANA platform and we need to keep that also into consideration and have few test cases for BO reports with BW backend. And We are using following tools to fulfill reports\dashboard requirements.

 

Web-I

Advance Analysis for office

Xcelsius\SAP Design Studio

SAP Lumira (Desktop version, no edge server)

 

If anyone has had similar move to cloud and if can help with steps they performed, it will be of great help.

 

I searched net with below(I tried copying below but they came up at the top of the page, apologies for that) links, but seems they are not very helpful. They are about the upgrade but not about cloud move.

↧

List of users getting reports through publication or schedule

May 19, 2016, 5:36 pm
$
0
0

Hi,

 

If there a way I can get a list of users who are recipient of the reports through a publication or a schedule? I need to get the list of these information consumers who are accessing the reports but are not actively using the system .

 

Appreciate all help!

 

Thanks

↧
↧

Delete Invalid LDAP groups from BO

May 18, 2016, 6:57 am
$
0
0

Hi,

 

We are upgrading to BO4.1sp6 from 3.1sp6.

 

In Dev environment the LDAP authentication was setup a year ago. One group is mapped into BO.

Later the password for the LDAP authentication user has expired and also no LDAP user was using the server.

 

Now we are doing the upgrade in the test environment. As the LDAP is not working in 3.1, i have disabled the LDAP authentication and then used the UMT to do a full upgrade to BO4.1.

 

In 4.1 , i got the LDAP group which was mapped in 3.1. But i am not able to delete this group. The Delete option is not appearing in the Right click.

 

I have gone through all the SAP notes related to LDAP and not found a way to get this group deleted from 4.1

 

 

Any idea how to get this group deleted?

 

Regards

Marven

↧

BI launch pad issue after installion

May 20, 2016, 11:26 pm
$
0
0

Hi all,

 

Recently we installed SAP BO4.1sp5 in windows2008 server

while installing client tool.it struck at below image

 

struck.jpg

Due to some updates ,server got restarted  popup closed

 

From server

 

iam able to view reports from webi rich client  and  same from  cmc

iam facing issue from BI launch pad

 

Bi launch pad.jpg

 

Tomact and serves are up

 

. Could you plz help in this

↧

Calculating Workdays

May 20, 2016, 1:12 am
$
0
0

Hi Webi Gurus,

 

 

I have to create a new Webi Report and there i need to calculate a new Date based on Value Date (ValueDate+4 Workdays)

 

eg.

 

Value Date                           New Date

20.05.2016  + 4 Workday = 26.05.2016

 

Can you help me ?

 

Thanks

Nas

↧
Viewing all 5403 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>