cancel
Showing results for 
Search instead for 
Did you mean: 

DCP absolutely does not work with BO 4.2

former_member203533
Participant
0 Kudos

Hello Team,

I'm currently working on a SAP BO upgrade. The system is being upgraded from 3.1 SP1 to 4.2 SP4.

I have tested the DCP and it is absolutely not working. At this time, the DCP is required because few reports will remain as Desktop Intelligence till full conversion / audit has been finished.

I have worked with DCP in other system upgrades, and it had been working fine up to now.

However, with BO 4.2 it is impossible to make it work.

*******************************************************************************************************

The environment which I have tested (in Windows 10 and 7😞

********** Environment 1:

SAP BO 4.2 SP4

(for DCP) BO 3.1 SP6 FP2 (the latest has been tested too)

********** Environment 2:

SAP BO 4.2 SP4

(for DCP) BO 3.1 SP7

**********Environment 3:

SAP BO 4.2 SP6

(for DCP) BO 3.1 SP7

*******************************************************************************************************

To test I have open the Desktop Intelligence, entered the credentials. As soon as I type the credentials nothing happens.

By using "ProcMon" software, I have listen all operations of "busobj.exe", And notice that when the binary "C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86\busobj.exe" is called, the system exists with an error code "-1073741511".

I have followed the instructions in the notes 2042056 and 1939383.

Would anyone have any suggestion? Any suggestion is highly appreciated.

I don't know what else to test.

Marcos Morais

Accepted Solutions (0)

Answers (5)

Answers (5)

DellSC
Active Contributor

In addition to the deprecated support that Denis mentions, I think at least part of the issue you're running into is that the security libraries for BO were upgraded with 4.2 SP4. Hence, anything like DCP and Deski that use the older security libraries is not going to be able to log in to the newer versions of the BI Platform.

-Dell

0 Kudos

Contact SAP They provided a patch ( an unofficial one ) . After applying the patch, the issue is resolved and DCP is working fine with 4.2 SP06. We have done this as well

former_member203533
Participant
0 Kudos

Could you share? 🙂

tomas_karnold
Discoverer
0 Kudos

Hi, the same scenario, the same problem.. We consider to downgrade/create new test instalaltion of 4.1 if DCP does work then.

by the way - Does the UMT tool work for you?
BOXI 3.1SP7.x -> UMT -> BOBI 4.2.x ?

Do you have to use the noauth parameter for file servers?

thx Tomas

denis_konovalov
Active Contributor
0 Kudos

BOXI 3.1SP7.x -> UMT -> BOBI 4.2.x

should work, provided source system is in working order.
kgreen
Discoverer
0 Kudos

Marcos, did you find a solution for this? DCP was working in 4.1 at my client but with the upgrade to 4.2sp6 it no longer works. I can start and login to 3.1 platform, but with 4.2 once I login DCP shuts down. Client needs DCP in 4.2 to facilitate the conversion of reports to WebI and eventual decommissioning of the 3.1 platform. Using 3.1 SP7.4 client tools.

denis_konovalov
Active Contributor
0 Kudos

You should convert your deski reports to webi as DCP or Deski is NOT supported anymore by SAP.
Which means if you don't get your answer here or in knowledge base - there is no esclation path for you.