Skip to Content
0

The entitlement system has to be re-enabled before it can be used again. After each restart

Jan 20, 2017 at 07:41 AM

298

avatar image

Hi.

We recently installed Support Packs & Patches on our Business Objects 4.1 environment (Development & Production). Our old environment was Business Objects 4.1 SP07. We installed SP's & Patches to go up to BO 4.1 SP08 Patch Level 3.

Since doing this, we are getting the following error message after each restart of the BO environments. What I need to do to resolve it each time, is to go into the CMC on each system, then into Authentication -> SAP and then click the "Update" button to restore the SAP Authentication. This works until the next restart of the system again.

I have checked the configs in the Tomcat -> WebApps folder, but I am almost sure that I am missing something somewhere.

Error message:

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]: [4, "RFC_COMMUNICATION_FAILURE", " LOCATION CPIC (TCP/IP) on local host with Unicode ERROR GSS-API(maj): No credentials were supplied GSS-API(min): SAPCRYPTO PSEDIR directory not found: C:\sec (<Default>) Could't acquire DEFAULT INITIATING credentials TIME Fri Jan 20 09:24:56 2017 RELEASE 720 COMPONENT SNC (Secure Network Communication) VERSION 6 RC -4 MODULE sncxxall.c LINE 1445 DETAIL SncPAcquireCred SYSTEM CALL gss_acquire_cred COUNTER 1 "]. 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.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Juandre Rautenbach Jan 20, 2017 at 07:48 AM
0

I suspect this is the cause of the issue, but I am not sure how to fix it.

SAPCRYPTO PSEDIR directory not found: C:\sec (<Default>)

Share
10 |10000 characters needed characters left characters exceeded
Tim Ziemba
Feb 28, 2017 at 03:58 PM
0

KBA 1724785 is similar and a 1st place to check is the entitlement user. There are other KBA's that mention the entitlement user type, or set with no initial password, etc. Possibly as a test try a different type entitlement user even an admin and see if that's related to the problem. It's not a common occurrance.

The sec directory is usually associated with SNC. Do you have SNC enabled and more importantly are you using an SNC string in the entitlement tab?

Regards,

Tim

Share
10 |10000 characters needed characters left characters exceeded