Skip to Content
Technical Articles

SAP BusinessObjects BI 4.2 SP08 (SAP BI 4.2 SP8) Released!

Source: Webi4Me

SAP BusinessObjects 4.2 SP08 Released

February 24th, 2020

Oh well I had this all planned for a Feb 14th release and ready to wish you all a Happy Valentines’s Day ? but that wasn’t meant to be.

Nearly a year after the release of SAP BI 4.2 SP07, I’m happy to announce today the latest Service Pack aka Support Package for SAP BI 4.2 – version

Released few days late according to the Q1 2020 Maintenance Schedule:



Source: Maintenance Schedule

Previous SAP BI 4.2 Support Pack releases:

  • December 2017: SAP BI 4.2 SP05

What was released?

The usual suspects were released for a fresh Installation or Support Package:

  • SBOP BI Platform 4.2 SP08 Server
  • SBOP BI Platform 4.2 SP08 Client Tools
  • SBOP BI Platform 4.2 SP08 Live Office
  • SBOP BI Platform 4.2 SP08 Integration for SharePoint
  • SBOP BI Platform 4.2 SP08 NET SDK Runtime
  • SAP BusinessObjects Dashboards (Xcelsius) 4.2 SP08
  • SAP BusinessObjects Explorer 4.2 SP08
  • SAP Crystal Server 2016 SP08
  • SBOP BI Platform 4.2 SP08 Crystal Reports for Enterprise
  • SAP Crystal Reports 2016 SP08

What’s New?

This is hopefully not coming as a surprise as it has been mentioned several times over the last few months but this Service Pack is not including new features.  We are now in SAP BI 4.3 territory!

This update is about keeping the BI 4.2 lights on a bit longer by fixing bugs and adding few extra things to the PAM.

  • More from SAP:

What’s New

  • LinkedIn Community:


Download Location

These packages are available from Software Downloads

Also see SAP Note 2896442

In my case, that’s a good old 12.5 GB download!


Installing / Upgrading – How did it go?

My test environment is running on an AWS EC2 t2.xlarge.  That’s 4 Cores and 16GB RAM.

I have the following installed in SAP BI 4.2 SP07 with 3x Languages: English, French and Finnish.

  • Installation: Well it took probably more time as always to unzip everything but all in all (without testing) it took about half day to patch everything.  It well smoothly except for this .NET error but everything I have tested so far works.

  • Results:


The usual documents have been made available on the SAP Help Portal:

  • SAP BusinessObjects BI Platform 4.2 SP08 Installation Guide



  • More Documents

BI Platform (SAP Help Portal)

SAP Analytics (SAP Help Portal)

Product Availability Matrix (PAM)

(Supported Platform)

Release to Customer (RTC): 13.11.2015

General Availability (GA): 08.03.2016

End of Mainstream Maintenance: 31.12.2022

End of Priority One Support Phase: 31.12.2024

  • URLs:

SAP BusinessObjects BI 4.2 Supported Platforms (PAM)

Product Availability Matrix | SAP Support Portal

  • Important:

Expiry of SAP BI 4.1 (Priority One Maintenance) on 31/12/2020 (PAM)

Expiry of SAP BI 4.2 SP06 in February 2020: BI 4.2 Support Pack End of Life Dates

Additions to the Relational Data Sources:

Amazon EMR 5.20 Hive (Hive2) 2.3.4
Amazon EMR 5.20 Hive (Hive2) 2.3.4
HP Vertica 9.2
HP Vertica 9.2
Microsoft Excel * 2019
Microsoft Access * 2019
Microsoft SQL Server 2017
Oracle Oracle Database 19c
Oracle Oracle Database 19c
Oracle Oracle Database 19c
Oracle Oracle Exadata Database Machine * 19c
Oracle Oracle Exadata Database Machine * 19c
Pivotal Greenplum* 6.0
Pivotal Greenplum* 6.0
PostgreSQL PostgreSQL 11
PostgreSQL PostgreSQL 11
SAP NW BW * 7.5 SP15
SAP NW BW * 7.5 SP15
Snowflake Snowflake N/A
Snowflake Snowflake N/A

Maintenance Schedule – What’s Next?

  • SAP BI 4.2 SP07:

