Skip to Content
avatar image
Former Member

Has anyone successfully configured 64-bit BW drivers & Sapcrypto to use BW UNV and Bex sources?

We have BW 7.4 and BI 4.1 SP3 FP4 environments. We want to upgrade to BI 4.1 SP8 FP2 (or maybe FP3 or FP4 soon).

There are about 10 different KB notes explaining (each partially) how to configure 64-bit SAP BW drivers and 64-bit Sapcrypto to be able to create BI 4.1 Webi documents with BW UNV (using SSO + SNC) and BW Bex (using SSO + STS) datasources. We followed all instructions without success. We opened a high priority ticket with SAP support - without success yet.

Is it supposed to work? Has anyone managed to configure this successfully with recent SP versions of BI 4.1?

We noted that related note 2271897 is not released. Does it mean that SAP is working on an SNC/STS issue that would make it impossible for us to configure correctly?

Any help would be appreciated.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Nov 09, 2016 at 04:40 PM

    Hi Chartier ,

    STS , SNC and 64-bit drivers configurations are different .Please check below if you haven't read.

    SAP KB 1930558, How to utilize the 64-bit SAP BAPI driver with UNV universes in BI 4.x (Windows)



    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Nov 09, 2016 at 07:43 PM

    Hi Sateesh,

    Thanks for your reply.

    Yes, we saw note KB 1930558 (and many others) and the wiki article.

    But according to this note, a security change was introduced and with the SP version, you must use 64-bit drivers or SNC and STS won't work:

    2319010 - Analysis Workspaces fail after upgrading to BI 4.1 Patch 5.13 / 6.7 / 7.2 or SP08 or newer


    1. Most BI installed should be using 64-bit SNC, but we have found that some are not. If you are using 32-bit SNC on BI 4.1 SP7+ then see KBA 2098464
    2. Reinstalling SNC with the 64-bit version can be done with the BI Platform Support Tool's new SNC configuration plugin, as per KBAs 1922012 and 1500150

    Work Around

    • If you do not use legacy SNC (if the option under CMC > Authentication > SAP > SNC configuration is disabled), then this issue will not occur.
    • If you do have and need legacy SNC enabled, then until this KBA has an updated solution 4.1 SP7 patch 1 is the latest recomended Patch until further notice

    What we're not clear is: if we update to 64-bit SNC as mentioned above, is it still considered "legacy SNC" and we should use 4.1 SP7 patch 1? Or with 64-bit SNC, BW UNV and STS Bex data source should be able to work side-by-side?

    Thanks !


    Add comment
    10|10000 characters needed characters exceeded

  • Feb 28, 2017 at 04:10 PM

    Setup STS in KBA 1670073 1st with SNC disabled. and verify STS works with KBA 1767629.

    Now once that is sorted out enable SNC (don't configure just enable). Does it break STS using the same test in 1767629. By default SNC should be using 64 bit common crypto library for encryption in the security note 2271897 mentioned (security notes are released just internal only)

    So if that fails then there is an issue with the SNC library, if it works then you need to setup 64 bit SNC for webi-unv (if you are using legacy unv), or 32 bit and 64 SNC for legacy crystal (2016). All references are in KBA 2319010 mentioned above. That part can be tricky and support should be able to assist.

    Add comment
    10|10000 characters needed characters exceeded