11.03.2020: SAP BI 4.2 SP07 Patch 9 (

24.04.2020: SAP BI 4.2 SP07 Patch 10 (

06.06.2020: SAP BI 4.2 SP07 Patch 11 (

07.08.2020: SAP BI 4.2 SP07 Patch 12 (

26.09.2020: SAP BI 4.2 SP07 Patch 13 ( (last one)

  • SAP BI 4.2 SP08:

10.04.2020: SAP BI 4.2 SP08 Patch 1 (

08.05.2020: SAP BI 4.2 SP08 Patch 2 (

26.06.2020: SAP BI 4.2 SP08 Patch 3 (

07.08.2020: SAP BI 4.2 SP08 Patch 4 (

23.09.2020: SAP BI 4.2 SP08 Patch 5 (

28.10.2020: SAP BI 4.2 SP08 Patch 6 (

04.12.2020: SAP BI 4.2 SP08 Patch 7 (

27.01.2021: SAP BI 4.2 SP08 Patch 8 (

12.03.2021: SAP BI 4.2 SP08 Patch 9 (

Week 18 (May): SAP BI 4.2 SP08 Patch 10

Week 26 (July): SAP BI 4.2 SP08 Patch 11

Week 35 (Sept): SAP BI 4.2 SP08 Patch 12

  • SAP BI 4.2 SP09 (01.03.2021:

Source: Maintenance Schedule

What’s Next… Next!?

Since it was announced at #SAPPHIRENOW 2018 and in my blog back in June 2018, a lot has happened with SAP BI 4.3.

“Early” BETA has come and gone back in late 2019.

“Standard” BETA is still ongoing and scheduled to close at the end of February 2020.

This is what we know about the roadmap so far:

SAP BusinessObjects BI 4.3:

Q4 2019: SAP BI 4.3 (RTC) – “Early” and “Standard” BETA

Q2 2020: SAP BI 4.3 (GA)

Q4 2020: SAP BI 4.3 SP01

Source: Webi4Me

Source: SAP


As planned, not a significant release.  Just bug fixes and minor updates to the PAM.

Except… It took me couple of weeks to notice that Snowflake is now supported!  I thought we’d have to wait for SAP BI 4.3.  Great #geeky news!

I have written a blog on how to make it work:

Looking forward to SAP BI 4.3 General Availability (GA) hopefully in Q2 2020!

Keep in Touch!

Hope this blog was useful.   Please do share your thoughts and comments.

Feel free to “like” and post it on social media!

Always happy to connect:

Take care… A+


You must be Logged on to comment or reply to a post.
  • Hi,

    we installed 4.2 SP 08 and we find out the  following issue:

    If you are using variables in the datafoundationlayer(.dfx)  coming from HANA as input parameters, and prompt to User is not activated, these prompts will not be mentioned in the script which is been used for generating the report in Webi. So the output of the report is not correct then.

    So if you want that all the variables will be taken in your report you have to activate prompt to user.

    In 4.2 SP 6 this was not a problem.

      • Patrick,

        I would like to know if BOE XI 4.2 SP8 can use SQL Server 2019 as a Reporting Data Source. The PAM guide page 24 on Data Access doesn't include anything on SQL Server 2019. The last updated on those excel files were Feb 2020. Please confirm if BOE XI 4.2 SP8 can connect to SQL Server 2019 for Universe Connection, Crystal Reports, Web Reports etc.




        Julliet L

        • Hello Julliet,

          I can confirm that it works.  I have been using MS SQL Server 2019 since SAP BI 4.2 SP07 actually.  No problems.

          But there is a difference between working and supported of course.

          What is interesting is that if you look at slide 19 of the PAM.  It does state that you can use MS SQL 2019 for the CMS DB and Audit DB.

          But indeed slide 24, no attachments refer to MS SQL Server 2019.

          I wonder if this is an error because BI 42-SL PAM - v1_1.21_SP8.xlsx states that MS SQL Server 2017 was added in BI 4.2 SP06 (correct) but again (ok a different driver) in BI 4.2 SP08.  Maybe it's meant to say 2019...

          Only SAP can confirm (or not) what the exact support is.  And then they will amend the PAM.

          If there is no mistake, it looks like you'll have to wait for either SAP BI 4.2 SP09 (as of now no scheduled date) or SAP BI 4.3 I guess.

          • So if we use IDT what is the driver type we should be using for Universe Connection Creation (JDBC 8.2) and what was the configuration that you used in the sqlsrv.sbo file to indicate that's its SQL 2019. Example



            <DataBase Active="Yes" Name="MS SQL Server 2017">
            <!--   Uncomment and edit the following lines
            to define java classes required by JDBC driver
            &amp;lt;Path&amp;gt;your jar or class files directory&amp;lt;/Path&amp;gt;
            <Parameter Name="JDBC Class"></Parameter>
            <Parameter Name="URL Format">jdbc:sqlserver://$DATASOURCE$;DatabaseName=$DATABASE$</Parameter>
            <Parameter Name="Extensions">sqlsrv2017,sqlsrv,jdbc</Parameter>
            <Parameter Name="Force Execute">Always</Parameter>
            <Parameter Name="Driver Capabilities">Query,Procedures,Cancel</Parameter>



            Or should we be using OLEDB Support

          • Hi,

            I used standard ODBC (32 and 64 bits).

            Then in IDT I selected MS SQL Server 2017 (although I use MS SQL Server 2019).

            Again: Not supported.  But it works.

  • Thanks for the information.  I'm considering an 'upgrade' from 4.1 SP3 to 4.2 by building a 4.2 installation and migrating objects from 4.1 into 4.2 using the 4.2 promotion management tool.  What SP level of 4.2 would you recommend please?

  • Hi Patrick, we havent been able to utilize Parallel queries with Snowflake connector. This works as expected when we use Generic ODBC connector to connect to Snowflake. Is there a setting specific for Snowflake connector that we need to update please.

    Note that we have tested with same report, Universe and server. Only changed connection to use ODBC vs Snowflake Connector.


    • Hello Nilim,

      I saw your email from Scott 🙂 I replied already, he will send it over.  But for the benefit of others:

      First I mentioned your concerns about parallel queries to Gregory BOTTICCHIO (Director, Analytics Product Management at SAP) and he confirmed that drivers and the processes running queries should be unrelated.  Ie Snowflake or other technologies shouldn't make a difference.

      I have personally tested today running a Webi with 5 Queries.  Each reading 100k rows.  See below:

      All 5 Queries started at the same time.  FYI The last one was quick as it was already cashed of course.

      Hope that helps.  If you have further concerns you should raise a support ticket with SAP.

      Take care.

  • Hi.  I'm installing 4.2 SP08 into a 4 host environment (two app hosts which will be a single cluster and two BO web app).  I've installed BIP servers on one host and wonder if I can  install the web tier on a web app host or if I need to install the BIP servers onto the second app host first?

    Also (sorry...) the web tier installation documentation states to select a CMS name but I took screenshots of the BIP server installation and the only name I was prompted to enter was the SIA name... Is the 'CMS name' simply the name of the host of BIP servers?

    Thanks for reading this far at least 🙂



    • Hi Steve,

      If I get this right, you want a cluster of Web Servers (2) and a cluster of App Servers (2).

      The first server you need to build is an App Server.  Then the order doesn't matter.

      You can build the second App Server by doing an expand install.

      For the Web Servers, it will indeed ask you to enter the name of the CMS.  That's the hostname of the server where the CMS reside.  Note your SIA name and Hostname may be different.

      Make sure you read the docs.  There are lots of small things to do when you cluster!

      I did a webinar not long ago that may help:  38 SAP BusinessObjects Tips And Tricks Every Administrator Should Know

      Good luck!


      • Hi Patrick!

        First, thanks for your time responding.  I really appreciate it.  Yes, you're absolutely spot-on with the requirements.  I think I'll go ahead and install the second app server using the same cluster key as the first.  I've found documentation which then states the cluster name can be updated on both servers by modifying the SIA 'cluster name' property.  Presumably I can then use this name in the web tier installations.  If you think otherwise and have a spare moment I'd really appreciate  your comment.

        Thanks again

        Warm regards,


        • Hi Steve,

          You’re welcome.

          When you install the second node using “expand” it will ask for your cluster key.  It’s the only way.

          Feel free to rename the cluster name.  I recommend it!

          But during the install of the webservers, it’s the hostname (server name) of the CMS you have to enter.  Anyway, it won’t allow you to continue of you put the wrong details.  No stress.

          I no longer do consulting (I work at 360Suite – we do software solutions for BOBJ – check us out!) but I can recommend good guys if you need help.  PM me if applicable.

          • Hi Patrick,

            Thanks very much again.  I'm just about to take a look at at the webinar you posted on youtube.  Thanks for sharing your knowledge and experience.

            Warm regards,



      • Hey Patrick,  Thanks for this info, it has been helpful to read since I am working on setting up a 4.2.8 cluster.  Never setup a cluster for BOE before.  You referenced in the post above to "Make sure you read the docs.  There are lots of small things to do when you cluster!"  Would you be able to point me in the right direction for the docs you are referencing?  I found some info in the Admin guide but it seems to lack clarity.  I also found info in the pattern books on the wiki but that info was published for 4.0 and seems like it may not all apply anymore.  Could you help point me in the direction of the docs?  Or is what I referenced it?

  • Hi Patrick,

    The install went well, thanks for your advice!

    Another question if you've time please.

    I'm looking to install the client tools on one of the app servers (there are two of these which form a cluster).  The install guide says 'Ensure ...All BI platform servers on the machine are stopped except the CMS and File Repository Servers (FRS)'.

    Do you know if i should do this activity on both app servers or just the one i'm installing the client tools into?

    Many thanks,


    • I had to go and read the doc as I wasn't aware of this to be honest!

      Personally, I have never stopped anything when installing/patching the Client Tools.  I'm no longer a consultant so knowing this I guess won't change my way of doing things 🙂

      (Curious to hear what others do - do they stop services as documented or just install on top and "whatever")

      But if you want to follow this "requirement", then no, it's only related to the server where you are installing it at tha moment.

      I guess there must be common librairies which servers (services) other than the CMS/FRS are sharing between BOBJ Platform and BOBJ Client.

      Thanks for the tip anyway!

  • Hi Patrick,

    We are in process of upgrading BOBJ 4.2 SP6 to 4.2 SP08 P3, the upgrade went fine and applications are working fine.

    But concern is, with BIP Client tools installation in one of my wiped off my ODBC configuration. I'm trying to setup the ODBC back again.

    Is there a way to avoid deletion of ODBC setup ?

    Thank you,


    • Hi,

      This is the first time I hear/read something like this.  And I'm very surprised.

      There is no reason why SAP would go and delete ODBCs.  Especially not yours.

      Honestly, I suspect something else happened.

      Were they User ODBC instead of System ODBC?  If so, are you logging on with a new profile and/or with a different user?

      I must have installed the BI Client Tools 1000s in my life, never had this issue.

      To answer your question, there is nothing to do to avoid this.  It should not happen.

      Just in case, next laptop you patch maybe you want to backup the ODBC (easy to do it's in the registry - Google will help)

      Take care,


      • Thank you Patrick for your response!

        Nope, the ODBC (32 and 64 bit) Data sources are under System DSN not under User DSN and am logging into my own profile.

        Also, after updating SAP BOBJ BIP Client tools (from 4.2 SP6 to 4.2 SP08 P3), the projects under Local Projects section got disappeared from IDT, not sure I need to update any .ini files or something like that. Any idea how to get back them ?




  • Hi
    We have integrated BO 4.2 SP3 in to our application(.Net C#) which had been working fine. The implementation is based on API integration. 
    Recently we upgraded BO 4.2  from SP3 to SP8. With that upgrade, we are able to create the report with out issues using Web Intelligence LAUNCH PAD,
    however we are not able to create/save the report through our application. Basically we make couple of calls from our application to BO, one of the call is
    "processSave.jsp" which is the one to save the report, where the response status is "200 OK" but the response message is different, 
    it is returning something like "opendocument\open.faces". This is not the response message that we used to have with SP3. 
    So after this call, we are trying to get the CUID of the newly created report which is returning as NULL, 
    but the same was returning the CUID with SP3.  So we dont know what is changed between SP3 and SP8 from this API integration perspective. 
    Note: It is not a Rest API integration, especially for saving the report, it is .JSP endpoint(processSave.jsp) call that we make from our application
    One more thing launch pad is working fine, with launchpad http traffice, we see a CSRF token being sent in the body while making call to "processSave.jsp" http call, this is something we are seeing in SP8
  • Hi All, I have recently upgraded my BOBJ Landscape from 4.2 SP7 Patch 1 to 4.2 SP8 Patch 3 as part of the SAP Note # 2927956. After 2 days of upgrade, I see strange behavior in all the DEV/QA/PRD environments that CMS server crashes automatically and it stucks in "starting/initializing" state. the only workaround is bounce the SIA from CCM... I never seen this behavior when I was on 4.2 SP7 Patch 1 ( for almost more than 1 1/2 yr on the same hardware).

    Anyone has faced the same issue with 4.2 SP8 ? If so, help me with solution and thanks in advance.


  • Hi SAP,  et al,

    We have applied the private patch shared by SAP but still there are issues. So we are considering to go for PL500, have anyone update to this and share the experience.

  • Hello Patrick,

    We've just patch our BO from 4.2 SP4 to 4.2 SP8. Upon completion of patch, we tried to login on CMC/BI using SAP authentication. We encountered the error below:


    Account information not recognized: CSecSAPR3Binding::XRFCCnxBroker::BorrowConnection() failed. See following log entries for details. Failed while trying to log on to SAP system. The following RFC error was returned: [Group, Key, Message]: [2, "CALL_FUNCTION_SIGNON_INCOMPL", "Logon data incomplete."]. The entitlement system has been disabled in memory. This may be because the SAP system is unavailable or because the credentials are invalid. The entitlement system has to be re-enabled before it can be used again.


    Username and password are valid and productive on BW system. We tried to create new entitlement of other BW system but we also encounter the same issue.




    • We are also seeing dump on st22 of SAP BW

      Category Installation error


      What happened?
      Installation error

      The current program had to be terminated because of an error when
      installing the SAP system.
      ABAP program "SAPMSSY1" had to be terminated because the logon process could
      not be completed.
      could not be completed.


      What can I do?
      Note which actions and entries caused the error to occur.

      Consult your SAP administrator.

      Using transaction ST22 for ABAP dump analysis, you can view, manage,
      and retain termination messages for longer periods.


      Error analysis
      The logon data for user "rfcuser " is incomplete.




  • Hello experts,


    We have upgraded from 4.2 SP4 to 4.2 SP8, everything went fine.


    I deleted the client tools on my laptop and try to install 4.2 SP8 clients tools, i downloaded the Software from the download center and when i install i got language validation errors-set up language subtitle is blank

    Any suggestions




    • Hi Christian Kaiser

      I didn't write a blog about a BOBJ Service Service Pack for the first time in years because there wasn't to say really.

      SAP BI 4.2 SP09, the last one for BI 4.2, was never going to be very exciting other than bug fixes.

      The docs are here now:

      The What's New only says: This release was focused on bug fixes and performance improvements.

      Worth reading the release notes as always though.

  • Hi Patrick and the rest of the experts/colleagues,

    Thank you very much for your guidance and your time to help us.
    Let me share with you an issue that is causing us a lot of headaches. We are trying to do a new installation of 4.2 SP 08 but we find out the following issue:
    Although we set as installation path an empty unit, with 399 GB of free space, we cannot complete the installation due to the lack of disk space.
    Only the BOBJ Platform installation is taking 90 GB of Disk Space (53.1 GB for InstallData and 35.2 GB for SAP BusinessObjects Enterprise XI 4.0), but when the installation Wizard starts deploying the web applications the situation goes worst and the disk space is totally used without be able to complete the installation (tomcat\webapps folder is taking 237 GB and SAP BusinessObjects Enterprise XI 4.0 is taking 95.3 GB).

    Could anyone assist me in case you have had a similar issue during the installation process? I would really, really appreciate it.

    We are trying to install BO in a virtual machine (Windows Server 2019) and connecting through ODBC to a SQL Server 2019 (CMS and Audit).

    Thanks in advance.


    • Hi all,

      The mystery is solved. It was a problem with how the disk had been formatted. The allocation unit size was set to 2 Mb instead of using the default value, 4 Kb.
      Now it is working as expected, and the installation taking the usual disk space.


      Kind Regards.